The The The following features are not supported by the SBC when Dialog Transparency is enabled:dialogTransparency
flag under the Zone object passes dialogs transparently for SIP messages processed in that specified zone. If dialog transparency is disabled, the SBC translates the dialog identifiers in the Target-Dialog header received in INVITE and REFER messages and sends the Target-Dialog header with translated dialog identifiers on the other leg. If dialog transparency is enabled, Target-Dialog header translation is not performed. However, the header is transparently passed if configured in transparency profile.dialogTransparency
flag must be enabled on both ingress and egress zones because if the flag is only enabled on one zone, all calls and messages are rejected. In this situation, the sonusSbxDialogTransparencyMisConfiguredNotification alarm is raised on the zone in which the flag is disabled.
For feature functionality, please see Dialog Transparency.
Ribbon recommends using the Transparency Profile to configure transparency on the SBC Core for new deployments, as well as applying additional transparency configurations to existing deployments. Do not use IP Signaling Profile flags in these scenarios because the flags will be retired in upcoming releases.
Refer to the SBC SIP Transparency Implementation Guide for additional information.
Command Syntax
% set addressContext <addressContext Name> zone <zone Name> dialogTransparency <disabled | enabled>
Command Parameters
Parameter | Length/Range | Description |
---|---|---|
| 1-23 characters | The name of the zone. You can configure signaling, media, and control for a zone in the address context. |
| N/A | Enable flag SBC to send "Call-ID", "From" tag, and "To" tag transparently in the outgoing SIP message.
|