Page History

Add_workflow_for_techpubs

AUTH1 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} JIRAIDAUTH SYMCHOR-244721761 REV5 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} REV6 UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} REV3 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cbbb06478a00a02355cd1c2f0155cd26cef30cd0, userName='null'} REV1 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc0e070f8a00a02355cd1c2f0155cd26cef20cbf, userName='null'}

Panel
In this section: Table of Contents maxLevel 3

Include Page
Not_for_SWe Not_for_SWe

ICE-Lite Overview

The ICE-Lite (Interactive Connection Establishment) feature interfaces to the Microsoft TEAMS Direct Routing interface. The

Spacevars
0 longproduct

SBC integrates Microsoft Teams clients by acting as an ICE Lite agent endpoint for SIP calls involving Network Address Translators (NATs). This feature enables direct routing between an existing enterprise voice infrastructure (that is, the PSTN carrier and SIP trunks used for trunking services) and the Microsoft Phone System in Office 365. The SBC acts as a PSTN gateway; sessions for Microsoft Teams users can be routed directly to the PSTN through the SBC.

How does the SBC interoperate with Microsoft TEAMS?

As communications sessions are set up and negotiated, Session Description Protocol (SDP) is used to carry the IP addresses and ports of all participants that receive RTP streams. Because Network Address Translators (NATs) alter IP addresses and ports, the exchange of local IP addresses and ports may not be sufficient for establishing connectivity. Acting as an ICE-Lite agent, the

Spacevars
0 longproduct

responds to connectivity checks as required to establish and verify connectivity.

A Teams client initiates the media flow and becomes the controlling ICE agent for the SBC. During the establishment of a media session that uses ICE-Lite, the 

Spacevars
0 longproduct

goes through candidate gathering and connectivity check phases that occur before the controlling agent (optionally) sends a final SDP offer that includes the best local and remote candidates selected for a media flow. The 

Spacevars
0 longproduct

, acting as ICE-Lite agent, acknowledges the final offer with an answer, and both endpoints use the selected candidate pair for the media flow.

Configuration

Configuration for ICE-Lite is completed through the SIP Signaling Group.

Info
For detailed configuration for using ICE-Lite with Microsoft TEAMS, refer to Best Practice - Configuring SBC Edge for Select Microsoft Teams Direct Routing Related Migration Scenarios. For details on ICE-Lite configuration, refer to Creating and Modifying SIP Signaling Groups.

Info
The screen shot below is for an SBC 2000.

Panel
borderStyle none
Caption 0 Figure 1 SIP Signaling Group - ICE-Lite Configuration

The following fields must be configured to enable the ICE-Lite feature:

ICE Support

Caption
0 Table 1 ICE Support - Field Definition
Field Location Definition ICE Support Settings > SIP Signaling Group Enables/disables ICE Lite support. This field must be enabled for ICE-Lite to be active.

Pagebreak

ICE Mode

Caption
0 Table 1 ICE Mode - Field Definition
Field Location Recommended Configuration ICE Mode Settings > SIP Signaling Group Specifies the Interactive Connection Establishment (ICE) mode. Valid entries: For SBC 1000/2000: Lite or Full. To access the ICE-Lite feature, configure this field as Lite. For SBC SWe Lite: This field is configured as Lite automatically when ICE support is Enabled.

Interoperability Notes

ICE-Lite impacts the following on the SBC 1000/2000 and SBC SWe Lite.

Pagebreak