fe meridian

JRR; Reviewed: SPOC 12/05/2008

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

1 of 69 FE-Meridian

Avaya Solution & Interoperability Test Lab

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

Abstract

These Application Notes illustrate a sample configuration of Nortel Meridian networked with Avaya Communication Manager using an ISDN-PRI QSIG trunk. The sample configuration includes an 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 IA770 INTUITY AUDIX Messaging Application is also configured for the Avaya S8300C Server, enabling the Avaya S8300C to provide voice messaging services to Avaya telephones controlled by Avaya Communication Manager as well as Nortel telephones controlled by Nortel Meridian. The verification of these Application Notes includes extension dialing among Avaya and Nortel telephones, name and number displays, call forwarding, call coverage, call transfer, automatic callback, and voice mail scenarios. 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.



2 of 69 FE-Meridian

1. Introduction These Application Notes illustrate a sample configuration of Nortel Meridian networked with Avaya Communication Manager using an ISDN-PRI QSIG trunk. 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 IA770 INTUITY AUDIX Messaging Application is also configured in the Avaya S8300C Server, enabling the Avaya system to provide voice messaging services to Avaya telephones controlled by Avaya Communication Manager and Nortel telephones controlled by Meridian. The set of basic features included in the verification of these Application Notes includes extension dialing among Avaya and Nortel telephones, name and number displays, call forwarding, call coverage, call transfer, automatic callback, and voice mail scenarios. 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. These Application Notes update previously published documents with testing of the latest Avaya Communication Manager software running on the S8300C Server with G450 Media Gateway platform. The Nortel Meridian configuration used to produce references [KB] and [KB2] was largely re-used in the testing associated with these Application Notes. 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. QSIG is a commonly used protocol for signaling between private branch exchanges (PBXs). In the test configuration, QSIG protocol exchanges between Avaya Communication Manager and the Nortel Meridian use a T1 ISDN-PRI trunk between an MM710 Media Module in an Avaya G450 Media Gateway and a Nortel TMDI DTI/PRI NTRB21AC card in the chassis of the Option 11C Mini. Although not the focal point of these Application Notes, QSIG over an “internal” H.323 IP Trunk is also used as the signaling protocol between Avaya Communication Manager and the Avaya IA770 Messaging system, co-resident on the Avaya S8300C Server.



3 of 69 FE-Meridian

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 similar Coordinated Dial Plan (CDP) feature to dial by extension to reach the Avaya users. Unique extension ranges are associated with Avaya Communication Manager (24xxx, 25xxx) extensions, and Nortel Meridian (45xxx) extensions. This five digit extension arrangement is simply an example; other extension lengths and extension ranges may be used. Figure 1 illustrates the most relevant aspects of the sample configuration. The four telephones for which names are shown in Figure 1 are used extensively in the verification of sample call flows in Section 7. The Avaya telephones, as well as the two Nortel telephones shown below, have been given subscriber mailboxes in Avaya IA770.

Figure 1: Sample Network: Avaya Communication Manager Using S8300C Server/G450

Media Gateway Networked with Nortel Meridian Option 11C Mini If QSIG is not available in the Nortel Meridian, an ISDN-PRI connection (without QSIG) may still be used for basic connectivity, extension dialing, and caller ID services between the Avaya and Nortel communities. However, the QSIG-related features illustrated in these Application Notes, such as Path Replacement, Diversion by Reroute, and Message Waiting Indication for Nortel phones using Avaya IA770 voice mail, would not be available using an ISDN-PRI connection without QSIG. Reference [IPE] is already available for an ISDN-PRI configuration, and contains additional information on cabling. In the future, it is intended that separate Application Notes, based on a configuration similar to the one illustrated in these Application Notes, will be provided for an ISDN-PRI configuration (i.e., same products without QSIG configuration).



4 of 69 FE-Meridian

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, and co-resident 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 / QSIG 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 5.

Nortel m3904 Digital Telephone N/A

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

This section focuses on configuring the T1 QSIG 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 these Application Notes, the following customer options are among those that are enabled:

• ISDN-PRI • Private Networking • Uniform Dialing Plan • QSIG Optional Features



5 of 69 FE-Meridian

o Basic Call Setup o Basic Supplementary Services o Supplementary Services with Rerouting o Transfer into QSIG Voice Mail o Value-Added (VALU) (for the IA770 integration)

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” • Frame Mode: “esf” • Signaling Mode: “isdn-pri” • Connect: “pbx” • Interface: “peer-slave” • Peer Protocol: “Q-SIG”

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 “slave”, and Nortel Meridian is administered as the “master”. 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: peer-slave TN-C7 Long Timers? n Peer Protocol: Q-SIG Interworking Message: PROGress Side: b Interface Companding: mulaw CRC? n Idle Code: 11111111 DCP/Analog Bearer Capability: 3.1kHz T303 Timer(sec): 4 Disable Restarts? n Slip Detection? n Near-end CSU Type: other

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.



6 of 69 FE-Meridian

• 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 “b” for QSIG. 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 a round-robin cyclical order for calls from Avaya users to Nortel users. Another alternative would be to have Avaya use an “ascending” approach if Nortel uses a “descending” approach, 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: b Digit Handling (in/out): enbloc/enbloc Trunk Hunt: cyclical Digital Loss Group: 13 Incoming Calling Number - Delete: Insert: Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 Administer Timers? n CONNECT Reliable When Call Leaves ISDN? n



7 of 69 FE-Meridian

Navigate to Page 3. Enable the Send Name, Send Calling Number, and Send Connected Number fields. For the Format field, enter “unk-pvt” to construct the calling and connected numbers using the “private numbering” table, but encode the numbering plan format as “unknown” in the ISDN messages toward the Nortel Meridian. (As part of the verification, “unknown” in the format field was also verified). 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 Hop Dgt? n Send EMU Visitor CPN? n Suppress # Outpulsing? n Format: unk-pvt Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: y Hold/Unhold Notifications? y 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 Show ANSWERED BY on Display? y

Navigate to Page 4 to view or change the QSIG options for the trunk group. The following screen shows the values used in the verification of the sample configuration. If the Avaya Auto Callback feature will be used with Nortel users, then the TSC Method for Auto Callback field must be set to “always-retain”, as shown in bold below. add trunk-group 30 Page 4 of 21 QSIG TRUNK GROUP OPTIONS TSC Method for Auto Callback: always-retain Diversion by Reroute? y Path Replacement? y Path Replacement with Retention? n Path Replacement Method: better-route SBS? n Display Forwarding Party Name? y Character Set for QSIG Name: eurofont QSIG Value-Added? 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



8 of 69 FE-Meridian

Primary D-Channel field, enter the slot number for the DS1 circuit pack from Section 3.1 and port “24”. For the Trunk Group for NCA TSC and Trunk Group for Channel Selection fields, enter the ISDN trunk group number from Section 3.2. For the TSC Supplementary Service Protocol field, enter “b” for QSIG. Enter an appropriately sized non-zero value in the Max number of NCA TSC field. For example, a NCA-TSC is used for Avaya Auto Callback and Nortel Ring Again features. The language “NCA-TSC” or “Non Call Associated Temporary Signaling Connection” is used in various screens, which is similar to QSIG Call-Independent Signaling Connections (CISC). Maintain the default values for the remaining fields, and submit the form. Note that Call Associated TSCs (CA TSCs) are used by Avaya Distributed Communication System (DCS), but are not needed for QSIG.

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: 10 Primary D-Channel: 001V424 Max number of CA TSC: Trunk Group for NCA TSC: 30 Trunk Group for Channel Selection: 30 TSC Supplementary Service Protocol: b 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 3. For the NCA-TSC Trunk Member field, enter a trunk group member number to use for routing of tandem QSIG call independent signaling connections. 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: 23 Send Name: y Send Calling Number: y Used for DCS? n Hop Dgt? n Send EMU Visitor CPN? n Suppress # Outpulsing? n Format: unk-pvt Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Connected Number: y Hold/Unhold Notifications? y 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 Show ANSWERED BY on Display? y



9 of 69 FE-Meridian

Navigate to Page 5 and 6. Enter all 23 ports of the DS1 circuit pack 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:



