Avaya IP600 User Manual

How to configure an AvayaTM IP600 Server with Cisco
Gatekeeper - Issue 1.0

Abstract

These Application Notes describe the configurations that enable the Avaya IP600 Server to
successfully interoperate with Cisco’s Gatekeeper. These notes describe both an Avaya
Gatekeeper to Cisco Gatekeeper peer configuration, as well as a Multiple Gatekeeper
Configuration between an Avaya Gatekeeper and multiple Cisco Gatekeepers.

SVS; Reviewed:
WCH/MI 6/20/02

Solution & Interoperability Test Lab Application Notes

© 2002 Avaya Inc. All Rights Reserved.

1 of 20

Gatekeeper-ext.doc

1. Introduction

One of the functions of a Gatekeeper is to perform E.164 to IP address resolution based on a dial
plan. All remote calls within a Zone are sent to its Gatekeeper, where it is sent either to a
gateway or to another remote gatekeeper zone. These Application Notes describe how to
configure an Avaya™ IP600 Server to interoperate with Cisco’s Gatekeepers and Gateways.

2. Background

In the block diagram (Figure 1) below, the Avaya™ IP600 Server is represented as a Gatekeeper
and Gateway within one box. This is because in H.323 terms, the Avaya IP600 Server is a
Gatekeeper with an embedded or fixed Gateway. Avaya’s IP600 Gatekeeper provides address
translation and control access. Avaya’s embedded Gateway performs the media conversions.

Once an endpoint registers with the Gatekeepers (via RAS), call signaling messages between the
endpoint are routed through Avaya’s Gatekeeper. This method of call signaling is called
Gatekeeper Routed Call Signaling and is the method used by Avaya.

Cisco4604

Gateway A

Avaya IP600

Gatekeeper

Gateway

Zone 1

Cisco 3660

Gatekeeper

Cisco 1751
Gateway B

Zone 2

Figure 1: Block Diagram of IP600 Server and Cisco Gatekeeper

The configuration in Figure 2 is based on the block diagram depicted in Figure 1. In this
configuration, Avaya and Cisco are considered to be in peer gatekeeper zones; that is, the Avaya
Gatekeeper zone manages extensions 77XX, while Cisco Gatekeeper zone manages extensions
62XX and 66XX. When an extension in Zone 1 calls an endpoint in Zone 2, Zone 2 is
considered a remote zone to Zone 1. Likewise in the other direction, when an endpoint in Zone 2
calls an extension in Zone 1, Zone 1 is considered to be a remote zone to Zone 2.

SVS; Reviewed:
WCH/MI 6/20/02

Solution & Interoperability Test Lab Application Notes

© 2002 Avaya Inc. All Rights Reserved.

2 of 20

Gatekeeper-ext.doc

All communications of E.164 traffic must first deal with the Gatekeeper because it is configured
to send or direct E.164 numbers to an appropriate IP endpoint. In Figure 2 for example, when a
phone on Gateway A (Catalyst 4000 Gateway) calls a phone on Gateway B (Cisco 1751), the
E.164 number being called from A is presented to the Cisco’s Gatekeeper. The Gatekeeper finds
the called number and its associated end-point IP address within its configuration. A direct
channel is set up between gateway A and gateway B, where the called number is directed.
Gateway B’s dial-peers steers the call to the port where the actual phone is located.

Cisco 3660

Catalyst 4000 - 4604-GWY

Gatekeeper

Zone 2

Cajun P333T

Avaya IP Phone

X 7702

Avaya IP Phone

X 7712

. 2

10.30.1.0

HS1HS2 OK1OK2 PS

To

DHCP Server

TFTP Server

.1

Cisco 4224

10.9.1.5

123456789101112
COL­ACT­STA-

. 2

Gateway A

10.50.1.0

.1

10.20.1.0

.1

CONSOLE

CLAN

10.9.1.4

10.9.1.3
Prowler

Avaya IP SoftPhone

X 7716

Avaya
IP 600

Zone 1

. 2

FXS

X 6200

Gateway B

Cisco 1751

DCP

X 7704

DCP

X 7705

FXS

X 6600

Figure 2: IP600 Server and Cisco Gatekeeper

3. Equipment and Software Validated

1. Avaya

Avaya Equipment Version

Avaya™ IP600 Server Version R010c.01.0.032.3
Avaya™ IP Telephone Version 1.51

2. Cisco (IOS)

Cisco Router Version of IOS

Cisco 3660 IOS 12.1.5T10

SVS; Reviewed:
WCH/MI 6/20/02

Solution & Interoperability Test Lab Application Notes

© 2002 Avaya Inc. All Rights Reserved.

3 of 20

Gatekeeper-ext.doc

Cisco 1750 IOS 12.2.4T1
Cisco 4224 IOS 12.1.5-YE4
Catalyst 4000 with WS-X4604-GWY IOS 12.2.6a

4. Avaya™ IP600 Configuration

The following screen shots show the pertinent aspects of the Avaya IP600 Server configuration.
The more important aspects are highlighted.

4.1. Outbound Signaling

The administration of the Cisco Gatekeeper as a remote peer requires the addition of a Signaling
/ Trunk Group that points at the Cisco Gatekeeper IP Address as the Far-End (10.30.1.2). In
addition, the appropriate routing (UDP, AAR/ARS, Routing Pattern, etc.) procedures to access
this Signaling / Trunk Group combination are required.

