Avaya Meridian PRI

8/11/2019 Avaya Meridian PRI

1/31

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 aconfiguration 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 runningNortel 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 Nortelhardware platforms using Nortel Meridian software.


2/31

JRR; Reviewed:

SPOC 12/19/2008



2 of 31

NI2-Meridian

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 ApplicationNotes 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 willgenerally 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 applicableto Avaya Communication Manager systems using other Avaya Server and Media Gateway

platforms, and also to other Nortel hardware platforms using Nortel Meridian software.

Figure 1illustrates 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


3/31

JRR; Reviewed:

SPOC 12/19/2008



3 of 31

NI2-Meridian

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 withG450 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 inlegacy equipment.

A five digit Uniform Dial Plan (UDP) is used to facilitate extension dialing from the Avayatelephones 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 AvayaCommunication 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 ValidatedThe following equipment and software were used for the sample configuration provided:

Equipment Software

Avaya S8300C Server running Avaya

Communication Manager, IA770 INTUITYAUDIX, 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 theISDN-PRI to the Nortel Meridian)

MM712 Digital Media Module (if Avaya digitaltelephones are desired)

MM711 Analog Media Module (if analogphones, 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


4/31

JRR; Reviewed:

SPOC 12/19/2008



4 of 31

NI2-Meridian

3. Configure Avaya Communication Manager for ISDN-PRIConnectivity 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 MediaModule. 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 correspondingconfiguration parameters on the Nortel Meridian.

Name: A descriptive name.

Line Coding: b8zsFraming Mode: esf

Signaling Mode: isdn-pri

Connect: pbx

Interface: user

Country Protocol: 1

Protocol Version: b

The setting of the Interfacefield 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.


5/31

JRR; Reviewed:

SPOC 12/19/2008



5 of 31

NI2-Meridian

add ds1 1v4 Page 1 of 2DS1 CI RCUI T PACK

Locat i on: 001V4 Name: To-MeridianBi t Rate: 1. 544 Line Coding: b8zs

Li ne Compensat i on: 1 Framing Mode: esfSignaling Mode: isdn-pri

Connect: pbx Interface: userTN- C7 Long Ti mer s? n Country Protocol: 1I nterworki ng Message: PROGr ess Protocol Version: bI nt er f ace Compandi ng: mul aw CRC? n

I dl e Code: 11111111DCP/ Anal og Bear er Capabi l i t y: 3. 1kHz

T303 Ti mer ( sec) : 4

Sl i p Detect i on? n Near - end CSU Type: other

Echo Cancel l ati on? n Bl ock Progr ess I ndi cat or? n

3.2. Administer Trunk GroupAdminister 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 21TRUNK GROUP

Gr oup Number : 30 Group Type: isdn CDR Repor t s: yGroup Name: To-Meridian COR: 1 TN: 1 TAC: 130Direction: two-way Outgoi ng Di spl ay? n Carrier Medium: PRI/BRI

Di al Access? n Busy Thr eshol d: 255 Ni ght Servi ce:Queue Length: 0Service Type: tie Aut h Code? n Test Cal l I TC: r est

Navigate toPage 2. For the Supplementary Service Protocolfield, enter a. Leave the

Formatfield 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 beretained for the remaining fields. If desired, the Trunk Huntfield 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 Managerused an ascending order for calls from Avaya users to Nortel users, to minimize the opportunities

for glare conditions.


6/31

JRR; Reviewed:

SPOC 12/19/2008



6 of 31

NI2-Meridian

add trunk-group 30 Page 2 of 21Gr oup Type: i sdn

TRUNK PARAMETERSCodeset to Send Di spl ay: 6 Codeset t o Send Nat i onal I Es: 6

Max Message Si ze t o Send: 260 Charge Advi ce: none

Supplementary Service Protocol: a Di gi t Handl i ng ( i n/ out ) : enbl oc/ enbl oc

Trunk Hunt: ascend

Di gi t al Loss Gr oup: 13I ncomi ng Cal l i ng Number - Del ete: I nsert : For mat:

Bi t Rate: 1200 Synchr oni zat i on: async Dupl ex: f ul lDi sconnect Supervi si on - I n? y Out? nAnswer Super vi si on Ti meout : 0

Admi ni st er Ti mers? n CONNECT Rel i abl e When Cal l Leaves I SDN? n

Navigate to Page 3. Enable the Send Nameand Send Calling Numberfields. In the sampleconfiguration, the Formatfield 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 theInternal Alertfield 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 Avayatelephone to an Avaya telephone.

add trunk-group 30 Page 3 of 21TRUNK FEATURES

ACA Ass i gnment? n Measur ed: none Wi deband Suppor t ? nInternal Alert? y Mai ntenance Test s? y

Dat a Rest r i ct i on? n NCA- TSC Trunk Member :Send Name: y Send Calling Number: y

Used f or DCS? n Send EMU Vi si t or CPN? nSuppr ess # Outpul si ng? n Format: public

Out goi ng Channel I D Encodi ng: pr ef err ed UUI I E Treatment : servi ce- pr ovi der

Repl ace Rest r i ct ed Number s? nRepl ace Unavai l abl e Number s? n

Send Connect ed Number : nNetwork Cal l Redi r ect i on: none Hol d/ Unhol d Not i f i cat i ons? n

Send UUI I E? y Modi f y Tandem Cal l i ng Number ? nSend UCI D? n

Send Codeset 6/ 7 LAI I E? y Ds1 Echo Cancel l at i on? n

Appl y Local Ri ngback? n US NI Del ayed Cal l i ng Name Updat e? nShow ANSWERED BY on Di spl ay? y

Network ( J apan) Needs Connect Bef ore Di sconnect ? 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-Channelfield, enter the slot number for the DS1 circuit pack from Section 3.1andport 24.


7/31


8/31

JRR; Reviewed:

SPOC 12/19/2008



8 of 31

NI2-Meridian

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 thenumbering 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 3Pat t ern Number : 30 Pattern Name: Nortel-Meridian

SCCAN? n Secure SI P? nGr p FRL NPA Pf x Hop Tol l No. I nsert ed DCS/ I XCNo Mr k Lmt Li st Del Di gi t s QSI G

Dgts I ntw1: 30 0 n user2: n user3: n user4: n user5: n user6: n user

BCC VALUE TSC CA- TSC I TC BCI E Servi ce/ Feat ure PARM No. Numberi ng LAR0 1 2 M 4 W Request Dgts Format

Subaddr ess1: y y y y y n n r est unk-unk none2: y y y y y n n r est none3: y y y y y n n r est none4: y y y y y n n r est none

5: y y y y y n n r est none6: y y y y y n n r est 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 inSection 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 2NUMBERI NG - PUBLI C/ UNKNOWN FORMATTot al

Ext Ext Tr k CPN CPNLen Code Gr p( s) Pref i x Len

Tot al Admi ni st ered: 25 2 30 5 Maxi mum Ent r i es: 240


9/31

JRR; Reviewed:

SPOC 12/19/2008



9 of 31

NI2-Meridian

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 2NUMBERI NG - PUBLI C/ UNKNOWN FORMAT

Tot alExt Ext Tr k CPN CPNLen Code Gr p( s) Pref i x Len

Tot al Admi ni st ered: 15 2 30 73285 10 Maxi mum Ent r i es: 240

3.7. Administer Uniform Dial Plan

This section provides sample routing for calls with dialed digits 45xxx to Nortel Meridian. Usethe 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 2UNI FORM DI AL PLAN TABLE

Per cent Ful l : 0Mat chi ng I nsert NodePat t ern Len Del Di gi t s 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])