10 of 69 FE-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. • TSC: “y” (NCA-TSCs will be used) • CA-TSC Request: “none” (since CA-TSC are used for DCS but not for QSIG) • Numbering Format: “unk-unk” (The numbering format and type of number for the Called

Party Number will 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 y none 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 Although shown below in the event that variations of the described configuration are used, the public unknown numbering configuration is not required for these Application Notes, since private numbering is used to construct the numbers. The “change public-unknown-numbering” command may be used to define the format of the calling party number to be sent to Nortel Meridian, if public or unknown numbering is used to construct the numbers. Add an entry for the trunk group defined in Section 3.2. In the bolded rows shown below, all calls originating from a 5-digit extension beginning with 2 and routed to trunk group 30 (or 99 for voice mail) 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 5 2 99 5

Use the “change private-numbering” command, to define the calling party number to be sent to Nortel Meridian, as defined in these Application Notes. Add an entry for the trunk group defined in Section 3.2. In the bolded rows shown below, all calls originating from a 5-digit extension beginning with 2 and routed to trunk group 30 (or 99 for voice mail) will result in the 5-digit calling number to be sent. Submit these changes. change private-numbering 1 Page 1 of 2 NUMBERING - PRIVATE FORMAT Ext Ext Trk Private Total Len Code Grp(s) Prefix Len 5 2 30 5 Total Administered: 2 5 2 99 5 Maximum Entries: 540

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 on, 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 to specify how to route the calls to 45xxx. Enter the following values for the specified fields and retain the default values for the remaining fields. (Entries associated with voice mail, configured in Section 4, can also be observed in the screen below). • Dialed String: The AAR digits to match on, 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: “lev0” for level 0 private numbering

change aar analysis 0 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 25100 5 5 99 lev0 n 25101 5 5 99 lev0 n 45 5 5 30 lev0 n

3.9. System Parameters Features The following screens illustrate the configuration of system level features applicable to the tested configuration. To facilitate the transfer testing in Section 7, the Trunk-to-Trunk Transfer feature was enabled with the value “all”. change system-parameters features Page 1 of 17 FEATURE-RELATED SYSTEM PARAMETERS Self Station Display Enabled? n Trunk-to-Trunk Transfer: all Automatic Callback - No Answer Timeout Interval (rings): 3 Call Park Timeout Interval (minutes): 10 Off-Premises Tone Detect Timeout Interval (seconds): 20 AAR/ARS Dial Tone Required? y Music/Tone on Hold: none Music (or Silence) on Transferred Trunk Calls? no DID/Tie/ISDN/SIP Intercept Treatment: attd Internal Auto-Answer of Attd-Extended/Transferred Calls: transferred Automatic Circuit Assurance (ACA) Enabled? n

Navigate to page 8. In the QSIG/ETSI TSC Extension and QSIG Path Replacement Extension fields, enter an unused extension in the dial plan. In the MWI – Number of Digits Per Voice Mail Subscriber, enter the length of the extensions used. In the sample




configuration, a 5-digit dial plan with matching 5-digit subscriber mailboxes was used. In the Unknown Numbers Considered Internal for AUDIX field, enter “y” and the appropriate length, in this case “5”. In the Network Level field, enter 0. 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? n Path Replacement with Measurements? y QSIG Path Replacement Extension: 24778 Send QSIG Path Replacement Conf. Event to ASAI? y




4. Configuration Associated with Avaya IA770 Optionally, it may be desirable to enable the Nortel station users with voice mail from the Avaya IA770 INTUITY AUDIX Application. The two Nortel station users shown in Figure 1 will have Avaya IA770 voice mail. Reference [IA770] is the product documentation reference for configuring IA770, and this reference was followed to configure the IA770 in the sample configuration. That is, the IA770 configuration is not unique to configurations involving the Nortel Meridian, but a portion of the configuration is included below to aid the understanding of the overall configuration and the verifications in Section 7. The screens are shown using “display” commands to emphasize that while relevant, the configuration is not intended to be prescriptive.

4.1. System Parameters Coverage The following screen illustrates the configuration of system level coverage features applicable to the tested configuration. display system-parameters coverage-forwarding Page 1 of 2 SYSTEM PARAMETERS CALL COVERAGE / CALL FORWARDING CALL COVERAGE/FORWARDING PARAMETERS Local Cvg Subsequent Redirection/CFWD No Ans Interval (rings): 2 Off-Net Cvg Subsequent Redirection/CFWD No Ans Interval (rings): 2 Coverage - Caller Response Interval (seconds): 2 Threshold for Blocking Off-Net Redirection of Incoming Trunk Calls: n Location for Covered and Forwarded Calls: called COVERAGE Keep Held SBA at Coverage Point? n External Coverage Treatment for Transferred Incoming Trunk Calls? n Immediate Redirection on Receipt of PROGRESS Inband Information? n Maintain SBA At Principal? n QSIG VALU Coverage Overrides QSIG Diversion with Rerouting? n Station Hunt Before Coverage? n FORWARDING Call Forward Override? n Coverage After Forwarding? y

4.2. Node Names The following screen illustrates the node names relevant to the configuration. These node names are used in the definition of an “internal” H.323 Signaling Group between the S8300C “procr” interface (e.g., 192.45.100.48) and a unique IP Address also on the S8300C Server, associated with the IA770 messaging application (e.g., 192.45.100.49). display node-names ip Page 1 of 2 IP NODE NAMES Name IP Address ia770 192.45.100.49 procr 192.45.100.48

4.3. Dial Plan Parameters The following screen illustrates the dial plan parameters relevant to the configuration.




display dialplan parameters Page 1 of 1 DIAL PLAN PARAMETERS Local Node Number: 1 ETA Node Number: ETA Routing Pattern: UDP Extension Search Order: local-extensions-first

4.4. Signaling Group for IA770 Messaging The following screen illustrates the H.323 Signaling Group with QSIG supporting the messaging application. In the sample configuration, the Far-end Network Region field was set to a region “2” different than the region associated with the Avaya G450 Media Gateway and associated Avaya telephones, which were in default region 1. Although not necessary, this allowed for different codec set parameters for calls among Avaya IP Telephones, and calls to voice mail. display signaling-group 99 Page 1 of 1 SIGNALING GROUP Group Number: 99 Group Type: h.323 Remote Office? n Max number of NCA TSC: 10 SBS? n Max number of CA TSC: IP Video? n Trunk Group for NCA TSC: 99 Trunk Group for Channel Selection: 99 TSC Supplementary Service Protocol: b Network Call Transfer? n T303 Timer(sec): 10 Near-end Node Name: procr Far-end Node Name: ia770 Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 2 LRQ Required? n Calls Share IP Signaling Connection? y RRQ Required? n Media Encryption? n Bypass If IP Threshold Exceeded? n H.235 Annex H Required? n DTMF over IP: out-of-band Direct IP-IP Audio Connections? y Link Loss Delay Timer(sec): 90 IP Audio Hairpinning? n Enable Layer 3 Test? n Interworking Message: PROGress H.323 Outgoing Direct Media? n DCP/Analog Bearer Capability: 3.1kHz

4.5. Trunk Group for IA770 Messaging The following screen illustrates the H.323 Trunk Group with QSIG supporting the messaging application. display trunk-group 99 Page 1 of 21 TRUNK GROUP Group Number: 99 Group Type: isdn CDR Reports: y Group Name: VoiceMail COR: 1 TN: 1 TAC: 199 Direction: two-way Outgoing Display? n Carrier Medium: H.323 Dial Access? n Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: tie Auth Code? n Member Assignment Method: auto Signaling Group: 99 Number of Members: 8

The following screen shows page 2 of the H.323 trunk group for messaging.




display trunk-group 99 Page 2 of 21 Group Type: isdn TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Charge Advice: none Supplementary Service Protocol: b Digit Handling (in/out): enbloc/enbloc Digital Loss Group: 18 Incoming Calling Number - Delete: Insert: Format: Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 CONNECT Reliable When Call Leaves ISDN? n

The following screen shows page 3 of the H.323 trunk group for messaging. display trunk-group 99 Page 3 of 21 TRUNK FEATURES ACA Assignment? n Measured: none Internal Alert? n Maintenance Tests? y Data Restriction? n NCA-TSC Trunk Member: 1 Send Name: n Send Calling Number: y Used for DCS? n Hop Dgt? n Send EMU Visitor CPN? n Suppress # Outpulsing? n Format: private UUI IE Treatment: service-provider Replace Restricted Numbers? n Replace Unavailable Numbers? n Send Called/Busy/Connected Number: y Hold/Unhold Notifications? y Send UUI IE? y Modify Tandem Calling Number? n Send UCID? n Send Codeset 6/7 LAI IE? y

The following screen shows the QSIG parameters on page 4 of the H.323 trunk group used for messaging. display trunk-group 99 Page 4 of 21 QSIG TRUNK GROUP OPTIONS TSC Method for Auto Callback: drop-if-possible Diversion by Reroute? y Path Replacement? y Path Replacement with Retention? n Path Replacement Method: better-route SBS? n Display Forwarding Party Name? y Character Set for QSIG Name: eurofont QSIG Value-Added? y QSIG-Value Coverage Encoding: proprietary




4.6. Routing Pattern for IA770 Messaging The following screen shows the route-pattern containing the trunk group used for messaging. display route-pattern 99 Page 1 of 3 Pattern Number: 99 Pattern Name: VoiceMail 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: 99 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 y none rest rehu 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

4.7. Hunt Group for Messaging The following screen shows the hunt group used for messaging. Avaya and Nortel users may dial the hunt group extension to reach the IA770 to retrieve voice mail. Calls can redirect to this number for voicemail answering services. display hunt-group 99 Page 1 of 60 HUNT GROUP Group Number: 99 ACD? n Group Name: IA770 Queue? n Group Extension: 25101 Vector? n Group Type: ucd-mia Coverage Path: TN: 1 Night Service Destination: COR: 1 MM Early Answer? n Security Code: Local Agent Preference? n

In this example, note that the hunt group extension is different than the Voice Mail Number on page 2. Although the feature access code screen is not shown, the digit “8” is the AAR access code in the configuration. A call to the hunt group extension 25101 will generate a call to 8-25100, based on the configuration shown below. In the sample configuration, a Nortel user could dial 25100 or 25101 to reach the IA770 voice mail, via incoming trunk group digit mapping to be illustrated subsequently.




display hunt-group 99 Page 2 of 60 HUNT GROUP LWC Reception: none AUDIX Name: Message Center: qsig-mwi Send Reroute Request: y Voice Mail Number: 25100 Routing Digits (e.g. AAR/ARS Access Code): 8 Provide Ringback? n TSC per MWI Interrogation? n

4.8. AAR Analysis Entries for Messaging The following screen bolds the AAR Analysis entries relevant to voice messaging. display aar analysis 0 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 25100 5 5 99 lev0 n 25101 5 5 99 lev0 n 45 5 5 30 lev0 n

4.9. Coverage Path for Messaging The following screen shows an example coverage path that has a point in coverage for the voice messaging hunt group 99. Although not shown, Avaya station users, such as stations 24001 and 24000, are assigned this coverage path. display coverage path 99 Page 1 of 1 COVERAGE PATH Coverage Path Number: 99 Cvg Enabled for VDN Route-To Party? n Hunt after Coverage? n Next Path Number: Linkage COVERAGE CRITERIA Station/Group Status Inside Call Outside Call Active? n n Busy? y y Don't Answer? y y Number of Rings: 2 All? n n DND/SAC/Goto Cover? y y Holiday Coverage? n n COVERAGE POINTS Terminate to Coverage Pts. with Bridged Appearances? n Point1: h99 Rng: Point2: Point3: Point4: Point5: Point6:

4.10. AAR and ARS Digit Conversion The following screen shows ARS digit-conversion entries that may be used if public numbering is used. This is not required in the sample configuration. Nortel is sending private numbering to Avaya for extension-dialed (CDP) calls.




display ars digit-conversion 0 Page 1 of 2 ARS DIGIT CONVERSION TABLE Location: all Percent Full: 0 Matching Pattern Min Max Del Replacement String Net Conv ANI Req 2 5 5 0 ext y n

The following screen shows AAR digit-conversion entries used in the tested configuration. display aar digit-conversion 0 Page 1 of 2 AAR DIGIT CONVERSION TABLE Location: all Percent Full: 0 Matching Pattern Min Max Del Replacement String Net Conv ANI Req 0 1 28 0 ars y n 1 4 28 0 ars y n 2 5 5 0 ext y n x11 3 3 0 ars y n

4.11. Incoming Call Handling Treatment for Messaging The following screen shows incoming call handling treatment for trunk group 30, the trunk group to the Nortel Meridian. With this configuration, Nortel station users may dial either 25101, the voicemail hunt group extension, or 25100, the voice mail number on page 2 of the voice mail hunt group 99, to reach the IA770. The form below matches on an incoming number of 25100 and replaces the number with 25101. The Nortel configuration for the redirection number on no-answer or busy, can use either 25100 or 25101. The Nortel configuration inherited from reference [KB] and [KB2] already used 25100, so 25100 was retained for these Application Notes, along with the configuration below to effect the digit mapping to 25101. display inc-call-handling-trmt trunk-group 30 Page 1 of 3 INCOMING CALL HANDLING TREATMENT Service/ Called Called Del Insert Per Call Night Feature Len Number CPN/BN Serv tie 5 25100 all 25101

4.12. Administer Subscriber Extension Ranges Access the IA770 web interface by using the URL “http://ip-address” in an Internet browser window, where “ip-address” is the IP address of the S8300C Server. Log in. Follow the steps detailed in reference [IA770]. The following screen shows a portion of the window where the “change machine” command was executed via Messaging Administration Messaging. This example shows the starting and ending extensions used in the sample configuration.




4.13. Administer Subscriber Mailboxes for Nortel and Avaya Users The following screen shows a portion of the window where the “add subscriber 45001” command was executed via Messaging Administration Messaging. This example shows one of the Meridian station extensions being configured as an Avaya IA770 subscriber. The same command is run for each subscriber.




5. Configure Nortel Meridian This section focuses on the relevant Nortel Meridian configuration, including the T1 ISDN-PRI QSIG trunks on Nortel Meridian and routing of the Coordinated Dial Plan numbers to reach Avaya Communication Manager. In addition, this section highlights feature parameters that allow the Nortel station users to use the Avaya IA770 for voice messaging services. The Nortel Meridian configuration used in the testing of these Application Notes is essentially the same configuration previously documented in reference [KB2]. 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.

5.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. >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. The QSIG-related packages (263, 305, 316) can be observed along with other packages used in these Application Notes. REQ prt TYPE pkg ……………………………… DDSP 19 ……………………………… NARS 58 CDP 59 ……………………………… PBXI 75 ……………………………… CPND 95 ……………………………… ISDN 145 PRA 146 ISL 147 ……………………………… PRI2 154 ……………………………… FNP 160 ISDN INTL SUP 161 ……………………………… GPRI 167 ……………………………… OVLP 184 ……………………………… IPRA 202 ……………………………… QSIG 263 ……………………………… QSIGGF 305 ……………………………… QSIG-SS 316

5.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. 7. At the PINX_DN prompt, type “45999” (or unused DN in the numbering block allotted

to the Nortel Meridian, which is 45XXX in these Application Notes).

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

8. Enter “ld 17” for Overlay 17. 9. At the REQ prompt, type “chg” and Enter. 10. At the Type prompt, type “cequ” and Enter. 11. Press Enter until the DLOP prompt appears. 12. At the DLOP prompt, enter “1 23 ESF”. This defines card 1 to use 23 channels and ESF

framing. 13. At the MODE prompt, type “PRI”. 14. At the TMDI prompt, type “YES”. 15. Press Enter until the TITE prompt appears. 16. At the TITE prompt, type “01”. 17. At the TRSH prompt, type “00”. Threshold Group 00, defined in load 73, is applied.

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

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

Channel number. 22. At the CTYP prompt, type “TMDI” and press Enter. 23. At the CDNO prompt, type “1” and press Enter (for the TMDI card in slot 1). 24. At the DES prompt, type an appropriate text description, such as “AvayaQsig”. 25. At the USR prompt, type “PRI” and press Enter. 26. At the IFC prompt, type “ISGF” and press Enter. 27. At the PINX_CUST prompt, type “0” (or appropriate customer number) and press Enter. 28. Press Enter until the DCHL prompt appears. 29. At the DCHL prompt, type “1” and press Enter. 30. Press Enter until the DRAT prompt appears. 31. At the DRAT prompt, type “64KC” and press Enter (to match the MM710). 32. At the SIDE prompt, type “net” and press Enter. (The Avaya side is slave). 33. Press Enter until the RCAP prompt appears. 34. At the RCAP prompt, type “COLP NDI CCBI CCNI PRI DV3I CTI QMWI” and Enter. 35. At the RCAP prompt, press Enter. See the bullet list below for RCAP descriptions. 36. At the PR_TRIGS prompt, type “div 3 1” and press Enter. Diversion may be used to

trigger path replacement. 37. At the PR_TRIGS prompt, type “cng 3 1” and press Enter. Congestion may be used to

trigger path replacement. 38. At the PR_TRIGS prompt, type “con 3 1” and press Enter. A connected number different

from a called number may be used to trigger path replacement. 39. At the PR_TRIGS prompt, type “ctr2 3 1” and press Enter. Call transfer is used to trigger

path replacement. The path replacement proposal will be triggered by the secondary end




of transfer. (Note that Avaya does not make this primary-secondary distinction. Instead, a randomized timer is started at both ends, and the side whose timer expires first sends the path replacement proposal.)

40. At the PR_TRIGS prompt, press Enter. The RCAP or “Remote Capabilities Configuration” listed in the command above corresponds to the following capabilities: • Call completion to busy subscriber using integer value (CCBI) • Call completion on no response using integer value (CCNI) • Connected line identification presentation (COLP) • Call transfer using integer value (CTI) • Diversion information sent, rerouting requests processed (DV3I) • Name display – integer ID coding (NDI) • Path replacement uses integer values (PRI) • Message waiting indication using integer values (QMWI)

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

41. Enter Overlay 16 using “ld 16”. 42. At the REQ prompt, type “new” and Enter. 43. At the TYPE prompt, type “rdb” and Enter. 44. At the CUST prompt, type “0” (or appropriate customer number). 45. At the ROUT prompt, type “51” and Enter (for new route 51). 46. At the DES prompt, enter appropriate descriptive text for this route. 47. At the TKTP prompt, type “TIE” and Enter. 48. At the RCLS prompt, type “ext” and Enter. 49. At the DTRK prompt, type “yes” and Enter. 50. At the DGTP prompt, type “PRI” and Enter. 51. At the ISDN prompt, type “YES” and Enter. 52. At the MODE prompt, type “PRA” and Enter. 53. At the IFC prompt, type “ISGF” and Enter. 54. At the CHTY prompt, type “BCH” and Enter. 55. At the CTYP prompt, type “UKWN” and Enter. 56. At the DSEL prompt, type “VOD” and Enter. 57. At the PTYP prompt, type “PRI” and Enter. 58. At the ICOG prompt, type “IAO” and Enter (for incoming and outgoing). 59. At the TRMB prompt, type “YES” and Enter (allowing an incoming call to be routed

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

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




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

common characteristics. 63. At the TYPE prompt, type “tie” and Enter. 64. At the TN prompt, type “1 1” and Enter. (Enter the TMDI slot number and port 1). 65. At the DES prompt, enter an appropriate text description such as “Avayaqsig”. 66. At the CUST prompt, type “0” and Enter (or appropriate customer number). 67. At the RTMB prompt, type “51 1” and press Enter. This assigns the route members from

route 51 previously created in load 16.

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

68. Enter Overlay 86 using “ld 86”. 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 “rlb” and Enter. 72. At the RLI prompt, type “4” and Enter. (This is route list index 4). 73. At the ENTR prompt, type “0” and Enter. 74. At the ROUT prompt, type “51” and Enter.

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

75. Enter Overlay 87 using “ld 87”. 76. At the REQ prompt, type “new” and Enter. 77. At the CUST prompt, type “0” and Enter (or appropriate customer number). 78. At the FEAT prompt, type “cdp” and Enter. 79. At the TYPE prompt, type “dsc” and Enter. (This is for “distant steering code”). 80. At the DSC prompt, type “24” and Enter. (This is for leading digits 24 in 24xxx) 81. At the FLEN prompt, type “5” and Enter. (5 digit extensions beginning with 24) 82. At the DSP prompt, type “lsc” and Enter. 83. At the RLI prompt, type “4” and Enter. (This corresponds to route list index 4 created

previously) Repeat the steps listed above, substituting “25” for “24” in the “DSC” prompt to create an entry matching dialed digits of the form 25xxx.

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

84. Enter load 60 using “ld 60”.




85. Type “enll 1” and Enter.

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

86. Enter load 96 using “ld 96”. 87. Type “enl dch 17” and Enter. 88. 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.)

5.11. Configure Parameters for Nortel Station Users This section contains information relevant to configuring Nortel station users to use Avaya IA770 messaging, and for general understanding of the verifications in Section 7. The steps shown below use “new” to add a station. Use “chg” to edit an existing station. Unless noted, press Enter at unmentioned prompts.

89. Enter Overlay 11 using “ld 11”. 90. At the REQ prompt, type “new” and Enter. 91. At the TYPE prompt, type “3904” and Enter. (Station type 3904 is used in the testing). 92. At the TN prompt, type “5 1” and Enter. (or appropriate physical location of station) 93. At the DES prompt, type “USER” and Enter. 94. At the CUST prompt, type “0” and Enter (or appropriate customer number). 95. At the FDN prompt, type “25100” and Enter. This is the flexible call forwarding no

answer destination. (This matches configuration from reference [KB2]. In these Application Notes, either “25100” or “25101” would work, where 25101 is the Avaya IA770 hunt group extension, and 25100 are the AAR routed digits associated with the hunt group. The incoming call handling treatment for the Avaya trunk group has been configured to match on 25100 and substitute 25101)

96. At the CLS prompt, type “mwa cnda” and Enter. (Allow message waiting indicator, and display of calling party name.) Other CLS options can be configured that will affect the displays for the call examples shown in Section 7. 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 party’s number and name), FNA (Call forward no answer allowed), HTA (hunting allowed), CFXA (call forward to external DN allowed).

