There is only so much SD-WAN vendors can do when it comes to VoIP and specifically WebRTC optimization. When a vendor claims for specific VoIP optimization that is based on quality of experience or similar considerations, I suggest to check the details of how this optimization is implemented and which applications it covers.
Delivery of WebRTC based communications services to the enterprise can be (and is today) done over best effort open internet but for higher adoption rates among enterprises it is required to enable the delivery of such services over managed networks.
The growing adoption of SD-WAN allows for agile and dynamic delivery of WebRTC services to enterprises
There is no one good answer for the debate between on premise vs. managed and each of these options have sub-options to consider and decide on. The devil is in the details and in many cases a hybrid solution is required, using some functions (such as NAT traversal) from 3rd party hosted services while licensing (open source or commercial) other components of the solution.
The official adoption of WebRTC by Apple is great news. As always, the devil is in the details. Before starting the party let’s see Apple’s approach to WebRTC, first and foremost not making it part of their walled garden and second in areas related to interoperability related to APIs, ORTC vs. WebRTC 1.0, codecs support and HW acceleration.
While there is adapter.js that quests to bridge browser compatibility issues, it focuses mainly on API mapping. There are other issues, such as differences in SDP, that it doesn’t handle and these issue cause applications to break when used on dissimilar browsers. The constant changes in browser versions and in some cases, lack of backward compatibility between them make this a moving target.
As part of Chrome 52 release there were some performance and security enhancements, one of them was the decision to switch over to using Elliptic Curve Cryptography for generating the self-sign certificate used in the DTLS handshake. ECDSA is mandatory in WebRTC, question is, should you be worried about patent claims in this regards.