10/31

JRR; Reviewed:

SPOC 12/19/2008



10 of 31

NI2-Meridian

change aar analysis 45 Page 1 of 2AAR DI GI T ANALYSI S TABLE

Locat i on: al l Percent Ful l : 2

Di al ed Tot al Rout e Cal l Node ANISt r i ng Mi n Max Pat t ern 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 Callsparameter 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 belowpertaining 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 17FEATURE- RELATED SYSTEM PARAMETERS

I SDN PARAMETERSPARAMETERS FOR CREATI NG

Send Non- I SDN Tr unk Gr oup Name as Connect ed Name? n QSI G SELECTI ON NUMBERSDi spl ay Connect ed Name/ Number f or I SDN DCS Cal l s? n Net work Level : 0

Send I SDN Tr unk Gr oup Name on Tandem Cal l s? n Level 2 Code:Send Cust om Messages Through QSI G? n Level 1 Code:

QSI G/ ETSI TSC Extensi on: 24777MWI - Number of Di gi t s Per Voi ce Mai l Subscr i ber: 5

Feat ur e Pl us Ext:Nat i onal CPN Pref i x:

I nt er nat i onal CPN Pr ef i x:Pass Pref i xed CPN t o ASAI ? n

Unknown Number s Consi der ed I nt ernal f or AUDI X? y Maxi mum Lengt h: 5USNI Calling Name for Outgoing Calls? y

