ATT DEFINITY Communications System Generic 3 Instructions Manual

							Property Management System (PMS) Interfac e
Issue  3   March 1996
3-977
— Active with PMS message exchange (act-pms)
nControlled Restriction—one of two choices must be administered:
— Active with no PMS message exchange (act-nopms)
— Active with PMS message exchange (act-pms)
nHousekeeping Status Information—one of two choices must be 
administered:
— Active with no PMS message exchange (act-nopms)
— Active with PMS message exchange (act-pms)
If active is selected, the following additional administration is required:
— The number of additional information (Housekeeper Identification) 
d i gits from zero to six that can be dialed.
nExtension Numbers—assigned to the PMS Journal/Schedule printer and 
PMS log printer, if used, and to the PMS. Before an extension is assigned, 
the System  Manager  should  chec k  to  make sure that the extension is not 
already assigned as a Call Detail Recording (CDR) or PSC extension.
nSeconds Before PMS Link Idle Time-Out—s pecifies the number of 
seconds that the system will wait b efore it concludes that the PMS is not 
sending data across the transmission link. Choice is a numb er of seconds 
from 5 to 20.
nMilliseconds Before PMS Link Acknowledgment Time-Out—sp ecifies 
the maximum time the system expects acknowledgment from the PMS that 
a message was received correctly. Choice is a number of milliseconds 
from 100 to 500.
nPMS Link Maximum Retransmissions—sp ecifies the maximum number 
of times that the system will retransmit a message in response to a 
negative a cknowledgment or send an inquiry for an acknowledgment from 
the PMS for a message  before giving up on  the message transmission. 
Choice is a number from 1 to 5.
nPMS Link Maximum Retransmission Requests—specifies the 
maximum number of times that the system will accept requests from the 
PMS to resend a reply (acknowledgment or negative acknowledgment) 
that the system did not receive b efore g iving up on the incoming 
message. Choice is a number from 1 to 5.
nPMS Protocol—s pecifies the communication protocol mode used 
between the switch and the PMS.  The choices are either normal or 
transparent. 
						

							Feature Descriptions
3-978Issue  3   March 1996 
nDefault Coverage Path for Client Rooms—s pecifies the coverage path 
value that is set for an extension when the switch receives a ‘‘check-out’’ 
message while in the ‘‘transparent’’ communication protocol mode, or 
when a save translation is stored for extensions with a Client Room COS. 
The choice is a number from 1 to 600.
nNumber of Digits in PMS Coverage Path—located on the second page 
of the “system-p arameter hospitality” form. The coverage path can be set 
to “3” or “4”. This is used to d etermine if the PMS adjunct software is using 
a 3- or 4-digit format for coverage path messaging.
Hardware and Software Requirements
A PMS, if used, can be connected through an MPDM and port on a Digital Line 
circuit pack or through an ADU and a port on a Data Line circuit pack. A DTDM 
(with a null mo dem), 7400A data mo dule, and 7400B data module can also b e 
used for the PMS link. Journal/Schedule and PMS log printers can be used and 
also require at least an MPDM and a p ort on a Digital Line circuit pack or an ADU 
and a port on a Data Line circuit pack. The Journal/Schedule and PMS log printer 
functionality can be on the same or two distinct printers.
For G3r, there is no means for connecting directly to the switch processor circ uit 
pack, like with G3i. G3r requires, in a ddition to the data module to connect 
directly to the adjunct, a TN726B and a TN553 circuit pack combination. 
						

							Pull Transfer
