Lucent/Avaya Definity G3si V9 PBX with CallManager using the Cisco 3640-T1 PRI as MGCP Gateway

Table Of Contents

Application Note

Integration Description

Cisco Systems Equipment Needed

PBX Requirements

Features

Configuring the Lucent/Avaya Definity G3si PBX

Circuit Pack

Signaling Group

Trunk Group

Uniform Dialing Plan

Configuring Cisco CallManager

Gateway Configuration

Route Pattern Configuration

Considerations

Calling Name and Number Feature

Integration Testing

CallManager Software Release:

Lucent/Avaya Definity G3si Software Release

Cisco 3640 Router Configuration

Test Configuration

Test Results

Application Note

Lucent/Avaya Definity G3si V9 PBX with CallManager using the Cisco 3640-T1 PRI as an MGCP Gateway

This application note discusses the integration of the Lucent/Avaya Definity G3si V9 PBX with CallManager using the Cisco 3640-T1 PRI as an MGCP Gateway.

Integration Description

Connectivity is achieved by using the industry standard PRI NI-2 protocol. The Lucent/Avaya Definity G3si can be configured as either the NETWORK or USER side. The figure below shows the general network layout for the integration.

Network Layout

Cisco Systems Equipment Needed

•Hardware (Gateway): Cisco 3640 Gateway with 2MFT T1 Port

•Software: CallManager Release 3.2, Cisco IOS image c3640-js-mz.122-2.XN

PBX Requirements

•Hardware: TN464F, DS1 INTFC 24/32

•Software: Version V9

Features

Key features supported:

•Calling/Called Number

•Calling Name

•Connected Name

Key features not supported:

•Connected Number

Configuring the Lucent/Avaya Definity G3si PBX

To configure the Lucent/Avaya Definity G3si PBX, do the following:

Step 1. Add the new circuit pack.

Step 2. Add the new signaling group.

Step 3. Add the new trunk group.

Step 4. Add the Uniform Dialing Plan.

Circuit Pack

The following figures show the configuration of the DS1 circuit pack.

DS1 Circuit Pack

DS1 Circuit Pack—ESF Data Link Options

Signaling Group

The following figure shows the configuration of the signaling group.

Signaling Group

Trunk Group

The following figures show the configuration of the trunk group.

Trunk Group

Trunk Group—Trunk Features

Trunk Group—Group Member Assignments

Trunk Group—Group Member Assignments Continued

Uniform Dialing Plan

The following figures show the configuration of the uniform dialing plan.

Dial Plan Record

Uniform Dialing Plan

Pattern Number

Configuring Cisco CallManager

To configure Cisco CallManager, do the following:

Step 1. Configure the gateway.

Step 2. Configure the route pattern.

Gateway Configuration

The following figures show the configuration of the Cisco 3640 MGCP Gateway.

Cisco 3640 MGCP Gateway Configuration

Cisco 3640 MGCP Gateway Configuration Continued

ISDN PRI Configuration

ISDN PRI Configuration Continued

ISDN PRI Configuration Continued

ISDN PRI Configuration Continued

Route Pattern Configuration

The following figures show the configuration of the route pattern.

Route Pattern Configuration

Route Pattern Configuration Continued

Considerations

Calling Name and Number Feature

When calling from a Cisco 7960 IP phone to a Lucent/Avaya digital phone, both phones display Calling Name and Number after the call is answered as expected.

When calling from a Lucent/Avaya digital phone to a Cisco 7960 IP phone, the IP phone displays the Connected Name and Number after the call is answered. The Lucent/Avaya phone, however, displays the Called Name but does not display the Called Number. It was verified using ISDN protocol analyzer that the CallManager was not sending the Connected Number information in the connect message back to PBX.

Integration Testing

This section contains information about the setup used in testing the integration of the Lucent/Avaya Definity G3si V9 PBX with CallManager using the Cisco 3640-T1 PRI as an MGCP Gateway.