Pat h Repl acement wi t h Measur ements? yQSI G Pat h Repl acement Extensi on: 24778


11/31


12/31

JRR; Reviewed:

SPOC 12/19/2008



12 of 31

NI2-Meridian

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 isthe 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

MAI N CABVERSI ON 2111RELEASE 25I SSUE 40 B +

I N- SERVI CE PATCHES : 28PAT# PRS PATCH REF # NAME DATE FI LENAME00 MP15566 I SS1: 1OF1 CORE 28/ 10/ 08 p11061_1. 11c01 MP16609 I SS1: 1OF1 Cor e 28/ 10/ 08 p16070_1. 11c

02 DEPLI ST I SSA: 1OF6 FEATURES 28/ 10/ 08 p16007aA. 11c03 DEPLI ST I SSA: 2OF6 FEATURES 28/ 10/ 08 p16007bA. 11c04 DEPLI ST I SSA: 3OF6 FEATURES 28/ 10/ 08 p16007cA. 11c05 DEPLI ST I SSA: 4OF6 FEATURES 28/ 10/ 08 p16007dA. 11c06 DEPLI ST I SSA: 5OF6 FEATURES 28/ 10/ 08 p16007eA. 11c07 DEPLI ST I SSA: 6OF6 FEATURES 28/ 10/ 08 p16007f A. 11c08 DEPLI ST I SSA: 1OF2 EURO 28/ 10/ 08 p16006aA. 11c09 DEPLI ST I SSA: 2OF2 EURO 28/ 10/ 08 p16006bA. 11c10 DEPLI ST I SSA: 1OF3 I NTL 28/ 10/ 08 p16005aA. 11c11 DEPLI ST I SSA: 1OF6 CORE 28/ 10/ 08 p16000aA. 11c12 DEPLI ST I SSA: 2OF6 CORE 28/ 10/ 08 p16000bA. 11c13 DEPLI ST I SSA: 3OF6 CORE 28/ 10/ 08 p16000cA. 11c14 DEPLI ST I SSA: 4OF6 CORE 28/ 10/ 08 p16000dA. 11c15 DEPLI ST I SSA: 5OF6 CORE 28/ 10/ 08 p16000eA. 11c16 DEPLI ST I SSA: 6OF6 CORE 28/ 10/ 08 p16000f A. 11c

17 DEPLI ST I SSA: 1OF2 TERMI NALS 28/ 10/ 08 p16003aA. 11c18 DEPLI ST I SSA: 2OF2 TERMI NALS 28/ 10/ 08 p16003bA. 11c19 DEPLI ST I SSA: 1OF2 I P 28/ 10/ 08 p16004aA. 11c20 DEPLI ST I SSA: 2OF3 I NTL 28/ 10/ 08 p16005bA. 11c21 DEPLI ST I SSA: 3OF3 I NTL 28/ 10/ 08 p16005cA. 11c22 Q008054 I SS2: 1OF1 QSI G 28/ 10/ 08 p18148_2. 11c23 Q003500 I SS1: 1OF1 p18666_1 28/ 10/ 08 p18666_1. 11c24 Q005716 I SS2: 1OF2 QSI G 28/ 10/ 08 p17039a2. 11c25 Q005716 I SS2: 2OF2 QSI G 28/ 10/ 08 p17039b2. 11c26 MP16071 I SS1: 1of 1 qsi g 28/ 10/ 08 p16744_1. 11c27 Q005272 I SS1: 1of 1 qsi g 28/ 10/ 08 p16757_1. 11c

