A Configuration of Avaya Communication Manager and a 3COM NBX 100 PBX using QSIG PRI Networking - Issue 1.0

Transcription

1 Avaya Solution & Interoperability Test Lab A Configuration of Avaya Communication Manager and a 3COM NBX 100 PBX using QSIG PRI Networking - Issue 1.0 Abstract These Application Notes describe the steps to follow to replicate a tested configuration of QSIG PRI Trunk networking between Avaya Communication Manager and a 3COM NBX 100 PBX. In the configuration, Avaya Communication Manager was running on an S8300 Media Server controlling a G350 Media Gateway. 1 of 18

2 1. Introduction These Application Notes describe the steps needed to replicate the configuration of a QSIG/PRI Trunk between an Avaya Communication Manager S8300/G350 and a 3Com NBX 100 PBX, as shown in Figure 1. This configuration supports basic calling, including calling party number display / 24 Avaya S8300/G350 T1 Cross over Cable QSIG/PRI / 24 3COM NBX Avaya P133 Workgroup Switch Avaya P133 Workgroup Switch Management PC.116 Analog Telephone x112 Avaya Analog Telephone x30001 Avaya 4620 IP Telephone x31001 PC w/browser for Administration 3COM Business Telephone x111 3COM Business Telephone x104 Figure 1: Tested Configuration More advanced QSIG features, such as Calling Party Name, are not supported. Calls can be transferred and conferenced from either end, but note that calls that are allowed to transfer back from one system to the other will use a second T1 channel. 2 of 18

3 2. Equipment and Software Validated The following hardware and software were validated: Equipment Software Avaya S8300 Media Server with G350 Media Gateway Avaya 4612 IP Telephone 2.0 Avaya 4620SW IP Telephone 2.0 Avaya 6408D Digital Telephone N/A 3COM NBX 100 R4_1_77 3COM Business Telephone N/A Communication Manager (R012x ) 3. Configure the Avaya Communication Manager This section provides instructions for setting up the QSIG interface to the 3COM NBX 100, assuming the user has terminal emulation access to the S8300/G350. Also assumed is that the S8300/G350 is configured with the appropriate licenses. Step 1 ) From the SAT command line type add or change ds1 001v4, where 001v4 is the slot where the T1 Media Module resides. The command list configuration all displays what modules are in the system. Set Line Coding to b8zs, Signaling Mode to isdn-pri, Connect to PBX and Interface to peer-master. Set Peer Protocol to Q-SIG and Side to a. Thus, the S8300/G350 is configured as the QSIG protocol master and, in a later 3COM configuration step, the 3COM will be configured as the QSIG protocol slave. change ds1 001v4 Page 1 of 2 DS1 CIRCUIT PACK Location: 001V4 Name: IP Office Bit Rate: Line Coding: b8zs Line Compensation: 1 Framing Mode: esf Signaling Mode: isdn-pri Connect: pbx Interface: peer-master TN-C7 Long Timers? n Peer Protocol: Q-SIG Interworking Message: PROGress Side: a Interface Companding: mulaw CRC? n Idle Code: DCP/Analog Bearer Capability: 3.1kHz Slip Detection? n Near-end CSU Type: other Figure 2: DS1 Form Click Submit. 3 of 18

4 Step 2 ) This step is the initial trunk group form configuration. Step 2 a) Type add or change trunk-group 6 and set the Group Type to isdn, assign a unique Trunk Access Code (TAC) according to the dialplan, set the Service Type to tie and the Trunk Hunt to ascend. change trunk-group 6 Page 1 of 22 TRUNK GROUP Group Number: 6 Group Type: isdn CDR Reports: n Group Name: 3com-nbx COR: 1 TN: 1 TAC: 106 Direction: two-way Outgoing Display? y Carrier Medium: PRI/BRI Dial Access? n Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: tie Auth Code? n TestCall ITC: rest Far End Test Line No: TestCall BCC: 4 TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Max Message Size to Send: 260 Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc Trunk Hunt: ascend QSIG Value-Added? n Digital Loss Group: 13 Calling Number - Delete: Insert: Numbering Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? y Answer Supervision Timeout: 0 Figure 3: Trunk-group Form Page 1 Step 2 b) Click Next Page. Set Send Calling Number to y, and Numbering Format to unk-pvt. These settings instruct the switch to mark the 5 digit calling party number sent from Avaya Communication Manager as an unknown type of number in a private numbering plan. Click Submit to submit the form and return to the command line. change trunk-group 6 Page 2 of 22 TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support? n Internal Alert? y Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: 1 Send Name: y Send Calling Number: y Used for DCS? n Suppress # Outpulsing? n Numbering Format: unk-pvt Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider Network Call Redirection: none Send UUI IE? y Send UCID? n Send Codeset 6/7 LAI IE? y Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: y Ds1 Echo Cancellation? n US NI Delayed Calling Name Update? n SBS? n Network (Japan) Needs Connect Before Disconnect? n Figure 4: Trunk Group form - Page 2 4 of 18

