Announcing Improved Voice 2.0 Infrastructure

Since the beginning, we at Plivo have invested in our infrastructure because we know that a quality backbone is key to providing you and your customers with a great user experience. Today, we’re excited to announce two enhancements to our infrastructure:

  • New data center locations in South America (Brazil) and US-West (Northern California)
  • Improvements in our global network and voice routing algorithm

These improvements will help improve voice call quality by decreasing audio latency and reducing distortion, garbled speech, and intermittent pauses.

Best of all, we’ve already enabled these improvements for you at no extra charge.

New data center locations

We analyze and optimize for data center locations that positively impact inter- and intra-region connectivity. This is why we’ve added two new data center locations: one in São Paulo, Brazil, to handle our growing South America traffic and another in Northern California to facilitate better connections in North America from the West Coast. These new data center locations enable us to provide optimized in-region connectivity with customers and carrier peering hubs.

Improvements in global network and voice routing algorithms

To achieve low latency on voice calls, we’ve made optimizations to help us route calls more efficiently.

To better illustrate how our optimizations have made positive impacts at every step, here’s an example of a call flow on Plivo’s network. Consider a WebRTC call dialing from Rio de Janeiro, Brazil, to a friend in New Jersey, United States. Upon dialing, the WebRTC application connects the caller to the nearest Plivo voice data center in São Paulo. Plivo then routes the call to the Plivo voice data center closest to the destination, which in this case is in Virginia. After that, the call is connected to a local US carrier in New York and then routed to the receiver in New Jersey.

Voice Infra Flow Diagram

Lower edge latency from customer locations for SIP, WebRTC, and Mobile SDK-based endpoints

We’ve made improvements in the underlying infrastructure that helps your SIP, WebRTC, and Mobile SDK-based endpoints connect to our nearest in-region data centers around the world. We’ve reduced latency between the customer location and Plivo data centers to less than 100ms, which reduces voice call quality issues.

Here are examples of average ping times between customer locations and our nearest data centers:

ContinentData Center LocationDestinationAverage Ping Time
North AmericaUSA West — Northern CaliforniaLos Angeles30ms
San Francisco3ms
Seattle20ms
USA East — VirginiaNew York10ms
Chicago45ms
Austin32ms
South AmericaBrazil — São PauloBrazil25ms
Argentina60ms
Venezuela95ms
EuropeGermany — FrankfurtGermany25ms
United Kingdom20ms
France20ms
AsiaSingaporeSingapore10ms
India85ms
Philippines45ms
AustraliaAustralia — SydneyAustralia20ms
New Zealand20ms

Optimized global routing

We route calls through the nearest network of strategically located data centers worldwide, which lowers inter-region latency and improves call audio quality. This optimized routing means fewer dropped packets, less jitter, and less crosstalk, which is caused by long delays in the time a spoken word needs to travel to the receiver’s ear.

Voice Infra Improvement Example

Optimized intra-region connectivity

After detailed analysis of our voice traffic, we found that more than 25% of calls on our infrastructure traverse multiple regions, so we improved routing between our data center locations to optimize for inter- and intra-region connectivity. We’ve seen the delta in latency reduced significantly, which directly impacts jitter (broken audio) on voice calls. We now have data centers in:

  • South America (São Paulo, Brazil) — New
  • US-West (Northern California) — New
  • US-East (Virginia) — Updated
  • Europe (Frankfurt, Germany) — Updated
  • Asia (Singapore) — Updated
  • Australia (Sydney)

Faster connectivity to carrier peering hubs

To guarantee high quality of service, Plivo peers with Tier 1 carriers around the world with latency less than 20ms at major hubs, which reduces the amount of time needed to connect directly to carriers. To lower the latency between our data centers and carrier peering hubs, we’ve developed algorithms to evaluate and connect to the nearest peering hubs based on each call.

ContinentCarrier Peering Hub LocationLatency
North AmericaBig APE, 60 Hudson, New York20ms
South AmericaPTT-SP — PTT São Paulo, Brazil20ms
EuropeTelehouse Frankfurt20ms
AustraliaEQIX-SYD — Equinix Exchange Sydney10ms
AsiaEQIX-SIN — Equinix Exchange Singapore10ms

Direct carrier connectivity and redundancy

Our carrier team has been working hard to make more local in-country carriers available to our networks. Increasing carrier availability and quality by providing multiple carriers in every country also improves connectivity between the destination carrier and the destination.

Of course, not all carriers are created equal, which is why we test every carrier on Plivo’s network for low post-dial delay (PDD), guaranteed features such as CLI and DTMF, and high mean opinion score (MOS). We also ensure that our networks connect to a minimum of two carriers in each country. This redundancy safeguards against single points of failure. In the event of a carrier failure, our infrastructure will automatically load balance and route traffic to more reliable carriers within the same region. We currently work with more than 100 in-county carriers globally to ensure that our network is always optimized, and we’re constantly adding more carriers to our network.

What do these improvements mean for you and your customers?

At Plivo, we understand that quality is at the core of any great product. High quality of service not only gives you access to clear voice quality, it also helps your business deliver the same level of quality to your customers.

 

comments powered by Disqus

By submitting this form, you agree we may contact you in the manner described in our Privacy Policy