Home > Triad > Telephone > Starplus Triad Xts Digital Key Telephone System System Programming And Operation Manual

Starplus Triad Xts Digital Key Telephone System System Programming And Operation Manual

    Download as PDF Print this page Share this page

    Have a look at the manual Starplus Triad Xts Digital Key Telephone System System Programming And Operation Manual 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 654
    							General DescriptionC-3
    Appendix C - Networking Systems
    General Description
    Networked telephone switches can be installed in one building or miles apart; however, each 
    call appears as though it is an intercom call. The use of ISDN, specifically Primary Rate 
    Interface (PRI), is used to create a star topology which has a “Hub” as a central point 
    connecting to as many as five “Node” switches. The Hub system is capable of interfacing one 
    centralized voice mail that can easily be accessed by each node system.
    When centralized voice mail is used, it is easy to integrate and allows each node system to 
    make an intercom-type call to access their voice mailboxes. For centralized voice mail, use 
    the Pathfinder system.
    Supported Features 
    Allows for partial PRIBs in clusters of four COs at a time
    4-digit dialing between all Nodes
    DSS/BLF
    Intercom-type calling between Nodes
    Call forwarding between Nodes
    Paging between Nodes
    Call transfer with caller ID passing between Nodes
    Centralized voice mail capability
    Directory dialing between Nodes
    Leading digit
    Direct access mailbox buttons per voice mail group
    Multiple mailboxes per key station/digital telephone
    Centralized LCR
    Centralized CO ring assignments
    DID routing between Nodes
    Capacities
    A Hub or an individual Node cannot have a voice mail of 24 ports or greater, or one that 
    handles 1000 calls per hour, because it will likely cause a bottleneck.
    Hardware
    The Networking interface requires the following boards:
    Primary Rate Interface Boards (PRIB)
    Channel Service Units (CSU), when KSUs are greater than 50 feet apart.
    Although a primary function of networking systems together is cost savings, it is 
    mandatory that each Node has local access to emergency 911 calling. 
    						
    							C-4General Description
    Appendix C - Networking Systems
    Standards
    ISDN
    Primary Rate Interface (PRI) Board 
    Vodavi has created a proprietary ISDN interface that ties two or more Vodavi telephone 
    systems together using PRI cards. The use of PRI cards allows Vodavi to convert the 24th 
    channel into a “D” channel. That channel passes the call processing information, while 
    leaving 23 channels for voice processing.
    This PRI must be running error-free prior to attempting any networking of systems.
    Each Node site requires a link to the Hub site using ”Star-type” topography (refer to
    Figure C-1: Network Configuration Diagram). The maximum number of connections possible in 
    the XTS is ten. A call will not hop more than twice (go through more than two switches) 
    before reaching its destination. If a centralized voice mail is in the configuration, it will be 
    installed at the Hub.
    Figure C-1: Network Configuration Diagram
    Terminal Emulation (TE) and Node Transmission (NT) are explained in Designing a Network.
    If KSUs are more than 50 feet apart or they are in different buildings, a CSU is required 
    at both ends. If KSUs are less than 50 feet apart and they are in the same building, 
    CSUs are not required.
    In a DSU/CSU, the 24th channel must be identified as a “D” (data) channel.
    TE
    Node
    Voice
    Mail
    NT
    Hub
    TE
    NodeTE
    Node
    TE
    Node
    TE
    Node 
    						
    							Designing a NetworkC-5
    Appendix C - Networking Systems
    Designing a Network 
    When more than one telephone switch is connected together, it is considered a network in 
    its simplest form. One system is considered the Main or Hub system (NT). The other is the 
    secondary or Node System (TE). There can only be one Hub (NT) and it cannot be attached 
    directly to another Hub (NT). Therefore, a Hub can only be connected to a node (TE). Similarly, 
    a node (TE) can only be connected to a Hub (NT) and it cannot be connected to another node 
    (TE). The key to managing a network is being able to maintain a clear flow of traffic and 
    making sure there is no bottleneck of calls at the Hub.
    Network Termination (NT )
    Generally, the Hub is the largest system and it has the most connections to the PSTN 
    interfaces. Because of this, it is more likely to be overloaded with calls and it needs to be 
    monitored closely to maintain free-flowing calls and information. A bottleneck will interfere 
    with voice quality.
    Terminal Equipment ( TE)
    A Node is generally a smaller less-active switch. However, it is just as important to monitor 
    each Node for processing speeds to eliminate calling problems. Because calls can make 
    multiple hops, it is important that all switches have an adequate number of interfaces to 
    eliminate bottlenecks.
    Connecting to Remote Devices
    A loop button is required to call between Nodes. If a station wants to establish a conference 
    between Nodes, it requires a second loop button. Therefore, it is recommended that each 
    station have at least two (2) loop buttons.
    Smart Trunks
    When a call is passed from one KSU to another KSU and back to the original KSU, the second 
    loop will drop after the call is answered. For example, a call is presented to System A, the 
    caller is transferred to System B, and then the call is forwarded back to System A. When the 
    call is answered in System A, the CO loop from System A to System B is dropped and the call is 
    only active in System A.
    The Numbering Plan
    Numbering must be carefully considered when planning a network. Each Node must have a 
    unique number to eliminate any conflicts. However, the entire network must have a basic 
    layout plan to eliminate duplicating extension numbering.
    The cornerstone to networking is the “Networking Tables”. The system compares every call 
    that comes from within the system with the internal numbering plan first (Flash 52 
    programming). Then the system checks the range of extensions in the first entry of the 
    networking table (Flash 16 programming). If a match is found, the call is made. 
    						
    							C-6Designing a Network
    Appendix C - Networking Systems
    If a match is not found, the system continues checking the next entry of the networking table 
    until a match is found or until it has examined each entry. If a match is not found within any 
    of the entries, an error tone sounds.
    Each Network has its own “line group”, which is its address. For example, Ta b l e C - 1   shows 
    that a call to extension 3500 will ring the switch that is connected in line group 2.
    The top portion (system configurations) and bottom portion (Networking tables) of
    Figu re C-11 are integrated to show how the networking table setup affects information 
    passing in a two-node system.
    Figu re C-12 is an example of a five-node system.
    Table C-1: Networking Tables - Example 1
    Table Number CO Group Station Range System Association Status Check
    FROM TO External
    01 00 1000 1999
    02 02 2000 2999
    03 03 3000 3999
    04 04 4000 4500
    05 05 4501 4599
    :
    :
    :
    16
    NOTE -- CO Group 00 = internal numbering plan
    Table C-2: Networking Tables - Example 2
    Table Number CO Group Station Range System Association Status Check
    FROM TO External
    01 00 1100 1199
    02 02 2100 2199
    03 03 3100 3352
    04 04 4100 4250
    :
    :
    :
    16
    NOTE -- CO Group 00 = internal numbering plan 
    						
    							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 to Ta b l e C - 3  and the note on page 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 to 
    Figu re C-2 and Ta b l e C - 5  ). 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 C-3: 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 C-4: 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.  
    						
    All Triad manuals Comments (0)

    Related Manuals for Starplus Triad Xts Digital Key Telephone System System Programming And Operation Manual