| Noprint |
|---|
| Panel |
|---|
| borderColor | green |
|---|
| bgColor | transparent |
|---|
| borderWidth | 2 |
|---|
|
|
...
Overview
The
supports Dialog Transparency which involves passing through "Call-ID", "From" tag, and "To" tag transparently in all the requests and responses. With a call traversing through multiple paths in an IMS VoLTE network, UEs and intermediate IMS entities need to correlate a call based on correct dialog information under various scenarios such as call transfer.
| Div |
|---|
|
| Excerpt |
|---|
The dialogTransparency flag under the Zone object passes dialogs transparently for SIP messages processed in that specified zone. If dialog transparency is disabled, 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. The dialogTransparency flag must be enabled on both ingress and egress zones because of 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. | Note |
|---|
The following features are not supported on SBC when Dialog Transparency is enabled: - Support of local handling of REFER (REFER relay is supported)
- Late media support
- Dialog Transparency support in REGISTER
- NICE recording call flows
- GW-GW support
|
|
|
SBC implements the SIP Dialog Identification internally based on certain SIP parameters. Manipulation of these parameters using the dialog scope
SIP Message Manipulation (SMM
) affects the intergrity of the dialog scope SMM functionality. The parameters to be considered differs based on whether the Dialog Transparency is enabled or not
. supports both dialog transparency and spiral calls. To support these features, dialog stateful SMM must support multiple dialogs that have the same dialog identifiers. Dialog stateful SMM variables also support dialog transparency, which is enabled with INVITE and SUBSCRIBE dialogs. supports dialog stateful SMM variables to modify inbound or outbound SIP messages and dialog transparency to pass the dialog identifiers (call-id and tags) transparently. Similarly, for spiral calls, handles multiple legs with same dialog identifiers (call-id and tags). distinguishes between the multiple legs using the proprietary parameter call-info. The parameter call-info is inserted in requests and responses outbound from the in such a way that it must present in almost every subsequent SIP requests and responses of a dialog.
is now enhanced to support different SMM dialog for multiple call legs with same SIP dialog identifiers (call-id and tags). supports 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.
For Dialog Scope SMM without Dialog Transparency
...
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" via through Trunk Group or Zone.
...
For CLI and EMA configuration details, see:
...
| Caption |
|---|
| 0 | Figure |
|---|
| 1 | Dialog Transparency Call Flow |
|---|
| 3 | Dialog Transparency Call Flow |
|---|
|
|
...