Page History

...

Overview

SBC is enhanced to support supports a subset of the functionality required for a full-ICE agent. This feature extends the existing implementation of full-ICE to support the following functionalities:

• In controlling role, SBC initiates connectivity check with a STUN Binding Request. The connectivity check by SBC is sent in response to the first connectivity check, which is received from the peer. SBC selects the remote Ip address for media based on the address signaled in the first STUN Binding Request, which is received from the peer. To assert the selection of media, SBC sends STUN Binding Request with the USE-CANDIDATE attribute.
• In controlled role, SBC initiates a single connectivity check with a STUN Binding Request to the peer. This request is sent after receiving a Binding Request from the peer, which contains the USE-CANDIDATE attribute. This behavior is important to complete the full-ICE procedures when inter-operating with WRTC peers such as Google and Chrome.
• In controlling role, SBC protects against network loss of STUN message exchanges by introducing internal guard timers and sends STUN Keep-Alive messages at a configurable interval. This functionality is based on the procedures defined in RFC5245.

These enhancements functionalities allow SBC to inter-operate with other ICE peers, which require the connecting peer to act as a full-ICE agent.

...

• Allows specification of IPv6 candidates at Signaling and in STUN messages.
• Validates the received STUN messages and attributes based on the MS-ICE2 standards.
• Protects against network loss of STUN message exchanges by introducing internal guard timers and sends STUN Keep-Alive messages at a configurable interval.

To implement this feature, SBC is enhanced to support SBC supports the following functionalities to implement pseudo full-ICE and MS-Lync ICE:

• Timers
• Pseudo Full ICE and MS-Lync ICE Support

...