Abstract. Avaya Solution & Interoperability Test Lab

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for Configuring Avaya Communication Manager and Avaya Modular Messaging to Interoperate with BT ITS p31 Platform and ITS.Netrix - Issue 1.0 Abstract These Application Notes describe the steps required for interoperability between the BT ITS p31 Platform and ITS.Netrix with Avaya Communication Manager and centralized messaging provided by Avaya Modular Messaging. The BT ITS p31 Platform is a compact telephony switch specifically designed for smaller trading floors, supporting voice distribution and conferencing between the corporate network, PBX, turrets, and other voice systems. The BT ITS.Netrix is a desktop device for networkcentric voice, video, and data communications to empower users with instant access to the customer, the market, and applications to support the business. The configuration of Avaya Communication Manager T1/QSIG signaling groups, T1/QSIG trunk groups, call routing, the addition of subscribers to Avaya Modular Messaging, and basic verification of the ITS p31 platform is documented. Using this test configuration, basic interswitch calling features and centralized messaging can be verified. 1 of 26

2 1. Introduction These Application Notes describe the steps required for interoperability between the BT ITS p31 Platform and ITS.Netrix with Avaya Communication Manager and centralized messaging provided by Avaya Modular Messaging. The BT ITS p31 Platform is a compact telephony switch specifically designed for smaller trading floors, supporting voice distribution and conferencing between the corporate network, PBX, turrets, and other voice systems. The BT ITS.Netrix is a desktop device for network-centric voice, video, and data communications to empower users with instant access to the customer, the market, and applications to support the business. The configuration of Avaya Communication Manager T1/QSIG signaling groups, T1/QSIG trunk groups, call routing, the addition of subscribers to Avaya Modular Messaging, and basic verification of the ITS p31 platform is documented. Using this test configuration, basic interswitch calling features and centralized messaging can be verified. Figure 1 illustrates the network configuration used to verify interoperability between the sample Avaya configuration and the BT platform solution. The sample Avaya configuration consists of redundant Avaya S8710 Media Servers with an Avaya SCC1 Media Gateway. Avaya Communication Manager runs on the S8710 Media Servers. Avaya Modular Messaging will provide centralized messaging across both platforms. Avaya 4621 and 9630 IP Telephones will be used to place test calls. A T1-PRI QSIG trunk from the Avaya SCC1 Media Gateway connects the sample Avaya configuration to the BT solution. The BT solution consists of an ITS p31 cabinet, ITS Application Server, and two ITS.Netrix devices. The ITS.Netrix devices support both IP and TDM connections to the ITS p31 cabinet. Extension uses a TDM connection for communication, and extension uses an IP connection for communication. Figure 1: Network Configuration 2 of 26

3 The ITS Application Server is a PC consisting of the following software packages: ITSmonitor: Provides system monitoring and system level fault correction tools. ITSprofile: Provides an integrated ITS system configuration tool. ITSdiagnostics: Provides component monitoring and component level fault correction tools. 2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment & Software S8700 Media Servers with Avaya Communication Manager Avaya SCC1 Media Gateway IPSI (TN2312BP) C-LAN (TN799DP) MEDPRO (TN2302AP) Avaya Modular Messaging Avaya 4621 SW IP Telephone Avaya 9630 IP Telephone BT ITS p31 Platform ITS Application Server ITSmonitor Enterprise Edition ITSprofile ITSdiagnostics ITS.Netrix Application Software Bootcode Version CM 4.0 (R014x ) HW12 FW058 HW01 FW158 HW20 FW116 MM 3.1 (R ) R2.8 (H.323) R1.5 (H.323) N/A Windows 2000 Server (Service Pack 4) Table 1: Equipment List 3 of 26

