Home > Triad > Telephone > Starplus Triad Xts Installation Digital Key Telephone System Instructions Guide

Starplus Triad Xts Installation Digital Key Telephone System Instructions Guide

    Download as PDF Print this page Share this page

    Have a look at the manual Starplus Triad Xts Installation Digital Key Telephone System Instructions Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 9 Triad manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    Page
    of 626
    							Network InstallationC-7
    Appendix C - Networking Systems
    Extension Numbering
    Valid extension range numbering is between 1000 and 8999. Numbering conflicts must be
    avoided. For example, if stations 100, 200, and 300 exist, the numbers 1000, 2000, and 3000
    are conflicts. This is because the system detects the first three digits as validly assigned.
    Therefore, the system is not prepared to accept a fourth digit.
    Feature Code Numbering
    Feature codes must be unique numbers that pose no conflicts. Therefore, the feature code
    numbering plan cannot conflict with station numbering. For example, a station numbered
    4400 is a direct conflict to the default voice mail group“440”.
    Leading Digit
    Enabling the leading digit feature quickly changes station and feature codes by placing a
    digit in front of the current 3-digit codes. For example, several Nodes can have stations
    100-351. To make station numbers unique, the leading digit can be programmed as 1, 2, 3,
    etc. to result in station numbers of 1000-1351, 2000-2351, 3000-3351, etc. Feature codes will
    then also have a leading digit assigned. For example, feature code 700 will result in feature
    codes of 1700, 2700, 3700, etc.
    Network Installation
    Network Distance
    If KSUs are greater than 50 feet apart, connect them through TELCO using a point to point T-1
    (Refer toTa b l e 1and thenote onpage C-4). If each KSU is less than 50 feet apart and there is no
    TELCO connection, then connect them using a straight-through connection (refer toFigure C-
    2andTa b l e C - 3). Connections between Nodes and either a Hub or to TELCO always use the
    straight-through connection.
    The“#”key can not be a leading digit when networking systems together. Pound (#)
    is a reserved digit, for the termination of specialized features such as LCR.
    Table 1: TELCO to Hub Interconnect Diagram - Pin Connections
    TELCO Hub (NT)
    RJ45 DB15 Female Pin #
    1-->    
    						
    							C-8Network Installation
    Appendix C - Networking Systems
    Figure C-2: PRI Connector
    ISDN and T-1 Clocking
    When using PRIB or T-1 cards in one KSU, specific settings are important for proper clocking.
    Popping, crackling, dropped calls, and one-way transmission are usually attributed to the
    clocking not being synchronized correctly.
    It is preferable to use a TELCO PRI to establish clocking for the Network (Figure C-4). If no
    TELCO PRI or T-1 is available, then clocking will be controlled by the Hub system (all PRI clock
    switches enabled) for the entire Network (Figure C-5). The following examples are provided
    to illustrate proper clocking settings under given scenarios.
    Table 2: TELCO to Node Interconnect Diagram - Pin Connections
    TELCO Node (TE)
    RJ45 DB15 Female Pin #
    1-->          
    						
    							Network InstallationC-9
    Appendix C - Networking Systems
    The following figures use a symbol to represent the clock switch position on a PRI or T1
    card. When the top of the symbol is black, it represents the switch in the Up or Enable
    position. When the bottom of the symbol is black, it represents the switch in the Down or
    Disable position.
    Figure C-3: Point-to-Point PRIs
    Figure C-4: TELCO PRI Connection to the Hub
    External Clock Setting:Hub
    Node
    Up = Enable Clock
    Down = Disable Clock
    (Clock Source)
    Hub
    Node
    Node TELCO
    PRI
    (Clock Source)
    External Clock Setting:
    Up = Enable Clock
    Down = Disable ClockNote: The horizontal arrow
    represents Out-to-In Cabling. 
    						
    							C-10Network Installation
    Appendix C - Networking Systems
    Figure C-5: No TELCO Connection
    Figure C-6: TELCO PRI Connection To a Node
    Hub
    Node
    Node
    (Clock Source)
    External Clock Setting:
    Up = Enable Clock
    Down = Disable Clock
    Hub
    Node
    Node
    TELCO
    PRI
    (Clock Source)
    External Clock Setting:
    Up = Enable Clock
    Down = Disable ClockNote: The horizontal arrow
    represents Out-to-In Cabling. 
    						
    							Network InstallationC-11
    Appendix C - Networking Systems
    Figure C-7: All Systems have TELCO PRI Connection
    Figure C-8: All Systems have TELCO T1 Connection
    Hub
    Node
    Node
    TELCO
    PRI
    TELCO
    PRI TELCO
    PRI
    (Clock Source)
    External Clock Setting:
    Up = Enable Clock
    Down = Disable ClockNote: The horizontal arrow
    represents Out-to-In Cabling.
    Hub
    Node
    Node
    TELCO
    T1
    TELCO
    T1 TELCO
    T1
    (Clock Source)
    External Clock Setting:
    Up = Enable Clock
    Down = Disable ClockNote: The horizontal arrow
    represents Out-to-In Cabling. 
    						
    							C-12Network Installation
    Appendix C - Networking Systems
    Figure C-9: Two PRIs from TELCO to Nodes
    Figure C-10: Two T1s in Hub Connected to PRI in Nodes
    Hub
    Node
    Node
    TELCO
    PRI
    (Clock Source)
    External Clock Setting:
    Up = Enable Clock
    Down = Disable ClockNote: The horizontal arrow
    represents Out-to-In Cabling.
    Hub
    Node
    Node
    TELCO
    T1
    (Clock Source)
    External Clock Setting:
    Up = Enable Clock
    Down = Disable ClockNote: The horizontal arrow
    represents Out-to-In Cabling. 
    						
    							ProgrammingC-13
    Appendix C - Networking Systems
    Programming
    Programming must be done with a 24-button display telephone or with WinDBA. It is
    recommended that WinDBA be used for network programming. The following sections
    describe programming steps that pertain to networking. Each section assumes that you have
    already entered system programming. The following sections provide a detailed description
    of programming steps necessary for networking. A Quick Start procedure is provided at the
    end of this document as an aid to understanding the flow of programming.
    Node/Hub Identification Programming
    Description
    In networking, there must be a central Hub. All communication within the network must be
    linked via the Hub. The Hub should be identified as system 1. Each Node should be identified
    with its own unique number between 2 and 16. Networking requires 4-digit dialing.
    Complete the following programming steps to specify numbers that identify
    Hub/Nodes and to specify the leading digit to be used for dialing.
    Programming Steps
    1. PressFLASHand dial[09]. The following message displays:
    2. Press Button #8. The following message displays:
    3. Dial a valid number (01-16) to identify the system by number.
    4. PressHOLDtosavetheentry.
    5. Press Button #9. The following message displays:
    6. Dial a valid number (0-8) to identify the desired leading digit.
    SYSTEM PARAMETERS
    ENTERBUTTONNUMBER
    SYSTEM NODE 1-16
    01
    The Hub should be identified as system 1. Each Node should be identified with
    its own unique number between 2 and 16.
    LEADING DIGIT 0-8
    0 
    						
    							C-14Programming
    Appendix C - Networking Systems
    7. PressHOLDtosavetheentry.
    Networking Tables Programming
    Description
    The Networking Table is used to route calls between systems. It identifies the table number
    (01-16), the CO Group (00-23), the range of station numbers (from xxxx to xxxx), which card
    sends DSS/BLF information to an external location (programming for external BLF is only
    done on the Hub system), and whether the Status Check is enabled or disabled.
    The Table Number establishes the sequence that the system uses to search for a match to the
    number being called. The system searches based on table number 01 parameters. If no
    match is found, then the system searches based on table number 02 parameters. This process
    continues until a match is found and the call is placed, or no match is found and the caller
    receives an error tone.
    An automatic Status Check is designed to cope with unique network configurations that
    have a system’s extension range that overlaps another system’s extension range. Status
    Check screens a call to determine if the station number is assigned
    within the network. If the
    extension number is unassigned, the call is not forwarded to another system in the network
    and the caller receives an error tone.
    EXAMPLE OF THE ISSUE -- System A has station numbers 6005, 6006, 6007, 6024 and
    6048; System B has station numbers 6008, 6009, 6010, 6025, and 6049. Station number
    6022 is not assigned. In this example, both Systems have overlapping station ranges. A
    problem can occur when an incoming call for station number 6022 enters System A.
    System A checks to determine if this is an assigned number within System A. Since it is
    not an assigned number within System A, the call is forwarded to System B. System B
    completes the same process, then forwards the call back to System A, etc.
    Networking Tables For Nodes (refer toFigure C-11andFigure C-12)
    Table Number 01 of a Node’s networking tables should include:
    
    						
    							ProgrammingC-15
    Appendix C - Networking Systems
    The system will screen and process calls in the following sequence:
    If the call matches an extension specified in Flash 52 programming, the call will be
    connected within the same system.
    -or-
    If the call matches an extension associated with Table Number 02, the call will be routed
    to the appropriate remote device.
    -or-
    If the call matches an extension associated with Table Number 03, the caller will receive
    an error tone.
    Networking Tables For the Hub (refer toFigure C-11andFigure C-12)
    Table Number 01 of a Hub’s networking tables should include:
    
    						
    							C-16Programming
    Appendix C - Networking Systems
    Figure C-11: Two-Node Networking Table Example
    LEGEND:
    Table Number= the identification number assigned to each array within the system.
    CO Group= the line group used to access each system. Co Group 00 = internal calls only.
    Extn Range= the extension numbering range for the array.
    Ext BLF Slot= identifies PRIB slot locations in the Hub that are associated with each Node within the
    network, other than the Node being defined by the Table Number row. This allows DSS/BLF updates to be
    sent to the correct systems within the network. Node systems do not identify Ext BLF Slot locations because
    the Hub system controls passing of information.SYSTEM 2 SYSTEM 1 (HUB) SYSTEM 3
    Ext 1000–1999 Ext 2000–2999 Ext 3000–3999
    PRIB Slot 7 PRIB Slot 2
    CO Group 02 CO Group 02
    PRIB Slot 3 PRIB Slot 4
    CO Group 03 CO Group 02
    Actions notify System 1
    (e.g., on/off hook)Actions notify both
    System 2 and System 3Actions notify System 1
    Table Number
    CO Group
    Extn Range
    Ext BLF Slot
    Table Number
    CO Group
    Extn Range
    Ext BLF Slot
    Table Number
    CO Group
    Extn Range
    Ext BLF Slot
    01 00 1000 -
    1999--- 01 00 2000 -
    2999-- 01 00 3000 -
    3999---
    02 02 1000 -
    3999--- 02 02 1000 -
    19993 02 02 1000 -
    3999---
    03 00 1000 -
    8999--- 03 03 3000 -
    39992 03 00 1000 -
    8999---
    ….to
    ….--- 04 00 1000 -
    8999---….to
    ….
    ….to
    ….….to
    ….….to
    ….
    16….to
    ….--- 16….to
    ….16….to
    ….--- 
    						
    All Triad manuals Comments (0)

    Related Manuals for Starplus Triad Xts Installation Digital Key Telephone System Instructions Guide