LOADWARE VERSI ON: PSWV 77


13/31

JRR; Reviewed:

SPOC 12/19/2008



13 of 31

NI2-Meridian

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 inputis 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 19NARS 58CDP 59PBXI 75CPND 95 ( Cal l Par t y Name Di spl ay)I SDN 145 ( I nt egr ated Servi ces Di gi t al Network)PRA 146 ( 1. 5 Mbps Pr i mary Rat e Access )I SL 147PRI 2 154FNP 160I SDN I NTL SUP 161GPRI 167OVLP 184I PRA 202QSI G 263

NI-2 291 ( NI - 2 TR- 1268 I nt erf ace Basi c Cal l Feature)CPP 301 ( Cal l i ng Par t y Pri vacy)QSI GGF 305QSI G- 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 152. 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.


14/31

JRR; Reviewed:

SPOC 12/19/2008



14 of 31

NI2-Meridian

4.3. Administer TMDI Card

For the sample configuration, the TMDI card is in slot number 1 of the Meridian chassis. Thefollowing 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-ChannelThe 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 Configurationcorresponds to the following capabilities:

Connected Line Identification Presentation (COLP)

NI-2 Name Display Service (NDS) With NDS configured, the Nortel Meridian can includethe 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


15/31

JRR; Reviewed:

SPOC 12/19/2008



15 of 31

NI2-Meridian

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 fromroute 51 previously created in overlay 16.

60.Press Enter until the Nortel Meridian begins printing the records for the newly created B-Channels.


16/31

JRR; Reviewed:

SPOC 12/19/2008



16 of 31

NI2-Meridian

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. Conf igure 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 unmentionedprompts.

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 CardEnable 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 establishmentshould 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-Channelconfiguration changes.


17/31

JRR; Reviewed:

SPOC 12/19/2008



17 of 31

NI2-Meridian

4.11. Conf igure Parameters for Nortel Station Users

This section contains information relevant to configuring Nortel station users. The steps shownbelow 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 displayallowed 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 KEYprompt. 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 callsdisplay).

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).


18/31


19/31

JRR; Reviewed:

SPOC 12/19/2008



19 of 31

NI2-Meridian

status trunk 30

TRUNK GROUP STATUS

Member Port Ser vi ce St at e Mt ce Connect ed Port sBusy

0030/ 015 001V415 i n- servi ce/ i dl e no

0030/ 016 001V416 i n- servi ce/ i dl e no0030/ 017 001V417 i n- servi ce/ i dl e no0030/ 018 001V418 i n- servi ce/ i dl e no0030/ 019 001V419 i n- servi ce/ i dl e no0030/ 020 001V420 i n- servi ce/ i dl e no0030/ 021 001V421 i n- servi ce/ i dl e no0030/ 022 001V422 i n- servi ce/ i dl e no0030/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 administeredin Section 3.3. Verify the signaling group is in-service as indicated in the Group Stateand

Level 3 State fields shown below.

status signaling-group 30

STATUS SI GNALI NG GROUP

Gr oup I D: 30 Act i ve NCA- TSC Count : 0Gr oup Type: i sdn- pr i Act i ve CA- TSC Count : 0

Si gnal i ng Type: f aci l i t y associ at ed si gnal i ngGroup State: in-service

Pr i mary D- Channel

Port: 001V424 Level 3 State: in-service

If the signaling group Level 3 Stateis not in service, the health of the physical level can be

checked by testing the DS1 board. Abridged output is shown below. While maintenancedocumentation 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., setsync interface primary v4 and set sync source primary have been included in the G450

configuration).


20/31

