Home
>
ATT
>
Communications System
>
ATT DEFINITY Communications System Generic 3 Instructions Manual
ATT DEFINITY Communications System Generic 3 Instructions Manual
Have a look at the manual ATT DEFINITY Communications System Generic 3 Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 164 ATT manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
Trunk Flash Issue 3 March 1996 3-1175 Trunk Flash Feature Availability This feature is available with all Generic 3 releases. However, for G3V2 and later releases, this feature encomp asses both the G3V1 ‘‘Trunk Flash’’ and ‘‘PCORR’’ features. Description Trunk Flash enables multi-function voice terminals to access ‘‘central office customized services’’ that are provided by the far-end/CO located directly behind the DEFINITY system. CO customized services are electronic features (such as conference and transfer) that are accessed by a sequence of flash signals and dialing from the DEFINITY system station on an active trunk call. The Trunk Flash feature can help to reduce the number of trunk lines connected to the DEFINITY switch by: nPerforming trunk-to-trunk call transfers at the far-end/CO, which eliminates the use of a second trunk line for the duration of the call and frees the original trunk line for the duration of the call. nPerforming a conference call with a second outside call party, which eliminates the need for a second trunk line for the duration of the call. G3V2 supports Trunk Flash activation via Feature Access Code (FAC) and from CAS and non-CAS attendant terminals. NOTE: Some analog DTMF telephone sets used in Italy and the United Kingd om are equip ped with a ‘‘FLASH’’ button that, when pressed, generates a rotary digit ‘‘1.’’ When an analog station which is administered as a DTMF station (for example, as a 2500 or 71nn-type station) transmits a rotary digit ‘‘1.’’ G3i-Global, G3V2, and later releases treat the digit 1 signal as a recall signal from the station set to the PBX. This is called ‘‘Digit 1 as Flash’’ and is not supported in G3vsV1/G3sV1, G3iV1, or G3rV1. Considerations Generic 3 supports the Trunk Flash signal for incoming, outgoing, or two-way call directions on selected two-wire analog (ground-start or loop-start) or digital (DS1) trunks. For G3i-Global, G3V2, and later releases, trunk hunting enhancements have been ad d ed which affect trunks that are loop-start and help handle glare p roblems. Access to this feature is restricted to trunk Group Types of co, fx, and wats with the “Trunk Flash” field enabled.
Feature Descriptions 3-1176Issue 3 March 1996 In G3V1: — A Trunk Flash b utton can be assigned to multifunction stations and CAS attendants. For stations, this button activates the Trunk Flash feature; for CAS attendants, this button controls certain CAS features via RLT trunks. — The Trunk Flash feature is unavailable to analog stations and attendant consoles and can not be used on PCOLs. In G3V2 and later releases: — A Trunk Flash b utton can be assigned on CAS attendant consoles, non-CAS attendant consoles, and multifunction stations. For CAS attendants, use of this button limited to certain CAS features via RLT trunks. For multifunction and non-CAS attendant consoles, this button is used for the Trunk Flash feature. — FAC activation of the trunk flash feature is allowed. The Flash button is used by the Trunk Flash and CAS features. Generic 3 features (such as internal c onference call, transfer, and call park) may be combined with custom services (that is, CO-based features that are activated/controlled by sending a ‘‘flash’’ signal over the trunk to the CO). However, mixing Generic 3 features with custom services causes complications for the user when tracking a call. DEFINITY syst em s cannot give the local station user status information on the custom services. The Trunk Flash feature may only b e accessed if the call has only one trunk, the trunk must be outgoing from the PBX’s perspective, and the trunk group of that trunk has ‘‘Trunk Flash’’ enabled. The Trunk Flash feature is disabled when the call involves more than one trunk, even if all the trunks have ‘‘Trunk Flash’’ enabled. NOTE: The facility connecting a PBX to the CO is referred to, from the perspective of the PBX, as a trunk and, from the persp ective of the CO, as a line. Any PBX station with a Flash button may access the ‘‘Trunk Flash’’ feature. There may b e up to five PBX stations involved in a PBX conference call with the trunk line party. However, to access the Trunk Flash feature, at least one of the PBX stations must have a Flash button. In a call involving more than one PBX station, one station may press the Flash button, and another station may d ial the phone number. The station that d ials the phone number is not required to have a Flash button. There must be no other trunk connection b etween the PBX that the station is connected to, and the far-end/CO supplying the custom services. If the call connection passes over a ‘‘tie’’ trunk, the station does not have a direct connection to the far-end/CO and, as a result, does not have access to the far-end/CO custom services.
Trunk Flash Issue 3 March 1996 3-1177 If the far-end/CO does not support custom services, the call may be dropped by the far-end/CO on sending the flash signal or the signal may be ignored and a ‘‘click click’’ sound is heard . Interactions The Trunk Flash feature may be com bined with other DEFINITY switch features. Calls made after the flash are not recorded in CDR record s. Administration The System Manager must perform the following tasks: nAdminister a “Station” form for each voice terminal and attendant console that is authorized for Trunk Flash. Each authorized voice terminal must be assigned a Flash button. nAdminister the “Trunk Flash?” field in the appropriate “Trunk Group” form(s) for CO, FX, and/or WATS group types. Also, to access Trunk Flash via the Feature Access Codes (FAC), the ‘‘Flash Access’’ field on the ‘‘Feature Access’’ form must be administered. Hardware and Software Requirements No a d ditional hardware or software is required.
Feature Descriptions 3-1178Issue 3 March 1996 Trunk Group Busy/Warning Indicators to Attendant Feature Availability This feature is available with all Generic 3 releases. Description Provides the attendant with a visual indication that the number of busy trunks in a group has reached an administered level. A visual indication is also provided when all trunks in a group are busy. The two lam ps whic h provide the visual indications are as follows: nWarn Lamp Located on Trunk Hundreds Select buttons that have three lamps. The Warn lamp lights when a preset numb er (warning threshold) of trunks are busy in the associated trunk group. nBusy Lamp Located at each of the 12 Fixed Trunk Hundreds Select buttons and on each feature b utton a dministered as a Trunk Hundreds Select button. The Busy lamp lights when all trunks in the associated trunk group are busy. Considerations The Trunk Group Busy and the Trunk Group Warning Indicators are particularly useful when the Attendant Control of Trunk Group Access feature is provided. The indicators show the attendant that control of access to trunk groups is necessary. Interactions If Trunk Hundreds Select buttons are assigned for Loudspeaker Paging Access zones, Trunk Group Busy In dicators provides a visual indication of the busy or idle status of the zones. Administration This feature is ad ministered by the System Manager. The following items require administration: nTrunk Hundreds Select buttons (per attendant console) nWarning threshold (p er trunk group)
Trunk Group Busy/Warning Indicators to Attendant Issue 3 March 1996 3-1179 Hardware and Software Requirements No a d ditional hardware or software is required.
Feature Descriptions 3-1180Issue 3 March 1996 Trunk Identification By Attendant Feature Availability This feature is available with all Generic 3 releases. Description Allows an attendant or d isplay-equipped voice terminal user to identify a specific trunk being used on a call. This capability is provided by assigning a Trunk ID button to the attendant console or voice terminal. The Trunk Id entification By Attendant feature can be used when a user is on an established call of one of the following types: nAn incoming trunk call nAn outgoing trunk call nA transferred or conferenced call involving a trunk nA trunk-to-trunk call In a d dition to its use during an established call, the Trunk ID button can be used while a trunk is being seized, while digits are being outpulsed on a trunk, or during intervals between digit outpulsing. When a user is connected to a trunk, as described above, and presses the Trunk ID button, the identification of the trunk is displayed on the 40-character alphanumeric display. The trunk identification consists of the trunk access code (two-digit) for that trunk group and the trunk group member number (two-d i git). The trunk identification displayed depends on the type of call in process. If the call is incoming, the incoming trunk identification is disp layed. If the call is outgoing, the outgoing trunk identification is displayed. If the call is trunk-to-trunk, the identification displayed is of the last trunk a dd e d to the call. Considerations Trunk Id entification By Attendant is useful whenever it is necessary to identify a particular trunk being used. The feature is particularly useful for i dentification of a faulty trunk. That trunk can then be removed from service and the problem quickly corrected. A maximum of one Trunk ID button is allowed per each attendant console and voice terminal with a display. The Trunk Identification By Attendant feature is denied if there are more than two trunks on the call.
Trunk Id entification By Attendant Issue 3 March 1996 3-1181 The Trunk Identification By Attendant feature is denied if there are exactly two trunks on the call, and the station p ressing the Trunk ID b utton is not the controlling party. In the case of a conference resulting from an incoming call followed by an outgoing call, the last trunk a d ded to the conference is the incoming one. Interactions The following features interact with the Trunk Identification By Attendant feature. nBusy Verification A trunk being busy-verified can be identified. nAttendant Display and Voice Terminal Display Any action by the user or the system which changes the display removes the trunk identification currently displayed. The lamp associated with the Trunk ID button remains lighted as long as the call on which the button was use d remains active. While the lamp is lighted, the user can use the associated button to redisplay the trunk identification. If the Trunk ID button is pressed during a call origination (before all digits have been dialed), the trunk identification appears. On a voice terminal display, any subsequently dialed d igits are not displayed. On an attendant display, the subsequently dialed digits overwrite other digits on the display. nHold A trunk held by a user cannot be identified. Administration Trunk Id entification By Attendant is assigned by the System Manager on a per-voice terminal and per attendant console basis. The only administration required is the assignment of a Trunk ID button. Hardware and Software Requirements No a d ditional hardware or software is required.
Feature Descriptions 3-1182Issue 3 March 1996 Trunk-to-Trunk Transfer Feature Availability This feature is available with all Generic 3 releases. Description Allows the attendant or voice terminal user to connect an incoming trunk call to an outgoing trunk. Considerations Trunk-to-Trunk Transfer is p articularly useful when a caller outside the system calls a user or attendant and requests a transfer to another outside number. For example, a worker, away on b usiness, can call in and have the call transferred elsewhere. Transferred trunk calls can be administered to receive either music or silence. Some central office (CO) trunks do not signal the PBX when the CO user disconnects from the call. The system assures that incoming CO trunks without Disconnect Supervision are not transferred to outgoing trunks, or other incoming CO trunks without Disconnect Supervision. An attendant-assisted call connecting an outgoing trunk or incoming trunk without Disconnect Supervision to an outgoing trunk must be held on the console. The system does not allow the attendant to release such a call. The attendant can, however, use the Forced Release button and disconnect all parties associated with the call. If a voice terminal user has connected two outgoing trunks or an outgoing call and an incoming call without Disconnect Supervision, the user must remain on the call. Otherwise, the call is dropped. An incoming trunk with Disconnect Supervision can be connected to an outgoing trunk without the user remaining on the call. An incoming trunk can also be connected to another incoming trunk without the user remaining on the call if one of the incoming trunks has Disconnect Supervision. G3rV1 and G3V2 and later releases support ‘‘Outgoing-Trunk-to-Outgoing-Trunk’’ transfer, which permits a station user or an attendant to initiate two or more outgoing trunk calls. If the Trunk-to-Trunk feature is assigned and one of the trunks is a dministered as ‘‘y’’ on the “Trunk Group” form ‘‘Disconnect Supervision-Out?’’ field, the station user or attendant can transfer the trunks together. Transferring in this way removes the controlling p arty from the connection and conferences the two outgoing trunks together.
Trunk-to-Trunk Transfer Issue 3 March 1996 3-1183 The Trunk-to-Trunk Transfer option on the “ Feature Relate d System Parameters” form has no affect on tie trunks. Restricted Trunk-to-Trunk Transfer only affects calls where b oth trunks are CAS, CO, DIOD, FX, WATS, DID, or CPE. Interactions The Attendant Lockout feature does not function on Trunk-to-Trunk Transfer. Administration Trunk-to-Trunk Transfer is a dministered on a per-system basis by the System Manager. Trunk-to-Trunk Transfer is administered on the “Feature-Relate d System Parameters” form. If the “ Trunk-to-Trunk Transfer” field contains all, all trunks are transferred. If the field contains restricted, public trunks (CAS, CO, DIOD, FX, DID, WATS, and CPE) are not transferred. If the field contains n, all trunks are restricted. Restriction means that any transfer/release/drop operation has calls dropped or receives denial. To enable ‘‘Outgoing-Trunk to Outgoing-Trunk Transfer,’’ set the ‘‘Disconnect Supervision-Out?’’ field to y. NOTE: Setting the value of this field to y may result in trunk lock-ups. Hardware and Software Requirements No a d ditional hardware or software is required.
Feature Descriptions 3-1184Issue 3 March 1996 3 Uniform Dial Plan (UDP) Feature Availability This feature is available with all Generic 3 releases. Description Provides a common 4- or 5-digit dial p lan (s pecified by Dialplan administration) that can be shared among a group of switches. Interswitch dialing and intraswitch dialing both require 4- or 5-d igit dialing. The UDP is used with ETN, Main/Satellite/Tributary, and DCS configurations. Ad ditionally, UDP can be used alone to provide uniform 4- or 5-digit dialing between two or more private switching systems without ETN, Main/Satellite/Tributary, or DCS configurations. For G3i, in a UDP, the first one, two, three, or four d i gits of the 4- or 5-digit extension number make u p a PBX code which determines the switch to which a call is directed. When a UDP is administered, a list of PBX codes is assigned to each switch. A UDP can have as many as 240 PBX codes. For G3r, each PBX code is assigned a private network location c o de (RNX) or node number. The RNX of a PBX in a UDP is the equivalent of an office code of a central office in a public network. It is this RNX that is actually used to determine how a UDP call is routed. Each PBX code is also a dministered as either local or remote to the switch UDP routes calls off the local PBX by converting the extension number into a type of private-network number with 7 digits. Such a number is formed by prepending a 3-d igit c o de (of the form XXX) to the (last) four digits of the extension numb er. Three types of conversion are supported: UDPCode, AARCode, and ENPNode. For UDPC o de and AARCode, XXX is a 3-digit private-network location code, and the result is analyzed and routed via AAR. UDPCode conversion prohibits digit conversion via AAR; AAR Code conversion permits it, just as if the user had dialed the AAR number instead of the extension. The third type of conversion, ENPCode, XXX is called an ‘‘ENP code,’’ and is not used for routing; instead, node number routing is used. The ENP code is chosen based on the first one or two digits of the dialed extension. The ENP code can be independent of location since it is not used for routing. UDP conversion can be specified for individual extensions, or groups of extensions sharing the same leading digits, via the “ UDP” form and ‘‘extension codes.’’ An extension code is just the desired leading digits of an extension followed by ‘x’ (wild cards). For example, ‘‘123xx’’ is the extension code for all 100 possible extensions beginning with ‘‘123’’ (‘‘12345’’ is an extension code specifying only one extension). Each extension c o de can be assigned to one of six possible treatments: