NI2 Meridian

JRR; Reviewed: SPOC 12/19/2008

Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.

1 of 31 NI2-Meridian

Avaya Solution & Interoperability Test Lab

Sample Configuration of Avaya Communication Manager Networked with Nortel Meridian using ISDN-PRI and NI-2 Issue 1.0

Abstract

These Application Notes illustrate a sample configuration of Nortel Meridian networked with Avaya Communication Manager using an ISDN-PRI trunk configured for NI-2. Such a configuration may be used when the Nortel Meridian is not QSIG-capable. These Application Notes are a companion document to previously published Application Notes describing an ISDN-PRI trunk with QSIG configuration. The sample configuration includes an Avaya S8300C Server running Avaya Communication Manager 5.1.1 in an Avaya G450 Media Gateway, and a Nortel Option 11c Mini running Nortel Meridian Release 25.40b. The verification of these Application Notes includes extension dialing among Avaya and Nortel telephones, and calling party name and number display and restriction. It is expected that the results in these Application Notes are applicable to Avaya Communication Manager systems using other Avaya Server and Media Gateway platforms, and also to other Nortel hardware platforms using Nortel Meridian software.




1. Introduction These Application Notes illustrate a sample configuration of Nortel Meridian networked with Avaya Communication Manager using an ISDN-PRI trunk configured for NI-2. This configuration may be used when the Nortel Meridian is not QSIG-capable. These Application Notes are a companion document to previously published Application Notes describing an ISDN-PRI trunk with QSIG configuration. QSIG is a commonly used protocol for signaling between private branch exchanges (PBXs). If the Nortel Meridian is QSIG-capable, it will generally be preferable to follow the Application Notes previously documented in Reference [QSIG]. Compared to an NI-2 configuration, QSIG offers benefits such as superior display features, trunk efficiency via Diversion by Reroute and Path Replacement, and voice messaging transparency with message waiting updates, as shown in reference [QSIG]. The sample configuration includes an Avaya S8300C Server running Avaya Communication Manager 5.1.1 in an Avaya G450 Media Gateway, and a Nortel Option 11c Mini running Nortel Meridian Release 25.40b. It is expected that the results in these Application Notes are applicable to Avaya Communication Manager systems using other Avaya Server and Media Gateway platforms, and also to other Nortel hardware platforms using Nortel Meridian software. Figure 1 illustrates the most relevant aspects of the sample configuration. The four telephones for which names are shown in Figure 1 are used in the verification of sample call flows in Section 6.

Figure 1: Sample Network: Avaya Communication Manager Using Avaya S8300C Server/G450 Media Gateway Networked with Nortel Meridian Option 11C Mini




The Avaya S8300C Server with G450 Media Gateway platform was used for the testing because it can be an attractive choice for customers interested in moving forward with state of the art Avaya applications for communities of users, while still retaining a user population on the Nortel Meridian that needs to communicate with the Avaya users. The Avaya S8300C Server with G450 Media Gateway can support a mix of analog, digital, H.323 IP, and SIP telephones and trunks, together with integrated voice mail (IA770), meet-me conferencing, contact center, and mobility features, making it a powerful and economical alternative to further investments in legacy equipment. A five digit Uniform Dial Plan (UDP) is used to facilitate extension dialing from the Avaya telephones to the Nortel telephones. Similarly, the Nortel telephones use the Coordinated Dial Plan (CDP) feature to dial by extension to reach the Avaya users. Unique extension ranges are associated with Avaya Communication Manager (24xxx) extensions, and Nortel Meridian (45xxx) extensions. This five digit extension arrangement is simply an example; other extension lengths and extension ranges may be used. Reference [IPE] documents an alternative for ISDN-PRI configuration between Avaya Communication Manager and Nortel Meridian (i.e., not NI-2 on the Nortel Meridian). Reference [IPE] also contains additional information on cabling.

2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided:

Equipment Software Avaya S8300C Server running Avaya Communication Manager, IA770 INTUITY AUDIX, SIP Enablement Services (SES)

Release 5.1.1 (415.1) with Service Pack 1 (16402)

Avaya G450 Media Gateway MM710 T1 Media Module (necessary for the

ISDN-PRI to the Nortel Meridian) MM712 Digital Media Module (if Avaya digital

telephones are desired) MM711 Analog Media Module (if analog

phones, trunks, devices such as fax are desired)

G450 Version 28.18.0 MM710BP HW11 FW044 MM712AP HW07 FW009 MM711AP HW33 FW088

Avaya 9600-Series Telephones (H.323) (optional) Release 2.0 H.323 Avaya 9600-Series Telephones (SIP) (optional) Release 2.0.4 SIP Avaya 2400-Series Digital Telephones (optional) N/A Nortel Option 11 C Mini

MSC MTDK97AD CPU NTRB21AC DTI/PRI TMDI Card

Meridian Version 25.40b with patches identified in Section 4.

Nortel m3904 Digital Telephone N/A




3. Configure Avaya Communication Manager for ISDN-PRI Connectivity to Nortel Meridian

This section focuses on configuring the trunks on Avaya Communication Manager to reach Nortel Meridian, and provides sample routing using Uniform Dial Plan (UDP) and Automatic Alternate Routing (AAR). All configuration is illustrated via System Access Terminal (SAT) screens. Avaya Integrated Management tools such as Avaya Site Administration could also have been used. A license file controls availability of Avaya Communication Manager features. The available features can be viewed using the command display system-parameters customer-options. For the Avaya Communication Manager system used in the verification of these Application Notes, the following customer options are among those that are enabled:

ISDN-PRI Private Networking Uniform Dialing Plan

3.1. Administer DS1 Circuit Pack Administer a DS1 circuit pack to be used for connectivity to Nortel Meridian. Use the add ds1 1v4 command, where 1v4 is the slot in the G450 Media Gateway containing the MM710 Media Module. Note that the actual slot number may vary. In the sample configuration, the following values were used for the specified fields, and the default values were retained for the remaining fields. The configuration of the DS1 interface must be coordinated with the corresponding configuration parameters on the Nortel Meridian.

Name: A descriptive name. Line Coding: b8zs Framing Mode: esf Signaling Mode: isdn-pri Connect: pbx Interface: user Country Protocol: 1 Protocol Version: b

The setting of the Interface field must be complementary to the configuration on the Nortel Meridian. For the sample configuration, Avaya Communication Manager is administered as the user side, and Nortel Meridian is administered as the network side.




add ds1 1v4 Page 1 of 2 DS1 CIRCUIT PACK Location: 001V4 Name: To-Meridian Bit Rate: 1.544 Line Coding: b8zs Line Compensation: 1 Framing Mode: esf Signaling Mode: isdn-pri Connect: pbx Interface: user TN-C7 Long Timers? n Country Protocol: 1 Interworking Message: PROGress Protocol Version: b Interface Companding: mulaw CRC? n Idle Code: 11111111 DCP/Analog Bearer Capability: 3.1kHz T303 Timer(sec): 4 Slip Detection? n Near-end CSU Type: other Echo Cancellation? n Block Progress Indicator? n