CallManager Software Release:

The following figure shows the information about the release of CallManager being used.

CallManager Software Release

Lucent/Avaya Definity G3si Software Release

The following release of the Lucent/Avaya Definity G3si was used:

•System: G3siV6

•Software Version: G3V9i.02.0.033.2

Cisco 3640 Router Configuration

The following shows the configuration of the Cisco 3640 router.

MGCP_3640#show version
Cisco Internetwork Operating System Software
IOS (tm) 3600 Software (C3640-JS-M), Experimental Version 12.2(20020124:013600) [accheung-v122_xn_throttle.build 101]
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Wed 23-Jan-02 17:57 by accheung
Image text-base: 0x60008948, data-base: 0x61608000

ROM: System Bootstrap, Version 11.1(19)AA, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)

MGCP_3640 uptime is 4 days, 2 hours, 11 minutes
System returned to ROM by power-on
System image file is "flash:c3640-js-mz.122-2.XN"

cisco 3640 (R4700) processor (revision 0x00) with 59392K/6144K bytes of memory.
Processor board ID 10620494
R4700 CPU at 100Mhz, Implementation 33, Rev 1.0
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
Primary Rate ISDN software, Version 1.1.
2 Ethernet/IEEE 802.3 interface(s)
24 Serial network interface(s)
2 Channelized T1/PRI port(s)
2 Voice FXO interface(s)
2 Voice FXS interface(s)
DRAM configuration is 64 bits wide with parity disabled.
125K bytes of non-volatile configuration memory.
16384K bytes of processor board System flash (Read/Write)
16384K bytes of processor board PCMCIA Slot0 flash (Read/Write)

Configuration register is 0x2102

_______________________________________________________________________________________

MGCP_3640#show diag
Slot 0:
   Combo 2E, 2W Port adapter, 4 ports
   Port adapter is analyzed
   Port adapter insertion time unknown
   EEPROM contents at hardware discovery:
   Hardware revision 1.2 Board revision B0
   Serial number 7687836 Part number 800-01171-04
   Test history 0x0 RMA number 00-00-00
   EEPROM format version 1
   EEPROM contents (hex):
     0x20: 01 1E 01 02 00 75 4E 9C 50 04 93 04 00 00 00 00
     0x30: 58 00 00 00 98 02 28 17 FF FF FF FF FF FF FF FF

Slot 2:
   4 PORT Voice PM for MARs Port adapter
   Port adapter is analyzed
   Port adapter insertion time unknown
   EEPROM contents at hardware discovery:
   Hardware revision 1.1 Board revision C0
   Serial number 10689987 Part number 800-02491-02
   Test history 0x0 RMA number 00-00-00
   EEPROM format version 1
   EEPROM contents (hex):
     0x20: 01 65 01 01 00 A3 1D C3 50 09 BB 02 00 00 00 00
     0x30: 60 00 00 00 98 11 22 17 FF FF FF FF FF FF FF FF

WIC Slot 0:
   FXS Voice daughter card (2 port)
   Hardware revision 1.1 Board revision C0
   Serial number 11291019 Part number 800-02493-01
   Test history 0x0 RMA number 00-00-00
   Connector type Wan Module
   EEPROM format version 1
   EEPROM contents (hex):
     0x20: 01 0E 01 01 00 AC 49 8B 50 09 BD 01 00 00 00 00
     0x30: 60 00 00 00 99 01 05 01 FF FF FF FF FF FF FF FF

   WIC Slot 1:
   FXO Voice daughter card (2 port)
   Hardware revision 1.1 Board revision C0
   Serial number 8421533 Part number 800-02495-01
   Test history 0x0 RMA number 00-00-00
   Connector type Wan Module
   EEPROM format version 1
   EEPROM contents (hex):
     0x20: 01 0D 01 01 00 80 80 9D 50 09 BF 01 00 00 00 00
     0x30: 60 00 00 00 98 06 02 01 FF FF FF FF FF FF FF FF