4 3. Verify Customer Options in Avaya Communication Manager There are a number of steps that must be performed in Avaya Communication Manager to allow interoperability with the BT solution. All the commands discussed in this section are executed on Avaya Communication Manager using the System Access Terminal (SAT). This section and section 4 assumes that basic configuration of Avaya Communication Manager has been done already. For more information on Avaya Communication Manager system administration, refer to [1] in Section 9. This section specifies the optional features required for T1-PRI QSIG in Avaya Communication Manager. Step 1. Log into Avaya Communication Manager with the proper credentials, and enter the display system-parameters customer-options command. Go to Page 3 and verify ARS/AAR Partitioning is enabled. display system-parameters customer-options Page 3 of 11 OPTIONAL FEATURES Abbreviated Dialing Enhanced List? y Audible Message Waiting? y Access Security Gateway (ASG)? y Authorization Codes? y Analog Trunk Incoming Call ID? y CAS Branch? n A/D Grp/Sys List Dialing Start at 01? y CAS Main? n Answer Supervision by Call Classifier? y Change COR by FAC? n ARS? y Computer Telephony Adjunct Links? y ARS/AAR Partitioning? y Cvg Of Calls Redirected Off-net? y ARS/AAR Dialing without FAC? y DCS (Basic)? n ASAI Link Core Capabilities? y DCS Call Coverage? n ASAI Link Plus Capabilities? y DCS with Rerouting? n Async. Transfer Mode (ATM) PNC? n Async. Transfer Mode (ATM) Trunking? y Digital Loss Plan Modification? n ATM WAN Spare Processor? n DS1 MSP? n ATMS? y DS1 Echo Cancellation? y Attendant Vectoring? y (NOTE: You must logoff & login to effect the permission changes.) 4 of 26

5 2. On Page 4, verify that ISDN-PRI is enabled. display system-parameters customer-options Page 4 of 11 OPTIONAL FEATURES Emergency Access to Attendant? y Enable 'dadmin' Login? y Enhanced Conferencing? y Enhanced EC500? y Enterprise Survivable Server? n Enterprise Wide Licensing? n ESS Administration? y Extended Cvg/Fwd Admin? y External Device Alarm Admin? n Five Port Networks Max Per MCC? n Flexible Billing? n Forced Entry of Account Codes? n Global Call Classification? n Hospitality (Basic)? y Hospitality (G3V3 Enhancements)? n IP Trunks? Y IP Stations? y ISDN Feature Plus? y ISDN Network Call Redirection? y ISDN-BRI Trunks? y ISDN-PRI? y Local Survivable Processor? n Malicious Call Trace? y Media Encryption Over IP? Y Mode Code for Centralized Voice Mail? n Multifrequency Signaling? y Multimedia Call Handling (Basic)? y Multimedia Call Handling (Enhanced)? y IP Attendant Consoles? y (NOTE: You must logoff & login to effect the permission changes.) 3. On Page 5, verify that Uniform Dialing Plan and Private Networking are enabled. display system-parameters customer-options Page 5 of 11 OPTIONAL FEATURES Multinational Locations? n Multiple Level Precedence & Preemption? n Multiple Locations? Y Personal Station Access (PSA)? y Posted Messages? n PNC Duplication? n Port Network Support? y Processor and System MSP? n Private Networking? y Processor Ethernet? y Remote Office? y Restrict Call Forward Off Net? y Secondary Data Module? y Station and Trunk MSP? n Station as Virtual Extension? n System Management Data Transfer? n Tenant Partitioning? n Terminal Trans. Init. (TTI)? y Time of Day Routing? y Uniform Dialing Plan? y Usage Allocation Enhancements? y TN2501 VAL Maximum Capacity? y Wideband Switching? y Wireless? y (NOTE: You must logoff & login to effect the permission changes.) 5 of 26

6 4. On Page 8, verify that Basic Call Setup and Basic Supplementary Services are enabled. display system-parameters customer-options Page 8 of 11 OPTIONAL FEATURES Basic Call Setup? y Basic Supplementary Services? y Centralized Attendant? y Interworking with DCS? n Supplementary Services with Rerouting? y Transfer into QSIG Voice Mail? y Value-Added (VALU)? y (NOTE: You must logoff & login to effect the permission changes.) 6 of 26

7 4. Configure Avaya Communication Manager This section represents the configuration steps for adding the T1/QSIG interface, signaling group, trunk group and call routing options to allow interoperability between the sample Avaya configuration with the BT solution. Step 1. Add the DS1 circuit pack. Enter add ds1 1a11 where 1a11 represents the cabinet/carrier/slot/ of the DS1 circuit pack in the Avaya SCC1 Media Gateway. In this sample configuration, Avaya Communication Manager was configured with an Interface of peer-master and the BT p31 platform was configured with an Interface of peer-slave (not shown). Set the Side option to a to match the peer-master setting. The b8zs and d4 settings for Line Coding and Framing Mode are required by the BT p31 platform T1-PRI card. The pbx option for Connect is used since the BT p31 platform is a peer switch. Signaling Mode of isdn-pri and Peer Protocol of Q-SIG are selected to enable the T1-PRI QSIG features on the trunk. A descriptive name of TO BT was entered as the Name. Default values are used in the remaining fields. add ds1 1a11 Page 1 of 1 DS1 CIRCUIT PACK Location: 01A11 Name: TO BT Bit Rate: Line Coding: b8zs Line Compensation: 1 Framing Mode: d4 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 T303 Timer(sec): 4 Slip Detection? n Near-end CSU Type: other Echo Cancellation? n 7 of 26