5 Step 3 ) Type add or change signaling-group 6. Set the Primary D-Channel to 001V424 and the Trunk Group for Channel Selection to 6. Click Submit to submit the form and return to the command line. change signaling-group 6 Page 1 of 5 SIGNALING GROUP Group Number: 6 Group Type: isdn-pri Associated Signaling? y Max number of NCA TSC: 0 Primary D-Channel: 001V424 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 6 Supplementary Service Protocol: a Network Call Transfer? n Figure 5: Signaling Group Form Step 4 ) Type change trunk-group 6. Enter each channel on the T1 media module to be used and the associated signaling group, 6. Make the entries in ascending order. Page to the next page to complete the entries if necessary and click Submit. change trunk-group 6 Page 6 of 22 TRUNK GROUP Administered Members (min/max): 1/23 GROUP MEMBER ASSIGNMENTS Total Administered Members: 23 Port Code Sfx Name Night Sig Grp 1: 001V401 MM : 001V402 MM : 001V403 MM : 001V404 MM : 001V405 MM : 001V406 MM : 001V407 MM : 001V408 MM : 001V409 MM : 001V410 MM : 001V411 MM : 001V412 MM : 001V413 MM : 001V414 MM : 001V415 MM710 6 Figure 6: Trunk Group Form Step 5 ) For this example configuration, a 5 digit uniform dialplan was used, although the 3COM NBX was configured for 3 digit dialing. In Avaya Communication Manager, users dial 66xxx to reach 3COM extensions, where the 66 is deleted before sending the call, as follows: 5 of 18

6 Step 5 a) Type change uniform-dialplan 6 and add the entry shown to convert all dialed calls of the format 66xxx to 7 digit numbers of the format 666-6xxx and send them to Automatic Alternate Routing (AAR) for processing. change uniform-dialplan 6 Page 1 of 2 UNIFORM DIAL PLAN TABLE Percent Full: 0 Matching Insert Node Matching Insert Node Pattern Len Del Digits Net Conv Num Pattern Len Del Digits Net Conv Num aar n n aar n n aar n n Figure 7: Uniform Dial Plan Table Step 5 b) Type change aar analysis 6 and create an entry as shown to direct AAR calls of the format 666-xxxx to Route Pattern 6. change aar analysis 6 Page 1 of 2 AAR DIGIT ANALYSIS TABLE Percent Full: 3 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd aar n aar n Figure 8: AAR Digit Analysis Table Step 5 c) Type change route-pattern 6. Create the entry shown to direct the call to trunk group 6 and delete the first four digits to send only the last 3 digits to the 3COM system. change route-pattern 6 Page 1 of 3 Pattern Number: 6 Pattern Name: 3comnbx Secure SIP? n Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC No Mrk Lmt List Del Digits QSIG Dgts Intw 1: n user 2: n user 3: n user 4: n user 5: n user 6: n user BCC VALUE TSC CA-TSC ITC BCIE Service/Feature BAND No. Numbering LAR W Request Dgts Format Subaddress 1: y y y y y n n rest none 2: y y y y y n n rest none 3: y y y y y n n rest none 4: y y y y y n n rest none 5: y y y y y n n rest none 6: y y y y y n n rest none Figure 9: Route-pattern Form 6 of 18

