In this section:

Related articles:


IMPORTANT

The SBC 5100, SBC 5110, SBC 5200, and SBC 5210 platforms are no longer supported beginning with the SBC Core 10.0.0R0 release. This release supports SBC 5400/7000/SWe/Cloud Native edition (CNe) platforms. Contact Ribbon Sales for upgrade information.


Warning

This feature must be enabled only when dialog transparency is enabled.

Feature Overview

The SBC Core is enhanced to address a scenario where early dialogs at the egress leg are retained at the ingress leg, and the callID is transparently relayed to/from the private to the public network.

With this enhancement, the SBC sends out multiple 18x messages (when using the Dialog Transparency feature) even when the ingress leg does not support 100rel/PRACK. The SBC processes all 18x messages with SDP answers (with different codecs) received at the egress leg, and then sends ingress SDP answers in all of the 18x messages at the ingress leg.

Additionally, the generateCallIdWithDialogTransparency flag is added at the Zone level for the SBC to natively generate the callId on the egress leg when the Dialog Transparency is enabled.

Note

To use this feature, you must enable the following flags:

  • Transcode Free Transparency – on both legs
  • Dialog Transparency – on both legs
  • Downstream Forking Support – on the egress leg (The SBC supports up to 10 forked calls)
Note

The SBC transparently relays the PEM header to the other leg only when the pEarlyMedia transparency flag is enabled.