AudioCodes Media 800 MSBR - Page 974

User's Manual 974 Document #: LTRT-12809
Mediant 800 MSBR
Parameter Description

[4] Both = The device provides temporary and public GRUU to
users. (Currently not supported.)
This parameter 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 denoted 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 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:userA@domain.com;gr=unique-id
Web: Bye Authentication
CLI: sbc-bye-auth
[SBCEnableByeAuthentica
tion]
Enables authenticating a SIP BYE request before disconnecting the
call. This feature prevents, for example, a scenario in which the SBC
SIP client receives a BYE request from a third-party imposer
assuming the identity of a participant in the call and as a
consequence, the call between the first and second parties is
inappropriately disconnected.
 [0] Disable (default)
 [1] Enable = The device forwards the SIP authentication
response (for the BYE request) to the request sender and waits
for the user to authenticate it. The call is disconnected only if the
authenticating server responds with a 200 OK.
[SBCExtensionsProvisioni
ngMode]
Enables SBC user registration for interoperability with BroadSoft's
BroadWorks server, to provide call survivability in case of
connectivity failure with the BroadWorks server.
 [0] = (Default) Normal processing of REGISTER messages.
 [1] = Registration method for BroadWorks server. In a failure
scenario with BroadWorks, the device acts as a backup SIP proxy
server, maintaining call continuity between the enterprise LAN
users (subscribers) and between the subscribers and the PSTN
(if provided).
Note: For a detailed description of this feature, see 'Auto-
Provisioning of Subscriber-Specific Information for BroadWorks
Server' on page 449.
Web: SBC Direct Media
CLI: sbc-direct-media
[SBCDirectMedia]
Enables the No Media Anchoring feature (i.e., direct media) for all
SBC calls. No Media Anchoring uses SIP signaling capabilities
without handling the RTP/SRTP (media) flow between remote SIP
user agents (UA). The RTP packets do not traverse the device,
instead, the two SIP UAs establish a direct RTP/SRTP flow between
one another. Signaling continues to traverse the device with minimal
intermediation and involvement to enable certain SBC abilities such
as routing
 [0] Disable = (Default) All SRD calls via SBC are not direct media
- internal SRD calls are according to SRD configuration.
 [1] Enable = All SBC calls use the No Media Anchoring feature
(i.e., direct media).
Notes:
 For more information on No Media Anchoring, see 'No Media
Anchoring (Anti Tromboning)' on page 435.