Home > ATT > Communications System > ATT DEFINITY Communications System Generic 3 Instructions Manual

ATT DEFINITY Communications System Generic 3 Instructions Manual

    Download as PDF Print this page Share this page

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

    Page
    of 1584
    							DCS Call Coverage
    Issue  3   March 1996
    3-627
    The following list describes the interworking between DCS and ISDN PRI:
    nWhen an incoming call on a DCS trunk is routed to an outgoing ISDN 
    PRI-only trunk, the contents of the display information element in the ISDN 
    PR I  S ETUP   message, which contains the calling party name, are taken 
    from the contents of the DCS name message.
    nWhen an incoming c all on an ISDN PR I trunk is routed to an outgoing DCS 
    trunk over an ISDN PRI trunk, the DCS name message is suppressed in 
    G3V2 and later systems. The reason for this is that the DCS name 
    message in this case contains only the trunk g roup name, if administered, 
    of the incoming ISDN PRI trunk. Since DCS messages normally take 
    precedence, the more informative ISDN PRI display IE would not b e used. 
    Thus, the DCS name message is turned off, allowing the ISDN PRI disp lay 
    IE to be used.
    DCS Call Coverage does not work in a mixed system of G3V4 and pre-G3V4 
    systems. The reason for this is that a pre-G3V4 system will not tandem call 
    associated messages that they do not understand. Since the call coverage DCS 
    messages are new starting with G3V4, earlier systems cannot understand them. 
    The following figure illustrates this
    :
    Figure 3-14. Interworking
    G3V4G3V4
    System A System B
    Pre G3V4
    Trunk group AC
    Trunk group CB Trunk group AB
    System C Principal
    Cov. Point
    Calls to the principal routed to the coverage point over trunk
    group AB will work. Calls to the principal routed to the coverage
    point over trunk group AC and then tandemed to trunk group CB
    will not receive coverage because system C cannot tandem the
    new call coverage messages. 
    						
    							Feature Descriptions
    3-628Issue  3   March 1996 
    Hardware and Software Requirements
    The following software is required for DCS Call Coverage:
    nG3V4 or later system software
    nDCS software
    nUDP or PNA software
    nDCS Call Coverage must be enabled on all systems having principals or 
    coverage points and on all intervening systems.
    DCS Call Coverage does not require any ad d itional hardware beyond what is 
    required by DCS or call coverage. 
    						
    							DCS Call Forward ing All Calls
    Issue  3   March 1996
    3-629
    DCS Call Forwarding All Calls
    Feature Availability
    DCS is available with all Generic 3 releases except G3vs/G3s ABP.  
    Description
    Allows all calls to an extension numb er to be forwarded to a selected extension 
    number within the DCS network or to an external (off-premises) numb er. If the 
    Call Forwarding and DCS Call Forwarding All Calls features are both active, and 
    if a call is forwarded between extensions on the same node, the Call Forwarding 
    coverage path is used. If the nodes are different, the DCS Call Forwarding All 
    Calls coverage path is used.
    This feature is activated or deactivated by dial access code or by a Call 
    Forwarding button. The feature can be activated or deactivated only by voice 
    terminal users within the DCS.
    Activation and deactivation of the feature is the same as d esc rib e d for the Call 
    Forwarding All Calls feature, described earlier in this chapter.
    Considerations
    With DCS Call Forwarding All Calls, voice terminal users can have their calls 
    follow them to any location within the DCS network or outside the DCS network.
    Calls to an attendant cannot be forwarded. However, an attendant can activate 
    or deactivate the feature for other extension numbers within the DCS.
    Interactions
    If the forwarding extension and the designated extension are at different nodes, 
    and the designated extension’s coverage c riteria are met on a forwarded call, the 
    call is redirected to a point in the d esignated extension’s coverage path.
    If the forwarding extension and the designated extension are at different nodes, 
    LWC and Coverage Callback cannot be activate d at the d esignated extension 
    for a forwarded call.
    There is a 30-second interval during which calls forwarded from the DEFI NI TY 
    switch to another DCS node is denied. This prevents forwarded incoming trunk 
    calls from being forwarded ad infinitum between two extensions. 
    						
    							Feature Descriptions
    3-630Issue  3   March 1996 
    Administration
    The administration for DCS Call Forwarding All Calls is the same as that for the 
    Call Forwarding All Calls feature, which is fully described elsewhere in this 
    chapter.
    Hardware and Software Requirements
    DCS interface hardware and DCS software are required. 
    						
    							DCS Call Waiting
    Issue  3   March 1996
    3-631
    DCS Call Waiting
    Feature Availability
    DCS is available with all Generic 3 releases except G3vs/G3s ABP.  
    Description
    Allows calls from one node to busy single-line voice terminals at another node to 
    wait until the called party is available to accept the call.
    DCS Call Waiting includes the following features:
    nAttendant Call Waiting
    nCall Waiting — Termination
    nPriority Calling
    Attendant Call Waiting, Call Waiting Termination, and Priority Calling function the 
    same between the DEFINITY system Generic 1, Generic 3, or System 75  nodes 
    in a DCS as they do from a single DEFINITY system Generic 1, Generic 3, or 
    System 75. These features are detailed in Chapter 3, Feature Descriptions.
    Considerations
    With DCS Call Waiting, a single-line voice terminal user, by knowing a call is 
    waiting, can quickly process calls from locations within the DCS.
    Call Waiting — Origination can only be received if Generic 3i not activated.
    DCS priority calling from the attendant station is 
    not available.
    Interactions
    DCS Call Waiting is denied when the following features are activated at the 
    single-line voice terminal:
    nAutomatic Callback (to or from the voice terminal)
    nData Privacy
    nData Restriction
    On incoming trunk calls to the attendant extended over DCS trunks, Attendant 
    Call Waiting interacts with the EDCS  f eature. 
    						
    							Feature Descriptions
    3-632Issue  3   March 1996 
    Administration
    None required.
    Hardware and Software Requirements
    DCS interface hardware and DCS software are required. 
    						
    							DCS Distinctive Ringing
    Issue  3   March 1996
    3-633
    DCS Distinctive Ringing
    Feature Availability
    DCS is available with all Generic 3 releases except G3vs/G3s ABP.
    Description
    Activates the alerting, or ringing, device of a called terminal so that the user is 
    aware of the type of incoming call before answering it.  Distinctive Alerting 
    functions in a DCS environment as it does within a System:
    nFor  G3sV1 and G3iV1, internal calls are identified by a 1-burst ringing 
    pattern; external calls by a 2-burst ringing pattern; and priority calls by a 
    3-burst ringing pattern.
    nFor G3i-Global, G3rV1, G3V2, and later releases, these values are 
    administrable; the defaults are the same as those given above for  G3sV1 
    and G3iV1.
    A detailed description of the Distinctive Ringing feature is given earlier in this 
    chapter.
    Considerations
    DCS Distinctive Ringing allows the user to identify the type of incoming calls.  By 
    knowing the type of incoming call, the user can answer each call properly.
    When DCS transparency is lost for any reason, terminal-to-terminal calls made 
    between nodes produce external ringing instead of the usual internal ringing. 
    Loss of transparency may occur when the data link between nodes is down or 
    when data transmission d elay exceeds the trunk signaling time.
    Interactions
    The following features interact with the DCS Distinctive Ringing feature:
    nDistinctive Ringing
    Distinctive Ringing treats a c all from another switch in a DCS arrangement 
    as external; DCS Distinctive Ringing treats such calls as internal. If  both 
    features are administered, DCS Distinctive Ringing takes precedence. If 
    EDCS  i s a c tivated, DID treatment may be different.  See the Enhanced 
    DCS (EDCS) feature.
    nIntercom — Automatic
    This feature and its distinctive ringing are not provided between nodes in 
    a DCS. 
    						
    							Feature Descriptions
    3-634Issue  3   March 1996 
    nIntercom — Dial
    This feature and its distinctive ringing are not provided between nodes in 
    a DCS.
    nManual Signaling
    This feature and its distinctive ringing are not provided between nodes in 
    a DCS.
    nTie Trunk A ccess
    On a DEFINITY Generic 3 switch, tie trunk g roups can be administered as 
    either internal or external tie trunk groups. Calls from internal tie trunk 
    groups are treated as terminal-originated calls and receive one-burst 
    ringing. Calls from external tie trunk groups are treated as externally 
    originated calls and receive two-burst ringing.
    Administration
    None required.
    Hardware and Software Requirements
    DCS interface hardware and DCS software are required. 
    						
    							DCS Leave Word Calling
    Issue  3   March 1996
    3-635
    DCS Leave Word Calling
    Feature Availability
    DCS is available with all Generic 3 releases except G3vs/G3s ABP.  
    Description
    Enables terminal users to leave preprogrammed ‘‘call me’’ messages at other 
    terminals within the DCS network. Messages can be left by calling, called, or 
    covering users.
    LWC transparency in a DCS configuration allows messages from a DEFINITY 
    switch to another node, depending on the storage c a pability of the remote node.
    Considerations
    DCS LWC lets users within the DCS leave short, simple messages for other 
    users.
    LWC cannot be successfully activated toward any system that is not capable of 
    storing the messages, either internally or in an associated adjunct.
    Messages from one node, through an interme diate node, to a remote node do 
    not require storage capability at the interme diate node.
    LWC transparency is supported for all DCS configurations except for cases when 
    either the activating node or the remote node is either an ENHANCED 
    DIMENSION PBX or a System 85 R2V1.
    Retrieval of LWC messages is permitted only from a terminal at the node where 
    the messages are stored.
    DCS LWC cannot be activated from an attendant console. 
    						
    							Feature Descriptions
    3-636Issue  3   March 1996 
    Interactions
    The following features interact with the DCS LWC feature.
    nDCS Multi-appearance Conference/Transfer 
    Activation of LWC is denied after a DCS call has been conferenced or 
    transferred.
    nDCS Call Forward ing All Calls 
    If the forwarding extension and the designated extension are at different 
    nodes, LWC cannot be activated at the designated extension for a 
    forward ed call.
    Administration
    The administration for DCS LWC is the same as that for LWC (Leave Word 
    Callin g), which is fully described elsewhere in this chapter.
    Hardware and Software Requirements
    DCS interface hardware and DCS software are required. 
    						
    All ATT manuals Comments (0)

    Related Manuals for ATT DEFINITY Communications System Generic 3 Instructions Manual