Page History

Overview

The 

Spacevars
0 series4

supports ICE and DTLS with direct media and antitrombone 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
0 product

supports conversion of a Direct Media call to Non Direct media and vice versa and handles the ICE/DTLS interactions as per the following:

• 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
  0 product

  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

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

• 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.

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

Note
icon false
Note The  Spacevars 0 product  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.

Pagebreak

Inter-SBC Direct Media Scenarios

In inter-

Spacevars
0 product

direct media scenario, the call legs are on different

Spacevars
0 product

s.

The following diagram illustrates inter-

Spacevars
0 product

direct media scenario with end to end ICE and DTLS procedure.

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

Intra-SBC Direct Media Scenarios

In intra-

Spacevars
0 product

direct media scenario, both the call legs are on same

Spacevars
0 product

.

The following diagram illustrates intra-

Spacevars
0 product

direct media scenario with end to end ICE and DTLS procedure.

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

Note

If both DTLS relay and Direct Media are configured on Spacevars 0 product , 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 0 product , the Egress side must have locally generated parameters (including local ICE candidates) in the SDP.

Pagebreak

Antitrombone Direct Media

Antitrombone direct media uses normal direct media on the 

Spacevars
0 product

facing the endpoints and antitrombone configuration on the 

Spacevars
0 product

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
0 Figure 1 Antitrombone Direct Media

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
0 Table 1 ICE Ingress and Egress Compatibility
Ingress TG ICE Configuration Egress TG ICE Configuration   NONE ICE-LYNC ICE-WRTC ICE-Full NONE Yes No No No ICE-LYNC No Yes No No ICE-WRTC No No Yes Yes ICE-FULL No No Yes Yes

Note

When a call is established as an ICE direct media call, the Spacevars 0 product 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 (old).

Call Flows

Pagebreak

Inter-SBC Direct Media

Caption
0 Figure 1 Inter SBC Direct Media Call Flow

Intra-SBC Direct Media

Caption
0 Figure 1 Intra SBC Direct Media Call Flow

Antitrombone Direct Media

Caption
0 Figure 1 Antitrombone Direct Media Call Flow
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 0 product

Note
The MS Lync/Skype Remote Desktop Sharing feature is supported on all Spacevars 0 series4 platforms: SBC 5000 series SBC 7000 SWe (all environments)