Avaya Solution and Interoperability Test Lab
Configuring Avaya Communication Manager 3.1.1 and
Interactive Response 2.0 with Cisco Call Manager 4.1 Using
H.323 Signaling and IP Trunk Groups to Support IP
Shuffling – Issue 1.0
Abstract
These Application Notes present a sample configuration for a network configuration
comprised of Avaya Communication Manager 3.1.1, Avaya Interactive Response 2.0, and
Cisco Call Manager 4.1. The focus of this configuration is to validate proper shuffling of IP
media paths in the sample network. This configuration supports the communication of Cisco
IP Phones controlled by Cisco Call Manager 4.1 with Avaya IP Phones and Avaya IR H.323
stations served by Avaya Communication Manager 3.1.1. These Application Notes were
written at the request of a customer.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
1 of 48
Acm-CiscoCM.doc
1. Introduction
These Application Notes present a sample configuration for a network configuration comprised
of Avaya Communication Manager 3.1.1, Avaya Interactive Response 2.0 and Cisco Call
Manager 4.1. The focus of this configuration is to validate proper shuffling of IP media paths in
the sample network. This configuration supports the communication of Cisco IP Phones
controlled by Cisco Call Manager 4.1 with Avaya IP Phones and Avaya IR H.323 stations served
by Avaya Communication Manager 3.1.1. These Application Notes were written at the request of
a customer.
Figure 1 illustrates the configuration used for this test.
PHONE /EXIT
P AGE
LEF T
PAGE
RIGHT
OP TIONS
S PEAKER
HOLD
HE ADSET
T RANS FER
ABC
MUTE
1
GH I
3
MNO
5
TUV
7
D EF
2
JKL
4
PQRS
CONFE RE NCE
DROP
6
W XYZ
8
*
REDIAL
9
#
0
ESD GROUND JACK
POW ER
1
2
3
4
5
6
7
8
9
10
PHONE /EXIT
P AGE
LEF T
PAGE
RIGHT
OP TIONS
S PEAKER
HOLD
HE ADSET
T RANS FER
ABC
MUTE
1
GH I
PHONE /EXIT
P AGE
LEF T
PAGE
RIGHT
HOLD
9
CONFE RE NCE
DROP
6
W XYZ
8
3
MNO
5
TUV
0
D EF
2
JKL
4
7
CONFE RE NCE
DROP
REDIAL
T RANS FER
ABC
1
GH I
PQRS
9
#
OP TIONS
S PEAKER
HE ADSET
MUTE
*
3
6
W XYZ
8
0
MNO
5
TUV
7
D EF
2
JKL
4
PQRS
*
REDIAL
#
Figure 1: Sample configuration
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
2 of 48
Acm-CiscoCM.doc
As shown in Figure 1, the network included S8700 Duplex Media Servers configured with a
G650 Media Gateway. The Media Gateway contains the IPSI, C-LAN and Media Processor
boards required for the configuration. The Avaya Interactive Response 2.0 system was
configured to serve H.323 IP endpoints. An H.323 IP trunk group is configured between Avaya
Communication Manager and Cisco Call Manager. Additionally, a TDM trunk was configured as
shown in Figure 1. A five-digit uniform dial plan was used to facilitate calling among the Cisco
and Avaya sites. The Cisco Call Manager utilized extensions in the format 5xxxx while Avaya
Communication Manager utilized extensions in the format 24xxx. Avaya Communication
Manager was configured to route calls to 5xxxx to the Cisco Call Manager over an H.323 trunk
group. Cisco Call Manager will in turn route calls in the format 24xxx to Avaya Communication
Manager.
The configuration depicted and described in Figure 1 was used to verify that the following call
flows are shuffled to “ip-direct” media paths.
•
•
•
•
•
A call placed from a Cisco 7960 IP phone originating from a Cisco Call Manager 4.1(3)
to an Avaya 4620 IP Phone controlled by Avaya Communication Manager 3.1.1 over an
H.323 IP trunk.
A call placed from an Avaya 4620 IP Phone to a Cisco 7960 IP Phone over an H.323 IP
trunk.
A call placed from a PSTN end point that arrives at the Cisco Call Manager and is routed
to an H.323 endpoint on the Avaya IR. The same call may be routed from the Avaya IR
to Avaya Communication Manager and queued to an available agent after playing an
announcement and collecting digits.
An IP phone call originated from Cisco Call Manager over an H.323 IP trunk terminating
on an H.323 Avaya IR 2.0 port controlled by Avaya Communication Manager.
An IP phone call originating from a Cisco Call Manager, routed to an Avaya IR 2.0
H.323 port, and then transferred to an agent served by Avaya Communication Manager.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
3 of 48
Acm-CiscoCM.doc
Table 1 lists the IP address assignment for the device interfaces and network assignments. For
the IP Telephones, the table lists only the telephones that appear in the call traces in Section 6.
Equipment
S8700 Media Server – 1
S8700 Media Server – 2
IP Network/Mask
172.16.254.216/24
172.16.254.217/24
G650 Media Gateway
– IPSI
– C-LAN
– MedPRO
Cisco Call Manager
Cisco Catalyst 6509 Switch
Cisco 2811 MGCP Gateway
Cisco 1841
Cisco ATA 188
Avaya IR 2.0
Avaya 4620 IP Telephone
Cisco 7960 IP Telephone x50502
20.1.1.9/24
20.1.1.10/24
20.1.1.11/24
192.44.130.50/24
192.45.130.10/24
192.45.139.129/24
192.45.130.5/24
192.45.130.30/24
192.45.121.122/24
20.1.1.102/24
192.45.130.223/24
JFZ; Reviewed:
PV 8/3/2006
Gateway
20.1.1.1
20.1.1.1
20.1.1.1
192.44.130.1
192.45.139.2
192.45.121.213
20.1.1.1
192.45.130.1
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
4 of 48
Acm-CiscoCM.doc
2. Equipment and Software Validated
The following hardware and software versions were used for this configuration:
Equipment
Avaya S8700 Media Server
Avaya G650 Media Gateway
Avaya TN2312BP IPSI
Avaya TN799DP C-LAN
Avaya TN2302AP MEDPRO
Avaya TN464F
Cisco Call Manager
Avaya Interactive Response
Avaya 4620SW IP Telephone
Cisco CP-7960 IP Telephone
Cisco Catalyst 6509 Switch
Cisco 2811 MGCP Gateway
Cisco 1841
Version
3.1.1 Load 628.7 , Patch 01.1.628.7-11846
HW03 FW030
HW01 FW017
HW20 FW110
Vintage 00020
V 4.1(3)
R. 2.0
2.3
PC03A300 v.7.2(2.0)
L3 12.3
12.3
12.3
Table 2 – Equipment and Version Validated
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
5 of 48
Acm-CiscoCM.doc
3. Avaya Communication Manager Configuration
This section describes the steps required for Avaya Communication Manager to interoperate with
the Cisco Call Manager supporting the configuration in Figure 1. The following pages provide
step-by-step instructions on how to verify and administer the required configuration parameters.
The assumption is that the appropriate license and authentication files have been installed on the
servers and that login and password credentials are available. It is assumed that the reader has a
basic understanding of the administration of Avaya Communication Manager and has access to
the System Administration Terminal screens.
3.1. Verify Avaya Communication Manager Licensing
The following commands were entered on an Avaya Communication Manager System Access
Terminal (SAT).
Step Description
1. Issue the command “display system-parameters customer-options” to display the
active licensed features. Go to Page 2 to ensure that the “Maximum Administered
H.323 Trunks” and “Maximum Concurrently Registered IP Stations” is set to a
value equal to or greater than the number of endpoints projected in the configuration.
display system-parameters customer-options
OPTIONAL FEATURES
Page
IP PORT CAPACITIES
Maximum Administered H.323 Trunks:
Maximum Concurrently Registered IP Stations:
Maximum Administered Remote Office Trunks:
Maximum Concurrently Registered Remote Office Stations:
Maximum Concurrently Registered IP eCons:
Max Concur Registered Unauthenticated H.323 Stations:
Maximum Video Capable H.323 Stations:
Maximum Video Capable IP Softphones:
Maximum Administered SIP Trunks:
Maximum Number of DS1 Boards with Echo Cancellation:
Maximum TN2501 VAL Boards:
Maximum G250/G350/G700 VAL Sources:
Maximum TN2602 Boards with 80 VoIP Channels:
Maximum TN2602 Boards with 320 VoIP Channels:
Maximum Number of Expanded Meet-me Conference Ports:
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
100
100
8000
12000
0
50
0
0
0
USED
6
7
0
0
0
0
0
0
0
0
1
1
0
0
0
0
0
0
0
0
0
2 of
10
6 of 48
Acm-CiscoCM.doc
Step Description
2. Go to Page 5 and verify the “IP Stations” field is set to “y”.
display system-parameters customer-options
OPTIONAL FEATURES
Emergency Access to Attendant?
Enable 'dadmin' Login?
Enhanced Conferencing?
Enhanced EC500?
Enterprise Survivable Server?
Enterprise Wide Licensing?
ESS Administration?
Extended Cvg/Fwd Admin?
External Device Alarm Admin?
Five Port Networks Max Per MCC?
Flexible Billing?
Forced Entry of Account Codes?
Global Call Classification?
Hospitality (Basic)?
Hospitality (G3V3 Enhancements)?
IP Trunks?
Page
4 of
10
y
IP Stations?
y
Internet Protocol (IP) PNC?
y
ISDN Feature Plus?
n
ISDN Network Call Redirection?
n
ISDN-BRI Trunks?
n
ISDN-PRI?
n
Local Survivable Processor?
n
Malicious Call Trace?
n
Media Encryption Over IP?
n
Mode Code for Centralized Voice Mail?
n
n
Multifrequency Signaling?
n Multimedia Appl. Server Interface (MASI)?
y
Multimedia Call Handling (Basic)?
n
Multimedia Call Handling (Enhanced)?
y
y
n
y
n
n
y
n
n
y
n
y
n
y
y
IP Attendant Consoles? n
3. Go to Page 9 and verify the “Maximum IP Registrations By Product ID” limit field
for “IP_API_A” is set to a value greater than or equal to the number of H.323 ports to
be used to connect to Avaya IR. The use of IP_API_A is new for Avaya IR 2.0. Also
verify “IP_Phone” is greater than or equal to the number of IP phones to be used.
display system-parameters customer-options
MAXIMUM IP REGISTRATIONS BY PRODUCT ID
Product ID
IP_API_A
IP_API_B
IP_API_C
IP_Agent
IP_IR_A
IP_Phone
IP_ROMax
IP_Soft
IP_eCons
JFZ; Reviewed:
PV 8/3/2006
Rel.
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
Limit
24
24
24
24
24
12000
12000
24
0
0
0
0
0
0
0
Page
9 of
10
Used
5
0
0
0
0
2
0
0
0
0
0
0
0
0
0
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
7 of 48
Acm-CiscoCM.doc
3.2. Avaya Communication Manager IP Administration
This section describes the steps for the configuration of Avaya Communication Manager for IP
interoperability.
Step
Description
4. Use the command “change node-names ip” which maps logical names to IP addresses.
These node names will be used in subsequent screens. Add an entry for the C-LAN,
Medpro and Cisco Call Manager.
change node-names ip
Name
Call-Manager
clan
medpro
Page
IP NODE NAMES
IP Address
Name
192.45 .130.50
20 .1 .1 .10
20 .1 .1 .11
1 of
1
IP Address
.
.
.
.
.
.
.
.
.
5. Configure the C-LAN by issuing the command “add ip-interface 01a03” where 01a03
is the board location of the C-LAN. Enter the previously assigned Node Name, a
Subnet Mask, and a Gateway Address. Ensure “Allow H.323 Endpoints?” is “y”.
add ip-interface 01a03
Page
1 of
1
IP INTERFACES
Type:
Slot:
Code/Suffix:
Node Name:
IP Address:
Subnet Mask:
Gateway Address:
Enable Ethernet Port?
Network Region:
VLAN:
C-LAN
01A03
TN799 D
clan
20 .1 .1 .10
255.255.255.0
20 .1 .1 .1
y
1
n
Link: 1
Allow H.323 Endpoints? y
Allow H.248 Gateways? y
Gatekeeper Priority: 5
Target socket load and Warning level: 400
Receive Buffer TCP Window Size: 8320
ETHERNET OPTIONS
Auto? y
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
8 of 48
Acm-CiscoCM.doc
Step
Description
6. Add a data module for the C-LAN circuit pack. Use the command “add data-module
24500”. Any available extension that conforms to the dial-plan can be used. For this
configuration, extension 24500 is used. Set the “Type” field to “Ethernet” and the
“Port” field to port 17 of the C-LAN circuit pack.
add data-module 24500
DATA MODULE
Data Extension:
Type:
Port:
Link:
24500
ethernet
01A0317
1
Name: clan
Network uses 1's for Broadcast Addresses? y
7. For informational purposes, the following screen illustrates the configuration of the
Medpro used in the sample configuration.
display ip-interface 01a04
Page
1 of
1
IP INTERFACES
Type:
Slot:
Code/Suffix:
Node Name:
IP Address:
Subnet Mask:
Gateway Address:
Enable Ethernet Port?
Network Region:
VLAN:
MEDPRO
01A04
TN2302
medpro
20 .1 .1 .11
255.255.255.0
20 .1 .1 .1
y
1
n
ETHERNET OPTIONS
Auto? y
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
9 of 48
Acm-CiscoCM.doc
Step
Description
8. Configure the Network Region that will be used in the configuration with an appropriate
codec set. Ensure the “IP Direct Audio” fields shown in bold are set to “y” to allow
“shuffling” to IP-Direct media paths.
change ip-network-region 1
Page
1 of
19
IP NETWORK REGION
Region: 1
Location: 1
Authoritative Domain:
Name: ACM
MEDIA PARAMETERS
Intra-region IP-IP Direct Audio: yes
Codec Set: 1
Inter-region IP-IP Direct Audio: yes
UDP Port Min: 2048
IP Audio Hairpinning? n
UDP Port Max: 3029
DIFFSERV/TOS PARAMETERS
RTCP Reporting Enabled? y
Call Control PHB Value: 46
RTCP MONITOR SERVER PARAMETERS
Audio PHB Value: 46
Use Default Server Parameters? y
Video PHB Value: 26
802.1P/Q PARAMETERS
Call Control 802.1p Priority: 6
Audio 802.1p Priority: 6
Video 802.1p Priority: 5
AUDIO RESOURCE RESERVATION PARAMETERS
H.323 IP ENDPOINTS
RSVP Enabled? n
H.323 Link Bounce Recovery? y
Idle Traffic Interval (sec): 20
Keep-Alive Interval (sec): 5
Keep-Alive Count: 5
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
10 of 48
Acm-CiscoCM.doc
3.3. H.323 Signaling Group and IP Trunk Group Configuration to
Cisco Call Manager
This section describes the parameter settings for the H.323 signaling group and IP Trunk group
used to connect with Cisco Call Manager. Signaling group 2 will be used to establish an H.323
signaling link between the C-LAN in the Avaya G650 and the Cisco Call Manager. The number
of the signaling group can be any available number.
Step
9.
Description
Issue the command “add signaling-group 2” from the SAT interface. The trunk
“Group Type” is h.323. The signaling group uses the C-LAN as the near end, and the
Cisco Call Manager node-name “Call-Manager” as the far end. Port 1720 is used for
the near-end and far-end listen port. The “Calls Share IP Signaling Connection” field
should remain set to the default setting of “n”. The “Direct IP-IP Audio Connections?”
field should be set to “y” to allow for IP shuffling. The “IP Audio Hairpinning?” is
intentionally set to “n”. The far-end Network Region field can be left blank or can be
configured to associate with the Cisco Call Manager. By configuring this field, one can
use an audio codec for inter-region calls from Avaya to Cisco and a different codec for
intra-region calls for Avaya endpoints.
add signaling-group 2
Page
1 of
5
SIGNALING GROUP
Group Number: 2
Group Type:
Remote Office?
SBS?
IP Video?
Trunk Group for Channel Selection:
Supplementary Service Protocol:
T303 Timer(sec):
Near-end Node Name: clan
Near-end Listen Port: 1720
LRQ Required? n
RRQ Required? n
Media Encryption? n
DTMF over IP: out-of-band
JFZ; Reviewed:
PV 8/3/2006
h.323
n
n
n
Max number of NCA TSC: 0
Max number of CA TSC: 0
Trunk Group for NCA TSC:
a
10
Far-end Node Name: Call-Manager
Far-end Listen Port: 1720
Far-end Network Region:
Calls Share IP Signaling Connection? n
H245 Control Addr On FACility? n
Bypass If IP Threshold Exceeded? n
H.235 Annex H Required? n
Direct IP-IP Audio Connections? y
IP Audio Hairpinning? n
Interworking Message: PROGress
DCP/Analog Bearer Capability: 3.1kHz
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
11 of 48
Acm-CiscoCM.doc
10. Use the command “add trunk-group 2” to create an H.323 IP trunk group. Set the
“Group Type” to “isdn”, configure an appropriate TAC, and set the Direction to “twoway”. The Carrier Medium is set to H.323.
add trunk-group 2
Page
1 of
21
TRUNK GROUP
Group Number:
Group Name:
Direction:
Dial Access?
Queue Length:
Service Type:
2
Group Type: isdn
CDR Reports: y
to Cisco Call Manager
COR: 1
TN: 1
TAC: 101
two-way
Outgoing Display? n
Carrier Medium: H.323
y
Busy Threshold: 255
Night Service:
0
tie
Auth Code? n
Member Assignment Method: manual
11. Proceed to page 2 of the ‘add trunk-group’ screen. Set the “Codeset to Send Display”
field to “0”. When set to 0, the Cisco Call Manager will display the calling party name
on incoming calls from Avaya to Cisco phones. Also, the Cisco Call Manager will
display the connected party name on Cisco phones when calls from Cisco to Avaya are
answered.
add trunk-group 2
Group Type: isdn
Page
TRUNK PARAMETERS
Codeset to Send Display: 0
Disconnect Supervision - In? y
Answer Supervision Timeout: 0
JFZ; Reviewed:
PV 8/3/2006
21
Codeset to Send National IEs: 6
Charge Advice: none
Digit Handling (in/out): enbloc/enbloc
Supplementary Service Protocol: a
Incoming Calling Number - Delete:
2 of
Insert:
Digital Loss Group: 18
Format:
Out? n
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
12 of 48
Acm-CiscoCM.doc
12. Proceed to page 3 of the “add trunk-group” command. The “Send Connected
Number” field should remain set to “n” so that the Avaya Media server will not include
a connected number information element in the Q.931 Connect message. Cisco Call
Manager will not display the connected number, if present in the Q.931 Connect
message. Set “y” in the fields “Send Name” and “Send Calling Number”. It is
assumed that other common procedures relevant to formatting the calling number have
been followed (i.e., not shown, and not unique to this configuration).
add trunk-group 2
TRUNK FEATURES
ACA Assignment? n
Used for DCS? n
Suppress # Outpulsing? n
Page
Measured:
Internal Alert?
Data Restriction?
Send Name:
none
n
n
y
3 of
21
Maintenance Tests? y
NCA-TSC Trunk Member:
Send Calling Number: y
Send EMU Visitor CPN? n
Format: public
UUI IE Treatment: service-provider
Replace Restricted Numbers?
Replace Unavailable Numbers?
Send Connected Number:
Hold/Unhold Notifications?
Modify Tandem Calling Number?
Send UUI IE? y
Send UCID? n
Send Codeset 6/7 LAI IE? y
n
n
n
n
n
13. Proceed to page 5 of the “add trunk-group” command. Add members into the trunk
group. Use keyword “ip” in the “Port” field and enter the respective signaling group
number of “2” which is used in this configuration.
add trunk-group 2
GROUP MEMBER ASSIGNMENTS
1:
2:
3:
4:
5:
6:
JFZ; Reviewed:
PV 8/3/2006
Port
ip
ip
ip
ip
ip
ip
Name
Page
5 of 21
TRUNK GROUP
Administered Members (min/max):
1/6
Total Administered Members:
6
Night
Sig Grp
2
2
2
2
2
2
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
13 of 48
Acm-CiscoCM.doc
14. Issue the command “change signaling-group 2”. The “Trunk Group for Channel
Selection” should be configured with the H.323 trunk group number defined in the
previous steps.
change signaling-group 2
Page
1 of
5
SIGNALING GROUP
Group Number: 2
Group Type:
Remote Office?
SBS?
IP Video?
Trunk Group for Channel Selection:
Supplementary Service Protocol:
T303 Timer(sec):
Near-end Node Name: clan
Near-end Listen Port: 1720
LRQ Required? n
RRQ Required? n
Media Encryption? n
DTMF over IP: out-of-band
h.323
n
n
n
2
a
10
Max number of NCA TSC: 0
Max number of CA TSC: 0
Trunk Group for NCA TSC:
Far-end Node Name: Call-Manager
Far-end Listen Port: 1720
Far-end Network Region:
Calls Share IP Signaling Connection? n
H245 Control Addr On FACility? n
Bypass If IP Threshold Exceeded? n
H.235 Annex H Required? n
Direct IP-IP Audio Connections? y
IP Audio Hairpinning? n
Interworking Message: PROGress
DCP/Analog Bearer Capability: 3.1kHz
3.4. IP Station Configuration for the Avaya IP and Avaya IR Ports
This section describes the parameter settings for the IP station for each Avaya IP phone and
Avaya IR station. Station extension 24001 is used for the Avaya 4620 IP phone. Any available
extension can be used that conforms to the dial plan. Station extensions 24444 thru 24448 are
used for the Avaya IR.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
14 of 48
Acm-CiscoCM.doc
Step Description
15. Issue the command “add station 24001” where extension 24001 will be used for the
4620 IP phone. Set the station “Type” to “4620” and the “Port” field is populated as
“IP”. Enter a “Name” in the optional name field for identification of stations. Assign a
“Security Code”.
add station 24001
Page
1 of
4
STATION
Extension:
Type:
Port:
Name:
24001
4620
IP
Avaya IP Station
STATION OPTIONS
Loss Group: 19
Speakerphone:
Display Language:
Survivable GK Node Name:
Survivable COR:
Survivable Trunk Dest?
2-way
english
Lock Messages? n
Security Code: 12345
Coverage Path 1:
Coverage Path 2:
Hunt-to Station:
BCC: 0
TN: 1
COR: 1
COS: 1
Personalized Ringing Pattern:
Message Lamp Ext:
Mute Button Enabled?
Expansion Module?
internal
y
1
24009
y
n
Media Complex Ext:
IP SoftPhone? n
16. Proceed to page 2 and set the “Multimedia Mode” field to “enhanced” and ensure
“Direct IP-IP Audio Connections” is set to “y” to allow “shuffling” of media paths to
“ip-direct” for this station.
add station 24001
Page
2 of
4
STATION
FEATURE OPTIONS
LWC Reception:
LWC Activation?
LWC Log External Calls?
none
CDR Privacy?
Redirect Notification?
Per Button Ring Control?
Bridged Call Alerting?
Active Station Ringing:
spe
y
n
n
y
n
n
single
H.320 Conversion? n
Service Link Mode: as-needed
Multimedia Mode: enhanced
MWI Served User Type:
AUDIX Name:
Emergency Location Ext: 24009
JFZ; Reviewed:
PV 8/3/2006
Auto Select Any Idle Appearance? n
Coverage Msg Retrieval? y
Auto Answer:
Data Restriction?
Idle Appearance Preference?
Bridged Idle Line Preference?
Restrict Last Appearance?
Conf/Trans on Primary Appearance?
n
n
n
y
n
Per Station CPN - Send Calling Number?
Display Client Redirection?
Select Last Used Appearance?
Coverage After Forwarding?
Multimedia Early Answer?
Direct IP-IP Audio Connections?
IP Audio Hairpinning?
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
n
n
s
n
y
n
15 of 48
Acm-CiscoCM.doc
Step Description
17. Configure the stations to be used for Avaya IR. Issue the command “add station
24444”. Set the station “Type” field as “7434ND”, the “Port” field as “IP” . Assign a
“Security Code”. Set the “IP Softphone” to “y”.
add station 24444
Page
1 of
4
STATION
Extension:
Type:
Port:
Name:
24444
7434ND
IP
IR Port
Lock Messages? n
Security Code: 12345
Coverage Path 1:
Coverage Path 2:
Hunt-to Station:
STATION OPTIONS
Loss Group: 2
Data Module? n
Display Module? n
BCC: 0
TN: 1
COR: 1
COS: 1
Personalized Ringing Pattern: 1
Message Lamp Ext: 24449
Coverage Module? n
Media Complex Ext:
IP SoftPhone? y
Remote Office Phone? n
18. Proceed to page 2 and set the “Multimedia Mode” field to “enhanced” and “Direct IPIP Audio Connections?” to “y”.
add station 24444
Page
2 of
4
STATION
FEATURE OPTIONS
LWC Reception:
LWC Activation?
LWC Log External Calls?
none
CDR Privacy?
Redirect Notification?
Per Button Ring Control?
Bridged Call Alerting?
Active Station Ringing:
spe
y
n
n
y
n
n
single
H.320 Conversion? n
Service Link Mode: as-needed
Multimedia Mode: enhanced
MWI Served User Type:
AUDIX Name:
Emergency Location Ext: 24009
Auto Select Any Idle Appearance? n
Coverage Msg Retrieval? y
Auto Answer:
Data Restriction?
Idle Appearance Preference?
Bridged Idle Line Preference?
Restrict Last Appearance?
Conf/Trans on Primary Appearance?
n
n
n
y
n
Per Station CPN - Send Calling Number?
Display Client Redirection?
Select Last Used Appearance?
Coverage After Forwarding?
Multimedia Early Answer?
Direct IP-IP Audio Connections?
IP Audio Hairpinning?
n
n
s
n
y
n
Repeat the above steps to add a new IP phone station or Avaya IR station.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
16 of 48
Acm-CiscoCM.doc
3.5. Hunt Group Configuration for Avaya IR Ports
This section describes the parameter settings for the hunt group that will be used to route calls to
the Avaya IR ports. For this configuration, hunt group 2 is used. Any available hunt group
number can be used.
Step Description
19. Issue the command “add hunt-group 2”. Assign the hunt group extension number in the
“Group Extension” field. Set the “Group Type” field to ”ucd-mia” to distribute calls
to the Avaya IR port hunt group members.
add hunt-group 2
Page
1 of
60
HUNT GROUP
Group Number:
Group Name:
Group Extension:
Group Type:
TN:
COR:
Security Code:
ISDN/SIP Caller Display:
2
ACD?
IR Hunt Group
Queue?
24400
Vector?
ucd-mia
Coverage Path:
1
Night Service Destination:
1
MM Early Answer?
Local Agent Preference?
grp-name
n
n
n
n
n
20. Go to page 3 and add the Avaya IR station extensions as members of this hunt group.
For this configuration, there were 5 members added in the range 24444 thru 24448.
add hunt-group 2
Page
3 of 60
HUNT GROUP
Group Number: 2
Group Extension: 24400
Group Type: ucd-mia
Member Range Allowed: 1 - 1500
Administered Members (min/max): 1
/5
Total Administered Members: 5
GROUP MEMBER ASSIGNMENTS
Ext
Name (24 characters)
Ext
Name (24 characters)
1: 24444
IR Port 1
14:
2: 24445
IR Port 2
15:
3: 24446
IR Port 3
16:
4: 24447
IR Port 3
17:
5: 24448
IR Port 5
18:
6:
19:
7:
20:
8:
21:
9:
22:
10:
23:
11:
24:
12:
25:
13:
26:
At End of Member List
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
17 of 48
Acm-CiscoCM.doc
3.6. Vector used for Call Prompting
The following vector “223” is used for the call prompting after the call is transferred from the
Avaya IR back to Avaya Communication Manager. The announcement is played via a voice
announcement board within the Avaya G650 Media Gateway.
display vector 223
Page
1 of
3
CALL VECTOR
Number:
Multimedia?
Basic?
Prompting?
Variables?
01 collect
02 route-to
03 route-to
04 stop
05
06
07
08
09
10
223
Name: IVR Route to
n
Meet-me Conf? n
Lock? n
y
EAS? y
G3V4 Enhanced? y
ANI/II-Digits? n
ASAI Routing? n
y
LAI? n G3V4 Adv Route? n
CINFO? n
BSR? n
Holidays? n
n
3.0 Enhanced? y
5
digits after announcement 24888
digits with coverage y
number 0
with cov n if unconditionally
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
18 of 48
Acm-CiscoCM.doc
4. Avaya Interactive Response Software Configuration
The following steps illustrate how to configure Avaya IR 2.0 using its web configuration.
Step Description
21. Launch a web browser and connect to URL http://192.45.121.122 (the IP address of the
Avaya IR). The following screen appears.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
19 of 48
Acm-CiscoCM.doc
Step Description
22. Click “Web Administration” on the main menu and enter a username and password with
administration privileges as shown below. Click the “Logon” Button to log in to the
Avaya IR system.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
20 of 48
Acm-CiscoCM.doc
4.1. Verify Avaya Interactive Response Licenses
Avaya IR 2.0 uses the WebLM licensing servers, which enable the features licenses. These
licenses are tied to the MAC address of each IR system. Both Primary and Secondary license
servers can be utilized. The following depicts how to verify that the licenses for a configuration
are active on the Avaya IR system.
Step Description
23. After logon to the Avaya IR system, the following screen appears. The left side of the
web page contains all of the Administrative tasks that can be performed. To verify the
licenses are correctly installed and active, click on “Feature Licensing” under the
“Configuration Management” section.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
21 of 48
Acm-CiscoCM.doc
Step Description
24. Verify the feature type “VALUE_IR_PORTS” has a value under free ports that is
equal to or greater than the number of ports to be configured on the IR system. In this
configuration, a total of 104 IR ports were available for use.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
22 of 48
Acm-CiscoCM.doc
4.2. Configure Interactive Response
The following screens explain how to configure the H.323 ports and assign a voice script to each
of the channels used in the configuration.
Step Description
25. Click on “Voice over IP” under the “Switch Interfaces” section. Click on the “Assign
Card” link to administer the IR VoIP Card.
26. Next, assign a VoIP card to the system. For this configuration, card number 6 is
configured in the “Card” field . Click the “Submit” button.
27. Assign the VoIP card parameters for Card 6 to use the CLAN board of the Avaya G650
Media Gateway. Click the “Submit” button when complete.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
23 of 48
Acm-CiscoCM.doc
Step Description
28. A confirmation page confirms the assignment of VoIP card number 6. The Card IP
Address is the local address assigned to the NIC of the Avaya IR. The Gatekeeper IP
Address is the IP address of the C-LAN board in the Avaya G650 Media Gateway. Set
the Avaya CM Version field to 3.0. (Avaya Communication Manager Release 3.1.1
uses the value 3.0). Click the “Submit” button.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
24 of 48
Acm-CiscoCM.doc
Step Description
29. Next assign the Avaya IR channels. Click on “Phone Number” under the “Voice
Equipment” section. Click on “Assign”.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
25 of 48
Acm-CiscoCM.doc
Step Description
30. Enter the station or range of stations for each VoIP channel in the “Phone Number”
fields, the IR channel in the “Channel Number” fields, and the password in the “VoIP
H.323 MultiVantage Station Password” fields. Note: The password must match the
“Security Code” on Page 1 of the Avaya Communication Manager SAT “add
station” command for the corresponding phone number. Repeat this step for each
phone number or range of phone numbers to be used. In this configuration, the
configured phones numbers were from 24444 to 24448. Click the “Submit” button to
complete the assignment of each phone number or range of phone numbers.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
26 of 48
Acm-CiscoCM.doc
Step Description
31. Click on “Channel Services” under “Voice Services”. This step is required to assign
an application to each of the channels configured. Select each of the channels and click
“Assign Selected”.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
27 of 48
Acm-CiscoCM.doc
Step Description
32. Assign the test application blindxfr from the drop down list for each of the channels to
be used. For this configuration, application blindxfr was used to test the transfer, and
shuffling capabilities. Note: The blindxfr application was modified with the Avaya
IVR designer application for the configuration tested. Click the “Submit” button.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
28 of 48
Acm-CiscoCM.doc
Step Description
33. The following screen will appear confirming that the application “bindxfr” has been
successfully assigned to each of the configured channels.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
29 of 48
Acm-CiscoCM.doc
4.3. Activating the Interactive Response System
To activate the voice system after administration of channels perform the following steps.
Step Description
34. Click on “Start Voice System” under the “System Control” section to start the voice
system. Click “Submit”.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
30 of 48
Acm-CiscoCM.doc
Step Description
35. Avaya IR confirms the voice system startup with the following screen:
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
31 of 48
Acm-CiscoCM.doc
5. Cisco Call Manager Configuration
This section describes the steps required for the Cisco Call Manager 4.1 to interoperate with
Avaya Communication Manager 3.1.1 over an H.323 IP trunk. The Cisco Call Manager will be
configured with an H.323 Gateway. Additionally, a route pattern configuration is required to
send calls to Avaya Communication Manager via the appropriate H.323 gateway configured on
the Cisco Call Manager.
Step
1.
Description
Start the Call Manager Administration program and select “Add a New Device” from
the “Device menu”. Use the drop down menu to select “H.323 Gateway” as “Gateway
type” and “H.225” as “Device Protocol” and click “Next”.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
32 of 48
Acm-CiscoCM.doc
Step
2.
Description
After clicking “Next”, enter the gateway configuration as shown below. The “Device
Name” corresponds to the C-LAN IP address used in the signaling group definition on
Avaya Communication Manager. Note that the Media Termination Point Required
field was not checked in this configuration.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
33 of 48
Acm-CiscoCM.doc
Step
3.
Description
Continuation of the Gateway configuration page is as follows:
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
34 of 48
Acm-CiscoCM.doc
Step
4.
Description
Next configure a route pattern such that calls from Cisco IP phones to extension range
24XXX are directed to the gateway 20.1.1.10, the IP address of the C-LAN in the Avaya
G650 Media Gateway. Click “Route Plan” and select “Route Pattern”. Enter
“24XXX” in the “Route Pattern” field as shown below. When complete, click
“Update” to add the route pattern.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
35 of 48
Acm-CiscoCM.doc
Step
5.
Description
Continuation of the route pattern configuration is as follows. Default values were used.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
36 of 48
Acm-CiscoCM.doc
6. Verification Steps
The following steps can be used to verify the configuration described in these Application Notes.
Step
1.
Description
Make a phone call from the Cisco 7960 IP phone to the Avaya 4620 IP phone and verify
the voice quality is good and the IP trunk is used to carry the signaling and the
G.711MU audio. From the Avaya SAT screen, run the command “status station 24001”
which will display the call signaling and audio information.
status station 24001
Page
3 of
6
CALL CONTROL SIGNALING
Port: S00003
Switch
Port
IP Signaling: 01A0317
H.245:
Node Name:
Network Region:
IP
Switch-end IP Addr:Port
20. 1. 1. 10
:1720
IP
Set-end IP Addr:Port
20. 1. 1.102:4069
clan
1
1
Shared Port:
Switch
Port
IP
Switch-end IP Addr:Port
IP
Set-end IP Addr:Port
IP Signaling:
H.245:
Node Name:
Network Region:
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
37 of 48
Acm-CiscoCM.doc
Step
2.
Description
To verify shuffling is operational from the Cisco 7960 IP phone (192.45.130.223) to the
Avaya IP phone x24001 (20.1.1.102), proceed to page 4 of the status station screen.
Observe that the final audio path is ip-direct between the two endpoints.
status station 24001
Switch
Port
G.711MU
Page
AUDIO CHANNEL
Port: S00003
IP
Other-end IP Addr :Port
192. 45.130.223
:27372
Audio:
Node Name:
Network Region:
1
Audio Connection Type: ip-direct
4 of
6
IP
Set-end IP Addr:Port
20. 1. 1.102:3022
1
The RTP message trace also verifies IP shuffling is successful. The Medpro (20.1.1.11)
is no longer required for the call once “shuffling” occurs. The final RTP media flow is
directly between the two IP telephones, as is indicated at the end of the trace.
3.
Issue the command “status trunk 2” which will display the trunk group status. The
result shown verifies that the voice channel is in service and active on trunk 2 and
member 1.
status trunk 2
TRUNK GROUP STATUS
Member
Port
Service State
Mtce Connected Ports
Busy
0002/001
0002/002
0002/003
0002/004
0002/005
0002/006
T00008
T00009
T00010
T00011
T00012
T00013
in-service/active
in-service/idle
in-service/idle
in-service/idle
in-service/idle
in-service/idle
no
no
no
no
no
no
JFZ; Reviewed:
PV 8/3/2006
S00003
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
38 of 48
Acm-CiscoCM.doc
Step
4.
Description
Make a phone call from the Cisco 7960 IP phone to a port on the Avaya IR system. The
caller should dial hunt group extension x24400 as previously configured. The call will
route to an available H.323 port on the Avaya IR. In this example, the call is routed to
station 24444. The caller will hear a script play. The caller enters “1” after the
announcement is played to be routed to the “Sales Department”. The call will then be
transferred to a VDN on Avaya Communication Manager. In this simple example, the
caller will hear an announcement to enter an extension. The caller enters “24001” and
the call is subsequently sent to an agent at x24001. The call should be direct and not be a
bridged call. Issue the command “status station 24444” which shows IP shuffling is
successful.
status station 24444
Page
1 of
6
GENERAL STATUS
Administered Type: 7434D
Service State: in-service/off-hook
Connected Type: N/A
TCP Signal Status: connected
Extension: 24444
Port: S00005
Parameter Download: not-applicable
Call Parked? no
SAC Activated? no
Ring Cut Off Act? no
CF Destination Ext:
Active Coverage Option: 1
EC500 Status: N/A
Message Waiting:
Connected Ports: T00008
User Cntrl Restr: none
Group Cntrl Restr: none
JFZ; Reviewed:
PV 8/3/2006
Off-PBX Service State: N/A
HOSPITALITY STATUS
Awaken at:
User DND: not activated
Group DND: not activated
Room Status: non-guest room
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
39 of 48
Acm-CiscoCM.doc
Step
5.
Description
To verify shuffling is operational from the Cisco 7960 IP phone (192.45.130.223) to the
Avaya IR port x24444 (192.45.121.122), proceed to page 4 of the status station screen.
Observe that the audio path is ip-direct between the two endpoints.
status station 24444
Switch
Port
G.711MU
Page
AUDIO CHANNEL
Port: S00005
IP
Other-end IP Addr :Port
192. 45.130.223
:25134
Audio:
Node Name:
Network Region:
1
Audio Connection Type: ip-direct
Product ID and Release:
H.245 Tunneled in Q.931?
Registration Status:
MAC Address:
Native NAT Address:
ALG - NAT WAN IP address:
Authentication Type:
JFZ; Reviewed:
PV 8/3/2006
Port: S00005
IP_API_A
1.300
does not apply
registered-authenticated
unavailable
not applicable
not applicable
DES-56
4 of
6
IP
Set-end IP Addr:Port
192. 45.121.122:8000
1
Shared Port:
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
40 of 48
Acm-CiscoCM.doc
Step
6.
Description
After the call is transferred from the Avaya IR to an agent on Avaya Communication
Manager, verify the call is shuffled by issuing the command “status station 24001”. The
audio is successfully shuffled between the Cisco IP 7960 IP phone with IP address
192.45.130.223, and the Avaya 4620 IP Phone with IP address 20.1.1.102.
status station 24001
Page 4 of 6
Switch
Port
G.711MU
AUDIO CHANNEL
Port: S00003
IP
Other-end IP Addr :Port
192. 45.130.223
:27750
Audio:
Node Name:
Network Region:
1
Audio Connection Type: ip-direct
IP
Set-end IP Addr:Port
20. 1. 1.102:3022
1
The entire RTP packet trace is as follows which first shows the audio connection from
the Cisco 7960 phone (192.45.130.223) to the Avaya IR endpoint (192.45.121.122). The
transfer is made and the last 2 entries show the direct connection between the Cisco 7960
phone (192.45.130.223) and the Avaya 4620 IP Phone (20.1.1.102). The Medpro
(20.1.1.11) is not involved in the final media path.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
41 of 48
Acm-CiscoCM.doc
Step
7.
Description
The following shows the “list trace tac 101” (TAC of H.323 trunk group) from the call
placed from the Cisco 7960 IP phone to the Avaya IR 2.0 system and then transferred to
the Avaya Communication Manager 4620 IP phone. This call is from the Cisco 7960 IP
phone x50502 to hunt group extension x24400. Caller enters ‘1’ after hearing the
announcement prompt. The call is then routed to a vector 223 on Avaya Communication
Manager where the caller is prompted via an announcement to enter an extension. The
caller enters “24001” and the call is subsequently transferred to the Avaya phone 4620
IP phone x24001.
list trace tac 101
Page
1
LIST TRACE
time
data
09:27:58
Calling party trunk-group 2 member 1 cid 0x13f
09:27:58
Calling Number & Name 50502 NO-CPName
09:27:58
active trunk-group 2 member 1 cid 0x13f
09:27:58
dial 24400
09:27:58
ring hunt-group 2
cid 0x13f
09:27:58
G711MU ss:off ps:20 rn:1/1 192.45.121.122:8008 20.1.1.11:2432
09:27:58
xoip: fax:Relay modem:off tty:US 20.1.1.11:2432 uid:0x5
09:27:59
active station
24448 cid 0x13f
09:27:59
G711MU ss:off ps:20 rn:1/1 192.45.130.223:30704 20.1.1.11:2428
09:27:59
xoip: fax:Relay modem:off tty:US 20.1.1.11:2428 uid:0x50008
09:27:59
G711MU ss:off ps:20 rn:1/1 192.45.130.50:4000 192.45.121.122:8008
09:27:59
G711MU ss:off ps:20 rn:1/1 192.45.121.122:8008
192.45.130.223:30758
09:28:05
conf/tran hold station
24448 cid 0x13f
09:28:05
active station
24448 cid 0x140
09:28:05
G711MU ss:off ps:20 rn:1/1 192.45.121.122:8008 20.1.1.11:2444
list trace tac 101
Page
2
LIST TRACE
time
09:28:05
09:28:06
09:28:06
09:28:06
09:28:06
09:28:06
09:28:06
09:28:06
09:28:09
09:28:09
09:28:12
09:28:12
09:28:12
09:28:12
09:28:14
JFZ; Reviewed:
PV 8/3/2006
data
xoip: fax:Relay modem:off tty:US 20.1.1.11:2444 uid:0x5
dial 24999
term announcement
24888 cid 0x140
active announcement
24888 cid 0x140
hear annc board 01A06 ext 24888 cid 0x140
transfer station
24448 cid 0x140
active announcement
24888 cid 0x140
hear annc board 01A06 ext 24888 cid 0x140
VOIP data from: 20.1.1.11:2440
Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:1 Avg:0
Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
dial 24001
ring station
24001 cid 0x140
G711MU ss:off ps:20 rn:1/1 20.1.1.102:2068 20.1.1.11:2448
xoip: fax:Relay modem:off tty:US 20.1.1.11:2448 uid:0x8ca0
active station
24001 cid 0x140
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
42 of 48
Acm-CiscoCM.doc
Step
8.
Description
Page 3 of the trace shows shuffling successful.
list trace tac 101
Page
3
LIST TRACE
time
09:28:14
09:28:14
9.
data
G711MU ss:off ps:20 rn:1/1 192.45.130.50:4000 20.1.1.102:2068
G711MU ss:off ps:20 rn:1/1 20.1.1.102:2068 192.45.130.223:32216
The above scenarios were repeated from an analog phone using the Cisco ATA 188
phone adapter. The following trace shows that IP shuffling is working correctly. Execute
the command “status station 24001”
status station 24001
Switch
Port
G.711MU
Page
AUDIO CHANNEL
Port: S00003
IP
Other-end IP Addr :Port
192. 45.130. 30
:16384
Audio:
Node Name:
Network Region:
1
Audio Connection Type: ip-direct
JFZ; Reviewed:
PV 8/3/2006
4 of
6
IP
Set-end IP Addr:Port
20. 1. 1.102:2068
1
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
43 of 48
Acm-CiscoCM.doc
Step
10.
Description
Issue the command “list trace tac 101”. This command shows the events that took place
over the trunk.
list trace tac 101
Page
1
LIST TRACE
time
09:33:37
09:33:37
09:33:37
09:33:37
09:33:37
09:33:37
09:33:37
09:33:37
09:33:37
09:33:37
09:33:38
09:33:38
09:33:45
09:33:45
09:33:45
data
Calling party trunk-group 2 member 2 cid 0x142
Calling Number & Name 80000 Red Phone
active trunk-group 2 member 2 cid 0x142
dial 24400
ring hunt-group 2
cid 0x142
G711MU ss:off ps:20 rn:1/1 192.45.121.122:8000 20.1.1.11:2456
xoip: fax:Relay modem:off tty:US 20.1.1.11:2456 uid:0x1
active station
24444 cid 0x142
G711MU ss:off ps:20 rn:1/1 192.45.130.30:16384 20.1.1.11:2452
xoip: fax:Relay modem:off tty:US 20.1.1.11:2452 uid:0x50009
G711MU ss:off ps:20 rn:1/1 192.45.130.50:4000 192.45.121.122:8000
G711MU ss:off ps:20 rn:1/1 192.45.121.122:8000 192.45.130.30:16384
conf/tran hold station
24444 cid 0x142
active station
24444 cid 0x143
G711MU ss:off ps:20 rn:1/1 192.45.121.122:8000 20.1.1.11:2468
list trace tac 101
Page
2
LIST TRACE
time
09:33:45
09:33:46
data
xoip: fax:Relay modem:off tty:US 20.1.1.11:2468 uid:0x1
dial 24999
09:33:46
09:33:46
09:33:46
09:33:46
09:33:46
09:33:46
term announcement
24888 cid 0x143
active announcement
24888 cid 0x143
hear annc board 01A06 ext 24888 cid 0x143
transfer station
24444 cid 0x143
active announcement
24888 cid 0x143
hear annc board 01A06 ext 24888 cid 0x143
VOIP data from: 20.1.1.11:2464
Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:3 Avg:0
Pkloss:0 0 0 * 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
dial 24001
ring station
24001 cid 0x143
active station
24001 cid 0x143
G711MU ss:off ps:20 rn:1/1 20.1.1.102:2068 20.1.1.11:2472
xoip: fax:Relay modem:off tty:US 20.1.1.11:2472 uid:0x8ca0
09:33:48
09:33:49
09:33:52
09:33:52
09:33:59
09:33:59
09:33:59
11.
Page 3 of the trace shows IP shuffling is successful.
list trace tac 101
Page
3
LIST TRACE
time
09:34:00
09:34:00
JFZ; Reviewed:
PV 8/3/2006
data
G711MU ss:off ps:20 rn:1/1 192.45.130.50:4000 20.1.1.102:2068
G711MU ss:off ps:20 rn:1/1 20.1.1.102:2068 192.45.130.30:16384
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
44 of 48
Acm-CiscoCM.doc
Step
12.
Description
To verify that IP calls originated from the (simulated) PSTN shuffle correctly, the
following scenario is used. A call is originated from Avaya Communication Manager
and is routed to Cisco Call Manager. The caller in this configuration would dial x50002.
AAR is configured on Avaya Communication Manager to route the call to the Avaya IR
(terminating on an H.323 endpoint). Issue the command “status station 24447” (for this
call this was the station used on Avaya IR). Verification that the call is shuffled is shown
where the IP address of the Cisco Gateway (192.45.139.129) (where the call originated)
and the Avaya IR (192.45.121.122) is shown as “ip-direct”. The caller will now be
hearing the announcement from the script on the IR.
status station 24447
Switch
Port
G.711MU
Page
AUDIO CHANNEL
Port: S00008
IP
Other-end IP Addr :Port
192. 45.139.129
:18654
Audio:
Node Name:
Network Region:
1
Audio Connection Type: ip-direct
13.
4 of
6
IP
Set-end IP Addr:Port
192. 45.121.122:8006
1
The caller enters “1” after hearing the announcement, in this case to be routed to the
“Sales Department” (per the IR script). This will then send the call to a VDN on Avaya
Communication Manager where the caller is prompted to enter an extension. The caller
enters “24001” and the call is subsequently routed to the agent at x24001. Issue the
command “status station 24001” to verify IP shuffling is successful between the Cisco
Gateway and Avaya IP phone.
status station 24001
Switch
Port
G.711MU
Page
AUDIO CHANNEL
Port: S00003
IP
Other-end IP Addr :Port
192. 45.139.129
:18654
Audio:
Node Name:
Network Region:
1
Audio Connection Type: ip-direct
JFZ; Reviewed:
PV 8/3/2006
4 of
6
IP
Set-end IP Addr:Port
20. 1. 1.102:2068
1
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
45 of 48
Acm-CiscoCM.doc
Step
14.
Description
The trace from the call shows the following:
list trace tac 101
Page
1
LIST TRACE
time
data
09:36:25
Calling party trunk-group 2 member 1 cid 0x145
09:36:25
Calling Number & Name 24111 Digital Line
09:36:25
active trunk-group 2 member 1 cid 0x145
09:36:25
dial 24400
09:36:25
ring hunt-group 2
cid 0x145
09:36:25
G711MU ss:off ps:20 rn:1/1 192.45.121.122:8002 20.1.1.11:2480
09:36:25
xoip: fax:Relay modem:off tty:US 20.1.1.11:2480 uid:0x2
09:36:26
active station
24445 cid 0x145
09:36:26
G711MU ss:off ps:20 rn:1/1 192.45.139.129:18886 20.1.1.11:2476
09:36:26
xoip: fax:Relay modem:off tty:US 20.1.1.11:2476 uid:0x50008
09:36:26
G711MU ss:off ps:20 rn:1/1 192.45.139.129:18886
192.45.121.122:8002
09:36:26
G711MU ss:off ps:20 rn:1/1 192.45.121.122:8002
192.45.139.129:18886
09:36:33
conf/tran hold station
24445 cid 0x145
09:36:33
active station
24445 cid 0x146
09:36:33
G711MU ss:off ps:20 rn:1/1 192.45.121.122:8002 20.1.1.11:2492
list trace tac 101
Page
2
LIST TRACE
time
09:36:33
09:36:35
09:36:35
09:36:35
09:36:35
09:36:35
09:36:35
09:36:35
09:36:36
09:36:36
09:36:41
09:36:41
09:36:41
09:36:41
09:36:48
data
xoip: fax:Relay modem:off tty:US 20.1.1.11:2492 uid:0x2
dial 24999
term announcement
24888 cid 0x146
active announcement
24888 cid 0x146
hear annc board 01A06 ext 24888 cid 0x146
transfer station
24445 cid 0x146
active announcement
24888 cid 0x146
hear annc board 01A06 ext 24888 cid 0x146
VOIP data from: 20.1.1.11:2488
Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:1 Avg:0
Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
dial 24001
ring station
24001 cid 0x146
G711MU ss:off ps:20 rn:1/1 20.1.1.102:2068 20.1.1.11:2496
xoip: fax:Relay modem:off tty:US 20.1.1.11:2496 uid:0x8ca0
active station
24001 cid 0x146
Page 3 shows that shuffling is successful.
list trace tac 101
Page
3
LIST TRACE
time
09:36:48
09:36:48
JFZ; Reviewed:
PV 8/3/2006
data
G711MU ss:off ps:20 rn:1/1 192.45.139.129:18886 20.1.1.102:2068
G711MU ss:off ps:20 rn:1/1 20.1.1.102:2068 192.45.139.129:18886
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
46 of 48
Acm-CiscoCM.doc
7. Conclusion
As illustrated in these Application Notes, Avaya Communication Manager 3.1.1 can interoperate
and shuffle calls with Cisco Call Manager 4.1 using H.323 IP Trunks. The media paths for all
calls placed were verified to be “ip-direct” between Cisco IP endpoints, Avaya IR 2.0 and Avaya
IP telephones.
8. Additional References
The following Avaya product documentation can be found at http://support.avaya.com.
[1] Installing and Configuring the Avaya S8700-Series Media Server, Release 3.1, Issue 5,
February 2006, Document ID: 03-300145.
[2] Installing the Avaya G650 Media Gateway, Release 3.1, Issue 1, February 2006, Document
ID: 03-300685.
[3] Configuring H.323 Signaling and IP Trunks between Avaya Communication Manager and
Cisco CallManager 4.0 – Issue 1.0.
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
47 of 48
Acm-CiscoCM.doc
© 2006 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 and filename, located in the lower right corner, directly to the Avaya Solution &
Interoperability Test Lab at [email protected]
JFZ; Reviewed:
PV 8/3/2006
Solution & Interoperability Test Lab Application Notes
© 2006 Avaya Inc. All Rights Reserved.
48 of 48
Acm-CiscoCM.doc