Slot 3:
   High Density Voice Port adapter
   Port adapter is analyzed
   Port adapter insertion time unknown
   EEPROM contents at hardware discovery:
   Hardware Revision : 1.0
   Top Assy. Part Number : 800-03567-01
   Baord Revision : A0
   Deviation Number : 0-0
   Fab Version : 02
   PCB Serial Number : JAB03350B9K
   RMA Test History : 00
   RMA Number : 0-0-0-0
   RMA History : 00
   EEPROM format version 4
   EEPROM contents (hex):
     0x00: 04 FF 40 00 CC 41 01 00 C0 46 03 20 00 0D EF 01
     0x10: 42 41 30 80 00 00 00 00 02 02 C1 8B 4A 41 42 30
     0x20: 33 33 35 30 42 39 4B 03 00 81 00 00 00 00 04 00
     0x30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
     0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
     0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
     0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
     0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

   WIC Slot 0:
   T1 (2 Port) Multi-Flex Trunk (Drop&Insert) WAN Daughter Card
   Hardware revision 1.0 Board revision A0
   Serial number 19621702 Part number 800-04614-02
   Test history 0x0 RMA number 00-00-00
   Connector type PCI
   EEPROM format version 1
   EEPROM contents (hex):
     0x20: 01 24 01 00 01 2B 67 46 50 12 06 02 00 00 00 00
     0x30: 50 00 00 00 00 05 20 00 FF FF FF FF FF FF FF FF

   HDV firmware: Compiled Fri 23-Mar-01 00:20 by miriyala
   HDV memory size 524280 heap free 175065

_______________________________________________________________________________________

MGCP_3640#show controller t1