8 2. Add a signaling group. Enter add signaling-group X where X is an available signaling group number. In this sample configuration, signaling group 20 was used. Set the Group Type to isdn-pri. Set the Primary D-Channel to port 24 (shown as 01A1124) of the DS1 circuit pack created in Step 1. Set TSC Supplementary Service Protocol to b to enable QSIG supplementary services on this signaling group. Once the trunk group is created (see Step 3), come back here and set Trunk Group for Channel Selection to 20. Default values are used in the remaining fields. add signaling-group 20 Page 1 of 1 SIGNALING GROUP Group Number: 20 Group Type: isdn-pri Associated Signaling? y Max number of NCA TSC: 0 Primary D-Channel: 01A1124 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 20 X-Mobility/Wireless Type: NONE TSC Supplementary Service Protocol: b Network Call Transfer? y 3. Create a trunk group that connects to the BT ITS p31 platform. Enter add trunk-group X where X is an available trunk group number. In this sample configuration, trunk group 20 was used. On Page 1, set Group Type to isdn to specify an ISDN trunk. Set the TAC to an available trunk access code. In this sample configuration, a TAC of 120 was used. Set the Service Type to tie as this is a general purpose trunk. A descriptive name of TO BT was used as the Group Name. Default values are used in the remaining fields. add trunk-group 20 Page 1 of 21 TRUNK GROUP Group Number: 20 Group Type: isdn CDR Reports: y Group Name: TO BT COR: 1 TN: 1 TAC: 120 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 8 of 26

9 4. On Page 2, set Supplementary Services Protocol to b which enables QSIG features. Default values are used in the remaining fields on this page. add trunk-group 20 Page 2 of 21 Group Type: isdn TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Max Message Size to Send: 260 Charge Advice: none Supplementary Service Protocol: b Digit Handling (in/out): enbloc/enbloc Trunk Hunt: cyclical Digital Loss Group: 13 Incoming Calling Number - Delete: Insert: Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 Administer Timers? n 5. On Page 3, enable Send Name, Send Calling Number, and Send Connected Number options so that name and number information will be displayed on ITS.Netrix devices. Default values are used in the remaining fields on this page. add trunk-group 20 Page 3 of 21 TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support? n Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: Send Name: y Send Calling Number: y Used for DCS? n Hop Dgt? n Send EMU Visitor CPN? n Suppress # Outpulsing? n Format: public Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider 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 Hold/Unhold Notifications? n Modify Tandem Calling Number? n Ds1 Echo Cancellation? n Apply Local Ringback? n Show ANSWERED BY on Display? y Network (Japan) Needs Connect Before Disconnect? n 9 of 26

10 6. On Page 5, assign bearer channels to the trunk group. For this sample configuration, only six channels will be used to carry call traffic between Avaya Communication Manager and the BT solution. For each circuit, enter the Port and Sig Grp associated with this trunk. For this sample configuration, signaling group 20, created back in Step 2, will be used. add trunk-group 20 Page 5 of 21 TRUNK GROUP Administered Members (min/max): 1/6 GROUP MEMBER ASSIGNMENTS Total Administered Members: 6 Port Code Sfx Name Night Sig Grp 1: 01A1101 TN464 H 20 2: 01A1102 TN464 H 20 3: 01A1103 TN464 H 20 4: 01A1104 TN464 H 20 5: 01A1105 TN464 H 20 6: 01A1106 TN464 H Enter display dialplan analysis. Verify dialed strings are configured for a 5-digit dial plan. Local Avaya Communication Manager extensions begin with 3 and ITS.Netrix devices begin with 2 and are routed using automatic alternate routing (AAR). display dialplan analysis Page 1 of 12 DIAL PLAN ANALYSIS TABLE Percent Full: 1 Dialed Total Call Dialed Total Call Dialed Total Call String Length Type String Length Type String Length Type 2 5 aar 3 5 ext 8. Enter change aar analysis 2. In this sample configuration, 5 digit dial strings beginning with the number 2 will be routed using Route Pattern 20, which will contain the T1/QSIG trunk to the BT solution as defined in step 9 below. change aar analysis 2 Page 1 of 2 AAR DIGIT ANALYSIS TABLE Percent Full: 1 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd aar n 10 of 26

