Twilio updated the “Twilio Client” used in the FastCall softphone.
WebRTC (real time communication) is the latest in-browser communication protocol. The headset in the FastCall app. Before WebRTC – and w/o WebRTC – the browser uses Flash for the softphone. For example, using the FastCall softphone in Internet Explorer uses Flash. Therefore we do not recommend it.
Chrome adopted WebRTC in Chrome in late 2012. Firefox followed in 2013.
If you are using the FastCall softphone in a browser other than the most recent Chrome or Firefox you may see degredated call quality. We have some added tips on the softphone here.
FastCall upgraded to Twilio Client 1.2 in our 1.65 release. Twilio Client enables calling in-browser, leveraging WebRTC and connecting to legacy PSTN networks (phones.) Twilio extended their Global Low Latency (GLL) architecture to Twilio Client’s WebRTC.
Twilio’s system dynamically determines the best route of the call so that there’s no lag/latency or extraneous noise. When a call is made from anywhere around the world, the system will determine which of the six data centers it should route through: Virginia, California, Tokyo, Sao Paulo, Dublin, Sydney or Singapore. All calls will appear to be a normal conversation that you’d be having with the caller on the other side of the line. The company hopes this will ensure that a great user experience is maintained and that it will continue to be the future of communication.
Please note: Twilio is not yet supporting Global Low Latency in a conference call; such as FastCall uses in our voicemail drop. If you are outside North America and using the FastCall softphone and our voicemail drop, you may experience degraded call quality.