AudioCodes MEDIAPACK VERSION 6.2 - Manual (Page 59)

Version 6.2 59 December 2010
SIP Release Notes 1. What's New in Release 6.2
Parameter Value
SIP Header Present in Received SIP Message
Diversion History-Info
Diversion and
History-Info
HistoryInfoMode =
Remove
DiversionMode = Add
Not present.
History-Info
converted to
Diversion.
History-Info
removed.
History-Info added
to Diversion.
History-Info
removed.
HistoryInfoMode =
Disable
DiversionMode = Add Diversion
converted to
History-Info.
Not present.
Diversion added to
History-Info.
HistoryInfoMode =
Disable
DiversionMode = Add
Not present.
History-Info
converted to
Diversion.
History-Info added
to Diversion.
HistoryInfoMode = Add
DiversionMode = Add
Diversion
converted to
History-Info. History-Info
converted to
Diversion.
Headers are
synced and sent.
HistoryInfoMode =
Remove
DiversionMode =
Remove
Diversion
removed. History-Info
removed.
Both removed.
12. GRUU Support According to RFC 5627:
Product
Mediant 800 MSBG Mediant 1000 MSBG
Mediant 3000/TP-6310 Mediant 3000 HA/TP-6310
Mediant 3000/TP-8410 Mediant 3000 HA/TP-8410
Management Protocol
Web INI SNMP EMS CLI
This feature provides support for Globally Routable User Agent (UA) URI (GRUU),
according to RFC 5627. This is used for obtaining a GRUU from a registrar and for
communicating a GRUU to a peer within a dialog. This support is provided by the
existing parameter, EnableGRUU. In addition, this feature allows the device to act as a
GRUU server for its SIP UA clients, providing them with public GRUU’s, according to
RFC 5627. The public GRUU provided to the client is depicted in the SIP Contact
header parameters, "pub-gruu". Public GRUU remains the same over registration
expirations. On the other SBC leg communicating with the Proxy/Registrar, the device
acts as a GRUU client. The GRUU server feature is enabled by the new parameter,
SBCGruuMode.
The device creates a GRUU value for each of its registered clients, which is mapped to
the GRUU value received from the Proxy server. In other words, the created GRUU
value is only used between the device and its clients (endpoints).
Public-GRUU: sip:[email protected];gr=unique-id
• Obtaining a GRUU: The mechanism for obtaining a GRUU is through
registrations. A UA can obtain a GRUU by generating a REGISTER request
containing a Supported header field with the value “gruu”. The UA includes a
“+sip.instance” Contact header parameter of each contact for which the GRUU is
desired. This Contact parameter contains a globally unique ID that identifies the
UA instance. The global unique ID is created from one of the following: