Inbound signaling, Unspecified signaling group – Avaya IP600 User Manual
Page 6

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