You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Back to Table of Contents

Back to IP Multimedia Subsystem (IMS)

Back to IMS Centralized Service Capability and Service Continuity Support 

In this section:

Related articles:

Overview

Unable to show "metadata-from": No such page "_space_variables"
supports downstream forking call flows when dialog transparency is enabled.

  • Unable to show "metadata-from": No such page "_space_variables"
    supports multiple early dialogs at ingress leg when dialog transparency is enabled. It relays each forked 18x response received for the INVITE at egress leg towards the ingress leg by transparently passing the Call-ID, "From" tag, and "To" tag thus exposing multiple early dialogs at ingress leg.

    The offer/answer negotiation on a forked call depends on the Packet Service Profile configured on either legs. As a result, SDP sent in the forked 18x response(s) towards ingress leg may vary depending on whether pass-through mode or transcoding mode is selected by

    Unable to show "metadata-from": No such page "_space_variables"
    . 
    Unable to show "metadata-from": No such page "_space_variables"
    continues to use the same media IP/Port that is sent in the first 18x SDP for all the forked 18x messages sent towards the ingress leg. Before sending a forked 18x response towards ingress leg, 
    Unable to show "metadata-from": No such page "_space_variables"
    sends UPDATE on the previous early dialog with SDP that contains "a=inactive" line. This is performed to prevent ingress peer from sending media on all the early dialogs exposed by
    Unable to show "metadata-from": No such page "_space_variables"
    . With this call flow, media is expected only on the last active early dialog exposed by the
    Unable to show "metadata-from": No such page "_space_variables"
    .

  • Unable to show "metadata-from": No such page "_space_variables"
    supports UPDATE with preconditions on each of the early dialogs exposed on the ingress leg and relays the same to the corresponding early dialog on the egress leg.
  • Unable to show "metadata-from": No such page "_space_variables"
    supports 199 response from the egress leg for an early dialog identified by the "To" tag. 
    Unable to show "metadata-from": No such page "_space_variables"
    removes the corresponding early dialog context after receiving 199 response and also relays the same to the ingress leg if configured. In this scenario, only the corresponding early dialog is removed and the call remains as it is.
  • Unable to show "metadata-from": No such page "_space_variables"
     supports BYE request within an early dialog identified by "To" tag. 
    Unable to show "metadata-from": No such page "_space_variables"
    removes the corresponding early dialog context after receiving a BYE request and also relays the same on the other leg.
  • Currently, 
    Unable to show "metadata-from": No such page "_space_variables"
    supports CANCEL request for a regular call by tearing down the call and forwarding the CANCEL to the egress leg. With this feature, all the early forked dialogs are also cleared internally.

The following diagram is an example call flow scenario for downstream forking with dialog transparency.

Downstream forking with dialog transparency call flow

Call-ID and From tag are assumed to be same in all the responses shown in the above call flow.

Preserving Early Dialog Context after 200 OK for INVITE

Unable to show "metadata-from": No such page "_space_variables"
 retains all the early dialog contexts, even after a forked call is answered or connected with 200 OK and ACK for 32 seconds.
Unable to show "metadata-from": No such page "_space_variables"
 handles all inactive early dialogs as follows:

  • 199 response from Egress is relayed to Ingress.
  • BYE from Ingress is relayed to Egress.

Unable to show "metadata-from": No such page "_space_variables"
clears any existing early dialogs automatically after 32 seconds.

The parameters dialogTransparency and downstreamForkingSupport must be enabled to perform these functionalities. 

The following diagram is an example call flow scenario for preserving early dialog context after 200 OK for INVITE.

Preserving Early Dialog Context After 200 OK for INVITE Call Flow

Support for UPDATE with Codec Change on Inactive Early Dialog

Unable to show "metadata-from": No such page "_space_variables"
supports UPDATE with Session Description Protocol (SDP) both for active and inactive early dialogs before a final 200 OK for INVITE is received.

 The parameters dialogTransparency and downstreamForkingSupport must be enabled to perform these functionalities.

The following diagram is an example call flow scenario for support for UPDATE with codec change on inactive early dialog.

Support for UPDATE with Codec Change on Inactive Early Dialog Call Flow

Deactivate Media Resources When Early Dialogs Do Not Exist

Unable to show "metadata-from": No such page "_space_variables"
 retains the call, but deactivates media resources when all the early dialogs are cleared for a forked call either due to 199 or BYE response.

 The parameters dialogTransparency and downstreamForkingSupport must be enabled to perform these functionalities.

The following diagram is an example call flow scenario for deactivating media resources when early dialogs don't exist.

Deactivate Media Resources When Early Dialogs Do Not Exist Call Flow

 

 

  • No labels