JRR; Reviewed:

SPOC 12/19/2008



20 of 31

NI2-Meridian

test board 1v4 Page 1TEST RESULTS

Port Mt ce Name Al t . Name Test No. Resul t Err or Code

001V4 MG- DS1 138 PASS001V4 MG- DS1 139 PASS

001V4 MG- DS1 140 PASS001V4 MG- DS1 141 PASS001V4 MG- DS1 142 PASS001V4 MG- DS1 143 PASS001V4 MG- DS1 144 PASS001V4 MG- DS1 145 PASS001V4 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 inbold below should appear.

logi admin2

PASS?

WARNI NG: THE PROGRAMS AND DATA STORED ON THI S SYSTEM ARE LI CENSED TOOR ARE THE PROPERTY OF NT/ BNR AND ARE LAWFULLY AVAI LABLE ONLY TOAUTHORI ZED USERS FOR APPROVED PURPOSES. UNAUTHORI ZED ACCESS TO ANYPROGRAM OR DATA ON SYSTEM I S NOT PERMI TTED. THI S SYSTEM MAY BEMONI TORED AT ANY TI ME FOR OPERATI ONAL REASONS. THEREFORE, I F YOUARE NOT AN AUTHORI ZED USER, DO NOT ATTEMPT TO LOGI N.

.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

DTI 000.stat 1

PRI * TRK LOOP 1 - ENBLFFMT/ LCMT/ YALMT: ESF/ B8Z/ FDLSERVI CE RESTORE: YESYEL ALM PROCESS: YESALARM STATUS : NO ALARMCH 01 - I DLE DI D VOD * CH 02 - I DLE DI D VOD *CH 03 - I DLE DI D VOD * CH 04 - I DLE DI D VOD *CH 05 - I DLE DI D VOD * CH 06 - I DLE DI D VOD *CH 07 - I DLE DI D VOD * CH 08 - I DLE DI D VOD *

CH 09 - I DLE DI D VOD * CH 10 - I DLE DI D VOD *CH 11 - I DLE DI D VOD * CH 12 - I DLE DI D VOD *CH 13 - I DLE DI D VOD * CH 14 - I DLE DI D VOD *CH 15 - I DLE DI D VOD * CH 16 - I DLE DI D VOD *CH 17 - I DLE DI D VOD * CH 18 - I DLE DI D VOD *CH 19 - I DLE DI D VOD * CH 20 - I DLE DI D VOD *CH 21 - I DLE DI D VOD * CH 22 - I DLE DI D VOD *CH 23 - I DLE DI D VOD * CH 24 - DCH 17


21/31

JRR; Reviewed:

SPOC 12/19/2008



21 of 31

NI2-Meridian

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 Avayato Nortel (using B-channel 1).

>ld 60

DTI 000

.stat 1

PRI * TRK LOOP 1 - ENBLFFMT/ LCMT/ YALMT: ESF/ B8Z/ FDLSERVI CE RESTORE: YESYEL ALM PROCESS: YESALARM STATUS : NO ALARMCH 01 - BUSY DID VOD * CH 02 - I DLE DI D VOD *CH 03 - I DLE DI D VOD * CH 04 - I DLE DI D VOD *CH 05 - I DLE DI D VOD * CH 06 - I DLE DI D VOD *CH 07 - I DLE DI D VOD * CH 08 - I DLE DI D VOD *CH 09 - I DLE DI D VOD * CH 10 - I DLE DI D VOD *CH 11 - I DLE DI D VOD * CH 12 - I DLE DI D VOD *CH 13 - I DLE DI D VOD * CH 14 - I DLE DI D VOD *CH 15 - I DLE DI D VOD * CH 16 - I DLE DI D VOD *

CH 17 - I DLE DI D VOD * CH 18 - I DLE DI D VOD *CH 19 - I DLE DI D VOD * CH 20 - I DLE DI D VOD *CH 21 - I DLE DI D VOD * CH 22 - I DLE DI D 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 AVAYAI SDNBCHTN 001 01TYPE DI DCDEN SDCUST 0TRK PRIPDCA 1PCML MUNCOS 0RTMB 51 1B- CHANNEL SI GNALI NGNI TESTRI / STRO OWK OWKAST NOI APG 0

