メニュー

Expand
Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

Twilio Client Edge Locations

Twilio Client JS SDK (twilio.js) v1.11 lets you select the specific Twilio data center edge locations used when your Twilio Client Device connects to Twilio. Network communication to and from Twilio will originate/terminate from the fixed, static IP address ranges listed for each edge location. Refer to these ranges if you need to configure your local network to allow communication or apply Quality of Service routing rules to communication with Twilio.

Twilio edge locations were added in version 1.11. Prior releases used a parameter named region that has now been deprecated.

Edge Location information for Twilio Client JS SDK

By default, the Twilio Client JS SDK will use Twilio's Global Low Latency (roaming edge location) routing capability to determine which data center is closest to your user, establishing a connection through Twilio's nearest point of presence. Global Low Latency uses latency-based DNS lookups to determine the nearest data center. You may want to override this in some cases, especially when your users are working from a fixed location and using a DNS server in another edge location.

GLL (roaming edge location) requires the upstream DNS to support RFC 7871. See GLL requirements for more information.

If you are operating a restricted network that requires allowing of media IPs, our recommendation is to specify the edge location in your application. Twilio will continue to expand our Global Low Latency (roaming) footprint in the future by adding more edges with different IP ranges and leaving the edge selection up to Global Low Latency could result in connections being established to edges that are not allowed by your infrastructure which may result in one-way audio or call set up failures.

Use any one of the available edge locations as the edge parameter when calling .setup(). Leaving the value undefined will cause Twilio to default to its Global Low Latency routing, which cause the Device to establish its connection to the Twilio edge closest to the user.

For connectivty and bandwidth requirements including IP address list and ports see Voice Client JS and Mobile SDKs’ Network Connectivity Requirements

使用例

Twilio アイルランド経由の接続を強制的に確立します。

Twilio.Device.setup(token, { edge: "dublin" });

Force connections through Twilio US East Coast edge over your private Interconnect connection to that edge:

Twilio.Device.setup(token, { edge: "ashburn-ix" });

Let Twilio choose the nearest edge:

Twilio.Device.setup(token);

詳細については、Twilio.Client.Device ドキュメントを参照してください。

Rate this page:

ヘルプが必要ですか?

誰しもが一度は考える「コーディングって難しい」。そんな時は、お問い合わせフォームから質問してください。 または、Stack Overflow でTwilioタグのついた情報から欲しいものを探してみましょう。