...
Panel | ||||
---|---|---|---|---|
In this section:
|
...
...
The ICE-Lite (Interactive Connection Establishment) feature interfaces to the Microsoft TEAMS Direct Routing interface. The 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.
...
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
responds to connectivity checks as required to establish and verify connectivity. Spacevars 0 longproductproduct
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
goes 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 longproductproduct
, acting as ICE-Lite agent, acknowledges the final offer with an answer, and both endpoints use the selected candidate pair for the media flow. Spacevars 0 longproductproduct
...
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- On Premises Deployment. For details on ICE-Lite configuration, refer to Creating and Modifying SIP Signaling Groups. |
...
Caption | ||||||
---|---|---|---|---|---|---|
| ||||||
|
Pagebreak |
---|
...
Caption | ||||||
---|---|---|---|---|---|---|
| ||||||
|
...
SBC Feature | Supports | Does not Support | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ICE Restarts The
| ||||||||||||||||||
TURN server operation The
traverse a NAT on the SBC 1000/2000 side, the SBC may be
the SBC is unable to establish connectivity between endpoints in such scenarios. | ||||||||||||||||||
STUN Server Operation in with Full ICE Mode SBC 1000/2000 supports ICE full mode using STUN server to gather candidates. STUN server is required to support ICE full mode. | Only The
| |||||||||||||||||
Internet Connection Using UDP Candidate As an ICE-Lite agent (controlled agent only) , the
ICE-Lite Mode When acting as an ICE Lite agent the SBC is connected to a public internet using only single host UDP candidate. | ||||||||||||||||||
RTP and RTCP Media The
| IPv4 only ICE protocol does not guarantee consecutive ports | |||||||||||||||||
Ports for RTP and | Real-Time Transport Control Protocol (RTCP).RTCP The
| RTP and RTCP on nonconsecutive ports for the
| ||||||||||||||||
IPv4 Support Only As an ICE-Lite agent, the
|
Pagebreak |
---|