AudioCodes Mediant 4000 SBC, User Manual

Page: 471 / 1037

CHAPTER 20 SIP Definitions
Mediant 4000 SBC | User's Manual
Parameter Description
Note:
■ If the parameter is not configured, the 'Contact User'
parameter in the IP Groups table is used instead.
■ If registration fails, the user part in the INVITE Contact
header contains the source party number.
'Register'
register
[Account_Register]
Enables registration.
■ [0] No = (Default) The device only performs
authentication (not registration). Authentication is
typically done for INVITE messages sent to the
"serving" IP Group. If the device receives a SIP 401
(Unauthorized) in response to a sent INVITE, the
device checks for a matching "serving" and "served"
entry in the table. If a matching row exists, the device
authenticates the INVITE by providing the
corresponding MD5 authentication username and
password to the "serving" IP Group.
■ [1] Regular = The device performs regular registration.
For more information, see Regular Registration Mode .
■ [2] GIN = The device performs registration for legacy
PBXs, using Global Identification Number (GIN). For
more information, see
Single Registration for Multiple
Phone Numbers using GIN .
Note:
■ Account registration is not affected by the
IsRegisterNeeded parameter.
'Registrar Stickiness'
registrar-stickiness
[Account_RegistrarStickiness]
Enables the Registrar Stickiness feature.
■ [0] Disable = (Default) Disables the Registrar
Stickiness feature. After a successful initial registration
of the Account with a registrar (IP address), whenever
the device receives a SIP request or registration
refresh, the device sends the request to whichever IP
address is the currently working registrar. In other
words, there is no binding to a specific IP address in the
Proxy Set and at any given time, requests may be sent
to a different IP address, whichever is the working one.
In the case of proxy load-balancing, there is no certainty
as to which IP address in the Proxy Set the request is
routed.
- 438 -