Support for ORTC in Microsoft Edge
We love APIs, especially APIs that make it easier to communicate. And Microsoft Edge’s Object Real-time Communications API, or ORTC, fits the bill. A variant of WebRTC, ORTC intends to give communications developers a greater degree of control and flexibility in their applications, and eliminate some unnecessary complexity in negotiating communications sessions in the process. You can try using Twilio Client 1.3 and ORTC in Microsoft Edge to start make calls now.
Best of all, ORTC makes this possible without depending on any browser plugins. Consequently, we’ve taken the additional step of eliminating Adobe Flash entirely from Twilio Client 1.3.
Qosmy, a company that uses Twilio Client to power real-time customer feedback, were thrilled at the support for Microsoft Edge. “It’s a big deal,” founder Michael Moore explained,
“Twilio Client 1.3 lets Qosmy run on Microsoft’s new Edge browser in addition to Chrome and Firefox. Overnight, we’re able to support a huge and growing population of Microsoft users migrating to Windows 10. Using Twilio Client, we can focus on delivering real-time customer service feedback and churn predictions to our enterprise clients — safe in the knowledge that our service has great underlying voice connectivity for every inbound caller.”
DSCP & Static IP addresses
This release of Twilio Client also takes some significant steps to improve quality of service and meet advanced network requirements. Twilio Client 1.3 now establishes media and signaling connections from a static set of IP address ranges, unique to each Twilio data center. This makes it easy to apply QoS policies to optimize call quality, or to whitelist inbound and outbound IP addresses for security reasons.
Additionally, Twilio Client 1.3 enables DSCP by default in compatible browsers (currently Google Chrome). Capable browsers will tag WebRTC media packets, enabling differentiated handling on a LAN, so that real-time media can be prioritized above other network traffic.
Select Client region
For security, privacy or performance reasons, developers and network admins can now force Twilio Client to establish media and signaling connections to a specific Twilio data center. By default Twilio Client will use our Global Low Latency functionality to select the data center automatically based on geo-DNS. However, this can now be overridden if there’s a different Twilio data center that has better connection characteristics to your client.
Why would you do such a thing? We’ve found in the real world that folks don’t always use DNS servers in the country or even region where they have clients deployed. We’ve also seen that the geographically closest data center doesn’t always provide the lowest latency connection. Now developers can make the decision of whether to use geo-DNS or manually select a data center.
Removing support for Adobe Flash
As mentioned above, Adobe Flash support has been removed from Twilio Client, following the addition of ORTC support in Microsoft Edge. Over the last year, we’ve seen Flash usage decline dramatically with our customer base, while the few customers who attempted to use Flash encountered more and more issues while browser vendors gradually remove the feature. We’ll continue to support Flash in the previous release of Twilio Client (1.2), but it’s time to wave goodbye to the plugin, and move ahead with a modern media stack.
WebRTC/ORTC support is becoming increasingly ubiquitous – Microsoft has already seen 200 million active devices using Windows 10 with Edge as the default browser, adding 200 million devices that can be reached through ORTC.
Removing Support for Presence Events
Twilio Client 1.3 also removes support for Presence Events. Removing Presence Events allows us to focus on the features that developers care about most. As with Flash, we will still support Presence Events in Client 1.2.
Getting started with Client 1.3