97. At the HUNT prompt, type “25100” and Enter. (to “25100” or “25101” as above). 98. At the KEY prompt, type “00 scr 45001” and Enter. (User’s station extension is 45001) 99. At the CPND prompt, type “new” and Enter. 100. At the NAME prompt, type “Joe Arias” and Enter. (Type the name of the user) 101. At the XPLN prompt, type “9” (or appropriate length) and Enter. 102. At the DISPLAY_FMT prompt, type “first,last” and Enter. 103. At the KEY prompt, type “16 mwk 25100” and Enter. This enables message

waiting indication on button 16.




104. At the KEY prompt, type “20 RGA” and Enter (for ring again feature).

5.12. Configure Call Party Name Display Data Block This section contains information relevant to the displays observed for Nortel telephones, as detailed in Section 7. Unless noted, press Enter at unmentioned prompts.

105. Enter Overlay 95 using “ld 95”. 106. At the REQ prompt, type “chg” and Enter. 107. At the TYPE prompt, type “CPND” and Enter. 108. At the CUST prompt, type “0” and Enter (or appropriate customer number). 109. At the RESN prompt, type “YES” and Enter. (Display redirection reasons are

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

display). 111. At the CFNA prompt, type “RNA” (or desired “call forward no answer” display). 112. At the HUNT prompt, type “BSY” (or desired “call forward busy” display) 113. At the XFER prompt, type “T” (or desired “call transfer” display).

6. Simple Verifications This section illustrates basic commands that can be run to ascertain whether the trunks are ready to handle calls. The next section contains detailed call flows and nuanced verifications.

6.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 (1v201) 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”. In the sample configuration, Avaya used a cyclical trunk hunt for calls to Nortel Meridian. status trunk 30 Page 1 TRUNK GROUP STATUS Member Port Service State Mtce Connected Ports Busy 0030/001 001V401 in-service/idle no 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/active no 001V201 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). 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 001V202

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

6.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 TIE 3VCE * CH 02 - IDLE TIE 3VCE * CH 03 - IDLE TIE 3VCE * CH 04 - IDLE TIE 3VCE * CH 05 - IDLE TIE 3VCE * CH 06 - IDLE TIE 3VCE * CH 07 - IDLE TIE 3VCE * CH 08 - IDLE TIE 3VCE * CH 09 - IDLE TIE 3VCE * CH 10 - IDLE TIE 3VCE * CH 11 - IDLE TIE 3VCE * CH 12 - IDLE TIE 3VCE * CH 13 - IDLE TIE 3VCE * CH 14 - IDLE TIE 3VCE * CH 15 - IDLE TIE 3VCE * CH 16 - IDLE TIE 3VCE * CH 17 - IDLE TIE 3VCE * CH 18 - IDLE TIE 3VCE * CH 19 - IDLE TIE 3VCE * CH 20 - IDLE TIE 3VCE * CH 21 - IDLE TIE 3VCE * CH 22 - IDLE TIE 3VCE * CH 23 - IDLE TIE 3VCE * 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 10). .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 TIE 3VCE * CH 02 - IDLE TIE 3VCE * CH 03 - IDLE TIE 3VCE * CH 04 - IDLE TIE 3VCE * CH 05 - IDLE TIE 3VCE * CH 06 - IDLE TIE 3VCE * CH 07 - IDLE TIE 3VCE * CH 08 - IDLE TIE 3VCE * CH 09 - IDLE TIE 3VCE * CH 10 - BUSY TIE 3VCE * CH 11 - IDLE TIE 3VCE * CH 12 - IDLE TIE 3VCE * CH 13 - IDLE TIE 3VCE * CH 14 - IDLE TIE 3VCE * CH 15 - IDLE TIE 3VCE * CH 16 - IDLE TIE 3VCE * CH 17 - IDLE TIE 3VCE * CH 18 - IDLE TIE 3VCE * CH 19 - IDLE TIE 3VCE * CH 20 - IDLE TIE 3VCE * CH 21 - IDLE TIE 3VCE * CH 22 - IDLE TIE 3VCE * CH 23 - BUSY TIE 3VCE * CH 24 - DCH 17

Another example output is shown below using “ld 20” to print information about a particular trunk member, in this case, member 1. >ld 20 PT0000 REQ: prt TYPE: trk TN 1 1 DATE PAGE DES AVAYAQSIG TN 001 01 TYPE TIE CDEN SD CUST 0 TRK PRI PDCA 1 PCML MU NCOS 0 RTMB 51 1 B-CHANNEL SIGNALING TGAR 1 AST NO IAPG 0 CLS CTD DIP CND WTA LPR APN THFD HKD P10 VNL TKID




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 AvayaQsigSIG USR PRI DCHL 1 OTBF 32 PARM RS232 DTE DRAT 64KC ………………………………………………………………… IFC ISGF PINX_CUST 0 ISDN_MCNT 300 CLID OPT0 CO_TYPE STD SIDE NET CNEG 1 RLS ID ** RCAP COLP NDI CCBI CCNI PRI DV3I CTI QMWI PR_TRIGS DIV 3 1 CNG 3 1 CON 3 1 CTR2 3 1 PR_RTN NO MBGA NO OVLR NO OVLS NO T310 120 T200 3 T203 10 N200 3 N201 260 K 7




7. Call Flow Verifications This section illustrates sample results obtained with the tested configuration. While it is not practical to illustrate all possible call scenarios, a representative sampling of calls is included as a reference. The observations in this section include observed displays and Avaya trace command output, to aid in understanding and troubleshooting. 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.

7.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 “Joe Arias”. Upon answer by the called user, the Avaya telephone display updates to show “Joe Arias 45001”. As a general note, if Avaya encodes the type of number as “private” rather than “unknown”, the Nortel user would see an “H” in front of the number, such as “H45001”. In the configuration described in these Application Notes, the Avaya configuration sends “unknown” numbering toward the Nortel Meridian. The Nortel called telephone displays “Victor Yee” and “24001” during the ringing and connected phases of the call. 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. list trace tac 130 Page 1 LIST TRACE time data 11:48:32 dial 45001 route:UDP|AAR 11:48:32 term trunk-group 30 cid 0x50 11:48:32 dial 45001 route:UDP|AAR 11:48:32 route-pattern 30 preference 1 cid 0x50 11:48:32 seize trunk-group 30 member 7 cid 0x50 11:48:32 Calling Number & Name 24001 Victor Yee 11:48:32 Proceed trunk-group 30 member 7 cid 0x50 11:48:32 Alert trunk-group 30 member 7 cid 0x50 11:48:42 active trunk-group 30 member 7 cid 0x50

7.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 “45001” during the ringing and connected phases of the call. The Nortel calling telephone displays “Victor Yee” and “24001” during the ringing and connected phases of the call. The following capture of “list trace” shows the activity on the ISDN trunk group for this incoming call to Avaya from trunk group 30. 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 11:56:02 Calling party trunk-group 30 member 23 cid 0x60 11:56:02 Calling Number & Name 45001 Joe Arias 11:56:02 active trunk-group 30 member 23 cid 0x60 11:56:02 dial 24001 11:56:02 ring station 24001 cid 0x60 11:56:09 active station 24001 cid 0x60

7.3. Avaya Telephone With Call Forwarding Active, Examples This section pertains to cases where an Avaya telephone has activated call forwarding, and subsequently receives an incoming call. Example: Avaya station call forwarded to Avaya station, call from Nortel station Assume Avaya station 24001 activates call forwarding-all calls to Avaya station 24000, whose name is “Tom Chu”. Nortel telephone 45001 dials 24001. The ringing Avaya forwarded-to telephone displays “Joe Arias to Victor Yee f” during the ringing and connected phases of the call. This is a typical Avaya redirected display, where the display shows the name of the caller, the name of the originally called party, and the reason for redirection, in this case “f” for call forwarding. While the forwarded-to station 24000 is ringing, the Nortel calling telephone displays “Tom Chu” (the name of the forwarded-to party) and “24001 ------ “CFWD””. When the call is answered by station 24000, the display updates to “Tom Chu” and “24001 24000 “CFWD””. The order of the numbers corresponds to the dialed number (24001), the answering number (24000), and the reason for redirection “CFWD”. The following capture of “list trace” shows the activity on the ISDN trunk group for this call. The call forwarding of the call matching the description above can be observed.