Issue  3   March 1996
3-979
Pull Transfer
Feature Availability
This feature is available with G3i-Global and all Generic V2 and later releases.
Description
NOTE:
G3i-Global, G3V2, and later systems come with this feature turned off by 
default. 
Pull transfer is an enhancement of the standard transfer operation. Standard 
transfer allows voice terminal users to transfer trunk or internal calls to other voice 
terminals within the system without attendant assistance. The Pull Transfer 
feature allows either the calling or the called party (the party to whom the held 
party will be transferred) to comp lete the transfer operation.
Analog telephone called parties who wish to p ull transfer the party that the 
controlling party has on hold should momentarily flash the switchhook (or press 
the Flash key or the Recall b utton). This comp letes the transfer of the held party 
to the called party.
Digital telephone called parties who wish to p ull transfer the p arty that the 
controlling party has on hold should press the Transfer key. This com pletes the 
transfer of the held party to the called party.
Please see the Transfer feature for a d escription of the regular (push) transfer 
feature.
Considerations
The pull transfer feature provides a convenient way to  connect a party with 
someone better qualified to handle the call.  Attendant assistance is not required 
and the call does not have to be redialed.
If the attendant is the controlling party, any attempt to com plete a Pull Transfer 
operation by the called party is ignored.  Pull Transfer cannot be c ompleted if the 
Attendant is the called party. A held party can only be transferred by the 
attendant with Push Transfer.
Pull Transfer can only be completed if the calling party is a station on the same 
switch as the called party, or if the called party on another switch has been 
reached via an Italian TGU/TGE tie trunks. 
						

							Feature Descriptions
3-980Issue  3   March 1996 
Interactions
nAnalog Station Recall  Operation  and Feature Ac tivation: If the controlling 
party (with a party on hold) is talking with the called party, and either 
analog station recall or feature activation is initiated by the called party, 
the controlling party will not be put into the Hold for Transfer mo de but will 
be Pull Transferred.
nDigital Station Transfer Operation: if the controlling party (with a party on 
hold) is talking with the called party and the transfer operation is initiated 
by the called party, the controlling party will not be p ut into the Hold for 
Transfer mode but will be Pull Transferred.
nCDR: Checks will be made to ensure that calls are correctly recorded with 
CDR when a Pull Transfer o peration is com pleted.
nNon-BRI Stations:
If the “Pull Transfer” field on page 6 of the System Parameters Features 
form is set to “y,” the following could occur: Station A calls Station B, who 
answers, then presses the Transfer b utton and dials Station C. Station C 
answers and presses the Transfer button. The call from Station A is 
transferred to Station C. 
nBRI Stations:
If the “Pull Transfer” field on page 6 of the System Parameters Features 
form is set to “y,” the following could occur: Station A calls Station B, who 
answers, then presses the Transfer b utton and dials Station C. Station C 
answers and presses the Transfer button to “ pull” the transfer. Instead, 
Station C goes off hook on another call appearance as if a new transfer is 
being originated. 
Administration
The ‘‘System Feature’’ form is used to enable Pull Transfer.
Hardware and Software Requirements
No sp ecial hardware is required to implement the Pull Transfer feature in a 
standalone configuration.  However, in a network environment, the TN497 
TGU/TGE tie trunks are the only trunks that support the flash signalling necessary 
to comp lete the Pull Transfer operation between switches. 
						

							QSIG Global Networking
Issue  3   March 1996
3-981
QSIG Global Networking
Feature Availability
This feature is available with Generic 3 Version 2 and later releases.
Description
QSIG Global Networking  provides compliance to the International Organization 
for Standardization (ISO) ISDN-PRI private networking specifications.
QSIG Global Networking Basic Call
QSIG Global Networking Basic Call is available with G3V2 and later releases. 
The Basic Call complies with ISO standard 11572 for layer 3 to support private 
network connectivity. This  means  it  provides the ISDN-PRI connection from 
PB X-t o - PB X.
QSIG Global Networking Platform
The QSIG Global Networking Platform, available in G3V3 and later releases, 
provides a private network protocol for the support of QSIG supplementary 
services. This p latform meets requirements for the ISO Private Network Generic 
Functional Procedures (Standard 11582) for Call-Related supplementary 
services. (Supplementary services are services provided by the PBX beyond 
voice or data connectivity and number transport and d isplay. Examples of 
supplementary services include Name Identification, Call Forwarding, and 
Transfer.)
The QSIG Global Networking platform is based on Integrated Services Digital 
Network-Primary Rate Interface (ISDN-PRI) basic call setup protocol. It supports 
Call Relate d supplementary service transport, Abstract Syntax Notation 1 
(ASN.1)/Basic Encoding Rules  (BER),  and Remote  Operation Service Element 
(ROSE) services/protocols.
QSIG is the generic name for a family of signaling protocols b ased on ITU-T 
(formerly CCITT) Q.931 a c cess protocols across the Q reference point. (The Q 
reference point or interface is the logical point where signaling is passed 
between two peer entities in a private network.) The QSIG signaling is used to 
provide PBX-to-PBX private networking in a multivendor environment. QSIG is 
being defined by the International Standard s Organization (ISO) to be the 
worldwide standard for PBX-to-PBX private networks. These standards are also 
supported b y the ISDN Private Networking Specification (IPNS) Forum, which is a 
consortium of PBX vendors working to esta blish worldwide standards for vendors 
to follow on a voluntary basis. 
						

							Feature Descriptions
