User`s manual

SIP User's Manual 6. Gateway's ini File Configuration
Version 5.0 153 October 2006
Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169)
ini File Field Name
Web Parameter Name
Valid Range and Description
UseSIPTgrp
[Use Tgrp Information]
0 = Tgrp parameter isn’t used (default).
1 = (send only) The trunk group number is added as the ‘tgrp’ parameter to the
Contact header of outgoing SIP messages. If a trunk group number is not
associated with the call, the ‘tgrp’ parameter isn’t included. If a ‘tgrp’ value is
specified in incoming messages, it is ignored.
2 = (send and receive) The functionality of outgoing SIP messages is identical
to the functionality described in option (1). In addition, for incoming SIP
messages, if the Request-URI includes a ‘tgrp’ parameter, the gateway routes
the call according to that value (if possible). If the Contact header includes a
‘tgrp’ parameter, it is copied to the corresponding outgoing messages in that
dialog.
EnableGRUU
[Enable GRUU]
Determines whether or not the GRUU mechanism is used.
Valid options include:
0 = Disable (default)
1 = Enable
The gateway obtains a GRUU by generating a normal REGISTER request.
This request contains a Supported header field with the value “gruu”. The
gateway includes a “+sip.instance” Contact header field parameter for each
contact for which the GRUU is desired. This Contact parameter contains a
globally unique ID that identifies the gateway instance.
The global unique id is as follows:
 If registration is per endpoint (AuthenticationMode=0), it is the MAC
address of the gateway concatenated with the phone number of the
endpoint.
 If the registration is per gateway (AuthenticationMode=1) it is only the
MAC address.
 When the “User Information” mechanism is used, the globally unique ID is
the MAC address concatenated with the phone number of the endpoint
(defined in the User-Info file).
If the Registrar/Proxy supports GRUU, the REGISTER responses contain the
“gruu” parameter in each Contact header field. The Registrar/Proxy provides
the same GRUU for the same AOR and instance-id in case of sending
REGISTER again after expiration of the registration.
The gateway places the GRUU in any header field which contains a URI. It
uses the GRUU in the following messages: INVITE requests, 2xx responses to
INVITE, SUBSCRIBE requests, 2xx responses to SUBSCRIBE, NOTIFY
requests, REFER requests, and 2xx responses to REFER.
Note: If the GRUU contains the "opaque" URI parameter, the gateway obtains
the AOR for the user by stripping the parameter. The resulting URI is the AOR.
For example:
AOR: sip:[e-mail]
GRUU: sip:[e-mail];opaque="kjh29x97us97d"
UserAgentDisplayInfo
[User-Agent Information]
Defines the string that is used in the SIP request header ‘User-Agent’ and SIP
response header ‘Server’. If not configured, the default string ‘AudioCodes
product-name s/w-version’ is used (e.g., User-Agent: Audiocodes-Sip-
Gateway-Mediant 2000/v.4.80.004.008). When configured, the string
‘UserAgentDisplayInfo s/w-version’ is used (e.g., User-Agent:
MyNewOEM/v.4.80.004.008). Note that the version number can't be modified.
The maximum string length is 50 characters.
SessionExpiresMethod
[Session Expires Method]
Defines the SIP method used for session-timer updates.
0 = Use Re-INVITE messages for session-timer updates (default).
1 = Use UPDATE messages.
Note 1: The gateway can receive session-timer refreshes using both methods.
Note 2: The UPDATE message used for session-timer purposes is not
included in the SDP body.