list trace tac 130 Page 1 LIST TRACE time data 12:01:42 Calling party trunk-group 30 member 23 cid 0x6c 12:01:42 Calling Number & Name 45001 Joe Arias 12:01:42 active trunk-group 30 member 23 cid 0x6c 12:01:42 dial 24001 12:01:42 term station 24001 cid 0x6c 12:01:42 call-forwarding 24000 12:01:42 ring station 24000 cid 0x6c 12:01:52 active station 24000 cid 0x6c 12:01:59 idle trunk-group 30 member 23 cid 0x6c

The following capture of “list trace tac 130/Q” shows some of the QSIG activity on the trunk group for this same type of call. list trace tac 130/Q Page 1 LIST TRACE time data 12:08:31 QSIG>out DV_L1 Invk 24000 invkid 0x59 12:08:31 QSIG>out DV_L3 Invk =6 invkid 0x5b 12:08:36 QSIG>out DV_L3 Invk =6 invkid 0x5d

Example: Avaya station call forwarded to Nortel station, call from Avaya station In this next example, assume Avaya station 24001 activates call forwarding-all calls to Nortel telephone 45001. Avaya telephone 24000 dials 24001. The Nortel forwarded-to telephone displays the name of the caller “Tom Chu” and “24000 24001 “CFWD””. The order of the numbers corresponds to the caller (24000), the originally called party (24001), and the reason for redirection “CFWD”. The Avaya caller’s display is “Joe Arias forward”. The following capture of “list trace station 24000” illustrates the flow of this call. list trace station 24000 Page 1 LIST TRACE time data 12:19:46 active station 24000 cid 0x9c 12:19:49 dial 24001 12:19:49 term station 24001 cid 0x9c 12:19:49 dial 45001 route:UDP|AAR 12:19:49 term trunk-group 30 cid 0x9c 12:19:49 call-forwarding 45001 12:19:49 route-pattern 30 preference 1 cid 0x9c 12:19:49 seize trunk-group 30 member 12 cid 0x9c 12:19:49 Calling Number & Name 24000 Tom Chu 12:19:49 Proceed trunk-group 30 member 12 cid 0x9c 12:19:49 Alert trunk-group 30 member 12 cid 0x9c 12:19:55 active trunk-group 30 member 12 cid 0x9c

The following capture of “list trace tac 130/Q” shows some of the QSIG activity on the trunk group for this same type of call.




list trace tac 130/Q Page 1 LIST TRACE time data 13:25:53 QSIG>out DV_L2 Invk 24001 invkid 0x79 13:25:53 QSIG>out DV_L2 Invk 24001 invkid 0x79 13:25:53 QSIG<in DV_L3 Invk 56 invkid 0x1

Example: Avaya station call forwarded to Nortel station, call from Nortel station In this next example, assume Avaya station 24001 still has call forwarding-all calls to Nortel telephone 45001. However, in this case, Nortel telephone 45002 dials 24001. The Nortel forwarded-to telephone displays the name of the caller “Khoa Bui” and “45002 24001 “CFWD””. The order of the numbers corresponds to the caller (45002), the originally called party (24001), and the reason for redirection “CFWD”. In the ringing phase, the Nortel calling telephone does not display a name, but displays “24001 45001 “CFWD””. The order of the numbers corresponds to the dialed number (24001), the forwarded-to number (45001), and the reason for redirection “CFWD”. Upon answering the call at station 45001, the numbers on the calling Nortel display remain the same, and the display updates with “Joe Arias”, the name of the answering party. The following capture of “list trace” illustrates the flow of this call. Observe that the trunk is idled at the same time as the call arrival. Since this call came in from Nortel, and was forwarded back to Nortel, the trunk was no longer required and was released. While this call was active (Nortel user 45001 talking to Nortel user 45002), no trunks from trunk group 30 were in use. list trace tac 130/q Page 1 LIST TRACE time data 13:32:36 Calling party trunk-group 30 member 23 cid 0xf8 13:32:36 Calling Number & Name 45002 Khoa Bui 13:32:36 active trunk-group 30 member 23 cid 0xf8 13:32:36 QSIG>out DV_RR Invk 45001 invkid 0x80 13:32:36 call-forwarding 24001 13:32:36 term station 24001 cid 0xf8 13:32:36 QSIG<in DV_RR Result invkid 0x80 13:32:36 idle trunk-group 30 member 23 cid 0xf8

The following capture of “list trace tac 130/Q” shows some of the QSIG activity on the trunk group for this same type of call. The “Diversion by Reroute” field on the ISDN Trunk Group form (page 4, trunk group 30) is set to “y”, and Diversion by Reroute is used to release the trunks in this case.




list trace tac 130/Q Page 1 LIST TRACE time data 12:29:49 QSIG>out DV_RR Invk 45001 invkid 0x7b 12:29:50 QSIG<in DV_RR Result invkid 0x7b

Example: Avaya Special Application SA8623 Enabling Chained Call Forwarding

If it is desired to allow a previously forwarded call to be forwarded again, as part of a “chain”, then Avaya Special Application SA8623 may be activated via the license file. The relevant Special Application is shown in the screen below. display system-parameters special-applications Page 5 of 8 SPECIAL APPLICATIONS (SA8622) - Enhanced Call Pickup Alerting? n (SA8623) - Chained Call Forwarding? y

As an example, assume station B has call forwarding active to station C, and station C has call forwarding active to station D. Without SA8623 enabled, if a user A (Nortel or Avaya) were to call station B, the call would ring at station C. With SA8623 enabled, such a call would ring at station D, since station C is also forwarded and chained call forwarding is allowed. Chained call forwarding for an incoming call from a Nortel user was verified successfully in the sample configuration. In the sample configuration, the Nortel Meridian also allowed chained call forwarding for calls to Nortel users. It was verified that “hop count” enforcement prevents excessive forwarding of the same call back and forth among Avaya and Nortel users with forwarding active.

7.4. Nortel Telephone With Call Forwarding Active, Examples This section pertains to cases where a Nortel telephone has activated call forwarding, and subsequently receives an incoming call. Example: Nortel station call forwarded to Nortel station, call from Avaya station Assume Nortel station 45002 activates call forwarding-all calls to Nortel station 45001, whose name is “Joe Arias”. Avaya telephone 24001 dials 45002. The following capture of “list trace” shows the activity on the ISDN trunk group for the outgoing call from 24001 to 45002. Note that the trunk member 14 used for this call is idled at the conclusion of this trace activity.




list trace tac 130 Page 1 LIST TRACE time data 16:21:17 dial 45002 route:UDP|AAR 16:21:17 term trunk-group 30 cid 0x22b 16:21:17 dial 45002 route:UDP|AAR 16:21:17 route-pattern 30 preference 1 cid 0x22b 16:21:17 seize trunk-group 30 member 14 cid 0x22b 16:21:17 Calling Number & Name 24001 Victor Yee 16:21:17 Proceed trunk-group 30 member 14 cid 0x22b 16:21:17 Alert trunk-group 30 member 14 cid 0x22b 16:21:25 active trunk-group 30 member 14 cid 0x22b 16:21:28 idle trunk-group 30 member 14 cid 0x22b

The end-user call remains up using a different trunk member. As can be seen in the following screen, the call remains up using trunk member 23. 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 001V202

The following capture of “list trace tac 130/Q” shows some of the QSIG “path replacement” activity on the trunk group for this same type of call. list trace tac 130/Q Page 1 LIST TRACE time data 16:28:17 QSIG<in DV_L1 Invk 45001 invkid 0x1 16:28:17 QSIG<in DV_L3 Invk 56 invkid 0x2 16:28:39 QSIG>out PR_PRO Invk 24001 invkid 0x8d 16:28:39 QSIG<in PR_SET Invk invkid 0x1 16:28:39 QSIG>out PR_SET Result invkid 0x1

The following capture of “list trace tac 130/q” shows another method of receiving QSIG-related activity, interspersed with traditional trunk trace information, for this same type of call.




list trace tac 130/q Page 1 LIST TRACE time data 16:30:30 dial 45002 route:UDP|AAR 16:30:30 term trunk-group 30 cid 0x23e 16:30:30 dial 45002 route:UDP|AAR 16:30:30 route-pattern 30 preference 1 cid 0x23e 16:30:30 seize trunk-group 30 member 16 cid 0x23e 16:30:30 Calling Number & Name 24001 Victor Yee 16:30:30 Proceed trunk-group 30 member 16 cid 0x23e 16:30:30 QSIG<in DV_L1 Invk 45001 invkid 0x1 16:30:30 QSIG<in DV_L3 Invk 56 invkid 0x2 16:30:30 Alert trunk-group 30 member 16 cid 0x23e 16:30:46 active trunk-group 30 member 16 cid 0x23e 16:30:54 QSIG>out PR_PRO Invk 24001 invkid 0x8f 16:30:54 QSIG>out PR_SET Result invkid 0x1 16:30:54 idle trunk-group 30 member 16 cid 0x23e

Finally, the following capture of “list trace tac 130/q” was started AFTER the forwarded-to party had answered the call. The trace information looks similar to a fresh incoming call from the Nortel Meridian, and shows the use of trunk member 23. list trace tac 130/q Page 1 LIST TRACE time data 16:41:35 Calling party trunk-group 30 member 23 cid 0x25a 16:41:35 Calling Number & Name 45001 Joe Arias 16:41:35 active trunk-group 30 member 23 cid 0x25a 16:41:35 dial 24000 16:41:35 term station 24000 cid 0x25a

While ringing, the Avaya calling telephone displays the dialed number “45002 forward”. In the steady-state (not immediately upon answer by the forwarded-to telephone at 45001, but rather after the QSIG procedures move the call to trunk 23) the Avaya display updates with "Joe Arias 45001" (similar to the display for a direct incoming call as would be expected from the final trace above). The forwarded-to Nortel telephone 45001 displays "Victor Yee" (the name of the Avaya caller) and "24001 45002 “CFWD”". Example: Nortel station call forwarded to Avaya station, call from Nortel station Assume Nortel station 45002, whose name is “Khoa Bui”, activates call forwarding-all calls to Avaya station 24001, whose name is “Victor Yee”. Nortel telephone 45001, whose name is “Joe Arias”, dials 45002. The following capture of “list trace” shows the activity on the ISDN trunk group used for the incoming call from Nortel. Once again, note that trunk member 23 used for this call is idled at the conclusion of this trace activity.




list trace tac 130/q Page 1 LIST TRACE time data 16:49:45 Calling party trunk-group 30 member 23 cid 0x268 16:49:45 Calling Number & Name 45001 Joe Arias 16:49:45 active trunk-group 30 member 23 cid 0x268 16:49:45 QSIG>out DV_L3 Invk 3647,627 invkid 0x98 16:49:45 dial 24001 16:49:45 ring station 24001 cid 0x268 16:49:55 no answer station 24001 cid 0x268 16:49:55 coverage-path 0 point 0 cid 0x268 16:49:57 QSIG>out DV_L3 Invk 3647,627 invkid 0x9a 16:49:57 active station 24001 cid 0x268 16:50:05 QSIG>out PR_PRO Invk 24001 invkid 0x9c 16:50:05 QSIG>out PR_SET Result invkid 0x1 16:50:05 idle trunk-group 30 member 23 cid 0x268

The end-user call remains up using a different trunk member. As can be seen in the following screen, the call remains up using trunk member 22. 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/active no 001V202 0030/023 001V423 in-service/idle no

The following screen captures another type of call trace for this same type of call. list trace tac 130/Q Page 1 LIST TRACE time data 16:57:04 QSIG<in DV_L2 Invk invkid 0x1 16:57:04 QSIG<in DV_L2 Invk 45002 invkid 0x1 16:57:04 QSIG>out DV_L3 Invk 3647,627 invkid 0xa7 16:57:35 QSIG>out DV_L3 Invk 3647,627 invkid 0xa9 16:57:38 QSIG>out PR_PRO Invk 24001 invkid 0xab 16:57:38 QSIG<in PR_SET Invk invkid 0x1 16:57:38 QSIG>out PR_SET Result invkid 0x1

Finally, the following capture of “list trace tac 130/q” was started AFTER the forwarded-to party had answered this same type of call. The trace information looks similar to a fresh incoming call from the Nortel Meridian, and shows the use of trunk member 22.




list trace tac 130/q Page 1 LIST TRACE time data 16:55:27 Calling party trunk-group 30 member 22 cid 0x276 16:55:27 Calling Number & Name 45001 Joe Arias 16:55:27 active trunk-group 30 member 22 cid 0x276 16:55:27 dial 24001 16:55:27 term station 24001 cid 0x276

