Mitel Voice Processing Solutions Instructions Manual
Have a look at the manual Mitel Voice Processing Solutions Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 55 Mitel manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
Default Hardware Types ORIGINATE ACTIONS Action 1 Send string 2 Sleep 3 Flush device 4 Sleep 5 Send string 6 Send access code 7 Send string 8 Sleep 9 Read string 10 Send string 11 Flush device 12 Sleep Parameter teinet -t connected hangup Timeout 3 seconds 2 seconds 4 seconds 20 seconds 2 seconds ANSWER ACTIONS I I I I 1 Action Parameter Timeout 1 Set signal hi DTR 2 Sleep 3 seconds 3 Read string hangup 0 seconds DISCONNECT ACTIONS 1 4 1 Set signal hi 1 5 1 Set signal hi 1 RTS LINE DROP SIGNAL = CD A-8
Default Hardware Types RIGINATE ACT10 Action Parameter Timeout 1 Send string hello 2 Sleep 5 seconds ANSWER ACT10 Action Parameter Timeout 1 Flush device 2 Sleep 2 seconds 3 Read string hello 0 seconds ISCONNECT ACTIONS I I Action Parameter I Timeout 1 I I Set signal lo DTR 2 Sleep 20 seconds 1 3 1 Set signal hi 1 DTR 1 E DROP SIGNAL = CD A-9
Default Hardware Types ORIGINATE ACTIONS i- 2 3 4 5 6 7 8 9 10 11 12 13 Action Send string Sleep Send string Sleep Flush device Send string Send access code Send string Flush device Sleep Read string Flush device Sleep ANSWER ACTIONS Action Send string Sleep Send string Sleep Flush device Sleep Read string Parameter ATH ATSO=O ATDT CONNECT Parameter ATH ATSO=l CONNECT DISCONNECT ACTIONS Action Set signal lo Sleep Set signal hi Sleep Send string Sleep Send string Sleep Parameter DTR DTR ATH ATEO A-10 Timeout 5 seconds 5 seconds 10 seconds 60 seconds 5 seconds Timeout 5 seconds 3 seconds 3 seconds 0 seconds Timeout 5 seconds 5 seconds 5 seconds 3 seconds
Default Hardware Types urier ORIGINATE ACTIONS - - 1 2 3 f 5 6 7 8 9 10 11 12 13 - Action Send string Sleep Send string Sleep Flush device Send string Send access code Send string Flush device Sleep Read string Flush device Sleep Parameter ATH ATSO=O ATDT CONNECT Timeout 5 seconds j seconds 10 seconds 60 seconds 5 seconds Action Parameter Timeout 1 Send string ATH 2 Sleep 5 seconds DISCONNECT / Action Set signal lo Sleep Set signal hi Sleep Send string Sleep Send string Sleei3 Parameter DTR DTR ATH ATEO Timeout 5 seconds 5 seconds 5 seconds 3 seconds A-11
i Prior to the introduction of MESA-Net TCI?/IP, MESA-Net Async used Tellabs multiplexing equipment for sites that required high-performance, dedicated digital transmission facilities. Although MESA-Net TCP/IP now provides high- performance connections, the MESA-Net Async optional feature still contains the predefmed hardware types required to work with Tellabs equipment. This appendix contains reference information regarding MESA-Net Async and Tellabs equipment, specifically the Tellabs 340 Dataplexer and the 33 1 D Xplexer. ell exer ent You must configure the channel profiles for both Tellabs Dataplexers and Xplexers to work with MESA-Net. The correct settings are: l)Channel Mode 2)Channel Code 3)Flow Control 4)XON/XOFFChars S)ENQ/ACK Pacing 6)Modem Controls 7)Echoplex 8)Flush on Break 9)Control Privileges 1O)High Priority 11)Slow Packetizing 12)Infq Messages wopf S)Save Asynchronous 9600, 8 bits, 1 stop bit, No parity CTS/DTR Set 1: 11H / 13H Inactive DCE Local* None Inactive Inactive Inactive Inactive Active *This parameter is DIM/DOM for Dataplexer channels connected to modems. et The following pages show example MESA-Net Async networks that use Tellabs equipment, either with or without additional equipment, such as modems. B-l
Working with Tellabs Equipment Example 1: etwork using Tellabs ataplexer/Xplexers Figure B-l shows a MESA-Net Async network in which all nodes use Tellabs 330 Dataplexers and 33 1 Xplexers for communications. San Jose Node 1 New York Node 4 Composife Data Link 0 tonne Xplexer and Dafaplexer Originate link at channel 6 Answer link at channel 7 Denver Node 6 Composite Data Link 1 Dataplexer connects Xplexer and Dafaplexer Originate link at channel 6 Answer link at channel 7 T&labs 330 Dataplexer Composite Data Link 0 connects Xplexer and Dataplexer Originate link at channel 6 Answer link at channel 7 igure B- Sample Tellcabs This Tellabs setup uses the addressing protocol “node number/composite data link.qhannel.” For example, Chicago is node 2, composite data link 0 connects the Xplexer and Dataplexer, and the answer link is at channel 7; therefore the address is 2/0.7. The local node sends data to the answer link channel on the Dataplexer. The Xplexers perform node-to-node routing. The Network Node Table entries for San Jose are: B-2 2 4 Chicago New York 210.7 411.7 1 1 Y Y G Denver 611.7 1 Y
Working with Tellabs Equipment 1 he Network Node 1 able entrles for ChIcago are: Node Number: 1 Node Name: San Jose String: 110.7 Hardware type: 1 Access (Y/N): Y 4 New York 411.7 1 Y The Network Node Table entries for Denver are: Node Number: 1 2 Node Name: San Jose Chicago String: l/O.7 210.7 Hardware type: 1 1 Access (Y/N) : Y Y .,8,,/ 611.7 1 Y 4 New York 4/1.7 1 Y The Network Node Table entries for New York are: Node Number: 1 Node Name: San Jose String: l/O.7 Hardware type: 1 Access (Y/N) : Y i 2 Chicago 210.7 1 Y 6 Denver B-3
Working with Tellabs Equipment Example 2: Tellabs Datciplexer/Xplexers and Modems onnections ial-Up Figure B-2 shows a Tellabs 330 Dataplexer/331 Xplexers network and a node in Long Island that communicates with the network using dial-up lines that are routed through the New York node. All other node-to-node routing is performed by the Xplexers. San Jose NewYork Node 1 Tellabs 330 Tellabs 331 Tellabs 331 Xplexer Tellabs 330 Dataplexer Node 4 Composite Data Link 1 connects Xplexer and Dataplexer Originate link at channel 6 Answer link at channel 7 Modems connected at channel 2 and channel 3 Composite Data Link 0 connects Xplexer and Dataplexer Originate link at channel 6 Answer link at channel 7 Denver Composite Data Link 1 connects Xplexer and Dataplexer Originate link at channel 6 Answer link at channel 7 Answer - _ ._ _ (212) 858-4661 S111MNET -2 Sample Tel Hardware Type 4 is a combination sf the default hardware types for Tellabs and modems. This hardware type routes ‘all network calls to Long Island through Channel 2 of the New York node’s Dataplexer, then over the modem connection. Hardware Type 5 is also a combination of the default hardware types for Tellabs and modems. This hardware type routes all calls from Long Island over the modem connection to Channel 3 of the New York node’s Dataplexer, then through the New York Xplexer to all other nodes. The programming for Hardware Types 4 and 5 used in this example are shown later in this appendix. B-4
Working with Tellabs Equipment- The Network Node Table entries for San Jose are: Node Number: 3 4 Node Name: Long Island New York String: 8584661 411.7 Hardware type: 4 1 Access (Y/N): Y Y The Network Node Table entries for Denver are: 6 Denver 611.7 1 Y Node Number: Node Name: String: Hardware type: Access (Y/N) : 1 San Jose l/O.7 1 Y 3 Long Island 8584661 4 Y 4 New York 4J1.7 1 Y The Network Node Table entries for New York are: Node Number: 1 Node Name: San Jose String: 110.7 Hardware type: 1 Access (Y/N) : Y 3 Long Island 8584661 4 Y The detwork Node Table entries for I;_ong Island are: 6 Denver 611.7 1 Y Node Number: 1 4 6 Node Name: San Jose New York Denver String: 110.7 411.7 611.7 Hardware type: 5 5 5 Access (Y/N) : Y Y Y 0duCms Using icated The modems in Figure B-2 can also be connected by dedicated analog lines, rather than dial-up lines. With this arrangement, the connections between Long Island and New York modems are always “up.” Calls from Long Island to New York are routed from the originate link, through the modems, and through channel 3 of the B-5