Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1bgoswami
REV5mshanmugam
REV6radaikalam
REV3dpaliyil
REV1sgibbard
REV2

...

lali

Panel

...

borderColorgreen
bgColortransparent
borderWidth2

...

Back to Table of Contents 

Back to SBC for WRTC

...

In this section:

Table of Contents
maxLevel4

...

width40%

Overview

The 

Spacevars
0series4
supports ICE and DTLS with direct media and anti-trombone scenarios. Any call, which is setup as Direct Media call can become a non-Direct Media call due to call transfer or Re-INVITE. The 
Spacevars
0product
supports conversion of a Direct Media call to Non Direct media and vice versa and handles the ICE/DTLS interactions as per the following:

Spacevars
0product

...

  • Direct media call between two devices that support ICE procedures and may use DTLS for media. The ICE procedures, connectivity checks, and DTLS procedures occur directly between the endpoints. The direct media works with early dialog (answer in 18x reliable) and/or 200 Ok. The 
    Spacevars
    0product
    sends the following ICE and DTLS parameters are copied from Ingress SDP and sent in Egress SDP for direct media:
    • ICE parameters
      • ice-ufrag
      • ice-pwd
      • ice-lite
      • ice-mismatch
      • candidate
      • remote-candidates
      • ice-options
      • end-of-candidates
    • DTLS parameters
      • setup (active/passive)
      • fingerprint
Spacevars
0product

...

  • ICE-Lite procedure for a call when it is reconfigured as non-direct media after setting up as a direct media call initially.

...

Spacevars
0product

...

Spacevars
0product

...

  • Reconfiguring a call to direct media with end to end ICE procedures after it is setup as non-direct media call using ICE-Lite procedures.

Spacevars
0product

...

  • Transferring a non-direct media call that used ICE-Lite to a direct media call to another party by Refer mechanism.

Note
iconfalse

Note

The 

Spacevars
0product
 does not play any role in the ICE procedures for the transfer of a direct media call (that is connected through an AS) to a direct media call to another party except relaying the SDP parameters.

 

Inter-SBC Direct Media Scenarios

In inter-

Spacevars
0product
direct media scenario, the call legs are on different
Spacevars
0product
s.

The following diagram illustrates inter-

Spacevars
0product
direct media scenario with end to end ICE and DTLS procedure.

Caption
0Figure
1The Inter-SBC Direct Media Scenario with End to End ICE and DTLS Procedure

 Image Modified

Intra-SBC Direct Media Scenarios

In intra-

Spacevars
0product
direct media scenario, both the call legs are on same
Spacevars
0product
.

The following diagram illustrates intra-

Spacevars
0product
direct media scenario with end to end ICE and DTLS procedure.

Caption
0Figure
1The Intra-SBC Direct Media Scenario with End to End ICE and DTLS Procedure

Image Modified

Note
  • If both DTLS relay and Direct Media are configured on
    Spacevars
    0product
    , Direct Media takes precedence over DTLS relay.
  • A late media with pass-through call can be established as a Direct Media call if Direct Media configuration is enabled.
  • A late media with convert call can be established as a Direct Media call if Direct Media configuration is enabled. However, in this case the first INVITE sent

...

  • by the 
    Spacevars
    0product
    , the Egress side must have locally generated parameters (including local ICE candidates) in the SDP.

Anti-trombone Direct Media

Anti-trombone direct media uses normal direct media on the 

Spacevars
0product
facing the endpoints and anti-trombone configuration on the 
Spacevars
0product
side facing the SIP AS. This feature is useful when x-dmi cannot be passed through the SIP AS. For more information, refer to Media Antitrombone.

Caption
0Figure
1Anti-trombone Direct Media

Image Modified

ICE Ingress and Egress Compatibility

  • DTLS must be enabled on Ingress and Egress Trunk Groups if required for Direct Media.
  • ICE must be enabled and compatible between Ingress and Egress Trunk Groups for Direct Media ICE calls.
Caption
0Table
1ICE Ingress and Egress Compatibility
Ingress TG ICE ConfigurationEgress TG ICE Configuration


 NONEICE-LYNCICE-WRTCICE-Full
NONEYesNoNoNo
ICE-LYNCNoYesNoNo
ICE-WRTCNoNoYesYes
ICE-FULLNoNoYesYes
Note

When a call is established as an ICE direct media call,

...

the

Spacevars
0product
does not support media handling. Therefore, the existing CDR fields are populated for Ingress and Egress local Ip address/ports as 255.255.255.255/65535 and Ingress and Egress remote IP address/ports as 127.0.0.0/5004 for each of the media streams on the call. For more information, refer to the section CDR Field Descriptions.

Call Flows

Inter-SBC Direct Media

Caption
0Figure
1Inter SBC Direct Media Call Flow

 Image Modified

Intra-SBC Direct Media

Caption
0Figure
1Intra SBC Direct Media Call Flow

 Image Modified

Anti-trombone Direct Media

Caption
0Figure
1Anti-trombone Direct Media Call Flow

Image Modified

SIP UA—IP Phone/PBX
SIP Server—PBX/Softswitch
Dialogx— Number of the dialog
IP—IP address in C line
SBCIP—IP address in Cline of

...

the

Spacevars
0product

Note

The MS Lync/Skype Remote Desktop Sharing feature is supported on

...

all

Spacevars
0series4
platforms:

  • SBC 5000 series
  • SBC 7000

...

  • SWe (all environments)