While ringing, the Avaya forwarded-to telephone displays "Joe Arias to Khoa Bui f". This is “calling name” to “called name” and “f” for forwarding. For several seconds after answering, the Avaya forwarded-to phone continues to display "Joe Arias to Khoa Bui f". In the steady state of the active call, the Avaya telephone displays "Joe Arias 45001 f". While ringing, the calling Nortel telephone (45001) displays “45002 H----- "CFWD"” Upon answer by Avaya telephone 24001, the display updates to “45002 24001 "CFWD"”. Example: Nortel station call forwarded to Avaya station, call from Avaya station In the next example call flow, assume Nortel station 45002, whose name is “Khoa Bui”, still has call forwarding-all calls to Avaya station 24001, whose name is “Victor Yee”. Now, Avaya telephone 24000, whose name is “Tom Chu”, dials 45002. The following capture of “list trace” shows the activity on the ISDN trunk group. list trace tac 130/q Page 1 LIST TRACE time data 16:19:19 dial 45002 route:UDP|AAR 16:19:19 term trunk-group 30 cid 0x43 16:19:19 dial 45002 route:UDP|AAR 16:19:19 route-pattern 30 preference 1 cid 0x43 16:19:19 seize trunk-group 30 member 4 cid 0x43 16:19:19 Calling Number & Name 24000 Tom Chu 16:19:19 Proceed trunk-group 30 member 4 cid 0x43 16:19:19 QSIG<in DV_L1 Invk 24001 invkid 0x1 16:19:19 QSIG<in DV_L3 Invk 001 invkid 0x8 16:19:19 Alert trunk-group 30 member 4 cid 0x43 16:19:26 QSIG<in DV_L3 Invk invkid 0xa 16:19:26 active trunk-group 30 member 4 cid 0x43 16:19:27 QSIG<in PR_PRO Invk 24001 invkid 0xc

The end-user call remains up, and no trunk member from trunk group 30 is required. That is, since the final connection is from an Avaya telephone to an Avaya telephone, the trunks have been released. The following is an annotated trace of this same type of call, showing the QSIG path replacement.




list trace tac 130/Q Page 1 LIST TRACE time data 13:49:45 QSIG<in DV_L2 Invk invkid 0x1 13:49:45 QSIG<in DV_L2 Invk 45002 invkid 0x1 13:49:45 QSIG<in DV_L1 Invk 24001 invkid 0x1 13:49:45 QSIG>out DV_L3 Invk 3647,627 invkid 0xab 13:49:45 QSIG<in DV_L3 Invk 001 invkid 0xab /* The above five messages are seen at time of ringing */ 13:49:49 QSIG>out DV_L3 Invk 3647,627 invkid 0xad 13:49:49 QSIG<in DV_L3 Invk 001 invkid 0xad /* The above two messages appear upon answer */ 13:49:52 QSIG>out PR_PRO Invk 24001 invkid 0xaf 13:49:52 QSIG<in PR_PRO Invk 24001 invkid 0xaf /* The above two appear several seconds after answer */

While the call is ringing, the Avaya caller (24000) sees: “45002 forward”. While the call is ringing, the forwarded-to Avaya telephone (24001) sees: “Tom Chu to Khoa Bui f”. Upon answer of the call at 24001, the Avaya caller briefly sees “Victor Yee forward”. In the steady state (after path replacement), the Avaya caller sees: “Victor Yee 24001”.

7.5. Avaya Telephone Following Call Coverage, Examples This section pertains to cases where a call to an Avaya telephone meets the “coverage criteria” and the call follows the user’s coverage path. The user’s coverage path does not take the call to voice mail. Voice mail cases are covered in Section 7.8. Example: Avaya station call coverage to Avaya station, call from Nortel station In the first example, assume Avaya station 24001 has a coverage path whose first point in coverage is Avaya station 24000. Nortel telephone 45001 dials 24001, and 24001 is idle, but does not answer the incoming call. The following capture of “list trace” shows the activity for such a call. list trace tac 130/q Page 1 LIST TRACE time data 11:23:26 Calling party trunk-group 30 member 23 cid 0x124 11:23:26 Calling Number & Name 45001 Joe Arias 11:23:26 active trunk-group 30 member 23 cid 0x124 11:23:26 dial 24001 11:23:26 ring station 24001 cid 0x124 11:23:36 QSIG>out DV_L1 Invk invkid 0xef 11:23:36 no answer station 24001 cid 0x124 11:23:36 coverage-path 1 point 1 cid 0x124 11:23:36 ring station 24000 cid 0x124 11:23:44 active station 24000 cid 0x124

The call remains on trunk member 23.




The Nortel caller sees the same display as previously illustrated for a basic call (e.g., “24001” and “Victor Yee”) until the coverage point answers. When station 24000 answers, the Nortel caller's display shows "Tom Chu 24001 24000 "RNA"" where Tom Chu is the name of the answering coverage point, and “RNA” corresponds to “Ring No Answer”, which is the reason for redirection. The numbers are the originally dialed number followed by the covered-to number. The Avaya covered-to party sees “Joe Arias to Victor Yee d”, where the “d” redirect reason corresponds to “didn’t answer” coverage reason. In the next example, assume Avaya station 24001 still has a coverage path whose first point in coverage is Avaya station 24000. Nortel telephone 45001 again dials 24001, but this time, station 24001 is already on another call. There are available call appearances for the second call to ring in, but the user does not answer the new incoming call. The following capture of “list trace” shows the activity for such a call. list trace tac 130/q Page 1 LIST TRACE time data 11:36:07 Calling party trunk-group 30 member 23 cid 0x142 11:36:07 Calling Number & Name 45001 Joe Arias 11:36:07 active trunk-group 30 member 23 cid 0x142 11:36:07 dial 24001 11:36:07 ring station 24001 cid 0x142 11:36:17 QSIG>out DV_L1 Invk invkid 0x4 11:36:17 no answer station 24001 cid 0x142 11:36:17 coverage-path 1 point 1 cid 0x142 11:36:17 ring station 24000 cid 0x142 11:36:23 active station 24000 cid 0x142

The call remains on trunk member 23. The Nortel caller sees the same display as previously illustrated for a basic call (e.g., “24001” and “Victor Yee”) until the coverage point answers. When station 24000 answers, the Nortel caller's display shows "Tom Chu 24001 24000 "BSY"" where Tom Chu is the name of the answering coverage point, and “BSY” alerts the user that the called user is already “busy” on a call. The numbers are the originally dialed number followed by the covered-to answering number. The Avaya covered-to party sees “Joe Arias to Victor Yee b”, where a small “b” redirect reason corresponds to a user who is on a call, but had an available call appearance to receive the new incoming call. Example: Avaya station call coverage to Nortel station, varied caller In the next series of examples, assume Avaya station 24001 has been assigned coverage path 1, whose first point in coverage is a remote coverage entry that directs the call to Nortel station 45001. The following screens illustrate the example coverage configuration applicable to the remote coverage test.




change coverage path 1 Page 1 of 1 COVERAGE PATH Coverage Path Number: 1 Cvg Enabled for VDN Route-To Party? n Hunt after Coverage? n Next Path Number: Linkage COVERAGE CRITERIA Station/Group Status Inside Call Outside Call Active? n n Busy? y y Don't Answer? y y Number of Rings: 2 All? n n DND/SAC/Goto Cover? y y Holiday Coverage? n n COVERAGE POINTS Terminate to Coverage Pts. with Bridged Appearances? n Point1: r1 Rng: Point2: Point3: Point4: Point5: Point6:

The following screen illustrates a portion of the remote coverage table. change coverage remote 1 Page 1 of 23 REMOTE CALL COVERAGE TABLE ENTRIES FROM 1 TO 1000 01: 45001 16: 31: 02: 17: 32:

Now assume station 24001 is idle, and Avaya station 24000 calls 24001. The following capture of “list trace” shows the activity for this type of call. list trace station 24000 Page 1 LIST TRACE time data 11:40:01 active station 24000 cid 0x149 11:40:06 dial 24001 11:40:06 ring station 24001 cid 0x149 11:40:16 no answer station 24001 cid 0x149 11:40:18 coverage-path 1 point 1 cid 0x149 11:40:18 dial 45001 route:UDP|AAR 11:40:18 term trunk-group 30 cid 0x149 11:40:18 call-forwarding 45001 11:40:18 route-pattern 30 preference 1 cid 0x149 11:40:18 seize trunk-group 30 member 11 cid 0x149 11:40:18 Calling Number & Name 24000 Tom Chu 11:40:18 Proceed trunk-group 30 member 11 cid 0x149 11:40:18 Alert trunk-group 30 member 11 cid 0x149 11:40:31 active trunk-group 30 member 11 cid 0x149

The following capture shows additional trace activity for this type of call. Although the Nortel Meridian proposes path replacement, it is not a better route, so Avaya rejects the path replacement.




list trace tac 130/q Page 1 LIST TRACE time data 14:18:04 QSIG>out DV_L2 Invk 24001 invkid 0xc9 14:18:04 QSIG>out DV_L2 Invk 24001 invkid 0xc9 14:18:04 dial 45001 route:UDP|AAR 14:18:04 term trunk-group 30 cid 0x167 14:18:04 call-forwarding 45001 14:18:04 route-pattern 30 preference 1 cid 0x167 14:18:04 seize trunk-group 30 member 12 cid 0x167 14:18:04 Calling Number & Name 24000 Tom Chu 14:18:04 Proceed trunk-group 30 member 12 cid 0x167 14:18:04 Alert trunk-group 30 member 12 cid 0x167 14:18:04 QSIG<in DV_L3 Invk 56 invkid 0x1 14:18:08 active trunk-group 30 member 12 cid 0x167 14:18:17 QSIG<in PR_PRO Invk 45001 invkid 0x2 14:18:17 denial event 2229: Qsig PR:Same Trunk Group D1=0x83001e D2=0x83001e 14:18:17 QSIG>out PR_PRO Error TempUnach, invkid 0x2

The Nortel covered-to user sees "Tom Chu 24000 24001 "RNA"" where Tom Chu is the name of the caller, and “RNA” corresponds to “Ring No Answer”, which is the reason for redirection. The numbers are the caller’s number followed by the originally dialed number. The Avaya caller sees “Victor Yee cover”. For the next example, assume station 24001 is already on a call, but has an available call appearance for another incoming call. Avaya station 24000 calls 24001. The following capture of “list trace” shows the trunk activity for this type of call. list trace tac 130/q Page 1 LIST TRACE time data 14:25:30 QSIG>out DV_L2 Invk 24001 invkid 0xcc 14:25:30 QSIG>out DV_L2 Invk 24001 invkid 0xcc 14:25:30 dial 45001 route:UDP|AAR 14:25:30 term trunk-group 30 cid 0x176 14:25:30 call-forwarding 45001 14:25:30 route-pattern 30 preference 1 cid 0x176 14:25:30 seize trunk-group 30 member 14 cid 0x176 14:25:30 Calling Number & Name 24000 Tom Chu 14:25:30 Proceed trunk-group 30 member 14 cid 0x176 14:25:30 QSIG<in DV_L3 Invk 56 invkid 0x1 14:25:30 Alert trunk-group 30 member 14 cid 0x176 14:25:34 active trunk-group 30 member 14 cid 0x176 14:25:44 QSIG<in PR_PRO Invk 45001 invkid 0x2 14:25:44 denial event 2229: Qsig PR:Same Trunk Group D1=0x83001e D2=0x83001e 14:25:44 QSIG>out PR_PRO Error unknown0, invkid 0x2

The Nortel covered-to user sees "Tom Chu 24000 24001 "BSY"" where Tom Chu is the name of the caller, and “BSY” corresponds to “busy” or “already on a call”. The numbers are the caller’s number followed by the originally dialed number. The Avaya caller sees “Victor Yee cover”.




For the next example, assume station 24001 has activated “send-all-calls” (e.g., by pressing a send-calls button on the telephone). Avaya station 24000 calls 24001. The following capture of “list trace” shows the trunk activity for this type of call. list trace tac 130/q Page 1 LIST TRACE time data 14:32:31 QSIG>out DV_L2 Invk 24001 invkid 0xd0 14:32:31 QSIG>out DV_L2 Invk 24001 invkid 0xd0 14:32:31 dial 45001 route:UDP|AAR 14:32:31 term trunk-group 30 cid 0x187 14:32:31 call-forwarding 45001 14:32:31 route-pattern 30 preference 1 cid 0x187 14:32:31 seize trunk-group 30 member 16 cid 0x187 14:32:31 Calling Number & Name 24000 Tom Chu 14:32:31 Proceed trunk-group 30 member 16 cid 0x187 14:32:31 QSIG<in DV_L3 Invk 56 invkid 0x1 14:32:31 Alert trunk-group 30 member 16 cid 0x187 14:32:34 active trunk-group 30 member 16 cid 0x187 14:32:42 QSIG<in PR_PRO Invk 45001 invkid 0x2 14:32:42 denial event 2229: Qsig PR:Same Trunk Group D1=0x83001e D2=0x83001e 14:32:42 QSIG>out PR_PRO Error unknown0, invkid 0x2

