In this section:
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.
Overview
The
The dialogTransparency
flag under the Zone object passes dialogs transparently for SIP messages processed in that specified zone. If dialog transparency is disabled, the
The 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.
The
The
The
call-id
and tags
) transparently. Similarly, for spiral calls, the call-id
and tags
). Thecall-info
. The parameter call-info
is inserted in requests and responses outbound from the The
call-id
and tags
) as well as dialog stateful SMM variables for INVITE and out-of-dialog SUBSCRIBE messages.For more information on dialog stateful SMM variables, refer to SMM (Advanced) Examples.
Dialog Scope SMM without Dialog Transparency
If the advanced SMM is enabled in any adapter profile which applies to Trunk Group, manipulation of "From tag", "To tag" and "Call-ID header" is not supported for that Trunk Group. In rare cases where there is no other solution, Ribbon Technical support can help with testing and implementing the "To Tag".
Dialog Scope SMM with Dialog Transparency
If the advanced SMM is enabled in any adapter profile applying to a Trunk Group under a zone where the Dialog Transparency is enabled, manipulation of "branch parameter", "Call-Info parameter" or "Call-ID header" is not supported for that Trunk Group.
For example (no dialog transparency): consider a configuration where dialog scope variable is used in the inbound adapter profile applicable to Trunk Group TG_1 via Zone or Trunk Group. The SMM rules for an action specifying modification of "From-tag", "To tag" or "Call-ID" cannot be present in that inbound adapter as well as in the outbound adapter if one applies to "TG_1" through Trunk Group or Zone.
Dialog Transparency Call Flow
When dialog transparency is enabled and "Advanced SMM" functionality is required:
- If both
inputAdapterProfile
andoutputAdapterProfile
are provisioned, enable theadvancedSMM
flag on both SIP Adapter Profiles (inputAdapterProfile
andoutputAdapterProfile
). - If only one SIP Adaptor Profile is provisioned (either
inputAdapterProfile
oroutputAdapterProfile
), enable theadvancedSMM
flag only for the provisioned SIP Adaptor Profile.