Twilio Media Streams IP Address Pool update 2024
Twilio Changelog | Jul. 18, 2023
Media Streams IP Address Pool upcoming change
Effective November 16, 2023, Twilio will stop using the current IP pools for sending Media Streams’ media and will begin sending Media Streams media from a broad range of publicly available AWS IPs, so that we can improve the flexibility, reliability, and scalability of our Voice products.
We’re giving advance notice to allow customers time to update your network infrastructure and applications, but before November 16, 2023, you must:
Update your network infrastructure to stop allow list the old IP range used for U.S. Media Streams media:
- 34.203.254.0/24
3.235.111.128/25
IP Addresses for Elastic SIP Trunking Services
Public Connections - Global Media IP Range
The Public Connections Destination IP Ranges and Port Ranges are now identical across all locations:
| Secure Media (ICE/STUN/SRTP) Edge Locations | Protocol | Source IP | Source Port † | Destination IP Ranges | Destination Port Range |
|---|---|---|---|---|---|
| sydney (au1 ) sao-paulo (br1 ) dublin (ie1 ) frankfurt (de1 ) tokyo (jp1 ) singapore (sg1 ) ashburn (us1 ) umatilla (us2 ) roaming (gll ) | UDP | ANY | ANY | 168.86.128.0/18 | 10,000 - 60,000 |
† The SDK will select any available port from the ephemeral range. On most machines, this means the port range 1,024 to 65,535.
You MUST allow ALL of Twilio's following IP address ranges and ports on your firewall for SIP signaling traffic. This is important if you have Numbers in different edge locations and for resiliency purposes (e.g. if North America Virginia gateways are down, then North America Oregon gateways will be used). Twilio does not guarantee which edge location the media will egress from, without using the edge parameter since it can depend on which PSTN-SIP Gateway delivers the call to which Twilio edge location.
Please also note that these IP addresses are provided for firewall configuration purposes only and not all of these IP addresses will host active gateways at a given time. However, your SIP infrastructure should be prepared to accept signaling traffic from any of these IP addresses at all times. Customers should also avoid sending traffic directly to these IP addresses and instead use your configured termination Fully Qualified Domain Name (FQDN). Please see our SIP Trunking configuration docs for more details.
Comments
Post a Comment