The Nortel covered-to user sees "Tom Chu 24000 24001 "CFWD"" where Tom Chu is the name of the caller. Note that the redirect reason “CFWD” is seen for send-all-calls, similar to the use of the Avaya call-forwarding feature. This is true whether the user whose coverage path is followed is idle, or on a call with available call appearances to receive a second call. The numbers are the caller’s number followed by the originally dialed number. The Avaya caller sees “Victor Yee cover”. For the next example, assume station 24001 has the same coverage remote configuration to Nortel user 45001, but now the caller is Nortel user 45002 dialing 24001. The user at 24001 is idle, and does not answer. The following capture of “list trace” shows the trunk activity for this type of call.




list trace tac 130/q Page 1 LIST TRACE time data 14:36:29 Calling party trunk-group 30 member 23 cid 0x191 14:36:29 Calling Number & Name 45002 Khoa Bui 14:36:29 active trunk-group 30 member 23 cid 0x191 14:36:30 dial 24001 14:36:30 ring station 24001 cid 0x191 14:36:40 no answer station 24001 cid 0x191 14:36:42 coverage-path 1 point 1 cid 0x191 14:36:42 QSIG>out DV_L2 Invk 24001 invkid 0xd3 14:36:42 QSIG>out DV_L2 Invk 24001 invkid 0xd3 14:36:42 dial 45001 route:UDP|AAR 14:36:42 term trunk-group 30 cid 0x191 14:36:42 call-forwarding 45001 14:36:42 route-pattern 30 preference 1 cid 0x191 14:36:42 seize trunk-group 30 member 17 cid 0x191 14:36:42 Calling Number & Name 45002 Khoa Bui 14:36:42 Proceed trunk-group 30 member 17 cid 0x191 14:36:42 Alert trunk-group 30 member 17 cid 0x191 14:36:48 active trunk-group 30 member 17 cid 0x191 14:36:58 idle trunk-group 30 member 23 cid 0x191

The Nortel covered-to user sees "Khoa Bui 45002 24001 "RNA"" where Khoa Bui is the name of the caller. The redirect reason is “RNA” for “ring no answer” as illustrated previously. The numbers are the caller’s number followed by the originally dialed number. After coverage has occurred, and Nortel user 45001 is ringing, the Nortel caller sees “Joe Arias”, the name of the covered-to user. Upon answer, the Nortel caller sees “Joe Arias 45001” (i.e., updates with the number). Note that the trunks are released in this case. While the call is active between the two Nortel users, “status trunk” confirms that all trunk members are idle (not shown). As with the prior examples, if the called user 24001 is already on a call, and receives an incoming call from 45002, and the call rings in on an available call appearance and is not answered, the display at the covered-to Nortel telephone is identical to the “idle” case, except that “BSY” is displayed rather than “RNA” (e.g., “Khoa Bui 45002 24001 “BSY””) In this case, the Nortel caller continues to see “Victor Yee 24001” until 45001 answers, when the display updates to “Joe Arias 45001”.

7.6. Avaya Telephone Controlling Call Transfer, Examples This section pertains to cases where an Avaya telephone already on a call transfers the call. For the trunk-trunk transfers in this section, it is assumed that the system and user’s permissions do not restrict the transfer. Example: Avaya station on call with Nortel station, Avaya station transfer to Avaya station In the first example, assume Avaya station 24000 has made a call to Nortel station 45001. Avaya station 24000 then does a “consult transfer” of the call to Avaya station 24001 (meaning




that 24000 waits for 24001 to answer before completing the transfer). The following capture of “list trace” shows the activity for such a call. list trace tac 130/q Page 1 LIST TRACE time data 14:30:27 dial 45001 route:UDP|AAR 14:30:27 term trunk-group 30 cid 0x28a 14:30:27 dial 45001 route:UDP|AAR 14:30:27 route-pattern 30 preference 1 cid 0x28a 14:30:27 seize trunk-group 30 member 8 cid 0x28a 14:30:27 Calling Number & Name 24000 Tom Chu 14:30:27 Proceed trunk-group 30 member 8 cid 0x28a 14:30:27 Alert trunk-group 30 member 8 cid 0x28a 14:30:30 active trunk-group 30 member 8 cid 0x28a 14:30:44 conf/tran hold station 24000 cid 0x28a 14:30:44 active station 24000 cid 0x28b 14:30:47 dial 24001 14:30:47 ring station 24001 cid 0x28b 14:30:51 active station 24001 cid 0x28b 14:30:54 transfer station 24000 cid 0x28b

After the transfer, the Nortel party sees “Victor Yee 24001 "T"”. Note that Victor Yee is the name of the transferred-to Avaya station, and “T” indicates transfer. After the transfer, the transferred-to Avaya telephone displays “Joe Arias 45001” (i.e., the name and number of the Nortel party). After the transfer, the call remains on trunk member 8. Although not illustrated further, the same results apply when “blind transfer” is used rather than “consult transfer”. Example: Avaya station on call with Nortel station, Avaya station transfer to Nortel station In the next example, assume Nortel station 45002 has made a call to Avaya station 24001. Station 24001 now blind transfers the call to Nortel station 45001 (meaning that 24001 does not wait for answer before completing the transfer). The following capture of “list trace” shows the activity for such a call.




list trace tac 130/q Page 1 LIST TRACE time data 15:38:20 Calling party trunk-group 30 member 23 cid 0x213 15:38:20 Calling Number & Name 45002 Khoa Bui 15:38:20 active trunk-group 30 member 23 cid 0x213 15:38:20 dial 24001 15:38:20 ring station 24001 cid 0x213 15:38:24 active station 24001 cid 0x213 15:38:31 conf/tran hold station 24001 cid 0x213 15:38:31 active station 24001 cid 0x214 15:38:32 dial 45001 route:UDP|AAR 15:38:32 term trunk-group 30 cid 0x214 15:38:32 dial 45001 route:UDP|AAR 15:38:32 route-pattern 30 preference 1 cid 0x214 15:38:32 seize trunk-group 30 member 9 cid 0x214 15:38:32 Calling Number & Name 24001 Victor Yee 15:38:33 Proceed trunk-group 30 member 9 cid 0x214 15:38:33 Alert trunk-group 30 member 9 cid 0x214 15:38:35 transfer station 24001 cid 0x214 15:38:41 active trunk-group 30 member 9 cid 0x214 15:38:50 idle trunk-group 30 member 23 cid 0x214

After the transfer, Nortel station 45001 sees “Khoa Bui H5002 "T"” Nortel station 45002 sees Joe Arias 45001 "T" A “status trunk” (not shown) confirms that the trunks are released. The final connection between the two Nortel telephones is local to the Nortel system. The same results are observed with consult transfer.

7.7. Nortel Telephone Controlling Call Transfer, Examples This section pertains to cases where a Nortel telephone already on a call transfers the call. Example: Avaya station on call with Nortel station, Nortel station transfer to Avaya station In the next example, assume Avaya station 24000 has made a call to Nortel station 45001. Nortel station 45001 then does a “blind transfer” of the call to Avaya station 24001 (meaning that 45001 does not wait for answer before completing the transfer). The following capture of “list trace” shows a portion of the trunk activity for such a call.




list trace tac 130/q Page 1 LIST TRACE time data 14:58:05 dial 45001 route:UDP|AAR 14:58:05 term trunk-group 30 cid 0x7 14:58:05 dial 45001 route:UDP|AAR 14:58:05 route-pattern 30 preference 1 cid 0x7 14:58:05 seize trunk-group 30 member 22 cid 0x7 14:58:05 Calling Number & Name 24000 Tom Chu 14:58:05 Proceed trunk-group 30 member 22 cid 0x7 14:58:05 Alert trunk-group 30 member 22 cid 0x7 14:58:08 active trunk-group 30 member 22 cid 0x7 14:58:29 QSIG<in PR_PRO Invk 24001 invkid 0x75

The following capture shows another type of trace for a similar call, where path replacement messaging can be observed. list trace tac 130/Q Page 1 LIST TRACE time data 15:00:14 QSIG>out PR_PRO Invk 24001 invkid 0x79 15:00:15 QSIG<in PR_PRO Invk 24001 invkid 0x79

The resultant connection is between two Avaya telephones. The trunk members that had been used from trunk group 30 are released. Although not shown, it was confirmed that all trunks were idle. The Avaya telephone displays are identical to a station to station call display between the two connected Avaya telephones. Although not shown, it was confirmed that a consult transfer for this same type of call produces the same result. Example: Avaya station on call with Nortel station, Nortel station transfer to Nortel station In the next example, assume Avaya station 24001 has made a call to Nortel station 45001. Nortel station 45001 then does a “blind transfer” of the call to Nortel station 45002 (meaning that 45001 does not wait for answer before completing the transfer). The following capture of “list trace” shows a portion of the trunk activity for such a call.




list trace tac 130/q Page 1 LIST TRACE time data 10:24:45 dial 45001 route:UDP|AAR 10:24:45 term trunk-group 30 cid 0x3e 10:24:45 dial 45001 route:UDP|AAR 10:24:45 route-pattern 30 preference 1 cid 0x3e 10:24:45 seize trunk-group 30 member 3 cid 0x3e 10:24:45 Calling Number & Name 24001 Victor Yee 10:24:45 Proceed trunk-group 30 member 3 cid 0x3e 10:24:45 Alert trunk-group 30 member 3 cid 0x3e 10:24:49 active trunk-group 30 member 3 cid 0x3e 10:25:18 QSIG>out PR_PRO Invk 24001 invkid 0x84 10:25:18 QSIG>out PR_SET Result invkid 0x1 10:25:18 idle trunk-group 30 member 3 cid 0x3e

Although the call began on trunk member 3 as shown above, the following capture shows that the steady-state call moves to trunk member 23. 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 001V202

The following capture shows another type of trace for a similar call, showing path replacement messaging. list trace tac 130/Q Page 1 LIST TRACE time data 10:28:34 QSIG>out PR_PRO Invk 24001 invkid 0x86 10:28:34 QSIG<in PR_SET Invk invkid 0x1 10:28:34 QSIG>out PR_SET Result invkid 0x1

In the steady state after the answer by the transferred-to party, the display on the Avaya telephone is “Khoa Bui 45002” (i.e., the identity of the transferred-to Nortel party). The display on the Nortel telephone is “Victor Yee 24001 "T"” (i.e., the identity of the Avaya party and a “T” for transfer). Although not illustrated, the same results apply when Nortel station 45001 does a “consult transfer” to Nortel station 45002.




7.8. Avaya Automatic Callback, Nortel Ring Again Feature Examples This section pertains to cases where an Avaya station calls a Nortel station, and uses the Automatic Callback (ACB) feature, or where a Nortel station calls an Avaya station, and uses the Ring Again feature. Although slightly different, both features allow the caller to receive a notification when the called user becomes available, and both features facilitate a new call between the caller and the called user, once the called user becomes available. Examples: Avaya station calls Nortel station and uses “auto-cback” feature Note that the “TSC Method for Auto Callback” parameter must be set to “always-retain” on the Avaya trunk group to the Nortel (as shown in Section 3.2), for reliable use of the Avaya ACB feature toward Nortel called users. When setting the parameter to “always-retain”, a message appears alerting the user to ensure there are a sufficient number of Non Call Associated Temporary Signaling Connections (NCA-TSCs) on the corresponding ISDN-PRI signaling group form. In the first example, assume Nortel station 45001 is idle. Assume Avaya station 24001 dials Nortel station 45001. While the caller is hearing ring back, the Avaya caller presses an “auto-cback” button (i.e., the ACB button). For example, perhaps the caller realizes the called party is not going to answer this call, but wishes to be alerted when the called party becomes available. When the ACB button is pressed, the Avaya caller hears confirmation tone, the ACB button illuminates showing ACB is active, and the called Nortel user stops ringing (i.e., the trunk call is cleared). The following capture of “list trace” shows the activity for the call described above. list trace tac 130/q Page 1 LIST TRACE time data 13:44:55 dial 45001 route:UDP|AAR 13:44:55 term trunk-group 30 cid 0xc4 13:44:55 dial 45001 route:UDP|AAR 13:44:55 route-pattern 30 preference 1 cid 0xc4 13:44:55 seize trunk-group 30 member 11 cid 0xc4 13:44:55 Calling Number & Name 24001 Victor Yee 13:44:55 Proceed trunk-group 30 member 11 cid 0xc4 13:44:55 Alert trunk-group 30 member 11 cid 0xc4 13:45:05 idle station 24001 cid 0xc4