7 4. Configure the 3COM NBX 100 These notes assume the user has a properly configured browser and network connection to the 3COM NBX. It is best to follow 3COM s documentation for installing 3COM s products. For reference, the 3COM NBX Administrator s Guide is listed in Section 7 of these Application Notes. The steps below show how this example was configured. Step 1 ) Open a browser to the management address of the 3COM NBX and log in as the administrator. Click the Tab To It icon from where most of the steps are referenced. Figure 10: Tab To It 7 of 18

8 Step 2 ) Click Device Configuration Digital Line Cards. Set the Device Type to T1/ISDN Board List and Click Apply. Figure 11: Digital Line Cards 8 of 18

9 Step 3 ) Click Modify and ensure that the Card Type is ISDN PRI and that the Online box is checked. Click Apply. Click OK. Figure 12: Modify Board 9 of 18

10 Step 4 ) Click Device Configuration Digital Line Cards. Set Select Device Type to ISDN PRI Span List. Click Apply. Click the Span of interest and Click Modify. Click QSIG slave as the CO Switch Protocol. Set the Framing Type to ESF, the Line code to B8ZS. Line Length should be set to the wiring distance to the next T1 device. In this case, 0-35 Meters is appropriate. The Timing Mode is set to Internal so that the NBX provides the clocking in this configuration. Check the On Line box. In general, Timing Mode must be set consistently with an overall clock synchronization plan. Click Apply. Click OK. Figure 13: Modify Span 10 of 18

11 Step 5 ) This step has two parts for configuring the trunk group. Step 5 a) Click Device Configuration Digital Line Cards. Set Select Device Type to T1 Group List. Click Apply. Click Group 1. Click Modify. Check the Online box. The Trunk-to- Trunk setting generally can be left as restricted, unless tandem trunking is allowed as in this configuration. Click Apply. Click OK. Figure 14: Modify Group 11 of 18

12 Step 5 b) Click Device Configuration Digital Line Cards. Set Select Device Type to ISDN PRI Group List. Click Apply. Click PRI Group 1. Click Membership. Ensure that the ports of the PRI that are to be used are moved from the non-member list to the member list. Click Close. Figure 15: Group Membership 12 of 18

13 Step 6 ) Click Dialplan Extension Lists. Click the entry for T1 Channels. Click Modify. Ensure that the channels to be used for outbound calls are in the list. Note that by default this configuration will hunt outgoing from channel 23. The hunt order can be changed, but then the Avaya Communication Manager trunk form must be changed to ensure that Avaya Communication Manager hunts in the opposite order. Figure 16: Extension List 13 of 18

14 Step 7 ) Click Dialplan Tables. Click the Internal 3 digit Extensions table. Click the Devices Using button. Ensure that all the PRI channels in this trunk group are listed in the Devices Using table. Click Close. Figure 17: Tables Step 8 ) Click Dialplan Operations. Follow 3Com instructions to modify your dialplan to route calls to the PRI trunk. The table below shows the relevant parts of the dialplan that was used in this configuration, with comments. Dial Plan ///////////////////////////////////////////////////////////////////////////////// / Settings ///////////////////////////////////////////////////////////////////////////////// ExtensionLength 3 ExtensionRange Telephone ExtensionRange Park ExtensionRange AutoAttendant ExtensionRange HuntGroup ExtensionRange External ///////////////////////////////////////////////////////////////////////////////// / The ExtensionRange External Setting MUST include the Park range. / If the Call Park range is outside of the ExtensionRange External, / the Call Park feature will not work. ///////////////////////////////////////////////////////////////////////////////// ExternalSettings ///////////////////////////////////////////////////////////////////////////////// / Dial Plan Tables ///////////////////////////////////////////////////////////////////////////////// Table Create 1 Internal 3 Digit Extensions / Id Entry Digits Min Max Class Prio Route 14 of 18

