AudioCodes Mediant 3000 User Manual page 173

Hide thumbs Also See for Mediant 3000:
Table of Contents

Advertisement

SIP User's Manual
Parameter
Serving IP Group ID
[TrunkGroupSettings_ServingIPGr
oup]
Gateway Name
[TrunkGroupSettings_GatewayNa
me]
Contact User
[TrunkGroupSettings_ContactUser
]
Version 5.8
Registration Parameters'' on page 114).
If the device is configured globally (ChannelSelectMode)
to register Per Endpoint, and a Trunk Group comprising
four channels is configured to register Per Gateway, the
device registers all channels except the first four
channels. The Trunk Group of these four channels sends
a single registration request.
The Serving IP Group ID to where INVITE messages
initiated by this Trunk Group's endpoints are sent. The actual
destination to where these INVITE messages are sent is
according to the Proxy Set ID (refer to ''Configuring the
Proxy Sets Table'' on page 116) associated with this Serving
IP Group. The Request URI hostname in the INVITE and
REGISTER messages (except for 'Per Account' registration
modes) is set to the value of the field 'SIP Group Name'
defined in the 'IP Group' table (refer to ''Configuring the IP
Groups'' on page 120).
If no Serving IP Group ID is selected, the INVITE messages
are sent to the default Proxy or according to the 'Tel to IP
Routing Table' (refer to ''Configuring the Tel to IP Routing
Table'' on page 151) or 'Outbound IP Routing Table' if the
IP2IP application is enabled (refer to "Configuring the
Outbound IP Routing Table" on page 156).
Note: If the parameter PreferRouteTable is set to 1 (refer to
''Configuring Proxy and Registration Parameters'' on page
114), the routing rules in the 'Tel to IP Routing Table' (or
'Outbound IP Routing Table') prevail over the selected
Serving IP Group ID.
The host name used in the SIP From header in INVITE
messages, and as a host name in From/To headers in
REGISTER requests. If not configured, the global parameter
SIPGatewayName is used instead.
The user part in the SIP Contact URI in INVITE messages,
and as a user part in From, To, and Contact headers in
REGISTER requests. This is applicable only if the field
'Registration Mode' is set to 'Per Account', and the
Registration through the Account table is successful.
Notes:
If registration fails, then the userpart in the INVITE
Contact header contains the source party number.
The 'ContactUser' parameter in the 'Account Table' page
overrides this parameter.
173
3. Web-Based Management
Description
September 2009

Advertisement

Table of Contents
loading

Table of Contents