3-982Issue  3   March 1996 
The G3V3 release of QSIG Global Networking is a foundation for the QSIG 
supplementary services. It provides the Name Identification supplementary 
service, as defined by ISO Standards 13864, 13868, and 11572. G3V4 a d ds to 
the QSIG supplementary services b y providing for Call Forwarding as defined b y 
ISO Standards 13872 and 13873 and Call Transfer as defined by ISO Standards 
13865 and 13869.
DEFI NI TY s yst em  G3V3 a n d later releases provide QSIG Global Networking in 
a d dition to some national protocols and the European Telecommunications 
Standards Institute (ETS I) protocols for supplementary services.  The p rotocols 
are mutually exclusive. Users must specify on the “ ISDN-PRI Trunk Group”  form 
which protocol they wish to use for ISDN-PRI supplementary services. Therefore, 
users who require the QSIG Global Networking Platform must a dminister it on the 
“ ISDN-PRI Trunk Group ”  form. On this form, the national supplementary service 
protocols are defined as protocol ‘‘a’’, the QSIG Global Networking protocol is 
identified as protocol ‘‘b’’, and the ETSI Sup plementary Service protocol is 
identified as protocol “c”.
Supplementary Services
Identification Services
The I dentification Services feature allows the PBX to send or receive the calling 
number, calling name, connected number, and connected name. Furthermore, it 
allows you to a dminister ‘‘yes,’’ ‘‘no,’’ or ‘‘restricted’’ for sending identification 
information. ‘‘Restricted’’ means that DEFINITY system sends the information but 
sends it ‘‘presentation restricted’’, which indicates to the receiving switch that the 
information should not be displayed. In the current release, a received restricted 
name or number is included on the Call Detail Record (CDR). Due to current 
networking limitations, a received Restricted Calling Party Number is d isplayed. 
However, a received restricted Connected Party Number or Calling/Connected 
Name is
 not d isplayed.
The I dentification Services feature displays up to 15 characters for the 
calling/connected name and up to 15 digits for the calling/connected number 
across ISDN-PRI interfaces. When the DEFINITY system acts as a transit PBX (a 
PBX, other than the originating or terminating PBX, through which a call passes), 
it usually passes the name information as it receives the information.  (A Transit 
PBX is defined as a PBX that routes an incoming call administered for 
Supplementary Services protocol “b” to a trunk also administered for 
Supplementary Services protocol ‘‘b.’’) However, in the case of tandemed calls, 
trunk g roup a dministration may override incoming tags, as long as d oing so does 
not lower the restriction on the information. For examp le, a tandemed call that 
comes in as restricted remains restricted even if the outgoing trunk is 
administered for ‘‘presentation restricted.’’ However, nonrestricted data is sent 
restricted if the trunk group administration is set for ‘‘presentation restricted.’’
The ability to send  Calling Name, Connected Name, Connected Number, and 
Calling Number, or to send them restricted, is administered on the ‘ISDN-PRI  
						

							QSIG Global Networking
