Read on for a deeper look at these improvements, or get started with the release by checking out the updated APIs here.
Catch pre-flight problems
Local environments are tricky, especially when you’re trying to test headsets and microphones. The problem with headset and microphone issues is that they’re hard to detect, which leads to misdiagnosed issues and unhappy users.
Twilio Client’s Connection class now reports the input and output volumes of the call, making it easy to show real-time volume indicators in your UI.
Audio Input and Output Selection
Using the new Device.audio API, developers may now specify which audio output device(s) to play Client sounds through, in browsers that support the feature (Chrome 49 and above). The incoming ringtone sound is separated into its own audio channel, allowing it to be played out of a different set of output devices than in-call audio. The Device.audio API also allows developers to swap the input device during an ongoing call, or set the input device and test it before making a call.
Local and Remote Stream APIs – With the new
connection.getLocalStream() APIs, developers can easily access the stream being used in the connection. This can be used to set up a mic and speaker test feature, which will help users diagnose their own problems before entering a call or conference.
Provide users an early warning system
Is it you? Is it me? Call quality warnings give users early warnings when their network misbehaves and is affects the communication. The Twilio.Connection object now emits events when network conditions deteriorate. You can use these events to let users know when their local network is affecting call quality. This can enable them to take corrective action like moving to a place with a better WiFi signal or plugging in an Ethernet cable. You can analyze these events for the entire account using Voice Insights.
Enterprise-Ready Security & Performance
You can get started today, just check out the following items: