3Com VCX v7111 User Manual page 71

Parameter
Enable GRUU
[EnableGRUU]
Use Tgrp Information
[UseSIPTgrp]
®
3Com VCX V7111 VoIP Gateway User Guide
Description
Determines whether or not the GRUU mechanism is used.
Valid options include:
Disable [0 ] (default)
Enable [1]
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.
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:alice@example.com
GRUU: sip:alice@example.com;opaque="kjh29x97us97d"
Disable [0] = Tgrp parameter is not used (default).
Send Only [1] = The hunt group number is added as the tgrp
parameter to the Contact header of outgoing SIP messages. If a hunt
group number is not associated with the call, the tgrp parameter is
not included. If a tgrp value is specified in incoming messages, it is
ignored.
Send and Receive [2] = 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.
71