Version 5.8 325 October 2009
SIP User's Manual 6. Configuration Parameters Reference
Parameter Description
Web: Use Tgrp Information
EMS: Use SIP Tgrp
[UseSIPTgrp]
Determines whether the SIP 'tgrp' parameter is used, which
specifies the Hunt Group to which the call belongs,
according to RFC 4904.
For example:
INVITE sip::+16305550100;tgrp=1;trunk-
context=example.com@10.1.0.3;user=phone SIP/2.0
[0] Disable = The 'tgrp' parameter isn't used (default).
[1] Send Only = The Hunt Group number is added to the
'tgrp' parameter value in the Contact header of outgoing
SIP messages. If a Hunt 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 INVITEs, if the
Request-URI includes a 'tgrp' parameter, the device
routes the call according to that value (if possible). The
Contact header in the outgoing SIP INVITE (Tel-to-IP
call) contains “tgrp=<source trunk group ID>;trunk-
context=<gateway IP address>”. The <source trunk group
ID> is the Hunt Group ID where incoming calls from Tel is
received. For IP-Tel calls, the SIP 200 OK device's
response contains “tgrp=<destination trunk group
ID>;trunk-context=<gateway IP address>”. The
<destination trunk group ID> is the Hunt Group ID used
for outgoing Tel calls. The <gateway IP address> in
“trunk-context” can be configured using the parameter
SIPGatewayName.
Web/EMS: Enable GRUU
[EnableGRUU]
Determines whether the Globally Routable User Agent URIs
(GRUU) mechanism is used.
[0] Disable = Disable (default)
[1] Enable = Enable
The device obtains a GRUU by generating a normal
REGISTER request. This request contains a Supported
header with the value 'gruu'. The device includes a
'+sip.instance' Contact header parameter for each contact
for which the GRUU is desired. This Contact parameter
contains a globally unique ID that identifies the device
instance.
The global unique ID is as follows:
If registration is per endpoint (AuthenticationMode=0), it
is the MAC address of the device concatenated with the
phone number of the endpoint.
If the registration is per device (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
To Next Page
Loading...
Need help?
General
