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 Multi-Appearance Conference/Transfer Issue 3 March 1996 3-637 DCS Multi-Appearance Conference/Transfer Feature Availability DCS is available with all Generic 3 releases except G3vs/G3s ABP. Description Provides transparency of transfer of calls, and of conference calls within a DCS network. A user in the DCS c an make conference calls or transfer calls originated from any extension in the DCS network to another extension within the DCS. (For transferred calls, the destination need not be within the DCS.) In a DCS, if a party in a conference hangs up or completes a transfer leaving only outgoing trunks on the call, an attempt is made to preserve the connection if any of the remaining parties on the call is a DCS tie trunk. This can be accomplished if the DCS tie trunk can signal the remote node when the party hangs up. The remote node sends a reply to the originating node, and disconnect supervision is provided for that trunk. Conference Calls can b e placed and calls can be transferred to users within the DCS by dialing the UDP extension number. A detailed description of the Conference — Attendant, Conference — Terminal, and Transfer features is given elsewhere in this chapter. Considerations DCS Multi-Appearance Conference/Transfer is useful when it is necessary to talk to more than one party at one time within a DCS. Multia p pearance voice terminals must have an idle ap pearance in order to transfer a call. Interactions The following features interact with the DCS Multi-Ap pearance Conference/Transfer feature. nVoice Terminal Display No display transparency is provided for DCS Multi-Ap pearance Conference/Transfer. nEDCS On calls to or from Public Network Trunks, calling/called party restrictions are checked when EDCS is active.
Feature Descriptions 3-638Issue 3 March 1996 Administration None required. Hardware and Software Requirements DCS interface hardware and DCS software are required.
DCS Over ISDN-PRI D-Channel Issue 3 March 1996 3-639 DCS Over ISDN-PRI D-Channel Feature Availability DCS is available with all Generic 3 releases except G3vs/G3s ABP. Description Enhances the DCS feature by allowing access to the public network for DCS feature connectivity b etween DCS switch nodes. With this feature, DCS features are no longer restricted to private facilities. The ISDN-PRI B-channel is used for voice communications, and the ISDN-PRI D-channel is used to transport DCS control information. The only d ifference b etween DCS networks that do not utilize the DCS Over ISDN-PRI feature and those that do is in the method of signaling. The DCS Over ISDN-PRI D-Channel feature uses Message-Associated User-to-User Information (MA-UUI) and Temp orary Signaling Connections (TSCs) to transport certain DCS control information. MA-UUI allows a d ditional user-specific information to be transported along with certain ISDN call-control messages. A TSC provides a temporary signaling path through ISDN switches for exchanging user-user information. There are two typ es of temporary signaling connections: Call Associated Temporary Signaling Connections (CA-TSC) and Non-Call Associated Temp orary Signaling Connections (NCA-TSC). A CA-TSC refers to a service for exchanging USER INFORMATION messages that are asso ciated with an ISDN B-Channel connection by the call reference value of the call control data p a ckets. An NCA-TSC is a connection not related with any ISDN B-channel connections. It is an a dministered virtual connection established for exc hanging USER INFORMATION messages on the ISDN D-channel for the DCS Over ISDN-PRI D-Channel application as well as for the DCS AUDIX a p plication. Once an NCA-TSC has been a dministered and enabled, it will be active for an extended period of time. There are two types of administered NCA-TSCs depending on their setup mechanism: Permanent and As-need e d. Once enabled, a permanent NCA-TSC will remain established while the system is running. If the permanent NCA-TSC is dropped for any reason, the system will attempt to reestablish the connection. An as-needed administered NCA-TSC is established based on user request and the availability of TSC facilities. The connection will be dropped after an administered period of inactivity. The system can transport DCS or DCS Audix messages over an ISDN-PRI D-channel and over BX.25 d ata links when functioning as a gateway between a PBX equipped with the DCS Over ISDN-PRI D-Channel feature and a PBX equip ped with traditional DCS using BX.25 data links. In this situation, the
Feature Descriptions 3-640Issue 3 March 1996 messages travel from the gateway through the %NCA-TSCs or %CA-TSCs to %TSC-cap a ble PBXs and from the gateway to PBXs that sup p ort only traditional DCS via a BX.25 logical channel. At least one PBX must be configured as an ISDN DCS Gateway node in a DCS network that consists of PBXs that support DCS Over ISDN-PRI D-Channel and PBXs that do not support the feature. For exam ples of various DCS network configurations and how they are administered, see DEFI NIT Y Com munications System Generic 3 Version 4 Implementation , 555-230-655, or DEFI NI TY Com munications System Generic 3 V2/ V3 Im p lem ent ati on , 555-230-653. Considerations System users should notice no difference between DCS features over ISDN-PRI and traditional DCS features. Interactions Most feature interactions with DCS Over ISDN-PRI D-Channel are the same as those with traditional DCS features. However, some interactions are unique to the DCS Over ISDN-PRI D-Channel feature. These unique interactions are listed below: nAttendant DXS with Busy Lamp Field An attempt by the attendant to directly select an extension that has been previously administered as belonging to a administered NCA-TSC will result in intercept tone being received. nD-Channel Backup In the event of a D-channel switchover (primary to secondary or secondary back to primary) in a p rivate network, a dministered NCA-TSCs that were active are assumed to have remained active. Any unacknowledged user-user service requests are assume d to be rejected, and administered NCA-TSCs which were in the p rocess of being established at the time of the switchover are dropped when the switchover occurs. Those a dministered NCA-TSCs that were dropped will be reattempted again. If a D-channel switchover occurs on a D-channel going to the pu blic network then all TSCs will be dropped. A maintenance-provided ‘‘heartbeat’’ message will periodically be sent over each permanent administered NCA-TSC to ensure that such a situation is detected and recovered from. nDistributed Communications System AUDIX (DCS AUDIX)
DCS Over ISDN-PRI D-Channel Issue 3 March 1996 3-641 The DCS over ISDN-PRI D-Channel feature can be used to support DCS Audix. (The connection between G3i and AUDIX should be BX.25.) nGR S GRS will select TSC c ompatible facilities when routing NCA-TSCs. In other words, a NCA-TSC request can only select a routing preference that supports TSCs. In a tandem node, GRS will first select facilities that sup p ort TSCs if the call falls into any one of the following two conditions: — It requests a CA-TSC explicitly — It contains a DCS information element in the SETUP message Once a trunk g roup with available memb ers is selected, the call will proceed even if all the TSCs belonging to the associated signaling group are active. In other words, the completion of a call is given priority over DCS transparency. nIS D N - PR I This feature uses ISDN-PRI call control protocol and messages. nSDN The DCS over ISDN-PRI D-Channel feature allows the system to access public networks such as SDN. SDN supports all DCS features except for the following: — DCS Attendant Control of Trunk Group Access — DCS Attendant Direct Trunk Group Selection — DCS Busy Verification of Terminals and Trunks nCDR CDR will record both the status and the utilization of TSCs. Both CA-TSCs and NCA-TSCs can be recorded. For more information, consult the CDR description in this manual or the CDR manual. nVoice Terminals An attempt to dial an extension that has been previously administered as belonging to a administered NCA-TSC will result in intercept tone being received. Administration The ISDN-PRI option must be enabled on the “System-Parameters Customer-Option” form before associated forms and fields on forms can be administered. To implement this feature, the following form(s) must be comp leted. nSignaling Group Form
Feature Descriptions 3-642Issue 3 March 1996 nISDN TSC Gateway Channel Assignment Form — Used to map administered NCA-TSCs to (BX.25) processor channels in an Integrated DCS Network. (Form only required for PBX location serving as an ISDN Gateway in an Integrated DCS Network.) Complete all fields as required. nISDN Trunk Group Form nRouting Pattern Form nCommunications-Links Processor Channels Form — The “ Ap pl” field specifies to which application channel this processor channel is connected. Enter gateway in the associated “Appl” field if the processor channel is used as one end of the gateway channel assigned in the “ ISDN TSC Gateway Channel Assignments” form. The gateway node serves as the terminating node to the D-Channel DCS network as well as the terminating node to the traditional DCS network. A PBX serving as an ISDN DCS Gateway node introduces some interesting situations when administering processor channels in an associated traditional DCS PBX. In a traditional DCS network, (BX.25 processor channel links) the “Remote Port” field in the “Processor Channel Assignments” form refers to the processor c hannel of the destination PBX. In an Integrated DCS network, the “Remote Proc Chan” field in the “Processor Channel Assignments” form refers to the processor channel of the Gateway PBX (if the d estination PBX is an ISDN DCS PBX), not the destination PBX. On the contrary, the “ Machine-ID” field in the “Processor Channel Assignments” form refers to the destination PBX, either an ISDN DCS PBX or a traditional DCS PBX. The Gateway PBX number must not b e used in this field if the destination PBX is an ISDN DCS PBX. NOTE: There are several differences in between G3i and G3r administration. For example, PRI is translated a little differently in G3r when traditional DCS and this feature are used in combination. On systems with AUDIX in a DCS environment, an a dditional column has been a d ded to the “Signalling Group” form so the administrator can specify which AUDIX on which switch to use. When traditional DCS and DCS over ISDN are used in combination, translations are also different. Refer to the DEFINITY Communications System Generic 3 Version 4 Implementation , 555-230-655, or DEFI NI TY Com munications System Generic 3 V2/V3 Imp lementation , 555-230-653, for further information. Hardware and Software Requirements The DCS over ISDN-PRI D-Channel feature requires the same hardware as other ISDN-PRI features. ISDN-PRI software is required.
DCS Trunk Group Busy/Warning Indication Issue 3 March 1996 3-643 DCS Trunk Group Busy/Warning Indication Feature Availability DCS is available with all Generic 3 releases except G3vs/G3s ABP. Description Provides attendants with a visual indication that the number of busy trunks in a remote group has reached an administered level. A visual indication is also provided when all trunks in a trunk g roup are busy. If an attendant has a Trunk Hundreds Select button assigned to a remote trunk group, the button’s Busy lamp lights when all trunks in the trunk group are busy. The lamp goes d ark when one of the busy trunks becomes available. If an attendant has a three-lamp Trunk Hundreds Select b utton assigned to a remote trunk g roup, the button’s Warn lam p lights when the numb er of busy trunks in the trunk group reaches the Busy Warning Threshold. The lamp goes dark when the numb er of busy trunks in the trunk group falls below the Busy Warning Threshold. To ensure that the b usy, warning, and control status of all Trunk Hundreds Select buttons in the DCS remain consistent with the status of the corresponding trunk groups, some nodes in the DCS broadcast the status of a different local trunk group, every 50 seconds, to all directly connected nodes. A pair of DCS nodes are directly-connected if the voice tie trunks between them are not connected through another switch. For example, a node with 30 trunk groups would take 1,500 (50 x 30) seconds to broadcast the status of all 30 trunk groups. This is called a lamp audit. When a node receives a lamp audit message, its TGB/TGW lamps are up d ated accordingly. Considerations Trunk Group Busy and Trunk Group Warning Indication is particularly useful with the Attendant Control of Trunk Group Access feature. The indicators alert the attendant when control of access to local and remote trunk groups is necessary. Except for remote S75 R1V3, S85/G2 and S75 R1V2 switches, this feature is only transparent if the remote switch is directly connected by voice tie trunks. For S75 R1V3 and S85/G2 remote switches, Trunk Group Busy and Trunk Group Warning Indication is provided regardless of whether the voice tie trunks are directly-connected or in tandem through an intermediate node; For S75 R1V2 remote switches, no Trunk Group Busy and Trunk Group Warning Indication transparency is provided.
Feature Descriptions 3-644Issue 3 March 1996 Interactions If Trunk Hundreds Select buttons are assigned for Loudspeaker Paging Access zones, Trunk Group Busy Indicators will provide a visual indication of the busy or idle status of the zones at the remote location as well as at the local node. Administration Administration for DCS Trunk Group Busy/Warning Indication can only be administered for remote trunk groups that are d irectly connected to the local switch. The trunk g roup access codes for such trunk g roups must be three d igits or less. Hardware and Software Requirements DCS interface hardware and DCS software are required.
Default Dialing Issue 3 March 1996 3-645 Default Dialing Feature Availability This feature is available with all Generic 3 releases. Description Default Dialing enhances Data Terminal (Keyboard) Dialing by allowing a data terminal user to place a data call to a preadministered destination by either entering Return at the DIAL: prompt (for data terminals using DCP d ata modules) or typing d and entering Return at the CMD: prompt (for data terminals using ISDN-BRI data modules). The d ata terminal user with a DCP data module can still place calls to other d estinations by entering the complete address after the DIAL: prompt (normal Data Terminal Dialing or Alphanumeric Dialing). The data terminal user with an ISDN-BRI data module can still place calls to other destinations by typing d, entering a space, typing the complete address, and entering Return after the CMD: prompt. Default Dialing provides data terminal users who dial a specific number the majority of the time a very simple method of dialing that number. Normal Data Terminal Dialing and Alphanumeric Dialing are unaffected. For the AT command interface supported by the 7400A d ata module, the ATD command may be entered instead of a carriage return to dial the default destination. The default destination is administered by the System Manager. Default Dialing can be assigned to any data endpoint that has the Data Terminal Dialing capability. Considerations Default Dialing provides data terminal users who dial a specific number the majority of the time a very simple method of dialing that number. Interactions The following features interact with the Default Dialing feature. nData Call Setu p Default Dialing enhances Data Terminal (Keyboard) Dialing by allowing a data terminal user to place a d ata c all to a preadministered destination by either Return at the DIAL: prompt (for DCP) or typing d and entering Return at the CMD: prompt (for ISDN-BRI).
Feature Descriptions 3-646Issue 3 March 1996 Administration Default Dialing is administered by the System Manager. In addition to those items listed in the Data Call Setu p feature description, elsewhere in this chapter, the following items must be administered: nThe preadministered d efault destination must b e stored in an abbreviated dialing list. This list can be a system list, group list, personal list, or enhanced list. Therefore, before this feature can be activated, users’ terminals need to b e administered with an abbreviated dialing list that stores the default d estination Then, each data module needs to specify the index number of the entry which stores the default destination. The following fields from the “Data Module” form are needed to activate the Default Dialing feature. — Special Dialing Option (default/hotline) — For Default Dialing, ‘‘default’’ must be selected. Default Dialing and the Data Hotline feature cannot both be assigned to an extension. — An Ab breviated Dialing List — One entry in the data mo dule’s a b breviated dialing list needs to store the d efault destination. — Dial Code — An index to the entry of the abbreviated dialing list that stores the default destination. Hardware and Software Requirements No a d ditional hardware or software is required.