ATT DEFINITY Communications System Generic 3 Instructions Manual

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...

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...

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...

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...

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,...

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,...

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...

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...