AudioCodes Mediant 500 E-SBC, Руководство пользователя

Страница: 892 / 920

User's Manual 892 Document #: LTRT-10437
Mediant 500 E-SBC
Parameter Description
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
[SBCEnableByeAuthentication]
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.
Web: SBC Enable Subscribe
Trying
CLI: configure voip > sbc general-
setting > set sbc-subs-try
[SBCSendTryingToSubscribe]
Enables the device to send SIP 100 Trying responses upon
receipt of SUBSCRIBE or NOTIFY messages.

[0] Disable (Default)

[1] Enable
[SBCExtensionsProvisioningMo
de] 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
464 .
Web: SBC Direct Media
CLI: sbc-direct-media
[SBCDirectMedia]
Enables the No Media Anchoring feature (i.e., direct media) for
all SBC calls, whereby SIP signaling is handled by the device
without handling the RTP/SRTP (media) flow between the 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 calls traverse the device (i.e., no
direct media). If No Media Anchoring is enabled for an SRD
(in the SRD table), then calls between endpoints belonging
to that SRD use No Media Anchoring.

[1] Enable = All SBC calls use the No Media Anchoring
feature (i.e., direct media).
Note: For more information on No Media Anchoring, see ''No
Media Anchoring (Anti Tromboning)'' on page 451 .