11 9. Enter change route-pattern 20. In the route pattern screen, specify the T1/QSIG trunk group that connects to the BT solution, by setting Grp No to 20. Trunk 20 was created back in Steps 3,4,5 and 6. A descriptive name of TO BT was used as the Pattern Name. Default values are used in the remaining fields on this page. change route-pattern 20 Page 1 of 3 Pattern Number: 20 Pattern Name: TO BT SCCAN? n Secure SIP? n Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC No Mrk Lmt List Del Digits QSIG Dgts Intw 1: 20 0 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 PARM No. Numbering LAR M 4 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 10. Enter change public-unknown-numbering to allow Avaya Communication Manager to send the calling party number along with the call information across a particular trunk group. For this sample configuration, set the Total CPN Len to 5 for any call that traverses trunk group 20 for any 5 digit extension that starts with the number 3. change public-unknown-numbering 2 Page 1 of 2 NUMBERING - PUBLIC/UNKNOWN FORMAT Total Ext Ext Trk CPN CPN Len Code Grp(s) Prefix Len Total Administered: Maximum Entries: of 26

12 5. Add ITS.Netrix Devices as Avaya Modular Messaging Subscribers This section represents the administrative steps for adding an account on the Avaya Message Storage Server (MSS) for the ITS.Netrix devices. It is assumed that Avaya Modular Messaging has been installed and configured, along with proper Avaya licensing. For more information on Avaya Modular Messaging system administration, refer to [2] in Section 9. Step 1. Open a web browser and enter the URL to access the login screen for the Avaya MSS. In this sample configuration, the Avaya MSS is located at Enter an authorized administrator account in Username. Press the Login button (not shown), then enter the appropriate Password. Click Login. This action will display the Messaging Administration screen shown in Step of 26

13 2. From the Messaging Administration page, select Messaging Administration Subscriber Management from the left hand navigation pane. This action will display the Manage Subscribers screen as shown in Step of 26

14 3. From the Manage Subscribers page, select the Manage button for Local Subscribers. This action will display the Manage Local Subscribers screen as shown in Step of 26

15 4. From the Manage Local Subscribers screen, click on the Add a New Subscriber button to add a new subscriber to Avaya Modular Messaging. This action will display the Add Local Subscriber screen as shown in Step of 26

16 5. From the Add Local Subscriber screen enter the following required information: Last Name: Last name of the subscriber. First Name: First name of the subscriber. Password: Default password for the subscriber. Mailbox Number: A 2-10 digit number. The mail box number length is defined during system installation. For this sample configuration, a 7-digit mailbox number is used. Numeric Address: Unique internal Avaya MSS number, which is usually the same value as the Mailbox Number. PBX Extension: Actual PBX extension of the ITS.Netrix device. Class of Service: Used for subscriber access of controls. The default value of 0 was used here. Community ID: Used to control message sending and receiving among groups of subscribers. The default value of 1 was used here. Default values are used in the remaining fields on this page. Scroll down and press the Save button when complete (not shown). Repeat these steps to create another Avaya Modular Messaging subscriber account for the ITS.Netrix device located at extension of 26

17 6. Configure BT ITS p31 Platform and ITS.Netrix Devices BT provides on-site custom installation and configuration of the ITS p31 Platform and ITS.Netrix devices. Nothing additional, other than providing the T1 QSIG trunk and call routing features in Avaya Communication Manager, and creating subscriber account on the Avaya MSS is needed. However, for purposes of this Application Note, it s important to verify the following on the ITS Application Server: Status of the T1/QSIG trunk Proper configuration of the Avaya Modular Messaging pilot number Step 1. From the ITS Application server desktop, select Start Programs ITSdiagnostics ITSdiagnostics. This action will display the ITSdiagnostics window. Drill down to ITSdiagnostics Avaya ITSADMIN COM1, and double click on COM1. COM1 represents the communications port on the PC used to communicate with the ITS p31 platform. This action will display a logon screen for COM1 access as shown in Step of 26

