AudioCodes Mediant 2000, User Manual

Page: 206 / 418

SIP User's Manual 206 Document #: LTRT-68808
Mediant 2000
Parameter Description
ƒ
The parameter 'Register' in this table is set to 1.
In addition, for a SIP call that is identified by both the Served Trunk Group/
Served IP Group and Serving IP Group, the username and password for digest
authentication defined in this table is used.
For Tel-to-IP calls, the Serving IP Group is the destination IP Group defined in
the 'Trunk Group Settings' table or 'Tel to IP Routing' table (refer to ''Tel to IP
Routing Table'' on page
175 ). For IP-to-Tel calls, the Serving IP Group is the
'Source IP Group ID' defined in the 'IP to Trunk Group Routing' table (refer to
''IP to Trunk Group Routing'' on page
181 ).
Note:
If no match is found in this table for incoming or outgoing calls, the
username and passwordthe global parameters (UserName and Password)
defined on the 'Proxy & Registration' page (refer to ''Proxy & Registration
Parameters'' on page
132 ) are used.
Username Digest MD5 Authentication user name (up to 50 characters).
Password Digest MD5 Authentication password (up to 50 characters).
HostName Defines the Address of Record (AOR) host name. It appears in REGISTER
From/To headers as ContactUser@HostName. For successful registrations,
this HostName is also included in the INVITE request's From header URI. If not
configured or if registration fails, the 'SIP Group Name' parameter from the ‘IP
Group’ table is used instead.
This parameter can be up to 49 characters.
Register Enables registration.
ƒ
No = Don't register
ƒ
Yes = Register
When enabled, the device sends REGISTER requests to the Serving IP Group.
In addition, to activate registration, you also need to set the parameter
'Registration Mode' to 'Per Account' in the 'Trunk Group Settings' table (refer to
''Configuring the Trunk Group Settings'' on page
197 ) for the specific Trunk
Group. The Host Name (i.e., host name in SIP From/To headers) and Contact
User (user in From/To and Contact headers) are taken from this table upon a
successful registration. See the example below:
REGISTER sip:audiocodes SIP/2.0
Via: SIP/2.0/UDP 10.33.37.78;branch=z9hG4bKac1397582418
From: <sip:ContactUser@HostName>;tag=1c1397576231
To: <sip: ContactUser@HostName >
Call-ID: 1397568957261200022256@10.33.37.78
CSeq: 1 REGISTER
Contact: <sip:ContactUser@10.33.37.78>;expires=3600
Expires: 3600
User-Agent: Audiocodes-Sip-Gateway/v.5.40A.008.002
Content-Length: 0
Notes:
ƒ
The Trunk Group account registration is not effected by the parameter
IsRegisterNeeded.
ƒ
You can configure this table so that a specific IP Group can register to
multiple ITSP’s.This is performed by defining several rows in this table
containing the same Served IP Group, but with different Serving IP Groups,
user/password, Host Name and Contact User parameters.
ƒ
If registration to an IP Group(s) fails for
all
the accounts defined in this table
for a specific Trunk Group, and if this Trunk Group includes all the channels
in the Trunk (refer to “Configuring the Trunk Group Table” on page
195 ), the