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+.
DCS Alphanumeric Display for Terminals Issue 3 March 1996 3-597 Within the same DEFI NIT Y syst em Generic 1 or Generic 3 node in a DCS, complete transparency of Calling and Called Name Display exists. Interactions The following DCS configurations provide transparency of alphanumeric display information: nNetworks of two or more DEFINITY switches (Generic 1 or Generic 3i) with a System 75 Version 3 or later, Generic 2, System 85 Release 2 Version 2 or later, or a Generic 2.1 as an interme diate node nA DEFINITY system Generic 1 connected to a System 85 Release 2 Version 2 or later, or a Generic 2.1 Configurations in which DEFINITY system Generic 1s are connected to or through a System 85 Release 2 Version 1 or an Enhanced DIMENSION PBX are not covered because these nodes do not provide display transparency. If both DCS and ISDN-PRI features are p rovid e d with a system, the ISDN-PRI display information is displayed in DCS format. The following features have transparency with respect to Calling and Called Name Display and miscellaneous ID. If the display for a DCS call differs at all from the display for a call between terminals at the same system, the difference is noted. Refer to the DEFINITY Communications System Generic 1 and Generic 3 Voice Terminal O perations , 555-230-701, for detailed descriptions of call information displays. nAutomatic Callback Complete display transparency. nCall Coverage At the calling terminal, the miscellaneous id ‘‘cover’’ is not displayed. nCall Forwarding When a system user calls a party on a different node in the DCS and the call is forward ed, the miscellaneous ID ‘‘forward’’ is not displayed. At the covering (forwarded-to) user’s terminal, only the calling party’s name is shown; the called party’s name is not d isplayed. nCall Park When a DCS call between a local system user and a user on another node is parked by the remote user, the miscellaneous ID ‘‘park’’ is not displayed at the local terminal. nCall Pickup When a DCS call from a system user to another node is answered by way of Call Pic kup, the miscellaneous ID ‘‘cover’’ is not displayed at the caller’s terminal.
Feature Descriptions 3-598Issue 3 March 1996 nCall Waiting When a DCS call from a system user to another node is waiting at the called terminal, the miscellaneous ID ‘‘wait’’ is not displayed at the caller’s terminal. nCAS When a user dials the extension for CAS, a RLT is seized or the caller is queued for an RLT. The caller’s terminal will display the trunk group identifier, such as OPERATOR. nConference When a DCS call is conferenced either at a remote node or at the local system, all DCS Calling and Called Name Display transparency is lost to local system users. If all parties drop out except for a local user and another DCS user, the local user’s terminal will display the trunk group identifier. nDDC/UCD Complete display transparency. nInternal Terminal-to-Terminal Callin g Complete display transparency. nTransfer When a DCS c all is transferred at a remote node to a user on any node, all DCS Calling and Called Name Display transparency is lost to users on the local system. Administration DCS tie trunk groups between nodes must be administered by the System Manager with the Outgoing Display disabled. This enables the called party’s name to be disp layed at the calling terminal. Hardware and Software Requirements DCS interface hardware and DCS software are required.
DCS Attendant Control of Trunk Group Ac cess Issue 3 March 1996 3-599 DCS Attendant Control of Trunk Group Access Feature Availability DCS is available with all Generic 3 releases except G3vs/G3s ABP. Description Allows an attendant at any node in the DCS to exercise control over an outgoing trunk group at an adjacent node in the cluster. Each attendant console has 12 Trunk Hundreds Select buttons to be used with the Attendant Direct Trunk Group selection feature. Each button allows the attendant d irect access to an outgoing trunk group by merely pressing the b utton assigned to that trunk g roup. Each of the 12 buttons has a Busy lamp which lights when all trunks in the associated trunk group are busy. On a basic console, six of these buttons have two a d ditional lamps that are used for Attendant Control of Trunk Group Access. On an enhanced console, all 12 buttons have the a d ditional lamps. The two a d ditional lamp s are as follows: nWarn (warning) lamp Lights when a preset numb er of trunks are busy in the associated trunk group. nCont (control) lamp Lights when the attendant activates Attendant Control of Trunk Group Access for the associated trunk group. Attendant control of a remote trunk group in the DCS network is activated by pressing the Cont Ac t button followed by the d esired Remote Trunk Hundreds Select button. Then the initiating node sends a message to the remote node where the trunk group to be controlled resides. The message indicates that control of that trunk group has been initiated. When the remote node receives the c ontrol activation message from the initiating node, it has four seconds to send a reply message back to the initiating node if control of the remote trunk group can be activated. A confirmation message will be sent to the initiating node and the Cont lamp at the corresponding Trunk Hundreds Select button is lighted at the remote node if control of the remote trunk group can be activated. An error message is sent to the attendant at the initiating node if the trunk access code is invalid, if the trunk group is already controlled, or if the remote node is a System 85 or Enhanced DIMENSION PBX and the attendant does not have a Trunk Hundreds Select b utton with Cont lamp for that trunk group.
Feature Descriptions 3-600Issue 3 March 1996 When a trunk group is controlled in a DCS environment, calls to the trunk group by anyone other than an attendant are routed to the local attendant at the node where the trunk group resides. If that node does not have an attendant, the call is routed to a CAS main attendant or an attendant at a location arranged for Inter-PBX Attendant Calls. However, if CAS or the Inter-PBX Attendant Calls feature is not provid e d, the party attempting to call on the controlled trunk receives intercept tone. A d etailed d esc ription of Centralized Attendant Service (CAS) and Inter-PBX Attendant Calls is given elsewhere in this chapter. Considerations DCS Attendant Control of Trunk Group Ac cess allows attendants to obtain control of access to specific trunk groups at any node in the DCS network. This allows the attendant to monitor the use of the controlled trunk group. There must be direct DCS tie trunk connections between the initiating node and the remote node where the trunk group to be controlled originates. Otherwise, control of remote trunk groups is denied. If the remote node (where the trunk group to b e controlled resides) is a System 75, Generic 1, or Generic 3, it is not necessary for that node to have an attendant c onsole with c orresponding three-lamp Trunk Hundreds Select button. However, if the remote node is a System 85, Generic 2.1, or Enhanced DIMENSION PBX, control of the trunk group is not allowed unless an attendant at that node has a corresponding three-lamp Trunk Group Select button. The attendant must use the Remote Trunk Hundreds Select button to d irectly access the controlled remote trunk group. If an attendant controls a remote trunk group, and that attendant dials the trunk access codes of the DCS tie trunk and the controlled remote trunk group, the call is routed to the attendant at the node where the trunk group resides. If Attendant Control of Trunk Group Access is activated, and no attendant is assigned, or the attendant is later removed, calls to a controlled trunk group route to the attendant queue.
DCS Attendant Control of Trunk Group Ac cess Issue 3 March 1996 3-601 Interactions The following features interact with the DCS Attendant Control of Trunk Group Access feature. nDCS Attendant Display When a user attempts to access a controlled trunk group and is routed to the local attendant, the disp lay shows the reason the call was redirected. If the call is routed via CAS or the Inter-PBX Attendant Calls feature, the display does not show the reason the call was redirected. nUDP DCS tie trunks should not be attendant controlled. This would result in all UDP calls on the controlled tie trunk being routed to the controlling attendant instead of to the desired destination. Administration The ability of an attendant to control access to a remote trunk group is d e pendent on the ad ministration by the System Manager of Trunk Hundreds Select buttons for remote trunk groups in the DCS. Hardware and Software Requirements DCS interface hardware and DCS software are required.
Feature Descriptions 3-602Issue 3 March 1996 DCS Attendant Direct Trunk Group Selection Feature Availability DCS is available with all Generic 3 releases except G3vs/G3s ABP. Description Allows attendants at one node to have direct access to an idle outgoing trunk at a different node in the DCS. A Trunk Hundreds Select button can be assigned to access a trunk group at the local node or a trunk group at a remote node. A Trunk Group Select button assigned to access a remote node is referred to as a remote Trunk Hundreds Select button. Pressing a remote Trunk Group Select button has the same affect as dialing the tie trunk group access code for the remote node and the trunk access code of the selected trunk. DCS Attendant Direct Trunk Group Selection functions the same as the regular DCS Attendant Direct Trunk Group Selection feature (fully described elsewhere in this chapter). The only difference is an attendant can access a trunk group at a remote node. Considerations With DCS Attendant Direct Trunk Group Selection, an attendant can have faster access to trunk groups at remote nodes. There is no need to look up trunk access codes, because the press of a button connects the attendant to the desired trunk group. There must be a direct DCS tie trunk connection b etween the initializing node and the remote node where the trunk group to be accessed originates. Otherwise, access to the remote trunk group is denied. Interactions None. Administration The system manager must assign: — A remote Trunk Hundreds Select button. — The tie trunk access code to the remote node.
DCS Attendant Direct Trunk Group Selection Issue 3 March 1996 3-603 — The trunk access code of the remote trunk group. The trunk access codes (TACs) must be three characters or less. In a ddition to the 12 fixed Trunk Hundreds Select buttons on each attendant console, feature b uttons may be assigned remote Trunk Hundreds Select buttons, Hardware and Software Requirements DCS interface hardware and DCS software are required.
Feature Descriptions 3-604Issue 3 March 1996 DCS Attendant Display Feature Availability DCS is available with all Generic 3 releases except G3vs/G3s ABP. Description Provides some transparency with respect to the display of call-related information. Calls to and from a DEFINITY switch in a DCS environment have Calling/Called Party Identification transparenc y under the following conditions: nThe other party is at another DEFINITY syst em Generic 1, Generic 3, or System 75, and the intermediate node is a DEFINITY system Generic 1, Generic 2.1, Generic 3, System 75 Version 3 or later, or a System 85 Release 2 Version 2 or later. nThe other party is at a System 85 Release 2 Version 2 or later, or a DEFI NI TY s yst em Generic 2.1. nThe call is not route d through an intermediate System 85 Release 2 Version 1 or Enhanced DIMENSION PBX node. (Such calls will display only the extension numb er of the calling or called party.) A d etailed description of the Attendant Display feature is given elsewhere in this chapter. Considerations DCS Attendant Display gives the attendant considerable call handling capabilities by displaying call relate d information on calls to and from both local and remote nodes. This detailed information can be very useful in processing calls. CORs for a DEFINITY switch may not correspond to those used by an Enhanced DIMENSION PBX, System 85, or DEFI NI TY s yst em Generic 2.1. Therefore, if the DCS network contains nodes other than DEFI NI TY s yst em Generic 1 or Generic 3, the display CORs may be misinterpreted. If it is important that certain CORs between various systems correspond with each other, those CORs should be administered accordingly. On outgoing calls, the d isplay of called party information may be delayed a few seconds until the required information arrives from the remote node. The called party information is displayed only if both nodes are DEFINITY system Generic 1 or System 75.
DCS Attendant Display Issue 3 March 1996 3-605 DCS tie trunks between nodes must be a dministered with the Outgoing Display enabled. This enables the called party’s name to be displayed at the calling attendant’s display. Interactions When both ISDN and DCS disp lay information, or only DCS display information, are received, the switch will display the DCS display information in the DCS format. If ISDN disp lay information is received, and no DCS display information is received, then the ISDN display information is displayed in the ISDN formats. Administration The administration required for DCS Attendant Disp lay is the same as that required for the Attendant Display feature. This information is given elsewhere in this chapter. Hardware and Software Requirements DCS interface hardware and DCS software are required.
Feature Descriptions 3-606Issue 3 March 1996 DCS Automatic Callback Feature Availability DCS is available with all Generic 3 releases except G3vs/G3s ABP. Description Allows a user at one node to make an automatic callback call to a user at another node in the DCS. A DCS Automatic Callback call can be activated from a voice terminal at one node to a voice terminal at another node in the same way as if at a local node under the following conditions. nIf the called party is at a System 85, DEFI NIT Y syst em Generic 2, or Enhanced DIMENSION PBX node, the callback call can only be activate d if the called node is returning b usy tone or special audible ringback. nIf the called party is at a DEFINITY system Generic 3, Generic 1 or System 75 node, the callback call can be activated if the called node is returning busy tone, Call Waiting rin g back tone, or ringb a ck tone. nThe calling party must disconnect within six seconds after hearing the confirmation tone for Automatic Callback activation. The callback of the calling or called parties is as follows when a callback call has been made to a user at another node: nWhen the calling party answers the callback call, and no tie trunk to the called party’s node is available, Automatic Callbac k is reactivated toward the called party. The calling party hears confirmation tone instead of ringback when this occurs. nIf the calling party is on a System 85, DEFINITY system Generic 2, or Enhanced DIMENSION PBX node and is unable to receive the callback call (for example, a busy single-line voice terminal without Call Waiting), Automatic Callback is reactivate d by the calling p arty’s node. If the calling party is on a DEFINITY syst em Generic 3, Generic 1, or System 75 node and is unable to receive the callback call, the callback call is canceled. nIf the called party is unable to receive the callback call because they are busy again (for examp le, the called party goes on hook and then off hook immediately to place another call), the calling party hears b usy tone a gain and can choose to reactivate Auto Callback, if desired. A d etailed d esc ription of the Automatic Callback feature is found on page 3-192.