3.2. Administer Trunk Group Administer an ISDN trunk group to interface with Nortel Meridian. Use the add trunk-group n command, where n is an available trunk group number. Enter the following values for the specified fields, and retain the default values for the remaining fields. Group Type: isdn Group Name: A descriptive name TAC: An available trunk access code Direction: two-way Carrier Medium: PRI/BRI Service Type: tie

add trunk-group 30 Page 1 of 21 TRUNK GROUP Group Number: 30 Group Type: isdn CDR Reports: y Group Name: To-Meridian COR: 1 TN: 1 TAC: 130 Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI Dial Access? n Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: tie Auth Code? n TestCall ITC: rest Navigate to Page 2. For the Supplementary Service Protocol field, enter a. Leave the Format field blank, unless there is a need to convert the numbering format received from Nortel on this trunk group. In the sample configuration, there is no need. Default values may be retained for the remaining fields. If desired, the Trunk Hunt field may be changed from the cyclical default. In the sample configuration, Nortel Meridian used a descending trunk selection order for calls from Nortel users to Avaya users, and Avaya Communication Manager used an ascending order for calls from Avaya users to Nortel users, to minimize the opportunities for glare conditions.




add trunk-group 30 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: a Digit Handling (in/out): enbloc/enbloc Trunk Hunt: ascend 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 CONNECT Reliable When Call Leaves ISDN? n Navigate to Page 3. Enable the Send Name and Send Calling Number fields. In the sample configuration, the Format field was set to public to construct the calling party number using the public unknown numbering table. An alternative where the Format field uses private numbering to construct the numbers can be found in reference [QSIG]. Optionally, setting the Internal Alert field to y allows calls arriving from the Nortel Meridian users to be treated as internal calls. For example, if a Nortel telephone dials an Avaya telephone, the Avaya telephone will ring with the ring pattern for an internal station-station call, internal coverage criteria will apply, and the Nortel caller will hear tones such as coverage tone, similar to a call from an Avaya telephone to an Avaya telephone. add trunk-group 30 Page 3 of 21 TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support? n Internal Alert? y Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: Send Name: y Send Calling Number: y Used for DCS? n Send EMU Visitor CPN? n Suppress # Outpulsing? n Format: public Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: n Network Call Redirection: none Hold/Unhold Notifications? n Send UUI IE? y Modify Tandem Calling Number? n Send UCID? n Send Codeset 6/7 LAI IE? y Ds1 Echo Cancellation? n Apply Local Ringback? n US NI Delayed Calling Name Update? n Show ANSWERED BY on Display? y Network (Japan) Needs Connect Before Disconnect? n

3.3. Administer Signaling Group Administer a signaling group for the new trunk group as shown in the screen below. Use the add signaling-group n command, where n is an available signaling group number. For the Primary D-Channel field, enter the slot number for the DS1 circuit pack from Section 3.1 and port 24.




add signaling-group 30 Page 1 of 1 SIGNALING GROUP Group Number: 30 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: 30 TSC Supplementary Service Protocol: a Network Call Transfer? n

3.4. Administer Trunk Group Members Use the change trunk-group n command, where n is the trunk group number added in Section 3.2. Navigate to Page 5 and 6. Enter the first 23 ports of the DS1 interface into the Port fields, and the corresponding Code and Sfx fields will be populated automatically. Enter the ISDN signaling group number from Section 3.3 into the Sig Grp fields as shown below. change trunk-group 30 Page 5 of 21 TRUNK GROUP Administered Members (min/max): 1/23 GROUP MEMBER ASSIGNMENTS Total Administered Members: 23 Port Code Sfx Name Night Sig Grp 1: 001V401 MM710 B 30 2: 001V402 MM710 B 30 3: 001V403 MM710 B 30 4: 001V404 MM710 B 30 5: 001V405 MM710 B 30 6: 001V406 MM710 B 30 7: 001V407 MM710 B 30 8: 001V408 MM710 B 30 9: 001V409 MM710 B 30 10: 001V410 MM710 B 30 11: 001V411 MM710 B 30 12: 001V412 MM710 B 30 13: 001V413 MM710 B 30 14: 001V414 MM710 B 30 15: 001V415 MM710 B 30 The following screen shows trunk members 16-23. add trunk-group 30 Page 6 of 21 TRUNK GROUP Administered Members (min/max): 1/23 GROUP MEMBER ASSIGNMENTS Total Administered Members: 23 Port Code Sfx Name Night Sig Grp 16: 001V416 MM710 B 30 17: 001V417 MM710 B 30 18: 001V418 MM710 B 30 19: 001V419 MM710 B 30 20: 001V420 MM710 B 30 21: 001V421 MM710 B 30 22: 001V422 MM710 B 30 23: 001V423 MM710 B 30 24:




3.5. Administer Route Pattern Create a route pattern to use for routing calls to the Nortel Meridian. Use the change route-pattern n command, where n is an available route pattern. Enter the following values for the specified fields, and retain the default values for the remaining fields. Pattern Name: A descriptive name. Grp No: The trunk group number from Section 3.2. FRL: A level that allows access to this trunk, with 0 being least restrictive. Numbering Format: unk-unk (This is not strictly required, but this causes the

numbering format and type of number for the Called Party Number to be encoded as unknown toward the Nortel Meridian).

change route-pattern 30 Page 1 of 3 Pattern Number: 30 Pattern Name: Nortel-Meridian 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: 30 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 0 1 2 M 4 W Request Dgts Format Subaddress 1: y y y y y n n rest unk-unk 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

3.6. Administer Public and/or Private Numbering Public unknown numbering configuration is used for these Application Notes. For an alternative, where numbers are constructed using private numbering, consult reference [QSIG]. The change public-unknown-numbering command may be used to define the format of the calling party number to be sent to Nortel Meridian. Add an entry for the trunk group defined in Section 3.2. In the bolded row shown below, all calls originating from a 5-digit extension beginning with 2 and routed to trunk group 30 will result in the 5-digit calling number to be sent. change public-unknown-numbering 0 Page 1 of 2 NUMBERING - PUBLIC/UNKNOWN FORMAT Total Ext Ext Trk CPN CPN Len Code Grp(s) Prefix Len Total Administered: 2 5 2 30 5 Maximum Entries: 240




The example screen shown below shows an alternative configuration that may be used if it is desirable to send a 10-digit number rather than the 5-digit extension, to the Nortel Meridian. With the configuration shown below, the calling party number sent to Nortel Meridian and displayed on Nortel telephones, would be 73285XXXXX, where XXXXX is the 5-digit extension (i.e., in this case, the first X is a 2). change public-unknown-numbering 0 Page 1 of 2 NUMBERING - PUBLIC/UNKNOWN FORMAT Total Ext Ext Trk CPN CPN Len Code Grp(s) Prefix Len Total Administered: 1 5 2 30 73285 10 Maximum Entries: 240