18 2. From the Log On screen, enter a proper Username and Password for access to COM1. Click the OK button when complete. This action will load the Diagnostic Screen View window as displayed in Step In this configuration, the Diagnostic Screen View window is configured to display the full diagnostic path of the BT platform (\Avaya\ITSADMIN\COM1). Press the PF2 button on the Button menu (below the Menu bar) to access the diagnostic menu as shown in Step of 26

19 4. From the diagnostic menu, enter P from the keyboard for Physical layer. This action will display the Physical Layer Status screen as shown in Step of 26

20 5. From the Physical Layer Status window, verify that both the Signal and Synch fields have a State of YES. This indicates that the trunk is in-service. 20 of 26

21 6. From the ITS Application server desktop, select Start Programs British Telecom ITSprofile. This action will display a Connect to SQL Server window. Select Use Windows Authentication and press the OK button. This action will launch the ITSprofile window as seen in Step of 26

22 7. From the ITSprofile window, expand the Avaya menu and select Utilities System Configuration. This action will launch the System Configuration window as seen in step of 26

23 8. In the General tab, verify that a voice mail system has been configured using the correct Avaya Modular Messaging pilot number. For this sample configuration, a pilot number of was used. 23 of 26

24 7. Verification Steps These verification steps can be performed to verify interoperability between the sample Avaya configuration and the BT solution. Step 1. Verify that the Avaya T1 trunk group is in-service using the status trunk 20 command from the Avaya Communication Manager SAT terminal. status trunk 20 Page 1 TRUNK GROUP STATUS Member Port Service State Mtce Connected Ports Busy 0020/001 01A1101 in-service/idle no 0020/002 01A1102 in-service/idle no 0020/003 01A1103 in-service/idle no 0020/004 01A1104 in-service/idle no 0020/005 01A1105 in-service/idle no 0020/006 01A1106 in-service/idle no 2. Place and answer a test call from a station on Avaya Communication Manager to a ITS.Netrix device. Verify talk path in both directions and that the ITS.Netrix device displays the caller number and caller name. 3. Initiate a 3-way test conference with two Avaya stations and an ITS.Netrix device. Verify all parties can join the conference with two way talk path in all directions. 4. Place and answer test call from an ITS.Netrix device to an Avaya station. Verify talk path in both directions and that the Avaya station displays the caller number and caller name. 5. Place a test call from a station on Avaya Communication Manager to a ITS.Netrix device. Do not answer the call on the ITS.Netrix device and allow the call to go to coverage. Verify that the call is covered to Avaya Modular Messaging. Leave a message for the ITS.Netrix device. 6. Verify that the message waiting light (MWI) on the ITS.Netrix device is lit. From the ITS.Netrix device, dial into Avaya Modular Messaging to retrieve the message. 7. Verify that the message can be heard, and that the MWI light is extinguished on the ITS.Netrix device once the message is retrieved. 8. Place a test call from an ITS.Netrix device to an Avaya station. Do not answer the call on the Avaya station and allow the call to go to coverage. Verify that the call is covered to Avaya Modular Messaging. Leave a message for the Avaya station. 9. Verify that the message waiting light (MWI) on the Avaya station is lit. From the Ayava station, dial into Avaya Modular Messaging to retrieve the message. 10. Verify that the message can be heard, and that the MWI light is extinguished on the Avaya station once the message is retrieved. 24 of 26

25 8. Conclusion These Application Notes describe the steps required for interoperability between the BT ITS p31 Platform and ITS.Netrix with Avaya Communication Manager and Avaya Modular Messaging. Using this configuration, basic inter-switch calling and centralized messaging can be verified. 9. Additional References The following Avaya product documentation can be found at [1] Administrator Guide for Avaya Communication Manager, Issue 3.1, February [2] Avaya Modular Messaging Release 3.1 Messaging Application Server Administration Guide for Avaya Modular Messaging with the Avaya MAS and MSS, February The following BT product documentation can be found at [3] BT ITS Platform p31 including ITS Platform p41, Issue 1.2, April [4] ITS.Netrix User Guide, draft B.1, March of 26

26 2007 Avaya Inc. All Rights Reserved. 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 and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at 26 of 26