Issue  3   March 1996
3-983
Trunk Group’ form.  Also, the ‘ISDN Public-Unknown-Numbering’ and/or ‘ISDN 
Private-Numbering’ forms must be administered. The numbering form used to 
create the number is based on the ‘Numbering Format:’ field on the ‘isdn-pri 
Trunk Group’ form. If 
public or unknown is specified, the ‘ISDN 
Public-Unknown-Numbering’ form is used. If 
private is sp ecified, the ‘ISDN 
Private-Numbering’ form is used.
Call Forwarding (Diversion)
QSIG Call Forwarding is based on the DEFINITY system Call Forwarding All Calls 
and Call Forward Off Premise features. It extends the feature transparency 
aspects of Call Forwarding if there is a QSIG link between any of the PBXs 
involved.
The feature is activated either by dialing a feature access code or by pressing a 
Call Forwarding button. See the Call Forwarding All Calls feature for a detailed 
description of how to use the Call Forwarding feature.
QSIG Call Forwarding differs from other Call Forwarding features in that 
a d ditional call information is available to both the caller and the diverted-to 
terminal above what is provided if the call is forwarded over a link that is not 
administered for QSIG Supplementary Service protocol “b.” The originator 
(caller) of the call will see “forward” on their display. The diverted-to user will 
receive information that the call has been forwarded with the redirection symbol 
“f.” Depending upon QSIG Identification Services administration, the originator 
will see the connected party’s name or number followed by “forward.” The 
diverted-to user will see the originator’s identification (name or numb er) and the 
diverting user’s (called party) identification (name or numb er) followed by “f.”
Up to 16 digits c an be stored as the forwarded-to number. A total of 20 digits can 
be sent at the time of forwarding (including the TAC or AAR/ARS access codes).
When a call has already been forwarded three times, it will not be forwarded 
again but instead will terminate at the final forwarded-to terminal. Remote 
activation and deactivation are not su pp orte d.
Because QSIG Call Forwarding is comp atible with the ISO QSIG standards, the 
DEFI NI TY s yst em  ca n  provide feature transparency for Call Forwarding with any 
PBX designed to these standards.
Transfer
QSIG Transfer is based on the current DEFI NIT Y syst em  Transfer and 
Trunk-to-Trunk Transfer features. QSIG Transfer signalling will occur as long as 
one of the calls involves a QSIG link b etween the two PBXs. QSIG Transfer 
c onforms to ISO 13869 for QSIG Call Transfer By Join. This means that the 
transfer occurs through the switch where the transferring user resides and if the 
transfer involves two trunks, neither will be released after the transferring party is 
dropped from the call. 
						

							Feature Descriptions
3-984Issue  3   March 1996 
The user activating the Transfer feature will see no difference between QSIG 
Transfer and the standard DEFINITY system Transfer or Trunk-to-Trunk Transfer 
features. See the Transfer feature and Trunk-to-Trunk Transfer feature 
descriptions for basic feature operation.
QSIG Transfer d iffers from the standard DEFINITY system Transfer feature in that 
a d ditional call information is available for the connected  parties after the transfer 
completes. However, the information is only sent on QSIG links, that is, if one c all 
is local to the transferring PBX, that user will not receive any new call information.
Depending upon QSIG Identification Services administration, the connected 
parties’ disp lays will show each other’s name and/or numb er. If the name and 
number are not available, the display of a connected party is updated with the 
name of the trunk group involved.
Interactions
Identification Services Interactions
nDistributed Communications Systems (DCS)
There is no interworking for Calling/Connected Numb ers information or for 
Connected Name information in a DCS network. The Calling Name from a 
DCS network is received by the QSIG Global Network platform. However, 
the Calling Name is not sent by the QSIG Global Network platform to a 
DCS network.
nNon-DCS Non-QSIG Global Networking ISDN-PRI Networks
Calling/Connected Name and Number information may be sent to and 
from a non- DCS non-QSIG Global Network platform, d e pending on the 
protocol version (country protocol) for the interface.
Call Forwarding (Diversion) Interactions
All interactions that ap p ly to the standard DEFINITY Call Forwarding -- All Calls 
feature also a p ply to Call Forward ing with QSIG. See Call Forward ing All Calls 
on p age 3-396 for a description of these interactions. The following are a dditional 
interactions.
nDistributed Communications Systems (DCS)
nCall Forwarding feature transparency will not exist on calls tandemed 
between a QSIG (Sup plementary Service p rotocol B) network and a 
traditional DCS network. However, the  basic call will continue.
nForwarding and Coverage
If the last c overage p oint in the coverage p ath is a number that routes over 
an ISDN PRI SSB trunk, the call will b e treated as a QSIG Diverting call. 
						

							QSIG Global Networking