3.7. Administer Uniform Dial Plan This section provides sample routing for calls with dialed digits 45xxx to Nortel Meridian. Use the change uniform-dialplan 4 command, and add an entry to specify use of AAR for routing of digits 45xxx. Enter the following values for the specified fields and retain the default values for the remaining fields. Matching Pattern: The dialed digits to match, in this case 45. Len: The length of the full dialed number. Del: The number of digits to delete, 0 in this case. Net: aar

change uniform-dialplan 4 Page 1 of 2 UNIFORM DIAL PLAN TABLE Percent Full: 0 Matching Insert Node Pattern Len Del Digits Net Conv Num 45 5 0 aar n

3.8. Administer AAR Analysis Use the change aar analysis command, and add an entry as shown in bold below. Enter the following values for the specified fields and retain the default values for the remaining fields: Dialed String: The AAR digits to match, in this case 45. Total Min: The minimum number of digits. Total Max: The maximum number of digits. Route Pattern: The route pattern number from Section 3.5. Call Type: aar (for an alternative configuration using lev0, consult [QSIG])




change aar analysis 45 Page 1 of 2 AAR DIGIT ANALYSIS TABLE Location: all Percent Full: 2 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd 45 5 5 30 aar n

3.9. System Parameters Features The following screen illustrates the configuration of system level features applicable to the tested configuration. Enter the change system-parameters features command. Navigate to page 8. To allow the Nortel telephones to display the name of an Avaya caller in the NI-2 configuration of the Nortel Meridian, set the USNI Calling Name for Outgoing Calls parameter to y. In the sample configuration, Avaya will include the calling name in a FACILITY Information Element in the ISDN-PRI SETUP message. Other parameters observable from the screen below pertaining to QSIG are not applicable to the configuration described in these Application Notes. See Reference [QSIG] if interested in a QSIG configuration. change system-parameters features Page 8 of 17 FEATURE-RELATED SYSTEM PARAMETERS ISDN PARAMETERS PARAMETERS FOR CREATING Send Non-ISDN Trunk Group Name as Connected Name? n QSIG SELECTION NUMBERS Display Connected Name/Number for ISDN DCS Calls? n Network Level: 0 Send ISDN Trunk Group Name on Tandem Calls? n Level 2 Code: Send Custom Messages Through QSIG? n Level 1 Code: QSIG/ETSI TSC Extension: 24777 MWI - Number of Digits Per Voice Mail Subscriber: 5 Feature Plus Ext: National CPN Prefix: International CPN Prefix: Pass Prefixed CPN to ASAI? n Unknown Numbers Considered Internal for AUDIX? y Maximum Length: 5 USNI Calling Name for Outgoing Calls? y Path Replacement with Measurements? y QSIG Path Replacement Extension: 24778




4. Configure Nortel Meridian This section focuses on the relevant Nortel Meridian configuration, including the T1 ISDN-PRI trunks on Nortel Meridian and routing of the Coordinated Dial Plan numbers to reach Avaya Communication Manager. The Nortel Meridian command line interface can be accessed via a hyper terminal application running on a PC. The PC has a serial cable connected to the Nortel Meridian serial port. The Nortel Meridian command line interface is a character-based serial interface. The program issues a prompt for input, and the system administrator enters the appropriate response through the keyboard followed by the Return (Enter) key. The output from the Nortel command line interface has been abridged in the subsequent sections to focus on the key settings for the configuration. Values shown in bold represent input by the system administrator.

4.1. Check Equipped Software and Feature Packages Log in to the Meridian. A message like the one shown in bold below should appear. logi admin2 PASS? WARNING: THE PROGRAMS AND DATA STORED ON THIS SYSTEM ARE LICENSED TO OR ARE THE PROPERTY OF NT/BNR AND ARE LAWFULLY AVAILABLE ONLY TO AUTHORIZED USERS FOR APPROVED PURPOSES. UNAUTHORIZED ACCESS TO ANY PROGRAM OR DATA ON SYSTEM IS NOT PERMITTED. THIS SYSTEM MAY BE MONITORED AT ANY TIME FOR OPERATIONAL REASONS. THEREFORE, IF YOU ARE NOT AN AUTHORIZED USER, DO NOT ATTEMPT TO LOGIN. . TTY #00 LOGGED IN ADMIN2 08:54 29/10/2008




The following output shows the software version and patches in the Nortel Meridian used for the interoperability testing of these Application Notes. The user input is shown in bold. Since this is the same Nortel Meridian system used to produce reference [QSIG] documenting the QSIG configuration, it can be observed that the Nortel Meridian was QSIG-capable. However, QSIG was not configured for the ISDN-PRI interface to Avaya Communication Manager. >ld 22 PT2000 REQ issp MAIN CAB VERSION 2111 RELEASE 25 ISSUE 40 B + IN-SERVICE PATCHES : 28 PAT# PRS PATCH REF # NAME DATE FILENAME 00 MP15566 ISS1:1OF1 CORE 28/10/08 p11061_1.11c 01 MP16609 ISS1:1OF1 Core 28/10/08 p16070_1.11c 02 DEPLIST ISSA:1OF6 FEATURES 28/10/08 p16007aA.11c 03 DEPLIST ISSA:2OF6 FEATURES 28/10/08 p16007bA.11c 04 DEPLIST ISSA:3OF6 FEATURES 28/10/08 p16007cA.11c 05 DEPLIST ISSA:4OF6 FEATURES 28/10/08 p16007dA.11c 06 DEPLIST ISSA:5OF6 FEATURES 28/10/08 p16007eA.11c 07 DEPLIST ISSA:6OF6 FEATURES 28/10/08 p16007fA.11c 08 DEPLIST ISSA:1OF2 EURO 28/10/08 p16006aA.11c 09 DEPLIST ISSA:2OF2 EURO 28/10/08 p16006bA.11c 10 DEPLIST ISSA:1OF3 INTL 28/10/08 p16005aA.11c 11 DEPLIST ISSA:1OF6 CORE 28/10/08 p16000aA.11c 12 DEPLIST ISSA:2OF6 CORE 28/10/08 p16000bA.11c 13 DEPLIST ISSA:3OF6 CORE 28/10/08 p16000cA.11c 14 DEPLIST ISSA:4OF6 CORE 28/10/08 p16000dA.11c 15 DEPLIST ISSA:5OF6 CORE 28/10/08 p16000eA.11c 16 DEPLIST ISSA:6OF6 CORE 28/10/08 p16000fA.11c 17 DEPLIST ISSA:1OF2 TERMINALS 28/10/08 p16003aA.11c 18 DEPLIST ISSA:2OF2 TERMINALS 28/10/08 p16003bA.11c 19 DEPLIST ISSA:1OF2 IP 28/10/08 p16004aA.11c 20 DEPLIST ISSA:2OF3 INTL 28/10/08 p16005bA.11c 21 DEPLIST ISSA:3OF3 INTL 28/10/08 p16005cA.11c 22 Q008054 ISS2:1OF1 QSIG 28/10/08 p18148_2.11c 23 Q003500 ISS1:1OF1 p18666_1 28/10/08 p18666_1.11c 24 Q005716 ISS2:1OF2 QSIG 28/10/08 p17039a2.11c 25 Q005716 ISS2:2OF2 QSIG 28/10/08 p17039b2.11c 26 MP16071 ISS1:1of1 qsig 28/10/08 p16744_1.11c 27 Q005272 ISS1:1of1 qsig 28/10/08 p16757_1.11c LOADWARE VERSION: PSWV 77