The following capture shows a different type of trace for this same type of call. list trace tac 130/Q Page 1 LIST TRACE time data 14:04:13 QSIG<in CC_NRQ Result invkid 0x56

The following “status signaling-group” capture shows that there is one active NCA-TSC. This NCA-TSC is associated with the active ACB.




status signaling-group 30 STATUS SIGNALING GROUP Group ID: 30 Active NCA-TSC Count: 1 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

Now, toggle the switch-hook for Nortel user 45001, the target of the ACB call. When Nortel user 45001 returns on-hook, it is an indication that this user may be available. The Avaya user that activated ACB now gets a “callback” call. A callback call rings with priority ringing, and in this case displays “Joe Arias callback” on the display. Upon answering the callback call at 24001, station 45001 begins to ring with a new incoming call from 24001. This call may be answered (or not) like any other incoming call. The NCA-TSC is cleared, as 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

The following variations of this test were also successfully verified:

• Sequential ACB activations and callbacks from the same activating user to the same Nortel target station. Note that this particular case would fail if the “TSC Method for Auto Callback” parameter is not set to “always-retain”.

• More than one concurrent Avaya ACB activation. For example, assume station 24001 calls 45001, and activates ACB, and station 24000 calls 45002 and activates ACB. The “Active NCA-TSC Count” on the signaling group would be “2” at this point. As another example, assume station 24001 is assigned two “auto-cback” (ACB) buttons. Station 24001 calls 45001, and presses one ACB button. Later, station 24001 calls 45002, and presses another ACB button. Two ACB buttons are illuminated at the station, and two NCA-TSCs are active for the signaling group.

• Avaya ACB activation and Nortel Ring Again active at the same time. Again, the Active NCA-TSC Count” would be “2” (or more).

• Explicit cancellation of an active ACB by the Avaya phone. For example, if the Avaya user no longer wishes to be notified when a called user becomes available, the Avaya user can cancel ACB. One way to do this is to press an illuminated ACB feature button. The NCA-TSC is cleared.

• Implicit cancellation of an active ACB. For example, if the Avaya user does not answer the priority callback call when the Nortel user becomes available, the ACB is cancelled, and the NCA-TSC is cleared.




• An Avaya user’s attempt to activate ACB when the maximum number of NCA-TSCs on the signaling group form has been reached. In this case, the Avaya user’s ACB button would flutter in denial, but the actual call would not be cleared. That is, the call will continue to ring at the called Nortel party until answered or redirected to voice mail.

Examples: Nortel station calls Avaya station and uses “RingAgn” button Assume Avaya station 24001 is idle. Assume Nortel station 45001 dials Avaya station 24001. While the caller is hearing ring back, the Nortel caller presses the “RingAgn” key. In the sample configuration, this soft-key appears when the Nortel user completes dialing. For example, perhaps the caller hears Avaya’s coverage tone, and realizes the called party is not going to answer this call, but wishes to be alerted when the called party becomes available. When the RingAgn key is pressed, the Nortel caller sees “Ring Again is Active” on the display as a confirmation that feature activation was successful. The called Avaya user stops ringing (i.e., the trunk call is cleared). The following capture of “list trace” shows the activity for the call described above. list trace tac 130/q LIST TRACE time data 15:15:20 Calling party trunk-group 30 member 23 cid 0x2ad 15:15:20 Calling Number & Name 45001 Joe Arias 15:15:20 active trunk-group 30 member 23 cid 0x2ad 15:15:20 dial 24001 15:15:20 ring station 24001 cid 0x2ad 15:15:23 idle trunk-group 30 member 23 cid 0x2ad

The following “status signaling-group” capture shows that there is one active NCA-TSC. This NCA-TSC is associated with the active “Ring Again”. status signaling-group 30 STATUS SIGNALING GROUP Group ID: 30 Active NCA-TSC Count: 1 Group Type: isdn-pri Active CA-TSC Count: 0 Signaling Type: facility associated signaling Group State: in-service

Now, toggle the switch-hook for Avaya user 24001, the target of the Ring Again call. The Nortel user that activated “Ring Again” gets a “Ring again ready” message on the display, with instructions to “Select LINE, RING AGAIN”. When Nortel user 45001 selects an idle appearance, and presses the “RngCall” soft-key, a new call is placed to Avaya user 24001. This call may be answered (or not) like any other incoming call. The NCA-TSC is cleared, as 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




The following variations of this test were also successfully verified:

• Sequential Ring Again activations and callbacks from the same activating user to the same Avaya target station.

• More than one concurrent Nortel Ring Again activation (from different Nortel phones), similar to the multiple Avaya ACB test.

• Activation of Ring Again for a call from a Nortel user to an Avaya user who is currently on another call, but has an available call appearance for the new incoming call.

• Explicit cancellation of an active Ring Again by the Nortel activating phone. For example, if the Nortel user no longer wishes to be notified when a called user becomes available, the Nortel user can press the “CancelR” soft-key. “Ring Again is cancelled” appears on the display, and the NCA-TSC is cleared.

• Implicit cancellation of an active Ring Again. For example, if the Nortel user takes no action when alerted via the display that the “Ring Again is Ready”, the Ring Again is cancelled in approximately 30 seconds, and the NCA-TSC is cleared.

• A Nortel user’s attempt to activate Ring Again when the maximum number of NCA-TSCs on the signaling group form has been reached. In this case, upon pressing Ring Again, the display shows “Ring Again is cancelled”, and (unlike the corresponding Avaya ACB case) the actual trunk call is cleared.

To determine if the case described in the final bullet has occurred, the Avaya “display events” command may be used, with a filter for denial events. The following is an example entry, if there are no NCA-TSCs available. This error would also be seen for an Avaya user’s attempt to activate ACB when the maximum number of NCA-TSCs has been reached for the signaling group. Event Data 1 is the signaling group number (in hexadecimal, “1E” = decimal 30) display events EVENTS REPORT Event Event Event Event First Last Evnt Type Description Data 1 Data 2 Occur Occur Cnt 2201 No TSC's for this D-chan 1E 1 11/03/15:00 11/03/15:00 1

An Avaya special application is available that can modify the behavior of the automatic callback feature. The next examples illustrate the behavior of special application SA8518, shown enabled in bold in the following screen. Special Applications can be activated via the license file. display system-parameters special-applications Page 4 of 8 SPECIAL APPLICATIONS (SA8481) - Replace Calling Party Number with ASAI ANI? n (SA8500) - Expanded UUI Display Information? n (SA8506) - Altura Interoperability (FIPN)? n (SA8507) - H245 Support With Other Vendors? n (SA8508) - Multiple Emergency Access Codes? n (SA8510) - NTT Mapping of ISDN Called-Party Subaddress IE? n (SA8517) - Authorization Code By COR? n (SA8518) - Automatic Callback with Called Party Queuing? y




Example: Two Nortel stations activate Ring Again toward the same Avaya called station Assume Nortel station 45001 dials Avaya station 24001 and activates Ring Again, as previously described. Before station 24001 becomes available, assume Nortel station 45002 also dials Avaya station 24001, and tries to activate Ring Again. Without SA8518 activated, the second ring again request (by 45002) is denied. Station 45002 sees the message “Ring again cancelled” and the call itself is cleared, as previously documented for cases where Nortel Ring Again activation is unsuccessful. With SA8518 activated in this same scenario, the second ring again request (by 45002) is also successful. Two Ring Again requests are active for the same Avaya called party (e.g., 24001). When 24001 becomes available (e.g. toggles the switch-hook), the user who activated ring again first, Nortel station 45001, is alerted that the “Ring again is ready” and can complete the “ringout” call to 24001 as previously described. Assume 24001 answers the ringout call. When 24001 returns on-hook, the user who activated the next ring again, Nortel station 45002, is alerted that the “Ring again is ready” and can complete the “ringout” call if desired. Example: Avaya station activates ACB toward Nortel station that is forwarded locally Assume Nortel station 45001 has activated call forwarding unconditional to Nortel station 45002. Assume Avaya station 24001 dials Nortel station 45001, and attempts to activate ACB. Without SA8518 activated, the ACB activation request is denied, and the call continues to ring. Without SA8518 activated, Avaya will not send the request to activate the feature to the Nortel system, after it has received indication that the call has diverted due to call forwarding. However, in this same scenario with SA8518 activated, the ACB activation request is allowed, and the Avaya caller receives confirmation tone that ACB has been activated. In this case, Nortel is monitoring the forwarded-to party (e.g., 45002 in this case) for availability. If the originally called user, 45001, toggles the switch-hook, no callback call occurs. When the forwarded-to party toggles the switch-hook, a callback call occurs to Avaya station 24001. When this callback call is answered, a new call is placed to the originally called party (45001), and this call is forwarded to station 45002, which has become available. The call rings in to station 45002 with the same display described for forwarded calls in Section 7.4. Examples: Avaya station with forwarding active is target of ACB or Ring Again SA8518 allows ACB when the called party has call forwarding active to another local Avaya user, who in turn is not forwarded. If the called Avaya user has call forwarding active to a Nortel user (i.e., not a local user), ACB attempts toward the forwarded user are denied. For example, assume Avaya user 24000 has activated call-forward-all to Nortel user 45002. Assume Avaya user 24001 calls 24000, and attempts to activate ACB. This ACB activation request is denied. As another example, assume Avaya user 24001 has call forwarding active to Avaya user 24000. Assume Nortel user 45001 dials 24001, and while 24000 is ringing with the forwarded call, the Nortel user activates Ring Again. In this case, Ring Again is successful, both with and without SA8518. The Nortel Ring Again request is actually activated towards the forwarded-to station (e.g., 24000 in this case), which the Nortel Meridian learns from the diversion information in the




QSIG messaging associated with the call forwarding. When station 24000 becomes available, Nortel station 45001 is notified that the “Ring Again is ready”, and can create the “ringout” call to 24000 using the same procedures previously described.

7.9. Calling Party Number and Name Presentation Restriction This section pertains to cases where an Avaya telephone calls a Nortel telephone, and the calling party information is not intended to be rendered on the display of the Nortel telephone. 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-9”. 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 caller’s number. If it is also desirable to restrict the presentation of the user’s 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 much broader restriction, sending but restricting the presentation of caller id for all calls over the trunk group, from all users (unless “cpn-unblk” is used).

• 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 party’s name should also be restricted along with the calling party’s 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-12”. Avaya sends the calling party’s name, but marks it for restricted presentation. The Nortel Meridian honors the request for restricted presentation, and display “XXXX” instead of the actual caller’s 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 caller’s 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 restriction configured via the trunk group form. With “Send Calling Number” set to “r” on the trunk group form, the Avaya caller’s name will still appear on the Nortel telephone with SA8967 enabled. Nortel User Calls Avaya User with Privacy 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: unk-pvt Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider Replace Restricted Numbers? y Replace Unavailable Numbers? n Send Connected Number: y




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-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.10. Calls Involving IA770 Voice Mail This section includes a representative sample of calls involving voice messaging. Avaya Station calls Nortel Station, Redirect to Avaya IA770 Voice Mail In the first example, assume Avaya station 24001 calls Nortel station 45001 when Nortel station 45001 is idle, and the message waiting lamp is out. Station 45001 does not answer. The Nortel station has a mailbox in IA770. The following is a trace of such a call. list trace tac 130/q Page 1 LIST TRACE time data 10:56:51 dial 45001 route:UDP|AAR 10:56:51 term trunk-group 30 cid 0x98 10:56:51 dial 45001 route:UDP|AAR 10:56:51 route-pattern 30 preference 1 cid 0x98 10:56:51 seize trunk-group 30 member 18 cid 0x98 10:56:51 Calling Number & Name 24001 Victor Yee 10:56:51 Proceed trunk-group 30 member 18 cid 0x98 10:56:51 Alert trunk-group 30 member 18 cid 0x98 10:57:11 QSIG<in DV_L1 Invk 25100 invkid 0x1 10:57:12 active trunk-group 30 member 18 cid 0x98 10:57:15 QSIG>out PR_PRO Invk 24001 invkid 0xaa

When the call enters voice mail, the caller hears that the called user “Joe Arias” is not available. The caller leaves a message, and the message waiting lamp for user 45001 illuminates. The following capture shows another type of trace for a similar call.




list trace tac 130/Q Page 1 LIST TRACE time data 11:03:53 QSIG<in DV_L2 Invk invkid 0x1 11:03:53 QSIG<in DV_L2 Invk 45001 invkid 0x1 11:03:54 QSIG<in DV_L1 Invk 25100 invkid 0x1 11:04:00 QSIG>out PR_PRO Invk 24001 invkid 0xae

The following capture taken while the caller was leaving the message shows that the trunks were not released for this type of call in the sample configuration (i.e., trunks are released once the caller hangs up after leaving the message but not before). 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/active no 001V202 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 T00028

