User Community Feedback

In order to deliver high call scalability in a Local Gateway solution we must rely in a 3rd party vendor. Looking at information (Ribbon, Audiocodes and Oracle ) it seems Webex Calling does not provide full support to ICE.

In case of Oracle the information is:

There is a limitation of ICE interworking with Cisco Webex calling. Cisco states the SBC needs to add a candidate attribute advertising the RTCP port as well as RTP port. As of now, the Oracle SBC is not sending both (SBC sends only one candidate line attribute i.e., for RTP even if rtcp-mux is disabled), there is an issue. Looking at traces from both the SBC and the client, the client does not send a STUN Binding request to the SBC unless both are advertised in SDP.

Oracle SBC do support ICE interworking using RTCP-Mux and we thought of trying that option to solve this issue, but Cisco clients do not support RTCP-Mux at this time. We also tried using 3rd party devices to solve ICE issues, but Cisco Webex Calling does not support ICE with those devices. Hence there is no support for ICE as of now and we are working internally to solve this issue. We will also update the app note once there is support for ICE with Cisco Webex calling.

So, support for ICE and RTCP-Mux is highly supported in several WebRTC applications. So, Webex Calling should support in the future.