The following abridged output shows some of the equipped feature packages available on the Nortel Meridian used for the interoperability testing of these Application Notes. The user input is shown in bold. Once again, although QSIG is equipped, the QSIG-related packages (263, 305, 316) are not required for the ISDN-PRI NI-2 configuration, which requires package 291. REQ prt TYPE pkg DDSP 19 NARS 58 CDP 59 PBXI 75 CPND 95 (Call Party Name Display) ISDN 145 (Integrated Services Digital Network) PRA 146 (1.5 Mbps Primary Rate Access) ISL 147 PRI2 154 FNP 160 ISDN INTL SUP 161 GPRI 167 OVLP 184 IPRA 202 QSIG 263 NI-2 291 (NI-2 TR-1268 Interface Basic Call Feature) CPP 301 (Calling Party Privacy) QSIGGF 305 QSIG-SS 316

4.2. Configure Customer Data for ISDN (if necessary) In the customer data block, create or modify the NET_DATA.

1. Enter ld 15 for Overlay 15 2. At the REQ prompt, type chg and press Enter. 3. At the TYPE prompt, type NET and press Enter. 4. At the CUST prompt, type 0 (or appropriate customer number). 5. Press Enter until the ISDN prompt appears. 6. At the ISDN prompt, type YES and press Enter.




4.3. Administer TMDI Card For the sample configuration, the TMDI card is in slot number 1 of the Meridian chassis. The following steps summarize the common equipment configuration. Define the TMDI PRI card as common equipment (cequ):

7. Enter ld 17 for Overlay 17. 8. At the REQ prompt, type chg and Enter. 9. At the Type prompt, type cequ and Enter. 10. Press Enter until the DLOP prompt appears. 11. At the DLOP prompt, enter 1 23 ESF. Card 1 will use 23 channels and ESF framing. 12. At the MODE prompt, type PRI. 13. At the TMDI prompt, type YES. 14. Press Enter until the TITE prompt appears. 15. At the TITE prompt, type 01. 16. At the TRSH prompt, type 00. Threshold Group 00, defined in load 73, is applied.

4.4. Administer the D-Channel The following summarizes the steps to configure the D-Channel.

17. Remain in, or enter Overlay 17 (ld 17). 18. At the REQ prompt, type chg and Enter. 19. At the Type prompt, type adan and Enter. 20. At the ADAN prompt, type new dch 17 and Enter. In this case, 17 is an unused D-

Channel number. 21. At the CTYP prompt, type TMDI and press Enter. 22. At the CDNO prompt, type 1 and press Enter (for the TMDI card in slot 1). 23. At the DES prompt, type an appropriate text description, such as AvayaISDN. 24. At the USR prompt, type PRI and press Enter. 25. At the IFC prompt, type NI2 and press Enter (for NI2 interface configuration). 26. Press Enter until the DCHL prompt appears. 27. At the DCHL prompt, type 1 and press Enter. 28. Press Enter until the DRAT prompt appears. 29. At the DRAT prompt, type 64KC and press Enter (to match the MM710). 30. At the SIDE prompt, type net and press Enter. (The Avaya side is user). 31. Press Enter until the RCAP prompt appears. 32. At the RCAP prompt, type COLP NDS and Enter. 33. At the RCAP prompt, press Enter. See the bullet list below for RCAP descriptions.

The RCAP or Remote Capabilities Configuration corresponds to the following capabilities: Connected Line Identification Presentation (COLP) NI-2 Name Display Service (NDS) With NDS configured, the Nortel Meridian can include

the calling party name in a FACILITY Information Element in the SETUP message. Also, the Nortel Meridian can include the connected party name in a FACILITY Information




Element in the CONNECT message. Avaya Communication Manager can display these calling and connected party names.

4.5. Configure Route Data Block Define a route in Overlay 16. Unless noted, press Enter at unmentioned prompts.

34. Enter Overlay 16 using ld 16. 35. At the REQ prompt, type new and Enter. 36. At the TYPE prompt, type rdb and Enter. 37. At the CUST prompt, type 0 (or appropriate customer number). 38. At the ROUT prompt, type 51 and Enter (for new route 51). 39. At the DES prompt, enter appropriate descriptive text for this route. 40. At the TKTP prompt, type DID and Enter. 41. At the RCLS prompt, type ext and Enter. 42. At the DTRK prompt, type yes and Enter. 43. At the DGTP prompt, type PRI and Enter. (ISDN YES should automatically appear). 44. At the MODE prompt, type PRA and Enter. 45. At the IFC prompt, type NI2 and Enter. (Again, NI-2 is the interface described in this

sample configuration). 46. At the CHTY prompt, type BCH and Enter. 47. At the CTYP prompt, type UKWN and Enter. 48. At the DSEL prompt, type VOD and Enter. 49. At the PTYP prompt, type PRI and Enter. 50. At the ICOG prompt, type IAO and Enter (for incoming and outgoing). 51. At the TRMB prompt, type YES and Enter (allowing an incoming call to be routed

back on the same route) 52. At the ACOD prompt, type an unused access code, such as 5012 and Enter.

4.6. Define B-Channels for the PRI Create B-Channels in Overlay 14. Unless otherwise noted, press Enter at unmentioned prompts.

53. Enter Overlay 14 using ld 14. 54. At the REQ prompt, type new 23 and Enter. The intent is to define 23 B-channels with

common characteristics. 55. At the TYPE prompt, type DID and Enter. 56. At the TN prompt, type 1 1 and Enter. (Enter the TMDI slot number and port 1). 57. At the DES prompt, enter an appropriate text description such as AvayaISDNBCh. 58. At the CUST prompt, type 0 and Enter (or appropriate customer number). 59. At the RTMB prompt, type 51 1 and press Enter. This assigns the route members from

route 51 previously created in overlay 16. 60. Press Enter until the Nortel Meridian begins printing the records for the newly created B-

Channels.




4.7. Configure a Route List Create a route list in Overlay 86. Unless noted, press Enter at unmentioned prompts.

61. Enter Overlay 86 using ld 86. 62. At the REQ prompt, type new and Enter. 63. At the CUST prompt, type 0 and Enter (or appropriate customer number). 64. At the FEAT prompt, type rlb and Enter. 65. At the RLI prompt, type 4 and Enter. (This is route list index 4). 66. At the ENTR prompt, type 0 and Enter. 67. At the ROUT prompt, type 51 and Enter.

