SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

How to Connect IPv6 SIP Clients to Twilio's IPv4 SIP Endpoints

Overview

Twilio’s Programmable Voice SIP Domains and SIP Trunking endpoints currently support only IPv4 connectivity. If your SIP client or infrastructure operates on IPv6, you may encounter challenges connecting directly to Twilio’s services. This article explains best practices and recommended solutions for bridging IPv6 SIP clients to Twilio’s IPv4 SIP endpoints.

 

Product

Elastic SIP Trunking

 

What You Need To Know

Why Doesn’t Twilio Support IPv6 for SIP Endpoints?

At this time, Twilio’s SIP endpoints are accessible only via IPv4. While IPv6 adoption is growing, many cloud communications providers including Twilio continue to rely on IPv4 for SIP signaling and media due to broad compatibility and network considerations.

 Recommended Solution: Dual-Stack Session Border Controller (SBC)

The industry-standard approach for connecting IPv6 SIP clients to IPv4-only SIP services is to use a dual-stack Session Border Controller (SBC). A dual-stack SBC is a network device or software that supports both IPv4 and IPv6, allowing it to:

  • Accept SIP signaling and RTP media from IPv6 clients.
  • Translate and forward that traffic to Twilio’s IPv4 SIP endpoints.
  • Bridge the protocol gap transparently, so your clients and Twilio can communicate seamlessly.

Key Benefits

  • Seamless interoperability between IPv6 and IPv4 networks.
  • Security and policy enforcement at the network edge.
  • Scalability for future network changes.

Tip: When selecting an SBC, ensure it supports dual-stack (IPv4/IPv6) operation and is compatible with your network and security requirements.

Alternative Solutions

  • NAT64 Gateways: These can translate IPv6 to IPv4, but Twilio does not currently provide a NAT64 gateway for SIP. If your infrastructure does not support dual-stack, deploying a dual-stack SBC is the recommended path.
  • Dual-Stack Clients: If possible, configure your SIP clients or infrastructure to support both IPv4 and IPv6. This may eliminate the need for protocol translation.

Implementation Steps

  1. Deploy a dual-stack SBC in your environment.
  2. Configure the SBC to accept IPv6 SIP and RTP traffic from your clients.
  3. Set up forwarding so the SBC sends SIP signaling and media to Twilio’s IPv4 SIP endpoints.
  4. Test your setup to ensure calls are established and media flows correctly.

 

Frequently Asked Questions

Will Twilio support IPv6 SIP endpoints in the future?

Twilio is always evaluating new features based on customer demand and industry trends. For now, only IPv4 is supported for SIP endpoints.

Can I use a cloud-based SBC?

Yes, many SBC vendors offer cloud or virtualized solutions that support dual-stack operation.

Does Twilio provide configuration guides for specific SBCs?

Twilio provides general SIP configuration guidance, but for detailed SBC setup, please refer to your SBC vendor’s documentation.

 

Conclusion

If you have questions about your specific network setup or need further guidance, please reach out to Twilio Support with details about your SIP client, network environment, and any error messages you encounter.

Below you will find references to useful documents:

Have more questions? Submit a request
We can’t wait to see what you build.
Powered by Zendesk