User`s manual

SIP User's Manual 230 Document #: LTRT-83303
Mediant 1000 & Mediant 600
Mode Description
 To enable Trunk Group registrations, configure the global parameter
IsRegisterNeeded to 1. This is unnecessary for 'Per Account' registration
mode.
 If no mode is selected, the registration is performed according to the global
registration parameter ChannelSelectMode (refer to ''Proxy & Registration
Parameters'' on page 146).
 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.
Serving IP Group ID The Serving IP Group ID to where INVITE messages initiated by the Trunk
Group endpoints are sent. The actual destination to where these INVITE
messages are sent is to the Proxy Set ID (refer to ''Proxy Sets Table'' on page
153) 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 for the field 'SIP Group Name' defined in the 'IP
Group' table (refer to ''Configuring the IP Groups'' on page 231).
If no ServingIPGroupID is selected, the INVITE messages are sent to the
default Proxy or according to the 'Tel to IP Routing Table' (refer to ''Tel to IP
Routing Table'' on page 200).
Note: If the parameter PreferRouteTable is set to 1 (refer to ''Proxy &
Registration Parameters'' on page 146), the routing rules in the 'Tel to IP
Routing Table' prevails over the selected ServingIPGroupID.
Gateway Name The host name used in the 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.
Contact User This is used as the user part in the 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.
An example is shown below of a REGISTER message for registering endpoint "101" using registration
Per Endpoint mode. The "SipGroupName" in the request URI is taken from the IP Group table.
REGISTER sip:SipGroupName SIP/2.0
Via: SIP/2.0/UDP 10.33.37.78;branch=z9hG4bKac862428454
From: <sip:101@GatewayName>;tag=1c862422082
To: <sip:101@GatewayName>
Call-ID: 9907977062512000232825@10.33.37.78
CSeq: 3 REGISTER
Contact: <sip:101@10.33.37.78>;expires=3600
Expires: 3600
User-Agent: Audiocodes-Sip-Gateway/v.5.40A.008.002
Content-Length: 0