AudioCodes MediaPack MP-124 User Manual page 183

SIP User's Manual
Mode
Gateway Name
Contact User
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-MP-118 FXS_FXO/v.5.40A.008.002
Content-Length: 0
3.4.4.8.2 Configuring the IP Groups
The 'IP Group Table' page allows you to create logical IP entities (IP Groups) that are later
used in the call routing tables.
The IP Groups are typically implemented in Tel-to-IP call routing. The IP Group can be
used as a destination entity (DestIPGroupID) in the 'Tel to IP Routing' table, and
ServingIPGroupID in the 'Hunt Group Settings' (refer to ''Configuring the Hunt Group
Settings'' on page 180) and 'Account' (refer to ''Configuring the Account Table'' on page
185) tables. These call routing tables are used for identifying the IP Group from where the
INVITE is sent for obtaining a digest user/password from the 'Account' table if there is a
need to authenticate subsequent SIP requests in the call. The IP Group can also be
implemented in IP-to-Tel call routing as a source IP Group (SourceIPGroupID).
The IP Groups are assigned various entities such as a Proxy Set ID, which represents an
IP address (created in ''Proxy Sets Table'' on page 117). You can also assign the IP Group
with a host name and other parameters that reflect parameters sent in SIP Request
From\To.
Version 5.4
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.
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.
Description
183
3. Web-Based Management
May 2008