4.8. Configure Coordinated Dial Plan The following steps show how to create a coordinated dial plan (CDP) to route calls of the format 24XXX to Avaya Communication Manager. Unless noted, press Enter at unmentioned prompts.

68. Enter Overlay 87 using ld 87. 69. At the REQ prompt, type new and Enter. 70. At the CUST prompt, type 0 and Enter (or appropriate customer number). 71. At the FEAT prompt, type cdp and Enter. 72. At the TYPE prompt, type dsc and Enter. (This is for distant steering code). 73. At the DSC prompt, type 24 and Enter. (This is for leading digits 24 in 24xxx) 74. At the FLEN prompt, type 5 and Enter. (5 digit extensions beginning with 24) 75. At the DSP prompt, type lsc and Enter. 76. At the RLI prompt, type 4 and Enter. (This corresponds to route list index 4 created

previously)

4.9. Enable TMDI Card Enable the TMDI card using Overlay 60.

77. Enter load 60 using ld 60. 78. Type enll 1 and Enter.

4.10. Enable D-channel Automatic Establishment Enable automatic establishment of the D-Channel using Overlay 96.

79. Enter load 96 using ld 96. 80. Type enl dch 17 and Enter. 81. Type enl auto 17 and Enter. (This enables D-Channel 17 for automatic establishment

should there be a need to recover automatically from a failure.) Note that if changes need to be made to the D-Channel configuration, it will be necessary to disable automatic recovery and disable the D-Channel before making the D-Channel configuration changes.




4.11. Configure Parameters for Nortel Station Users This section contains information relevant to configuring Nortel station users. The steps shown below use new to add a station. Use chg to edit an existing station. Unless noted, press Enter at unmentioned prompts.

82. Enter Overlay 11 using ld 11. 83. At the REQ prompt, type new and Enter. 84. At the TYPE prompt, type 3904 and Enter. (Station type 3904 is used in the testing). 85. At the TN prompt, type 5 1 and Enter. (or appropriate physical location of station) 86. At the DES prompt, type USER and Enter. 87. At the CUST prompt, type 0 and Enter (or appropriate customer number). 88. At the FDN prompt, enter the desired flexible call forwarding no answer destination. 89. At the CLS prompt, type cnda and Enter. (Allow display of calling party name.)

Other CLS options can be configured that will affect displays. For the testing associated with the verifications, the CLS of the Nortel telephones included: NAMA (name display allowed on other phones), DDGA (DN display allowed on other phones), DNDD (dialed name display denied), DNO3 (notification with diverted-to partys number and name), FNA (Call forward no answer allowed), HTA (hunting allowed), CFXA (call forward to external DN allowed).

90. At the HUNT prompt, enter an extension if desired for hunting when the set is busy. 91. At the KEY prompt, type 00 scr 45001 and Enter. (Users station extension is 45001)

Parameters affecting Calling Line ID for the set may also be configured via the KEY prompt. Consult Nortel Meridian product documentation f or more information.

92. At the CPND prompt, type new and Enter. 93. At the NAME prompt, type Joe Arias and Enter. (Type the name of the user) 94. At the XPLN prompt, type 9 (or appropriate length) and Enter. 95. At the DISPLAY_FMT prompt, type first,last and Enter.

4.12. Configure Call Party Name Display Data Block This section contains information relevant to displays that may be observed for Nortel telephones. This configuration is optional. Unless noted, press Enter at unmentioned prompts.

96. Enter Overlay 95 using ld 95. 97. At the REQ prompt, type chg and Enter. 98. At the TYPE prompt, type CPND and Enter. 99. At the CUST prompt, type 0 and Enter (or appropriate customer number). 100. At the RESN prompt, type YES and Enter. (Display redirection reasons are

allowed). 101. At the CFWD prompt, type CFWD (or desired call forwarding all calls

display). 102. At the CFNA prompt, type RNA (or desired call forward no answer display). 103. At the HUNT prompt, type BSY (or desired call forward busy display) 104. At the XFER prompt, type T (or desired call transfer display).




4.13. Configure LDN Data in Customer Data Block As shown below, LDN0 must be defined for ISDN-PRI DID service, which is used with the NI-2 ISDN-PRI interface configuration. Unless noted, press Enter at unmentioned prompts.

105. Enter Overlay 15 using ld 15. 106. At the REQ prompt, type chg and Enter. 107. At the TYPE prompt, type LDN_DATA and Enter. 108. At the CUST prompt, type 0 and Enter (or appropriate customer number). 109. At the LDN0 prompt, type 45555 and Enter. The number 45555 is not

prescriptive, but in general, the length of LDN0 determines the number of trailing digits translated on the dialed DN for ISDN-PRI DID routes. In the sample configuration, LDN0 has a length of 5, and Avaya Communication Manager is sending the 5-digit number of the called Nortel Meridian user in the Called Party Number Information Element in the ISDN SETUP message.

5. Simple Verifications This section illustrates basic commands that can be run to ascertain whether the trunks are ready to handle calls.

5.1. Verify Avaya Communication Manager ISDN-PRI Status Verify the status of the ISDN trunk group to the Nortel Meridian using the status trunk command. An example screen, captured while there was an outbound call from an Avaya digital telephone to a Nortel telephone, is shown below. Idle trunk members should show in-service/idle and trunk members carrying calls should show in-service/active. Recall that Avaya Communication Manager was configured to use an ascending trunk hunt. status trunk 30 Page 1 TRUNK GROUP STATUS Member Port Service State Mtce Connected Ports Busy 0030/001 001V401 in-service/active no 001V202 0030/002 001V402 in-service/idle no 0030/003 001V403 in-service/idle no 0030/004 001V404 in-service/idle no 0030/005 001V405 in-service/idle no 0030/006 001V406 in-service/idle no 0030/007 001V407 in-service/idle no 0030/008 001V408 in-service/idle no 0030/009 001V409 in-service/idle no 0030/010 001V410 in-service/idle no 0030/011 001V411 in-service/idle no 0030/012 001V412 in-service/idle no 0030/013 001V413 in-service/idle no 0030/014 001V414 in-service/idle no The following status trunk command screen was captured at a time when there was an active call from a Nortel telephone to an Avaya telephone. In the sample configuration, Nortel always selected channel 23 first for calls to Avaya (i.e., descending trunk hunt).