Issue  3   March 1996
3-985
nQSIG Identification Services
Availability of name and/or num ber display at the originating and 
diverted-to users depends upon how QSIG Identification Services have 
been administered for the PBXs involved.
nTerminating Call has Coverage Active
If a call is forwarded off switch, the terminating switch has call coverage 
activated, and the criteria are met, the call does not route to the 
forward ing party’s coverage path, it routes to the terminating station’s 
coverage path.
Transfer Interactions
nDistributed Communications Systems (DCS)
The only DCS transparency that will exist when a call is transferred in a 
DCS network and passed over a QSIG administered trunk is calling name.
nQSIG Identification Services
Availability of name and/or num ber display at the connected parties 
depends upon how QSIG Identification Services have been administered 
for the PBXs involved.
Administration
QSIG Global Networking and the Supplementary Services it provides require 
ISDN-PRI. Therefore, ISDN-PRI must be enabled on the “System-Parameter 
Customer-Options” form.
On the ‘ISDN-PRI Trunk Group ’ form, the “ Supplementary Services Protocol” field 
must be administered to ‘‘b’’ to enable the QSIG sup plementary services 
protocols.
See 
DEFINITY Communications System Generic 3 Version 4 Imp lementation, 
555-230-655, or 
DEFI NI TY Com munications System Generic 3 V2/V3 
Implementation
, 555-230-653, for information about a dministering QSIG Name 
and Number Identification, Call Forwarding and Transfer.
Hardware and Software Requirements
QSIG Global Networking does not require any hardware or software b eyond what 
is required for normal ISDN-PRI connectivity. The TN767 circuit board is  used for 
24 channel applications and the TN464 with suffixes C and greater are used for 
both 24 channel and 32 channel applications.
Users must have display-equipped voices terminals for displaying the call 
identification information. 
						

							Feature Descriptions
3-986Issue  3   March 1996 
Queue Status Indications
Feature Availability
This feature is available with all Generic 3 releases.
Description
Provides indications of queue status for ACD calls based on the  number of calls 
in queue and time in queue.  These indications are provided via lamps assigned 
to the terminals or consoles  of split agents or supervisors.  In addition, an 
auxiliary warning lamp can be provided to  track queue status based on the 
number of calls or time in queue. Also,  display-equipped voice terminals and 
consoles can display the time in queue of a split’s oldest call and the number of 
calls in that split’s queue.
Two types of Queue Status Indications are provided:
nNumber of Queued Calls
The Number of Queued Calls status indication is based on the  total 
number of calls, excluding Direct Agent Calls (DACs), in queue at a split.  
DAC calls are not counted here, nor are they included in the count when 
checking whether a threshold warning should be given.
The status indication can be provided by an Number of Queued Calls 
button with associated lamp on a voice terminal or console.  Each split is 
assigned a Number of Queued Calls warning threshold.  When this 
threshold is reached, the lamp associated with the Number of Queued 
Calls b utton flashes.  If there are calls in the q ueue, b ut the threshold is not 
reached, the lamp lights steadily. If there are no calls in queue, the lamp 
goes dark.
In a ddition to the Number of Queued Calls button(s),  the Numb er of 
Queued Calls status indication can be provided b y an auxiliary queue 
warning lamp. This lamp can b e installed at any location c onvenient  to the 
split agents. When the Number of Queued Calls warning threshold is 
reached, the auxiliary queue warning lamp  lights steadily.
nOldest Queued Time
The Oldest Queued Time status indication is based on the time in queue 
of the oldest call in a split queue. The status indication can b e provided b y 
an Oldest Queued Time  (Oldest Queued Time) button with associated 
lamp on a voice terminal or console.  Each split is assigned an Oldest 
Queued Time warning threshold of 0 to 999 seconds.  When the oldest c all 
in queue has been in queue for this length of time, the lamp associated 
with the Oldest Queued Time button flashes.  If there are calls in the 
queue, but the threshold is not reached, the lamp lights steadily. If there 
are no calls in queue, the lamp goes dark.