CLS UNR DI P CND WTA LPR APN THFD HKDP10 VNLTKI DDATE 3 DEC 2008


22/31

JRR; Reviewed:

SPOC 12/19/2008



22 of 31

NI2-Meridian

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

PT2000REQ prt

TYPE adan dch 17

ADAN DCH 17CTYP TMDICARD 01PORT 1DES AVAYA-NI 2- I SDNUSR PRIDCHL 1OTBF 32PARM RS232 DTEDRAT 64KCCLOK EXTI FC NI 2

I SDN_MCNT 300

CLI D OPT0CO_TYPE STDSI DE NETCNEG 1RLS I D **RCAP COLP NDSMBGA NOOVLR NOOVLS NOT310 120T200 3T203 10N200 3N201 260K 7

BSERV NO

6. Call VerificationsThis 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 theQSIG 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 optionssuch 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 TelephoneThis 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


23/31

JRR; Reviewed:

SPOC 12/19/2008



23 of 31

NI2-Meridian

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 beobserved. In this case, a five-digit calling number 24001 was sent to the Nortel Meridian.

list trace tac 130 Page 1LI ST TRACE

t i me dat a15: 02: 50 di al 45001 r out e: UDP| AAR15: 02: 50 t erm t r unk- gr oup 30 ci d 0x21715: 02: 50 di al 45001 r out e: UDP| AAR15: 02: 50 r out e- patt ern 30 pr ef erence 1 ci d 0x21715: 02: 50 sei ze t r unk- group 30 member 1 ci d 0x21715: 02: 50 Cal l i ng Number & Name 24001 Vi ct or Yee15: 02: 50 Pr oceed t r unk- group 30 member 1 ci d 0x21715: 02: 51 Al er t t r unk- group 30 member 1 ci d 0x21715: 03: 06 act i ve t r unk- group 30 member 1 ci d 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 15characters. 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

STATI ON

Extensi on: 24002 Lock Messages? n BCC: 0Type: 6408D+ Secur i t y Code: TN: 1Port : 001V203 Cover age Path 1: COR: 1

Name: ABCDEFGHIJKLMNOPQRSTUVWXYZ Cover age 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 1or the prior section for moreinformation on name translations.

The Avaya called telephone displays Joe Arias and during the ringing andconnected 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.


24/31

JRR; Reviewed:

SPOC 12/19/2008



24 of 31

NI2-Meridian

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 availablechannel, for the call.

list trace tac 130 Page 1LI ST TRACE

t i me dat a15: 08: 10 Cal l i ng par t y t r unk- group 30 member 23 ci d 0x22215: 08: 10 Cal l i ng Number & Name 4427745001 J oe Ar i as15: 08: 10 act i ve t r unk- group 30 member 23 ci d 0x22215: 08: 10 di al 2400115: 08: 10 r i ng st at i on 24001 ci d 0x22215: 08: 12 act i ve st at i on 24001 ci d 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: clidCUST 0

SI ZE 256RNGEI NTL

ENTRY 0HNTN 442ESA_HLCLESA_I NHN NOESA_APDN YESHLCL 77DI DN YES

HLOCLSCCLASS_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 renderedon 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-blkbutton. 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.


25/31

JRR; Reviewed:

SPOC 12/19/2008



25 of 31

NI2-Meridian

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 aspecific 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 forrestricted. 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 beactivated. 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 8SPECI AL APPLI CATI ONS

