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
    							Dial Access to Attendant
    Issue  3   March 1996
    3-647
    Dial Access to Attendant
    Feature Availability
    This feature is available with all Generic 3 releases.
    Description
    Allows voice terminal users to access an attendant by dialing an attendant 
    access code. Attendants can then extend the call to a trunk or to another voice 
    terminal.
    In  G3vsV1/G3sV1 and G3iV1, the access code is always the single digit 0. For 
    G3i-Global, G3rV1, G3V2, and later releases, this code is a dministrable and may 
    be any one or two d i git numb er; the default is 0.
    Considerations
    With Dial Access to Attendant, voice terminal users can access the attendant 
    whenever attendant aid is needed by dialing the attendant access code.
    A voice terminal user calling the attendant b y dial access cannot be added to an 
    existing conference by the attendant.
    Interactions
    Restriction — Origination (administered to a voice terminal by the COR) prohibits 
    placing any calls, including Dial Access to Attendant calls.
    For  G3v1/G3sV1 and G3iV1 only, the attendant group dial c o de must be zero 
    and cannot b e administered to another value. (This dial code can be 
    administered for G3i-global, G3rV1, G3V2, and later releases.)
    Administration
    The administrator may select an extension numb er other than zero for this 
    feature. However, in the United States 0 has traditionally been use d for operator 
    assistance in both the p ublic network and in PBXs, Also, consideration should be 
    given to the fact that prior to the emergence of 911 systems, the dialing of 0 was 
    customary in the United States for emergencies and other urgent assistance 
    requests. Using an extension numb er other than 0 for dial access to the 
    attendant could create confusion and delay resp onse to an emergency.  
    						
    							Feature Descriptions
    3-648Issue  3   March 1996 
    Hardware and Software Requirements
    No a d ditional hardware or software is required. 
    						
    							Dial Plan
    Issue  3   March 1996
    3-649
    Dial Plan
    Feature Availability
    This feature is available with all Generic 3 releases.
    Description
    The Dial Plan is the system’s guide to digit translation. When  a  digit  is  dialed,  the 
    system must know what to expect, based on that d i git. For exam ple, if a voice 
    terminal user dials a 4, the system must know how many more digits to exp ect 
    before the call is processed.
    There are a number of enhancements and changes for G3i-Global, G3rV1, G3V2, 
    and later releases. There are two digit tables giving more flexibility in the d ial 
    plan. The numb er of extensions is greatly increased and, for G3rV1, G3V2, and 
    later releases, there is the introduction of Extension Number Portability. The 
    number of trunk access c odes increased significantly as well as other capacities. 
    See the System Capacity Limits table in  for more details.
    The Dial Plan, or first-digit (and in G3rV1, G3i-Global, G3V2, and later releases, 
    the second-digit) table, established during administration for each system, 
    provides information to the switch on what to d o with dialed digits. The tables 
    define the intended use of a code beginning with a specific first digit (and or first 
    two digits for G3i-Global, G3rV1, G3i-Global, G3V2, and later releases) and 
    relates to the system how many digits to collect before processing the code. The 
    choices of a first d igit are 0 through 9, *, and #. Permissible code uses and the 
    allowable numb er of digits are listed below.
    nExtension Numbers
    Flexible numbering allows  one, two, three, four, or five-digit extension 
    numbers. The first digit in the extension number tells the system how many 
    d i gits to exp ect the extension number to have.
    Extension numbers can have a first digit of 1 (0 for G3rV1, G3i-Global, 
    G3V2, and later releases) through 9. For example, if a three-digit extension 
    number is administered and the first digit is a 4, the extension numb ers 
    can range from 400 to 499. Also, if a four-digit number with a 6 as the first 
    d i git is a dministered, the extension numbers can range from 6000 to 6999.  
    If multiple extension numb er lengths begin with the same digit, G3i-Global 
    uses a timer to identify when all the d igits have been entered.
    nAttendant
    Dial access to the attendant group may b e  achieved by dialing the single 
    d i git ‘‘0.’’ It is also possible to set the dial plan so that some other digit is 
    used to reach the attendant (for examp le, 9 in Italy). For G3rV1, 
    G3i-Global, G3V2, and later releases, access can range from 0 to 9 with a  
    						
    							Feature Descriptions
    3-650Issue  3   March 1996 
    length of one or more digits. In a d dition, Generic 3 provides for Individual 
    Attendant Access by assigning each attendant an individual extension 
    number.
    nTrunk Ac cess Codes
    A minimum of one digit and a maximum of three (G3iV1) d igits or four 
    (G3i-Global and G3rV1, G3V2, and  later releases) can be used. Trunk 
    access codes can have a first digit of 1 (0 for G3rV1, G3i-Global, and 
    G3V2) through 9. For example, 9 could be used for local trunks, 8 for 
    WATS trunks, and 7 for tie trunks. For G3r and G3i-Global, * and # can be 
    the first digit for TACs. TACs may be a maximum of 4 digit. TACs for DCS 
    trunk groups and trunk groups controlled by DCS can be a maximum of 3 
    d i gits (or 4 if no DCS).
    nFeature A c cess Codes
    A minimum of one digit and a maximum of three digits can be used. The * 
    and # buttons can be used as part of a feature a c cess c o de and, when 
    used, must b e the first  digit.  The * or # counts as one d igit. For example, * 
    2 could be used to activate Call Forwarding All Calls and # 2 used to 
    deactivate Call Forwarding All Calls.
    Feature access codes can also have a first digit of 1 through 9.  For 
    example,  3 2 could be used to activate Call Forwarding All Calls and 3 3 
    used to deactivate Call Forwarding All Calls.
    nPrefixed Extensions
    The dial plan does not route on the first digit prefix (0 through 9) but routes 
    on the rest of the d igits.
    nMisc ellaneous Code
    Used to indicate that any dialed digit string starting with the first digit uses 
    the second digit table for interpretation. For G3i-Global, G3V2, and later 
    releases only, the length of this code can only be one. It can have a 
    feature access code, trunk access code, attendant access code, and 
    extensions on the second digit table.
    For G3rV1, G3V2, and later releases, UDP has its own forms in administration. 
    This information is given in the UDP and ENP Tables.
    A UDP may also be established during administration as p art of the Dial Plan. 
    This plan provides a common extension number plan that can be shared among 
    a group of switches. If a UDP is to be established, all extension numbers (in the 
    UDP numbering plan) must b e the same length (four or five d i gits b ut not both). 
    So that calls route to the d esired switch, a UDP requires the following information:
    nA PBX Code, which represents the first 1 to 4 digits (five d i gits for G3rV1, 
    G3V2, and later releases) of a 4- or 5-digit extension number and can 
    range from 1 to 9999 with a maximum of 240 PBX Codes.
    nWhether or not the PBX Code is local to this system — this information is 
    required for each PBX Code for G3vsV1/G3sV1, G3iV1, and G3i-Global. 
    						
    							Dial Plan
    Issue  3   March 1996
    3-651
    nAn RNX, which is associated with the PBX code and is used to select an 
    AAR pattern for the call — this information is required for each PBX code. 
    With G3i, the RNX is flexible (no fixed form). (With G3rV1, G3V2,a n d later 
    releases, an ENP can also be used to route UDP calls.)
    nA PBX ID (1 to 63), which represents a specific switch — this information is 
    required for G3V1 (exc ept G3rV1) for each PBX Code when the switch is 
    located within a DCS. For G3rV1, G3V2, and later releases, the PBX ID is 
    administered in the Node Number column of the ‘‘AAR Analysis”  form.’
    nA Local PBX ID, which represents the PBX ID of the local switch.
    Considerations
    The entire Dial Plan is d ependent on the first and second digit dialed. The 12 
    possible choices of a first d i git are 0 through 9, *, and #.
    Interactions
    nAll dial access features and services provided by the system require the 
    Dial Plan.
    nWhen an ISDN/BRI station dials sufficient digits to route a call, b ut could 
    route differently if a dditional digits were dialed, the station will not 
    recognize the Conference or Transfer buttons. The user must delay dialing 
    for three se conds or dial a # to indicate the call can be routed based on 
    the digits already dialed. The Conference or Transfer b uttons are then 
    recognized and the operation is completed by the switch.
    nFlexible numbering is supported in countries using R2-MFC  trunk 
    signaling without Group II tones. Different length extension numb ers can 
    exist as long as the extensions have different first digits. Contact your 
    AT&T representative for more information.
    Administration
    The Dial Plan is administered on a per-system basis by the System Manager.  
    The following items require administration:
    nArea code where the system is located (in North America only)
    nWhether or not the serving central office requires the digit 1 to indicate a 
    long-distance call (in North America only)
    nWhether or not a UDP is to be esta blished 
    nThe type of code and the number of digits in the code for each first digit
    nO ptionally, a second digit table 
    						
    							Feature Descriptions
    3-652Issue  3   March 1996 
    If a UDP is to be established on G3i (G3r contains ad d itional features as 
    described in  Uniform Dial Plan feature and is a dministered on a different form), 
    the following items can be administered:
    nNumber of digits in plan (4 or 5)
    nPBX Codes
    nWhether or not each PBX Code is local to the PBX being administered
    nRNX (Per PBX Code)
    nPBX ID (Per PBX Code)
    Hardware and Software Requirements
    No a d ditional hardware or software is required. 
    						
    							Digital Multiplexed Interface
    Issue  3   March 1996
    3-653
    Digital Multiplexed Interface
    Feature Availability
    This feature is available with all Generic 3 releases.
    Description
    Supports two signaling techniques:  Bit Oriented Signaling and Message 
    Oriented Signaling for direct connection to host computers.
    Message Oriente d Signaling is used with ISDN-PRI.
    The DMI provides twenty-three 64 k b ps d ata c hannels, p lus one 64 k b ps channel 
    for Common Channel Signaling. Within the data channel, DMI provides control 
    information exchange and data formats supporting data transport at all standard  
    data rates; each data channel can be used in one of the following transfer 
    modes:
    nMode 0 — 64 kb ps Channel
    nMode 1 — 56 kb ps Channel
    nMode 2 — 0-19.2 kb ps Synchronous/Asynchronous
    nMode 3 — Multiple Virtual Channels
    ISDN-PRI can be assigned as the signaling mode. In this case, for G3i only, the 
    TN767 DS1 or TN464C/D DS1 circuit pack and the TN765 Processor Interface 
    circuit p ack must be used. For G3r, the TN464B/C/D circuit pack is required. The 
    ISDN-PRI is a 1.544 Mb ps digital interface that consists of a 1.536 Mb ps signal 
    multiplexed with an 8 kbps framing channel. The 1.536 M bps signal is divided 
    into 24 channels of 64 kbps each (23 ‘‘B’’ voice or data channels and 1 ‘‘D’’ 
    signaling channel). The  D  channel  multiplexes  signaling messages for the 23 
    B-c hannels.
    NOTE:
    The TN767 and the TN464C and later revisions of the DS1 circ uit packs 
    provide a DSX1 interface.
    DMI trunks are accessed the same as tie trunks. The  only difference is that DMI 
    trunks are connected to host computers while tie trunks are c onnected to another 
    switch. Each trunk functions like a PDM since the DMI protocol is identical to the 
    DCP format used by the data modules. 
    						
    							Feature Descriptions
    3-654Issue  3   March 1996 
    Considerations
    System DMI support offers high-volume (high-speed, high-capacity) data 
    transmission, via DS1 digital facilities, between host computers and analog or 
    digital data endpoints.
    DMI is widely supported. To date, more than 100 data processing suppliers, 
    communications equipment suppliers, and device manufacturers have licensed 
    DMI sp ecifications and have obtained the rights to implement DMI in their 
    products.
    DMI trunks with ISDN-PRI signaling can be connected to a host computer, 
    another PBX, or a p u blic or private network.
    Interactions
    The following features interact with the Digital Multiplexed Interface feature.
    nData Restriction
    DMI trunks cannot be data restricted.
    nModem Poolin g
    Data calls dialed from a local analog data endpoint to a DMI trunk must 
    contain the Data Origination Access Code to obtain a conversion 
    resource. Data calls on DMI trunks to local analog data endpoints will 
    automatically obtain conversion resources, if available.
    Administration
    DMI sup port is assigned on a per-system basis by the System Manager. The 
    following items require administration.
    nDS1 Circuit Pack — Assign the circuit pack to the system b efore 
    administration of the associated trunks.
    nProcessor Interface Circ uit or Packet Control p ack (for G3i) — If ISDN-PRI 
    Signaling is used, a TN765 Processor Interface circ uit pack or TN778 
    Packet Control must be assigned to work in tandem with the TN767 DS1 
    circuit pack or TN464C/D.
    NOTE:
    The TN767 and the TN464C and later revisions of the DS1 circ uit packs 
    provide a DSX1 interface.
    nDMI Trunk Group — Associate the trunks to the groups. 
    						
    							Digital Multiplexed Interface
    Issue  3   March 1996
    3-655
    Hardware and Software Requirements
    One TN722B, TN767, or TN464  is required for every 23 DMI trunks. The TN464 is 
    needed for G3r. If ISDN-PRI signaling is used, a TN765 Processor Interface or 
    TN778 Packet Control is required for G3i.
    No a d ditional software is required. 
    						
    							Feature Descriptions
    3-656Issue  3   March 1996 
    Direct Department Calling (DDC) and
    Uniform Call Distribution (UCD)
    Feature Availability
    This feature is available with all Generic 3 releases.
    Description
    Allows direct inward access to an answering group other than the attendant even 
    if the system d oes not have the DID feature.
    This feature was called ‘‘Enhanced Uniform Call Distribution’’ in G2.
    A DDC or UCD answering group can consist of voice terminals and individual 
    attendants (desc ribed in the Individual Attendant Access feature elsewhere in 
    this document). In addition, a UCD group can consist of data modules, data line 
    circuit ports, or modems.
    One extension number is assigned to all voice terminals, individual attendants, 
    data modules, data line circuit ports, or modems in a group or department, that 
    is, to a set that serves the same function and requires call distribution among the 
    members of the group. Incoming calls to a DDC group or UCD group can be 
    internal or external.
    The hunting algorithm used by the system to select an idle terminal or console is 
    the only difference between DDC and UCD.
    With DDC, an incoming call rings the first available voice terminal or individual 
    attendant in the administered sequence.  If the first group member in the 
    sequence is active on a call (busy), or has had his or her calls temporarily 
    redirected (via Send All Calls, Call Forwarding All Calls, or the Hunt Group Busy 
    Function discussed later), the call routes to the next group member, and so on. In 
    other words, incoming calls always try to complete at the first group member in 
    the administered sequence.  Therefore, the calls are not evenly distributed 
    among the DDC group members.
    With UCD, an incoming call rings the member of the group that has not received 
    a UCD group call for the longest period of time (the most idle member).  In other 
    words, incoming calls to a UCD group extension number are distributed evenly 
    among the group members.
    When DDC or UCD is not p rovid e d, incoming LDN calls, international exchange 
    calls, 800 service calls, and automatic tie trunk calls are normally directed to an 
    attendant who must extend the call.  When DDC or UCD is provided on a trunk 
    group, incoming calls are automatically directed to the d esired DDC group by 
    the switch. Attendant intervention is not required. 
    						
    All ATT manuals Comments (0)

    Related Manuals for ATT DEFINITY Communications System Generic 3 Instructions Manual