T1 3/0 is up.
Applique type is Channelized T1
Cablelength is long gain36 0db
No alarms detected.
alarm-trigger is not set
Version info Firmware: 20010315, FPGA: 15
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
Data in current interval (5 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
_______________________________________________________________________________________

MGCP_3640#show configuration
Using 1874 out of 129016 bytes
!
version 12.2
no parser cache
no service single-slot-reload-enable
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
no service dhcp
!
hostname MGCP_3640
!
logging rate-limit console 10 except errors
!
!
!
voice-card 3
!
ip subnet-zero
!
!
!
no ip dhcp-client network-discovery
mgcp
mgcp call-agent 10.1.1.2 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode cisco
mgcp sdp simple
mgcp package-capability rtp-package
mgcp package-capability sst-package
no mgcp timer receive-rtcp
no mgcp explicit hookstate
isdn switch-type primary-ni
call rsvp-sync
!
!
!
!
!
ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server 10.1.1.2
ccm-manager config
!
!
controller T1 3/0
framing esf
linecode b8zs
pri-group timeslots 1-24 service mgcp
!
controller T1 3/1
framing sf
linecode ami
!
!
!
interface Ethernet0/0
ip address 10.1.1.200 255.255.255.0
no ip mroute-cache
half-duplex
!
interface Ethernet0/1
ip address 171.69.231.23 255.255.255.0
no ip mroute-cache
half-duplex
!
interface Serial3/0:23
no ip address
no logging event link-status
isdn switch-type primary-ni
isdn incoming-voice voice
isdn T306 30000
isdn T310 40000
isdn bind-l3 ccm-manager
no cdp enable
!
ip classless
no ip http server
!
snmp-server manager
!
voice-port 2/0/0
!
voice-port 2/0/1
!
voice-port 2/1/0
!
voice-port 2/1/1
!
voice-port 3/0:23
!
dial-peer cor custom
!
!
!
dial-peer voice 2 pots
application mgcpapp
port 2/0/0
!
dial-peer voice 1 pots
application mgcpapp
!
dial-peer voice 3 pots
application mgcpapp
port 2/0/1
!
dial-peer voice 999200 pots
application mgcpapp
port 2/0/0
!
dial-peer voice 9993023 pots
application mgcpapp
port 3/0:23
!
!
line con 0
line aux 0
line vty 0 4
login
!
!
end
MGCP_3640#
Test Configuration

The following figure represents the various configurations used for testing.

Testbed Network Configuration

As shown in the figure above, a Lucent/Avaya Definity G3si PBX was connected via an ISDN T1 PRI link to a Cisco 3640 Gateway, which in turn, was connected to an Ethernet switch. The interoperability testing involved Layers 1, 2 and 3 on the ISDN PRI link between a Cisco 3640 and the PBX.

Layer 1 (Physical Layer)

The Lucent/Avaya Definity G3si PBX configuration screen for the DS1 trunk interface is reached using change the ds1 a12 command, which sets the T1 physical layer parameters.

Layers 2 & 3 (Q.921 and Q.931)

Layer 2 and 3 packet exchanges were monitored using an Acacia Clarinet protocol analyzer, bridged across the PRI link in high impedance mode.

Layer 2 Q.921 packets were monitored to ensure that each PBX/3640 software configuration properly exchanged SABME/UA packets to initialize the ISDN link, and then RR packets were exchanged every 30 seconds.

Layer 3 Q.931 packets were monitored to ensure that the appropriate call setup/teardown packets were exchanged for each configuration, and that the SETUP packets contained the mandatory Information Elements with the necessary details, as well as optional IEs such as Calling Name and Number.

Telephone calls were made end-to-end in both directions through the Cisco 3640 Gateway, and a check was made to ensure that there was an audio path in both directions for each call.

User/Network Settings

The Cisco 3640 Gateway with ISDN protocol type setting of PRI-NI2 supports both protocol sides by selecting "Network/User" in the protocol side field when configuring the Gateway via CallManager.

The Lucent/Avaya Definity G3si PBX supports both "USER" and "NETWORK" protocol sides by using change ds1 a12 command.

Test Results

Testing was performed by Test Engineer(s): Samir Batio and Bob Graves, February 25, 2002

Test 1

In test 1:

•The PBX1 country-protocol is set to 1a (US / AT&T TR 41449/41459) to emulate the Network.

•The Cisco 3640 Gateway was configured as a PRI NI2 to emulate the User.

The results are shown in the following tables.

Table 1  Basic Calls (Enbloc Sending)

Calls Made

Call Comp?

Calling Number passed to final destination?

Calling Name passed to final destination?

Called Number passed to original side?

Called Name passed to the original side?

Phone A to Phone C

Yes

Yes

Yes

No ¹

Yes

Phone C to Phone A

Yes

Yes

Yes

Yes

Yes

¹CallManager is not sending "Connected Number" information in the connect message back to PBX.

.

Table 2  Basic Calls (FXS Port)

Calls Made

Call Comp?

Number displayed on digital phone

Name displayed on digital phone

Pone E to Phone A

Yes

Yes

Yes

Phone A to Phone E

Yes

No

Yes

Phone E to Phone C

Yes

Yes

Yes

Phone C to Phone E

Yes

Yes

Yes

Table 3  Call Transfers (Supervised Local Transfers)

Calls Made

Call Comp?

Original Calling Number displayed on final dest phone?

Original Calling Name displayed on final dest phone?

Called Number display on original phone updated after transfer?

Called Name display on original phone updated after transfer?

Phone C to Phone A Xfr to Phone B

Yes

Yes

Yes

No

No

Phone A to Phone C Xfr to Phone D

Yes

Yes

Yes

No

No

Table 4  Call Conferencing (Local)

Calls Made

Call Comp?

Calling Number passed to the remaining conferee when the conferencing phone drops out?

Calling Name passed to the remaining conferee when the conferencing phone drops out?

Connected Number updated on original caller phone display when a conferee drops out?

Connected Name updated on original caller phone display when a conferee drops out?

Phone C to Phone A, Phone A conf Phone B

Yes

(A Drops out)

Yes

(A Drops out)

Yes

(A Drops out)

No

(A Drops out)

No

Phone C to Phone A, Phone C conf Phone D

Yes

(C Drops out)

No

(C Drops out)

No

(D Drops out)

No

(D Drops out)

No

Phone A to Phone C, Phone C conf Phone D

Yes

(C Drops out)

No

(C Drops out)

No

(C Drops out)

No

(C Drops out)

No

Phone A to Phone C, Phone A conf Phone B

Yes

(A Drops out)

No

(A Drops out)

No

(B Drops out)

No

(B Drops out)

No

Table 5  Call Forward (Local)

Calls Made

Call Comp?

Original Calling Number passed to final dest?

Original Calling Name passed to final dest?

Forwarding Called Number passed to final dest?

Forwarding Called Name passed to final dest

Final destination Connected Number updated at original side?

Final destination Connected Name updated at original side?

Phone C to Phone A fwd to Phone B

Yes

No

Yes

No

Yes

No

Yes

Phone A to Phone C fwd to Phone D

Yes

Yes

Yes

No

No

No

Yes

Test 2

In test 2:

•The PBX1 country-protocol is set to 1a (US / AT&T TR 41449/41459) to emulate the User.

•The Cisco 3640 Gateway is configured as a PRI NI2 to emulate the Network.

The test results are identical to those in Test 1.

Calls Made	Call Comp?	Calling Number passed to the remaining conferee when the conferencing phone drops out?	Calling Name passed to the remaining conferee when the conferencing phone drops out?	Connected Number updated on original caller phone display when a conferee drops out?	Connected Name updated on original caller phone display when a conferee drops out?
Phone C to Phone A, Phone A conf Phone B	Yes	(A Drops out) Yes	(A Drops out) Yes	(A Drops out) No	(A Drops out) No
Phone C to Phone A, Phone C conf Phone D	Yes	(C Drops out) No	(C Drops out) No	(D Drops out) No	(D Drops out) No
Phone A to Phone C, Phone C conf Phone D	Yes	(C Drops out) No	(C Drops out) No	(C Drops out) No	(C Drops out) No
Phone A to Phone C, Phone A conf Phone B	Yes	(A Drops out) No	(A Drops out) No	(B Drops out) No	(B Drops out) No

Calls Made	Call Comp?	Calling Number passed to final destination?	Calling Name passed to final destination?	Called Number passed to original side?	Called Name passed to the original side?
Phone A to Phone C	Yes	Yes	Yes	No ¹	Yes
Phone C to Phone A	Yes	Yes	Yes	Yes	Yes

Calls Made	Call Comp?	Number displayed on digital phone	Name displayed on digital phone
Pone E to Phone A	Yes	Yes	Yes
Phone A to Phone E	Yes	No	Yes
Phone E to Phone C	Yes	Yes	Yes
Phone C to Phone E	Yes	Yes	Yes

Calls Made	Call Comp?	Original Calling Number displayed on final dest phone?	Original Calling Name displayed on final dest phone?	Called Number display on original phone updated after transfer?	Called Name display on original phone updated after transfer?
Phone C to Phone A Xfr to Phone B	Yes	Yes	Yes	No	No
Phone A to Phone C Xfr to Phone D	Yes	Yes	Yes	No	No

Calls Made	Call Comp?	Original Calling Number passed to final dest?	Original Calling Name passed to final dest?	Forwarding Called Number passed to final dest?	Forwarding Called Name passed to final dest	Final destination Connected Number updated at original side?	Final destination Connected Name updated at original side?
Phone C to Phone A fwd to Phone B	Yes	No	Yes	No	Yes	No	Yes
Phone A to Phone C fwd to Phone D	Yes	Yes	Yes	No	No	No	Yes