(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 callto 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 forrestricted. 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 anunrestricted 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, theAvaya callers name will still appear on the Nortel telephone with SA8967 enabled. The Send


26/31

JRR; Reviewed:

SPOC 12/19/2008



26 of 31

NI2-Meridian

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 followingscreen 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 Meridianmarks 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 partynumber, the Replace Restricted Numbers field on the trunk group form must be set to y.

change trunk-group 30 Page 3 of 21TRUNK FEATURES

ACA Ass i gnment? n Measur ed: none Wi deband Suppor t ? nI nt ernal Al ert ? y Mai nt enance Test s? y

Dat a Rest r i ct i on? n NCA- TSC Trunk Member :Send Name: y Send Cal l i ng Number: y

Used f or DCS? n Hop Dgt? n Send EMU Vi si t or CPN? n

Suppr ess # Outpul si ng? n Format : publ i cOut goi ng Channel I D Encodi ng: pr ef err ed UUI I E Treatment : servi ce- pr ovi der

Replace Restricted Numbers? y

Repl ace Unavai l abl e Number s? 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 configuredon 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 thissame result.

change system-parameters features Page 9 of 17FEATURE- RELATED SYSTEM PARAMETERS

CPN/ ANI / I CLI D PARAMETERSCPN/ANI/ICLID Replacement for Restricted Calls: AV-restricted

CPN/ ANI / I CLI D Repl acement f or Unavai l abl e Cal l s: AV- unavai l abl e


27/31

JRR; Reviewed:

SPOC 12/19/2008



27 of 31

NI2-Meridian

7. Detailed Status and Tracing ToolsIf the information in Sections 5 and 6 are insufficient for troubleshooting, Avaya Communication

Manager and Nortel Meridian provide tracing mechanisms. While detailed protocol traces arebeyond 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 fromthe maintenance web pages of the server. Click DiagnosticsSystem Logsfrom the

maintenance web pages to view the available logs (not shown).


28/31

JRR; Reviewed:

SPOC 12/19/2008



28 of 31

NI2-Meridian

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 asshown in the screens below. First, disable mst so that the data may be changed, then change

mst.

change mst Page 1 of 16MESSAGE SEQUENCE TRACE

Run Ti me Li mi t : 99 days Di sabl e On Buf f er Ful l ? n Generi c Fi l t er s? nSt ore Ti mest amp? y St art Tri gger? n Log Mst? yMessage St orage: ent i r e St op Tri gger? n Trace Analyzer? y

Stop Count :Retr i gger ? n

X. 25? n GATEWAY? n EWT? n DEBUG BUTTON? n HWERROR LOG? nISDN-PRI? y CCMS? n SI P Tr unks? n PRECs? n PROC ERRORS? yI SDN- BRI ? n PACKET? n CALL TRACE? n BSR? n I P? n

ASAI ? n VECTORS? n CDR? n DENI AL EVENTS? y BASM? nCMS? n VECTOR EVENTS? n PMS? n FW ERROR LOG? n

I P St at i ons/ 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 16MESSAGE SEQUENCE TRACE

I SDN- PRI Fi l t er Dat a:Port Type: d-channel Port: 1v424

Call Control? y I ncomi ng Cal l i ng Number :Mai ntenance? n I ncomi ng Cal l ed Number :

Unrecogni zed? y Outgoi ng Cal l i ng Number :Level 2 Pr i mi t i ves? n Outgoi ng Cal l ed Number :

Once the mst configuration is changed, enter clear mst and enable mst. Make the desiredcalls 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 DiagnosticsSystem

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).


29/31

JRR; Reviewed:

SPOC 12/19/2008



29 of 31

NI2-Meridian

The following is an example screen, showing a portion of the output for the beginning of a callfrom 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 MeridianConsult reference [QSIG] for instructions and examples of trace information available fromNortel 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. ConclusionAs 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 byextension 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.


30/31

JRR; Reviewed:

SPOC 12/19/2008



30 of 31

NI2-Meridian

9. Additional ReferencesThis 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 NortelMeridian Using ISDN-PRI and QSIG, Issue 1.0, 11/2008http://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


31/31


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 issubject to change without notice. The configurations, technical data, and recommendationsprovided 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 anyproducts specified in these Application Notes.

Please e-mail any questions or comments pertaining to these Application Notes along with thefull title name and filename, located in the lower right corner, directly to the Avaya Solution &

Interoperability Test Lab at [email protected].

Avaya Meridian PRI

Documents

Transcript of Avaya Meridian PRI