status trunk 30 TRUNK GROUP STATUS Member Port Service State Mtce Connected Ports Busy 0030/015 001V415 in-service/idle no 0030/016 001V416 in-service/idle no 0030/017 001V417 in-service/idle no 0030/018 001V418 in-service/idle no 0030/019 001V419 in-service/idle no 0030/020 001V420 in-service/idle no 0030/021 001V421 in-service/idle no 0030/022 001V422 in-service/idle no 0030/023 001V423 in-service/active no 001V201 If the trunk members are not in-service, check the signaling group status, as shown below, using the status signaling-group n command, where n is the signaling group number administered in Section 3.3. Verify the signaling group is in-service as indicated in the Group State and Level 3 State fields shown below. status signaling-group 30 STATUS SIGNALING GROUP Group ID: 30 Active NCA-TSC Count: 0 Group Type: isdn-pri Active CA-TSC Count: 0 Signaling Type: facility associated signaling Group State: in-service Primary D-Channel Port: 001V424 Level 3 State: in-service If the signaling group Level 3 State is not in service, the health of the physical level can be checked by testing the DS1 board. Abridged output is shown below. While maintenance documentation is beyond the scope of these Application Notes, failure of the initial tests of the DS1 board likely indicate a problem with the physical layer connectivity to the Nortel Meridian (e.g., improper cabling, framing, etc.). If test 144 fails, check that the G450 Media Gateway is deriving clock synchronization properly. In the sample configuration, the primary sync source of the G450 Media Gateway is the MM710 in slot v4 connecting to the Nortel Meridian (i.e., set sync interface primary v4 and set sync source primary have been included in the G450 configuration).




test board 1v4 Page 1 TEST RESULTS Port Mtce Name Alt. Name Test No. Result Error Code 001V4 MG-DS1 138 PASS 001V4 MG-DS1 139 PASS 001V4 MG-DS1 140 PASS 001V4 MG-DS1 141 PASS 001V4 MG-DS1 142 PASS 001V4 MG-DS1 143 PASS 001V4 MG-DS1 144 PASS 001V4 MG-DS1 145 PASS 001V4 MG-DS1 146 PASS

5.2. Verify Nortel Meridian Status This section shows sample commands from the Nortel Meridian CLI that can be used to verify status and configuration information. Log in to the Meridian. A message like the one shown in bold below should appear. logi admin2 PASS? WARNING: THE PROGRAMS AND DATA STORED ON THIS SYSTEM ARE LICENSED TO OR ARE THE PROPERTY OF NT/BNR AND ARE LAWFULLY AVAILABLE ONLY TO AUTHORIZED USERS FOR APPROVED PURPOSES. UNAUTHORIZED ACCESS TO ANY PROGRAM OR DATA ON SYSTEM IS NOT PERMITTED. THIS SYSTEM MAY BE MONITORED AT ANY TIME FOR OPERATIONAL REASONS. THEREFORE, IF YOU ARE NOT AN AUTHORIZED USER, DO NOT ATTEMPT TO LOGIN. . TTY #00 LOGGED IN ADMIN2 08:54 29/10/2008 The following screen capture shows how the stat 1 command can be used to check the status of the ISDN-PRI interface in ld 60. This first status command is run while all channels are idle. >ld 60 DTI000 .stat 1 PRI* TRK LOOP 1 - ENBL FFMT/LCMT/YALMT: ESF/B8Z/FDL SERVICE RESTORE: YES YEL ALM PROCESS: YES ALARM STATUS : NO ALARM CH 01 - IDLE DID VOD * CH 02 - IDLE DID VOD * CH 03 - IDLE DID VOD * CH 04 - IDLE DID VOD * CH 05 - IDLE DID VOD * CH 06 - IDLE DID VOD * CH 07 - IDLE DID VOD * CH 08 - IDLE DID VOD * CH 09 - IDLE DID VOD * CH 10 - IDLE DID VOD * CH 11 - IDLE DID VOD * CH 12 - IDLE DID VOD * CH 13 - IDLE DID VOD * CH 14 - IDLE DID VOD * CH 15 - IDLE DID VOD * CH 16 - IDLE DID VOD * CH 17 - IDLE DID VOD * CH 18 - IDLE DID VOD * CH 19 - IDLE DID VOD * CH 20 - IDLE DID VOD * CH 21 - IDLE DID VOD * CH 22 - IDLE DID VOD * CH 23 - IDLE DID VOD * CH 24 - DCH 17




The following screen capture shows similar output where the status command is run while one call is up from Nortel to Avaya (using B-channel 23) and another call is up that was from Avaya to Nortel (using B-channel 1). >ld 60 DTI000 .stat 1 PRI* TRK LOOP 1 - ENBL FFMT/LCMT/YALMT: ESF/B8Z/FDL SERVICE RESTORE: YES YEL ALM PROCESS: YES ALARM STATUS : NO ALARM CH 01 - BUSY DID VOD * CH 02 - IDLE DID VOD * CH 03 - IDLE DID VOD * CH 04 - IDLE DID VOD * CH 05 - IDLE DID VOD * CH 06 - IDLE DID VOD * CH 07 - IDLE DID VOD * CH 08 - IDLE DID VOD * CH 09 - IDLE DID VOD * CH 10 - IDLE DID VOD * CH 11 - IDLE DID VOD * CH 12 - IDLE DID VOD * CH 13 - IDLE DID VOD * CH 14 - IDLE DID VOD * CH 15 - IDLE DID VOD * CH 16 - IDLE DID VOD * CH 17 - IDLE DID VOD * CH 18 - IDLE DID VOD * CH 19 - IDLE DID VOD * CH 20 - IDLE DID VOD * CH 21 - IDLE DID VOD * CH 22 - IDLE DID VOD * CH 23 - BUSY DID VOD * CH 24 - DCH 17 Another example output, using load 20 to print information about a particular ISDN B-Channel, is shown below. Observe that B-Channel 1 (TN 1 1) is route member (RTMB) 51 1. .ld 20 prt trk 1 1 DES AVAYAISDNBCH TN 001 01 TYPE DID CDEN SD CUST 0 TRK PRI PDCA 1 PCML MU NCOS 0 RTMB 51 1 B-CHANNEL SIGNALING NITE STRI/STRO OWK OWK AST NO IAPG 0 CLS UNR DIP CND WTA LPR APN THFD HKD P10 VNL TKID DATE 3 DEC 2008




Another example output is shown below using ld 22 to print information about a particular D-Channel, in this case, D-Channel 17 used in this configuration. >ld 22 PT2000 REQ prt TYPE adan dch 17 ADAN DCH 17 CTYP TMDI CARD 01 PORT 1 DES AVAYA-NI2-ISDN USR PRI DCHL 1 OTBF 32 PARM RS232 DTE DRAT 64KC CLOK EXT IFC NI2 ISDN_MCNT 300 CLID OPT0 CO_TYPE STD SIDE NET CNEG 1 RLS ID ** RCAP COLP NDS MBGA NO OVLR NO OVLS NO T310 120 T200 3 T203 10 N200 3 N201 260 K 7 BSERV NO

6. Call Verifications This section illustrates sample call results obtained with the tested configuration. The observations in this section include observed displays and Avaya trace command output, to aid in understanding and troubleshooting. More detailed and nuanced verifications are available for the QSIG configuration documented in reference [QSIG]. The displays observed on telephones may vary depending on telephone type, class of service options (e.g., Nortel Meridian CLS options such as DNDD, DNDA, NAMA, DDGA, etc.), and other factors. The focus here is to illustrate an example of display content, but not necessarily precise syntax or layout of that content.

