Umatilla Client Edge Overview

The Umatilla Oregon public edge location (previously known as US2 or the US West edge) is now available to your JavaScript/Android/iOS Voice SDKs. This guide explains the details you'll need to test and use this network edge.

Initial rollout

Here's how we'll launch launch access to this network edge:

  • On November 10, 2022 between 10 and 11 AM PST, we’ll activate GLL for an hour for you to test your media IP firewall block list changes.
  • On December 1, 2022, you’ll be automatically opted into Umatilla Global Low Latency (GLL, or “roaming”). GLL helps ensure users have the best call quality by connecting to the nearest network edge or region.

Notice: If you maintain media IP firewall block lists, you’ll need to open a firewall to allow traffic from the Umatilla media ranges. Additionally, you may need to update to the latest Twilio Voice SDK version to use this new edge location.

SDK versions supported

The Umatilla Oregon edge is supported as of the following SDK versions:

  • Android SDK: 6.1.2 [Maven Central], [docs] (MD5 Checksum : 1e9ce7d72f561c46711bbcdfa1df2873).
  • iOS SDK: 6.4.2 [XCFramework] (checksum: caebcfde5540e6aefeab61edb5d131c55565eb72b690fc50e8201836f0c21735).
  • Javascript SDK: We recommend using the latest versions; however, Twilio supports all 2.x and 1.10.3 versions.

For more information, please review the JS SDK and Mobile SDK guides.

What happens if you don’t take action?

Calls may fail if you maintain media IP firewall block lists and firewalls aren’t opened to allow traffic from Umatilla media ranges before the November 10, 2022 testing window.

FAQs and more information

Q: Can the Umatilla edge be used now, before GLL is enabled?

A: Yes, you can now point your calls to Umatilla.

Q: What is the Umatilla port range and GLL port range?

A: Both Umatilla and GLL have a destination port range of 1,024 - 65,535.

Q: Do Flex customers have to take action?

A: Flex uses the voice client SDK to make calls which uses GLL (roaming) as the default region. If you have a firewall that blocks RTP traffic, you’ll need to ensure the firewall allows the traffic from Umatilla.

Also, if you have reconfigured the Voice Client SDK through sdkOptions with fallback to GLL or roaming, and you have a firewall that blocks RTP traffic, you’ll need to ensure the firewall allows the traffic from Umatilla.

Q: Will calls fail if I don’t update Android or iOS SDK versions?

A: No. If you use an older mobile SDK and GLL, you can still connect to Umatilla. Older clients can’t explicitly pick Umatilla/US2. If you want to use Umatilla for optimized latency, you’ll need to upgrade to the most recent versions.

Q: Will calls fail if I don’t update Javascript SDK versions?

A: We recommend using the latest versions; however, Twilio supports all 2.x and 1.10.3 versions.

Q: How can I test that my network is properly configured?

A: If you’re using the JS SDK, you can use this Network Tester to test Umatilla and check if the environment works with Twilio. The mobile SDK doesn’t have preflight check API built into the SDK, so you’ll need to use the network connectivity requirement doc and allow the IP/port range.

Q: What happens if my firewall doesn’t allow media ports for the new IP ranges?

A: You’ll be able to make and receive calls, but you won’t be able to hear audio. If you have a restrictive network and you specify GLL when connecting to Twilio, all media server IP addresses in all edge locations must be allowed. If you’re not operating in all edges, we recommend you specify the edge that is closest to your deployment. With this approach, you'll only need to allow the Media server addresses for the edge that you specify.

Q: I still need more time to allowlist for Umatilla. Is there a workaround?

A: You can specify a failover edge. The Javascript SDK has additional capability that will enable automatic edge fallback functionality if you specify an array of edge locations:

Twilio.Device.setup(token, { edge: [‘gll’,’ashburn’,'umatilla', 'sydney'] });

This lets you specify the preferred edge to use, along with one or more fallback locations in case the first location fails.

Flex customer guidance

If you want to confirm whether or not this might have been modified for your customers, you can review the Flex configuration file which determines whether any of the SDKs have any non-default options that would be used for the environment. By default, the voice edge (voice.sdkOptions.edge) is not defined, and so GLL will be used to determine the edge a call should be delivered from.

If you wish to double check, you can review an account's Flex configuration file (ui_attributes) to confirm these settings.

Have more questions? Submit a request
Powered by Zendesk