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 Automatic Callback Issue 3 March 1996 3-607 Considerations DCS Automatic Callback eliminates the need for voice terminal users to continuously redial busy or unanswered calls to voice terminals within the DCS network. An Automatic Callback request is canceled automatically if the called party does not become available within 40 minutes, or if the calling party does not hang up within six seconds after activating Automatic Callback. DCS Automatic Callback does not work on the last trunk between nodes. Thus, if ‘‘n’’ trunks are provided, there can be up to ‘‘n - 1’’ Automatic Callback calls. Interactions The following features interact with the DCS Automatic Callback feature. nAttendant Control of Trunk Group Access and DCS Attendant Control of Trunk Group Access Automatic Callback cannot be activated if the call uses a controlled trunk group. nCall Forwarding All Calls and DCS Call Forwarding All Calls Automatic Callback calls cannot be activated on a voice terminal at a DEFI NI TY switch or System 75 node that has Call Forwarding activated. Administration The administration required for DCS Automatic Callback is the same as that required for the Automatic Callbac k feature. This information is given elsewhere in this chapter. Hardware and Software Requirements DCS interface and DCS software are required.
Feature Descriptions 3-608Issue 3 March 1996 DCS Automatic Circuit Assurance (ACA) Feature Availability DCS is available with all Generic 3 releases except G3vs/G3s ABP. Description Allows a voice terminal user or attendant at a node to activate or deactivate ACA referral c alls for the entire DCS network. This transparency also allows the referral calls to be generate d at a node other than the node that detects the problem. If referral calls are generated at a node for one or more remote nodes, the remote nodes are notified when ACA referral is activated or deactivated. If referral calls are generated at a remote node for a DEFI NI TY system Generic 3 node, the DEFINITY system Generic 3 node is notified when ACA referral is activated or deactivate d at the remote node. This notification is accomplished via the ACA button located on the attendant console or voice terminal at the DEFI NI TY s yst em Generic 3 node. The lamp associated with the ACA button lights when ACA referral is activated and goes dark when ACA referral is deactivate d. The ACA b utton serves no other purpose when a remote node generates the DEFINITY system Generic 3 referral calls. A d etailed description of the Automatic Circuit Assurance (ACA) feature is given elsewhere in this chapter. Considerations The DCS Automatic Circuit Assurance feature provides better service through early detection of faulty trunks and consequently reduces out-of-service time. Interactions None. Administration DCS Automatic Circuit Assurance requires that the System Manager administer whether ACA referral calls are to be local, remote, or primary: nIf administered as local, referral calls are g enerate d at the Generic 3 node for the Generic 3 node.
DCS Automatic Circuit Assurance (ACA) Issue 3 March 1996 3-609 nIf administered as remote, referral calls are generated at a remote node for the Generic 3 node. In this case, the remote node identification must also be entered. nIf administered as primary, referral calls are ma de at the Generic 3 node for a remote node. Hardware and Software Requirements DCS interface hardware and DCS software are required.
Feature Descriptions 3-610Issue 3 March 1996 DCS Busy Verification of Terminals and Trunks Feature Availability DCS is available with all Generic 3 releases except G3vs/G3s ABP. Description Allows attendants and multiappearance voice terminal users to make test calls to voice terminals and trunk groups that are located at other nodes within the DCS. Attendants and multiappearance voice terminal users can busy verify voice terminals at a remote location. This is done by first pressing the Verify b utton and then entering the desired UDP extension number. The verification then continues the same as if the voice terminal being verified is on the same node. Multiappearance voice terminal users can busy verify an adjacent at a remote location. This is done by first pressing the Verify button, then dialing the trunk access code of the tie trunk group to the remote node, pressing the Verify button a second time, and then entering the desired trunk access code and the trunk group member number to be verified. The verification of the trunk then continues as if the trunk being verified is on the same node. Attendant operation is the same except a Trunk Hundreds Select button can be used to access the tie trunk to the remote node. A detailed description of the Busy Verification of Terminals and Trunks feature is given elsewhere in this chapter. Considerations DCS Busy Verification of Terminals and Trunks provides an easy method of checking the working condition of extensions and trunks at remote nodes. Interactions If the Trunk Identification by Attendant feature is used during busy verification of a trunk (Trunk ID button is pressed), the trunk access code and trunk group member number of the DCS tie trunk b eing used is disp layed. DCS Busy Verification of Terminals and Trunks transparency is lost if the routing pattern is administered to not delete the RNX and the AAR prefix is inserted on the terminating switch trunk group. The voice terminal display at the terminating switch displays only a=station name. The “Extension” field is left blank.
DCS Busy Verification of Terminals and Trunks Issue 3 March 1996 3-611 Administration The administration for DCS Busy Verification of Terminals and Trunks is the same as that for the Busy Verification of Terminals and Trunks feature, which is fully described elsewhere in this chapter. Hardware and Software Requirements DCS interface hardware and DCS software are required.
Feature Descriptions 3-612Issue 3 March 1996 DCS Call Coverage Feature Availability This feature is available in G3V4. It is not available in a mixed system of G3V4 and pre-G3V4 systems. Description DCS Call Coverage provides the additional DCS messaging required to allow calls to be covered by coverage points on remote systems providing there is a DCS signaling link (BX.25 or ISDN PR I) for the trunk groups to which the c overed calls are routed. Thus, with DCS Call Coverage, calls to an extension on one system can be covered by extensions administered as coverage points on remote systems in a similar way to how Call Coverage functions within a single system. It provides transparency across systems for the Call Coverage feature. NOTE: DCS Call Coverage should not be confused with coverage to a remote AUDIX. DCS Call Coverage appears to the user to operate the same as Call Coverage with the following exceptions: nCoverage Answer Groups across nodes are not supported. nUnder some conditions, a call will follow the coverage point’s coverage path. See Operation Under Error Conditions on p age 3-618 for specific information. nDisplays will differ in some cases. See Disp lays on p age 3-619 for more details. nDCS Call Coverage does not support Coverage Call Back from a remote node. See “Feature Interactions” for more information. nUnder some conditions consult will not work properly. See Operation Under Error Conditions later in this description for more information. In releases prior to G3V4, transp arent call coverage to remote systems with normal call coverage functionality was limited to a single p oint of c overage on the remote system. Furthermore, that coverage point had to be an AUDIX, DEFINITY AUDIX, or Intuity. Note that you could cover to a remote point with the Call Coverage Off Premises feature, but this d oes not have the normal call coverage functionality.
DCS Call Coverage Issue 3 March 1996 3-613 Feature Applications Consider the following figure : Figure 3-4. Applications for DCS Call Coverage The following list describes some of the applications for DCS Call Coverage not otherwise possible without this feature: nA user sp ends time in multiple locations. An account executive, for example, might spend a lot of time at locations A and B. He or she might want calls to station B, for example, to be covered first by station A and the n b y A UDI X, DE FI NITY A UDI X, o r I ntuity. nA user moves from location A to location B. In this case, the user might want calls to station A to be covered first at station B then at AUDIX. nA secretary is located in different locations. A user at station B might want calls to first be covered by a secretary at station A and then by the AUDIX at location B. Previous Feature Operation The following figure illustrates the extent of call coverage over DCS tie trunks in pre G3V4 systems. Previous to G3V4 there was only one case when a call would cover to a point on a remote switch, with normal call coverage functionality, which was when covering to a remote AUDIX as described below. G3V4G3V4 Lo cation A L ocatio n B Station A Station BAUDIX D E FIN ITY AUDIX In tu ity
Feature Descriptions 3-614Issue 3 March 1996 . Figure 3-5. DCS AUDIX Coverage to Remote System Prior to G3V4 In this scenario, calls to extensions on system A can be c overed by the AUDIX on system B as follows: nA call comes into the station at extension 34567. After the administered number of rings, the call goes to coverage. nIf the coverage point is an AUDIX hunt group with rem-audix in the “Message Center” field and 44000 in the “AUDIX Extension” field on page 2 of the “Hunt Group” form, the AUDIX, if it is available, will cover this call with user A’s personal greeting. If the AUDIX is not available, no further coverage points will be attempted. If the trunk between the two systems is busy, the next coverage point, which must be on system A, will be tried. nThe connect message sent to AUDIX by System B g ets the principal’s extension (34567) from a DCS message sent on the DCS link between system A and system B. System A System B Tie trunk groups AU D I X X44000 G1 or G3 System PGATE or PI Board G1 or G3 System PGATE or PI BoardUser B X45678 X.25 or ISDN PRI DCS signaling link AUDIX link to system A viahop. Thislinkis required in G1 and G3iV1 but not in G3r or G3V2.hop AUDIX link to system BAUDIX Voice lines User A X34567 Previous to G3V4, calls to extension 34567 can be covered by the AUDIX on the remote system but not by any other type of coverage point on the remote system, such as the station at extension 45678.
DCS Call Coverage Issue 3 March 1996 3-615 nAfter AUDIX answers the covered call, it sends a message to system A via an AUDIX signaling link to system A lighting user A’s message lamp. nSince a physical link does not exist between the AUDIX and system A, the signaling link must hop from the system B-to-AUDIX BX.25 link to the system B-to-system A BX.25 link. In G1 and G3iV1, this link between AUDIX and system A must b e p resent for the call to b e covered. In G3rV1, G3V2, and G3V3 the call will be covered without this link present but the message lamp will not be u p dated. New Feature Operation The DCS Call Coverage feature for G3V4 a d ds the capability to cover to points other than AUDIX on a remote system. It d oes this by providing DCS messaging that provides transparency for the G3V4 Call Coverage feature. The following figure illustrates some of the possibilities associated with DCS Call Coverage . Figure 3-6. G3V4 DCS Call Coverage Syst em A Syst em B Ti e tr unk groups AUDI X X34000 G3V4 System PGATE or PI Boar d G3V4 System PGATE or PI Boar dUs er C X45678 User A X34567 User B X34568X.25 or I SDN PRI DCS signaling link hop AUDI X Voice lines User D X45679
Feature Descriptions 3-616Issue 3 March 1996 In this scenario using DCS Call Coverage, calls to user A can be covered first by user B, then by user C, and then finally by the AUDIX on system A. Alternatively, calls could be covered by user C, then user B, and so on. If the principal party answers after the call has gone to coverage and the coverage point has answered, the calling party, the principal, and the coverage point are conferenced together. In this same case, if the coverage point has not answered, the call to the coverage point is dropped and the calling party and principal are connected. Detailed Operation To illustrate how DCS Call Coverage works in more detail, consider the following scenario . Figure 3-7. Detailed Operation Scenario The following sections describe the DCS message flow for possibilities in this scenario. Operation under Normal Conditions. In a normal DCS Call Coverage scenario where the DCS link is up , a DCS trunk group is available, and DCS Call Coverage is activated on the local and remote systems, DCS Call Coverage works as follows: 1. A call comes into the principal. 2. The principal does not answer within the administered number of rings or has Send All Calls activated. G3V4G3V4 Local System Rem ote System Principal Coverage Point