6.1. Basic Call: Avaya Telephone Calls Nortel Telephone This section pertains to a basic UDP-dialed call from an Avaya telephone to a Nortel telephone. Specifically, extension 24001, whose name is Victor Yee, dials 45001, whose name is Joe Arias. While the Nortel telephone is ringing, the Avaya calling telephone displays 45001. Upon answer by the called user, the Avaya telephone display updates to show Joe Arias. (Nortel




Meridian includes Joe Arias in the Connected Name in the FACILITY IE in the ISDN CONNECT message, and Avaya Communication Manager displays the name). The Nortel called telephone displays Victor Yee and during the ringing and connected phases of the call. In the verification, both five-digit calling numbers, as well as ten digit calling numbers, were verified to be displayed properly on the Nortel telephone. The following capture of list trace shows the activity on the ISDN trunk group. The UDP and AAR routing of the dialed number, 45001, to route-pattern 30 and trunk group 30 can be observed. In this case, a five-digit calling number 24001 was sent to the Nortel Meridian. list trace tac 130 Page 1 LIST TRACE time data 15:02:50 dial 45001 route:UDP|AAR 15:02:50 term trunk-group 30 cid 0x217 15:02:50 dial 45001 route:UDP|AAR 15:02:50 route-pattern 30 preference 1 cid 0x217 15:02:50 seize trunk-group 30 member 1 cid 0x217 15:02:50 Calling Number & Name 24001 Victor Yee 15:02:50 Proceed trunk-group 30 member 1 cid 0x217 15:02:51 Alert trunk-group 30 member 1 cid 0x217 15:03:06 active trunk-group 30 member 1 cid 0x217 Note that the name display length in this ISDN-PRI configuration is limited to 15 characters. For example, the calling name in the FACILITY IE in the SETUP message is truncated at 15 characters. If a station on Avaya Communication Manager were translated with a long name, such as the alphabet below, a Nortel telephone receiving a call from this Avaya station would display the name from the A to the O (15 characters). change station 24002 Page 1 of 5 STATION Extension: 24002 Lock Messages? n BCC: 0 Type: 6408D+ Security Code: TN: 1 Port: 001V203 Coverage Path 1: COR: 1 Name: ABCDEFGHIJKLMNOPQRSTUVWXYZ Coverage Path 2: COS: 1

6.2. Basic Call: Nortel Telephone Calls Avaya Telephone This section pertains to a basic CDP-dialed call from a Nortel telephone to an Avaya telephone. Specifically, extension 45001 dials 24001. Refer to Figure 1 or the prior section for more information on name translations. The Avaya called telephone displays Joe Arias and during the ringing and connected phases of the call. In the example call trace below, the Nortel Meridian was sending the number 4427745001, and Avaya Communication Manager would display this number. The Nortel calling telephone displays 24001 during the ringing and connected phases of the call.




The following capture of list trace shows the activity on the ISDN trunk group. As noted previously, it can be observed that Nortel chooses channel 23, the highest numbered available channel, for the call. list trace tac 130 Page 1 LIST TRACE time data 15:08:10 Calling party trunk-group 30 member 23 cid 0x222 15:08:10 Calling Number & Name 4427745001 Joe Arias 15:08:10 active trunk-group 30 member 23 cid 0x222 15:08:10 dial 24001 15:08:10 ring station 24001 cid 0x222 15:08:12 active station 24001 cid 0x222 Consult the Nortel Meridian product documentation for the rules governing the creation of the caller ID for outgoing calls. In the sample configuration, the number 442-774-5001 is the result of the following configuration. .ld 21 REQ PRT TYPE: clid CUST 0 SIZE 256 RNGE INTL ENTRY 0 HNTN 442 ESA_HLCL ESA_INHN NO ESA_APDN YES HLCL 77 DIDN YES HLOC LSC CLASS_FMT DN

6.3. Calling Party Number and Name Presentation Restriction This section pertains to cases where the calling party information is not intended to be rendered on the display of the called telephone. Avaya User Calls Nortel User Normally, as illustrated previously, when station 24001 makes a call, the caller id and name are presented to the called user. In this case, assume that station 24001 does not want the caller id to be displayed for this particular call. Assume Avaya station 24001 has been assigned a cpn-blk button. From station 24001, press the cpn-blk button, and dial Nortel user 45001. When cpn-blk is used for a call, the calling party number is sent, but the number is marked presentation restricted. A feature access code for the feature is also available.




The Nortel telephone displays Victor Yee 5012-1. Rather than seeing the calling number 24001 on the display, the called user sees the numerical trunk information (ACOD and B-Channel number used for the call). In other words, the Nortel Meridian honors the restriction for the presentation of the callers number. If it is also desirable to restrict the presentation of the users name, see the discussion of SA8967 below. Other methods of marking the number as restricted, or not sending the calling number at all, were also tested with the same observed result for the Nortel display, including:

Setting the field Per Station CPN - Send Calling Number? on the station form for a specific Avaya station to the value r for restricted. This creates calling number presentation restriction for this station (to any trunk). A user so configured could use the cpn-unblk feature to remove calling number restrictions for specific calls.

Setting the field Send Calling Number on the Avaya trunk group to the value r for restricted. This is a broader restriction, sending but restricting the presentation of caller id for all calls over the trunk group (unless the call is otherwise marked to remove the restriction).

Setting the field Send Calling Number on the Avaya trunk group to the value n. In this case, the calling number is simply not sent for any call using this trunk group.

If it is desired that the calling partys name should also be restricted along with the calling partys number (i.e., neither should be displayed), then an Avaya special application can be activated. Special application SA8967, highlighted in bold in the abridged screen capture below, was also tested as part of the verification of these Application Notes. A special application can be activated via the license file. display system-parameters special-applications Page 7 of 8 SPECIAL APPLICATIONS (SA8967) - Mask CLI and Station Name for QSIG/ISDN Calls? y When SA8967 is enabled, and an Avaya user presses the cpn-blk button before placing a call to a Nortel user, the called Nortel telephone display will be XXXX 5012-1. Avaya sends the calling partys name, but marks it for restricted presentation. The Nortel Meridian honors the request for restricted presentation, and displays XXXX instead of the actual callers name. With SA8967 enabled, the field on the station form referenced in the prior bullet list is renamed Per Station Send Calling Number and Name. This field can be set to the value r for restricted. If a station with this configuration calls a Nortel user, the callers name and number will not appear on the Nortel telephone (i.e., same display as using cpn-blk from an unrestricted station). A station with r for restricted can use the cpn-unblk feature to cause name and number to be displayed for a specific call. Note that SA8967 does not change the behavior of calling party number restriction configured via the trunk group form. With Send Calling Number set to r on the trunk group form, the Avaya callers name will still appear on the Nortel telephone with SA8967 enabled. The Send