4.1.1. Signaling Group

Permitting the Avaya IP600 server to be administered as a Gatekeeper requires an IP Trunk, and
an H.323 Signaling Group set up as follows. The Signaling Group’s “LRQ Required” is set to
“y”, the Near-End IP address is set to the IP node name of the CLAN (see Node Names-IP) at
port 1719, and the Far-End node name is set to the IP node name of the Cisco Gatekeeper at port

1719. This Signaling Group along with its Trunk Group handles all outbound traffic from Zone
1 to Zone 2.

This Signaling and Trunk Group handle all outbound traffic from Zone 1 to Zone 2. In
addition, the Signaling group points at the Cisco Gatekeeper utilizing port 1719 and “LRQ
Required” must be set to “y”. Note: Cisco uses Port 1719 by default. Also, note that Direct IP­IP Audio Connections and IP Audio Hairpinning are set to “n”.

SIGNALING GROUP

Group Number: 6 Group Type: h.323
Remote Office? n Max number of NCA TSC: 0

Max number of CA TSC: 0

Trunk Group for NCA TSC:
Trunk Group for Channel Selection: 6
Supplementary Service Protocol: a Network Call Transfer? n

Near-end Node Name: clan-IP600-gk Far-end Node Name: Gatekeeper
Near-end Listen Port: 1719 Far-end Listen Port: 1719

Far-end Network Region:

LRQ Required? y Calls Share IP Signaling Connection? n
RRQ Required? n

Bypass If IP Threshold Exceeded? n

Direct IP-IP Audio Connections? n

IP Audio Hairpinning? n

Interworking Message: PROGress

SVS; Reviewed:
WCH/MI 6/20/02

Solution & Interoperability Test Lab Application Notes

© 2002 Avaya Inc. All Rights Reserved.

4 of 20

Gatekeeper-ext.doc

4.1.2. Trunk Group

In this example, Trunk Group 6 is associated with Signaling Group 6, and includes trunk
member assignment.

TRUNK GROUP

Group Number: 6 Group Type: isdn CDR Reports: y

Group Name: Alternate IP600 Test Networ COR: 1 TN: 1 TAC: 106
Direction: two-way Outgoing Display? y Carrier Medium: IP
Dial Access? n Busy Threshold: 99 Night Service:
Queue Length: 0
Service Type: tie Auth Code? n TestCall ITC: rest

Far End Test Line No:
TestCall BCC: 4
TRUNK PARAMETERS

Codeset to Send Display: 6 Codeset to Send National IEs: 6

Max Message Size to Send: 260 Charge Advice: none

Supplementary Service Protocol: a Digit Handling (in/out):enbloc/enbloc

Trunk Hunt: cyclical QSIG Value-Added? n

Digital Loss Group: 13

Calling Number - Delete: Insert: Numbering Format:

Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? n
Answer Supervision Timeout: 0

Trunk Members

Trunk member port values are initially created by assigning the term “ip” in the Port column.
The system will then assign the T000xx value to the port as shown below.

TRUNK GROUP

Administered Members (min/max): 1/7

GROUP MEMBER ASSIGNMENTS Total Administered Members: 7

Port Code Sfx Name Night Sig Grp
1: T00049 6
2: T00050 6
3: T00051 6
4: T00052 6
5: T00053 6
6: T00054 6
7: T00055 6

SVS; Reviewed:
WCH/MI 6/20/02

Solution & Interoperability Test Lab Application Notes

© 2002 Avaya Inc. All Rights Reserved.

5 of 20

Gatekeeper-ext.doc

4.2. Inbound Signaling

All inbound traffic from Zone 2 to Zone 1 requires an additional Trunk and Signaling Group.
In this case, the Signaling Group’s Near-End IP address is set to the IP address of the CLAN at
port 1720, and the Far-End is unspecified.

The unspecified far-end signaling group is used for all incoming calls from Zone 2 to Zone 1.
The Avaya IP600 Server listens on Port 1720 to handle H.225 /Q.931 traffic.

4.2.1. Unspecified Signaling Group

The “Far-end Node Name” field is left blank, and it is necessary that “Direct IP-IP Audio
Connections” and “IP Audio Hairpinning” be set to “n” on this screen.

SIGNALING GROUP

Group Number: 10 Group Type: h.323
Remote Office? n Max number of NCA TSC: 0

Max number of CA TSC: 0

Trunk Group for NCA TSC:
Trunk Group for Channel Selection: 10
Supplementary Service Protocol: a Network Call Transfer? n

Near-end Node Name: clan-IP600-gk Far-end Node Name:
Near-end Listen Port: 1720 Far-end Listen Port:

Far-end Network Region:

LRQ Required? n Calls Share IP Signaling Connection? n
RRQ Required? n

Bypass If IP Threshold Exceeded? n

Direct IP-IP Audio Connections? n

IP Audio Hairpinning? n

Interworking Message: PROGress

SVS; Reviewed:
WCH/MI 6/20/02

Solution & Interoperability Test Lab Application Notes

© 2002 Avaya Inc. All Rights Reserved.

6 of 20

Gatekeeper-ext.doc