SIP User's Manual 258 Document #: LTRT-65412
MP-11x & MP-124
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 messages, if
the Request-URI includes a 'tgrp' parameter, the device
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.
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
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 device 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.
To Next Page
Loading...
