This article original from Http://blog.csdn.net/voipmaker reprint annotated source.
I built a communication learning Exchange Group, 45211986, Welcome to join.
WEBRTC Technology is committed to the browser to achieve real-time audio and video, multimedia data interoperability, its NAT traversal part of the ice framework, the purpose is to achieve media P2P,SBC called the session Border controller, dedicated to the media, signaling NAT traversal, but SBC technology in the media by the server relay, This violates the original intention of WEBRTC, but when the client based on WEBRTC technology and non-WEBRTC technology clients (such as sip,h323-based protocol) interoperate, it is necessary to use a gateway that is responsible for the conversion of the two sides of the protocol. At this time SBC as an access device can consider implementing WEBRTC related standards for WEBRTC client and non-WEBRTC client interoperability, while the WEBRTC client NAT traversal failure to go turn, which is the same as the SBC's Media relay task, If this time through the SBC forwarding media to a certain extent improve the timeliness of call establishment, I think the SBC will play a key role in the WEBRTC, the traditional domain if no SBC will be isolated from WEBRTC, the latter can provide the old World and New World transition.