15 / TableEntry Create Internal 0 4 TableEntry Create Internal 0 0 TableEntry Create Internal 0 2 TableEntry Create Internal 0 2 TableEntry Create Internal 0 3 TableEntry Create Diagnostics 0 0 TableEntry Create Internal 0 5 TableEntry If Create a caller dials 1 5 digits 9 *9 beginning with 9 3, use 9 Local route 2 as defined below. 0 1 TableEntry Create Operator 0 1 TableEntry Create International 0 1 TableEntry Create LongDistance 0 1 TableEntry Create AlternateLong 0 1 TableEntry Create Emergency 0 2 TableEntry Create TollFree 0 1 TableEntry Create TollFree 0 1 TableEntry Create TollFree 0 1 TableEntry Create Toll 0 1 TableEntry Create Toll 0 1 TableEntry Create Emergency 0 1 TableEntry Create Operator 0 1 TableEntry Create * 4 4 COCode 0 1 TableEntry Create Internal 0 2 TableEntry Create 1 37 V WAN 0 9 Table Create 2 Incoming DID and Auto Attendant / Id Entry Digits Min Max Class Prio Route / TableEntry Create Internal 0 4 TableEntry Create Internal 0 0 TableEntry Create Internal 0 0 TableEntry Create Internal 0 3 Table Create 3 Least Cost Routing ///////////////////////////////////////////////////////////////////////////////// / Routes ///////////////////////////////////////////////////////////////////////////////// / Route Description / DestinationRoute Create 1 LocalCO DestinationRoute Create 2 LocalCONoStrip DestinationRoute Create 3 Voice Application DestinationRoute Create 4 Attendant DestinationRoute Create 5 H323 ConneXtions Ports DestinationRoute Create 8 8 Pool DestinationRoute Create 9 VPIM to IP Office / Route Entry DestinationExtension / DestinationRouteEntry Create 1 1 *0001 DestinationRouteEntry Create 1 2 *0002 DestinationRouteEntry Create 2 1 *0002 DestinationRouteEntry Create 3 1 *0003 DestinationRouteEntry Create 4 1 *0004 DestinationRouteEntry Create 5 1 *0005 DestinationRouteEntry Create DestinationRouteEntry Create 9 1 *0003 Route 2, entry 1 sends all calls to the *0002 extension list. That list was administered to contain the outgoing PRI channels. 15 of 18

16 5. Verification Steps I. Is the T1 and framing operational? Carrier Failure can be caused by improper cabling (e.g., using a straight cable or an Ethernet Cross-over cable when a T1 cross-over is required) or misadministration. Framing errors indicate that the signal is getting through, but the reporting end cannot find the expected framing sequence reliably. This is usually caused by misadministration (e.g., D4 framing vs. ESF) but can also be caused by poor signaling quality. A. 3COM NBX side 1. Check the Equipment LEDs 2. Check the LEDs on the 3COM T1 card. CF Carrier Fail RA Remote Alarm LB Card is in Loopback Mode. Nominal The T1 Line is framed. (In other words, good.) 3. This status can also be seen through the Device Configuration Digital Line Cards tab by selecting the T1 Span List and selecting Apply. B. Avaya Communication Manager Side 1. Check the DS1 module lights to ensure that the SIG light is green, the Act light is amber, and the alarm light is out. No signaling is likely a cabling error. Signal, but alarm is likely to be a framing setting issue. 2. The monitor jacks near the T1 interface can be used, if necessary, to check the signal level and, with the proper sniffer, ISDN PRI Q.931 signaling. 3. The command line status signaling-group 6 and status trunk-group 6 can be used to check that the signaling group and trunk group are in service and, what if any channels are in use. II. Is the call routing/dial plan properly taking calls to/from the T1 line? A. 3COM Side. 1. In the 3Com NBX, Click Dial Plan Operations and Click the Test button. 2. Click a Device to Dial From (e.g., an extension on the NBX) 3. Enter a Number to Dial (e.g., an IP Office extension). 4. Click Test. 5. Verify that the Results screen shows that the Trunk chosen and the Digits to outpulse match what Avaya Communication Manager is configured to expect. B. Avaya Communication Manager side. 16 of 18

17 1. From the command line, type list trace tac 106 where 106 is the trunk access code in this configuration. 2. Dial an outgoing or incoming call to see what called party number digits are being passed and to see the calling party number. 6. Conclusion Following these steps will result in a successful implementation of ISDN PRI trunk operation between an Avaya Communication Manager S8300 Media Server with G350 Media Gateway and 3COM NBX References Avaya product information and similar Application Notes can be found at NBX Administration instructions were found in: - January 2003, NBX Administrator s Guide, Release 4.1, 3COM 17 of 18

18 Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at 18 of 18