Name field on the trunk group form can be set to the value r to restrict presentation of calling party name. Nortel User Calls Avaya User The Nortel Meridian also provides a means for Nortel users to request privacy. The following screen capture shows the configuration of a Calling Party Privacy (CPP) Flexible Feature Code (FFC). As is common, the FFC to request privacy is configured to *67. >ld 57 REQ chg TYPE ffc CUST 0 FFCT yes CODE CPP CPP *67 With this configuration, assume that Nortel user 45001 dials *6724001. The Nortel Meridian marks both the calling name and calling number for restricted presentation. By default, Avaya Communication Manager will honor the request to restrict calling name presentation (i.e., not present the name on the display). However, to honor the request to restrict the calling party number, the Replace Restricted Numbers field on the trunk group form must be set to y. change trunk-group 30 Page 3 of 21 TRUNK FEATURES ACA Assignment? n Measured: none Wideband Support? n Internal Alert? y 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 Replace Restricted Numbers? y Replace Unavailable Numbers? n When the trunk group is configured to replace restricted numbers and a number is marked for presentation restriction, Avaya Communication Manager will display the text string configured on the system-parameters features form instead of the restricted number, as shown in the screen below. In the example, the display will read CALL FROM AV-restricted when the Nortel user dials the CPP code followed by the Avaya extension. Although not tested, it can be extrapolated that other mechanisms available in the Nortel Meridian to achieve this restriction (e.g., Calling Line Identification Restriction CLIR, class of service DDGD) would yield this same result. change system-parameters features Page 9 of 17 FEATURE-RELATED SYSTEM PARAMETERS CPN/ANI/ICLID PARAMETERS CPN/ANI/ICLID Replacement for Restricted Calls: AV-restricted CPN/ANI/ICLID Replacement for Unavailable Calls: AV-unavailable




7. Detailed Status and Tracing Tools If the information in Sections 5 and 6 are insufficient for troubleshooting, Avaya Communication Manager and Nortel Meridian provide tracing mechanisms. While detailed protocol traces are beyond the scope of these Application Notes, this section describes methods that can be used to obtain trace information.

7.1. Trace Information From Avaya Communication Manager Avaya Communication Manager includes extensive logs and tracing capabilities, accessible from the maintenance web pages of the server. Click Diagnostics System Logs from the maintenance web pages to view the available logs (not shown).




To obtain detailed message sequence trace output for the ISDN-PRI messages to and from the Nortel Meridian, the mst capability can be enabled in Avaya Communication Manager as shown in the screens below. First, disable mst so that the data may be changed, then change mst. change mst Page 1 of 16 MESSAGE SEQUENCE TRACE Run Time Limit: 99 days Disable On Buffer Full? n Generic Filters? n Store Timestamp? y Start Trigger? n Log Mst? y Message Storage: entire Stop Trigger? n Trace Analyzer? y Stop Count: Retrigger? n X.25? n GATEWAY? n EWT? n DEBUG BUTTON? n HW ERROR LOG? n ISDN-PRI? y CCMS? n SIP Trunks? n PRECs? n PROC ERRORS? y ISDN-BRI? n PACKET? n CALL TRACE? n BSR? n IP? n ASAI? n VECTORS? n CDR? n DENIAL EVENTS? y BASM? n CMS? n VECTOR EVENTS? n PMS? n FW ERROR LOG? n IP Stations/LSPs/ESSs? n Navigate to page 3, and enter the desired D-Channel to trace, and any other desired filtering. change mst Page 2 of 16 MESSAGE SEQUENCE TRACE ISDN-PRI Filter Data: Port Type: d-channel Port: 1v424 Call Control? y Incoming Calling Number: Maintenance? n Incoming Called Number: Unrecognized? y Outgoing Calling Number: Level 2 Primitives? n Outgoing Called Number: Once the mst configuration is changed, enter clear mst and enable mst. Make the desired calls to trace. Low-level data may be viewed from the SAT interface with commands such as list mst continuous. However, this is raw data without interpretation. For interpreted data, return to the maintenance web pages, and click Diagnostics System Logs. Check Communication Managers interpreted Message Tracer (MTA), and enter date or event filters (e.g., Today). It may be helpful to check Newest First (not shown).




The following is an example screen, showing a portion of the output for the beginning of a call from Avaya station 24001 to a Nortel station. In the sample below, Avaya is sending a 10 digit calling party number constructed using public unknown numbering. The calling party name Victor Yee in the FACILITY IE in the SETUP message can be observed. This type of interpreted trace information facilitates problem identification and resolution.

7.2. Trace Information From Nortel Meridian Consult reference [QSIG] for instructions and examples of trace information available from Nortel Meridian. In summary, in ld 96, detailed protocol traces can be obtained. The screen below shows the commands to enable incoming and outgoing traces for D-Channel 17. .enl msgi 17 .enl msgo 17

8. Conclusion As illustrated in these Application Notes, Avaya Communication Manager 5.1.1 can interoperate with Nortel Meridian Release 25.40b using ISDN-PRI. Avaya users may dial Nortel users by extension dialing (using Avaya UDP), and Nortel users may dial Avaya users by extension dialing (using Nortel CDP). Calling Party Name and Number displays can be provided (or restricted) as described in Section 6.




9. Additional References This section references the documentation relevant to these Application Notes. Additional Avaya product documentation is available at http://support.avaya.com. [QSIG] Sample Configuration of Avaya Communication Manager Networked with Nortel Meridian Using ISDN-PRI and QSIG, Issue 1.0, 11/2008 http://www.avaya.com/master-usa/en-us/resource/assets/applicationnotes/FE-Meridian.pdf The next (older) reference describes an alternate configuration where ISDN-PRI is used, but QSIG is not. [IPE] IP Enabling Nortel Meridian 1 with Avaya MultiVantage Solutions, Issue 1.0, 10/7/2002 http://www.avaya.com/master-usa/en-us/resource/assets/applicationnotes/s8300g700.pdf [CM1] Administrator Guide for Avaya Communication Manager, January 2008, Document Number 03-300509. http://support.avaya.com/elmodocs2/comm_mgr/r5.0/03-300509_4.pdf The following reference also documents an NI-2 configuration of the Nortel Meridian. [IPO] Configuring an ISDN Primary Rate Interface between an Avaya IP Office Server and a Nortel Meridian, Issue 1.0, 10/31/2003 [CM2] Feature Description and Implementation for Avaya Communication Manager, January 2008, Document Number 555-245-205 http://support.avaya.com/elmodocs2/comm_mgr/r5.0/245205_6.pdf [IA770] Avaya IA770 INTUITY AUDIX Messaging Application Release 5.1 Administering Communication Manager Servers to Work with IA770, June 2008 http://support.avaya.com/elmodocs2/IA770/R5_1/Admin_Switch.pdf




2008 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 e-mail 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 [email protected].

Documents

NI2 Meridian