Now assume the user of station 45001 calls in to retrieve the voice mail. The following is a trace of such a call. The caller need not enter his extension to log on. That is, the caller id of 45001 sent to the voice messaging system identifies the user in the sample configuration, allowing the user to enter only the password. Note that “Internal Alert” is set to “y’ for trunk group 30 in the sample configuration. list trace tac 199/q Page 1 LIST TRACE time data 11:22:38 Setup digits 25100 11:22:38 Calling Number & Name 45001 NO-CPName 11:22:38 Proceed trunk-group 99 member 1 cid 0xe2 11:22:39 Alert trunk-group 99 member 1 cid 0xe2 11:22:39 G711MU ss:off ps:20 rn:2/1 192.45.100.49:8000 192.45.100.47:2052 11:22:39 xoip: fax:Relay modem:off tty:US 192.45.100.47:2052 uid:0x50018 11:22:39 active trunk-group 99 member 1 cid 0xe2 11:22:48 idle trunk-group 30 member 23 cid 0xe2

The header of the voice mail identifies the caller as “Victor Yee” and includes his extension. After the caller listens to or deletes the message, the message waiting lamp is successfully extinguished for the Nortel telephone 45001.




In the next example, assume that the Nortel user 45001 was on a call and had no available call appearances to receive a second incoming call when station 24001 calls 45001. The following capture shows a trace for such a call. list trace tac 130/q Page 1 LIST TRACE time data 11:15:25 dial 45001 route:UDP|AAR 11:15:25 term trunk-group 30 cid 0xcc 11:15:25 dial 45001 route:UDP|AAR 11:15:25 route-pattern 30 preference 1 cid 0xcc 11:15:25 seize trunk-group 30 member 22 cid 0xcc 11:15:25 Calling Number & Name 24001 Victor Yee 11:15:25 Proceed trunk-group 30 member 22 cid 0xcc 11:15:25 QSIG<in DV_L1 Invk 25100 invkid 0x1 11:15:26 Alert trunk-group 30 member 22 cid 0xcc 11:15:26 active trunk-group 30 member 22 cid 0xcc 11:15:31 QSIG>out PR_PRO Invk 24001 invkid 0xba

In this case, when the call is answered in voicemail, the caller hears that the called user is “busy”. That is, voice messaging can distinguish between “no answer” and “busy” cases for the Nortel user. In the next example, assume the user of Nortel station 45001 has activated call forwarding to the IA770 pilot number, 25101. Place a call from 24001 to 45001. The call goes immediately to voice mail, and the caller hears that the called party is not available. list trace tac 130/q Page 1 LIST TRACE time data 14:35:41 dial 45001 route:UDP|AAR 14:35:41 term trunk-group 30 cid 0x237 14:35:41 dial 45001 route:UDP|AAR 14:35:41 route-pattern 30 preference 1 cid 0x237 14:35:41 seize trunk-group 30 member 6 cid 0x237 14:35:41 Calling Number & Name 24001 Victor Yee 14:35:41 Proceed trunk-group 30 member 6 cid 0x237 14:35:41 QSIG<in DV_L1 Invk 25101 invkid 0x1 14:35:41 Alert trunk-group 30 member 6 cid 0x237 14:35:41 active trunk-group 30 member 6 cid 0x237 14:35:45 QSIG>out PR_PRO Invk 24001 invkid 0xdc

Nortel Station calls Nortel Station, Redirect to Avaya IA770 Voice Mail In the next example, assume Nortel station 45002 calls Nortel station 45001 when Nortel station 45001 is idle, and the message waiting lamp is out. Station 45001 does not answer. The Nortel station has a mailbox in IA770. The following is a trace of such a call.




list trace tac 199/q Page 1 LIST TRACE time data 14:38:55 Setup digits 25100 14:38:55 Calling Number & Name 45002 NO-CPName 14:38:55 Proceed trunk-group 99 member 1 cid 0x23f 14:38:55 Alert trunk-group 99 member 1 cid 0x23f 14:38:55 G711MU ss:off ps:20 rn:2/1 192.45.100.49:8000 192.45.100.47:2052 14:38:55 xoip: fax:Relay modem:off tty:US 192.45.100.47:2052 uid:0x50018 14:38:56 active trunk-group 99 member 1 cid 0x23f

When the call enters voice mail, the caller hears that the called user “Joe Arias” is not available. The caller leaves a message, and the message waiting lamp for user 45001 illuminates. When station 45001 retrieves the message, the message header indicates that it is a message from “Khoa Bui” at extension 45002. The message waiting lamp is extinguished as expected. In the next example, assume Nortel station 45002 calls Nortel station 45001 when Nortel station 45001 is busy. The caller hears that the called user “Joe Arias” is busy. The following capture shows another type of trace for this call. list trace tac 130/q Page 1 LIST TRACE time data 14:43:13 Calling party trunk-group 30 member 23 cid 0x24b 14:43:13 Calling Number & Name 45002 Khoa Bui 14:43:13 active trunk-group 30 member 23 cid 0x24b 14:43:13 call-forwarding 14:43:13 term hunt-group 99 cid 0x24b 14:43:13 call-forwarding 825100# 14:43:13 term trunk-group 99 cid 0x24b 14:43:13 call-forwarding 825100# 14:43:13 route-pattern 99 preference 1 cid 0x24b 14:43:13 seize trunk-group 99 member 4 cid 0x24b 14:43:13 Calling Number & Name NO-CPNumber NO-CPName 14:43:13 Setup digits 25100 14:43:13 Calling Number & Name 45002 NO-CPName 14:43:13 Proceed trunk-group 99 member 4 cid 0x24b 14:43:13 Alert trunk-group 99 member 4 cid 0x24b 14:43:13 G711MU ss:off ps:20 rn:2/1 192.45.100.49:8000 192.45.100.47:2052 14:43:13 xoip: fax:Relay modem:off tty:US 192.45.100.47:2052 uid:0x5001b 14:43:13 active trunk-group 99 member 4 cid 0x24b 14:43:25 idle trunk-group 30 member 23 cid 0x24b

When the message is retrieved, the header indicates the call is from Khoa Bui, extension 45002. Nortel Station calls Avaya Station, Call Coverage to Avaya IA770 Voice Mail In the next example, assume Nortel station 45001 calls Avaya station 24001 when Avaya station 24001 is idle, and the message waiting lamp is out. Station 24001 does not answer. The Avaya station has a mailbox in IA770. The following is a trace of such a call.




list trace tac 130/q Page 1 LIST TRACE time data 14:50:00 Calling party trunk-group 30 member 23 cid 0x25d 14:50:00 Calling Number & Name 45001 Joe Arias 14:50:00 active trunk-group 30 member 23 cid 0x25d 14:50:00 dial 24001 14:50:00 ring station 24001 cid 0x25d 14:50:10 no answer station 24001 cid 0x25d 14:50:12 QSIG>out DV_RR Invk 25100 invkid 0xe6 14:50:12 coverage-path 99 point 1 cid 0x25d 14:50:12 QSIG<in DV_RR Result invkid 0xe6 14:50:12 idle trunk-group 30 member 23 cid 0x25d

Note the similarity of the trace above to the trace for an incoming call to an Avaya user with call forwarding active. The following “status trunk” capture taken while the Nortel caller is leaving the voice message shows the call is now using trunk member 22, which is different than the trunk member 23 associated with the original call (diversion by reroute). 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/active no T00026 0030/023 001V423 in-service/idle no

When the call enters voice mail, the caller hears that the called user “Victor Yee” is not available. While leaving the message, the Nortel caller sees “24001 25100 "RNA"”. Note that 25100 is the routed-to number on the second page of the Avaya IA770 hunt group (which need not match the IA770 pilot number or hunt group number). The caller leaves a message, and the message waiting lamp for user 24001 is lit. When station 24001 retrieves the message, the message header indicates that it is a message from “Joe Arias” at extension 45001, which is correct. The message waiting lamp is extinguished as expected. In the next example, assume Nortel station 45001 calls Avaya station 24001 when Avaya station 24001 is already active on a call, but has call appearances for the call to ring in. The caller hears that the called user “Victor Yee” is busy. While leaving the message, the Nortel caller sees “24001 25100 "BSY"”. Other aspects of the call are the same as the idle case. In the next example, assume Avaya station 24001 has activated send-all-calls and is idle. Nortel station 45001 calls Avaya station 24001. In this case, the caller hears that the called user “Victor Yee” is not available. While leaving the message, the Nortel caller sees “24001 25100 "RNA"”.




In the next example, assume Avaya station 24001 has activated send-all-calls and is already on a call, but has available call appearances for a new call to ring in. Nortel station 45001 calls Avaya station 24001. In this case, the caller hears that the called user “Victor Yee” is busy. While leaving the message, the Nortel caller sees “24001 25100 "BSY"”.

8. Detailed Status and Tracing Tools If the information in Sections 6 and 7 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.

8.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 / QSIG 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 Manager’s 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 (truncated, entire SETUP message is not shown), showing a portion of the output for the beginning of a call from Avaya station 24000 to a Nortel station. This type of interpreted trace information facilitates problem identification and resolution.

8.2. Trace Information From Nortel Meridian In “ld 80”, snapshot traces can be obtained. The screen below shows an (abbreviated) example where “trac 0 45001” sets up a trace on DN 45001, and a call is made to 24001 trac 0 45001 ACTIVE TN 005 0 00 01 ORIG 005 0 00 01 0 SCR MARP 0 45001 3904 TERM 001 23 TIE RMBR 51 23 DIAL DN 24001 MAIN_PM DIAL AUX_PM COMPLETE TALKSLOT ORIG 19 TERM 19 EES_DATA: NONE QUEU NONE CALL ID 0 111 AUX NARS ---- ISDN PRA CALL (TERM) ---- CALL REF # = 102 BEARER CAP = VOICE HLC = CALL STATE = 4 DELIVERY CALLING NO = 45001 CALLED NO = 24001 PDCA 1 PAD 0 6 PCML MU MU




In “ld 96”, more detailed protocol traces can be obtained. The screen below shows commands to enable incoming and outgoing traces for D-Channel 17, followed by trace information for a call from Avaya station 24001 to Nortel station 45001. .enl msgi 17 .enl msgo 17 DCH 17 UIPE_IMSG CC_SETUP_IND REF 0000023A CH 0 TOD 14:43:54 CALLED #:45001 NUM PLAN: UNKNOWN TON: UNKNOWN PROGRESS: ORIGINATING END IS NOT ISDN CALLING #:24001 NUM PLAN: UNKNOWN TON: UNKNOWN DCH 17 UIPE_OMSG CC_PROCEED_REQ REF 0000823A CH 1 16 TOD 14:43:54 DCH 17 UIPE_OMSG CC_ALERT_REQ REF 0000823A CH 1 16 TOD 14:43:54 PROGRESS: TERMINATING END IS NOT ISDN

Trace information can also be obtained for active Call-Independent Signaling Connections, such as those used for “Ring Again” as follows. The following screen shows an example output when there is one such connection (ring again active toward Avaya user 24001) for D-Channel 17. .stat ncal 17 NCALL CONN ID: 1 CREF: 00000072 STATE: CONN_EST TIME: 2008 11 5 15:03:40 APPL: 3 ORIG: DEST: 24001

9. Conclusion As illustrated in these Application Notes, Avaya Communication Manager 5.1.1 can interoperate with Nortel Meridian Release 25.40b using ISDN-PRI and T1 QSIG. 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). Name and number displays are provided to both the Avaya and Nortel telephones as detailed in Section 7. Avaya and Nortel users can be subscribers in Avaya IA770 Intuity AUDIX, and receive voice messaging services, including caller identification, the ability to distinguish between “no answer” and “busy” conditions, and message waiting indication. Nortel users may use “Ring Again” toward Avaya users, and Avaya users may use “Automatic Callback” toward Nortel users. For many call scenarios, the QSIG Diversion by Reroute and Path Replacement features enable the ISDN-PRI / QSIG trunk members to be released when no longer required to serve a call.

10. Additional References This section references the documentation relevant to these Application Notes. Additional Avaya product documentation is available at http://support.avaya.com. The Nortel Meridian configuration steps described in the first two references below apply to the configuration in these Application Notes as well. [KB] Configuring a QSIG Centralized Messaging Solution using Avaya Modular Messaging




with Avaya Communication Manager for a Nortel Meridian Option 11C Mini, Issue 1.0, 5/26/2005 [KB2] Configuring QSIG Over ISDN-PRI Trunks between Avaya Communication Manager and Nortel Meridian, Issue 1.0, 5/26/2005 http://www.avaya.com/master-usa/en-us/resource/assets/applicationnotes/qsigtrkcmnortel.pdf The next reference describes a configuration where ISDN-PRI is used, but QSIG is not. It is expected that a new document showing an ISDN-PRI only configuration will be published in the future. [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 [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].

fe meridian

Documents