IP address whitelisting
To ensure that your communication infrastructure doesn’t block communication with Plivo, we encourage you to whitelist these IP address ranges and ports on your firewall for SIP signaling and RTP media traffic.
Subscribe to be notified of any updates regarding IP address changes via email or RSS feed.
SIP signaling
| Type | IP Addresses | Ports |
| SIP phones (phone.plivo.com) | 52.9.254.123/32 52.9.254.127/32 216.120.187.64/32 216.120.187.65/32 216.120.187.66/32 216.120.187.67/32 216.120.187.68/32 204.89.148.64/32 204.89.148.65/32 204.89.148.66/32 204.89.148.67/32 204.89.148.68/32 3.120.121.128/26 13.238.202.192/26 18.136.1.128/26 18.215.142.0/26 18.228.70.64/26 |
5060, 5080 (UDP) 5060, 5061, 5063, 5080, 443 (TCP) |
| Mobile phones (mobile.phone.plivo.com) | 2600:1f1c:4ad:2f02:ac95:55cc:9a28:3891/128 | 5060, 5080 (UDP) 5060, 5061, 5063, 5080, 443 (TCP) |
| External SIP endpoints | 107.20.176.37 184.169.138.133 107.20.251.237 54.215.5.82 13.52.9.4 13.52.9.5 18.214.109.132 18.214.109.133 184.72.218.254 204.89.148.132 204.89.148.133 204.89.148.134 204.89.148.135 216.120.187.132 216.120.187.133 216.120.187.134 216.120.187.135 |
5060 (UDP) |
| app.plivo.com | 52.9.254.123 52.9.254.127 216.120.187.64/32 216.120.187.65/32 216.120.187.66/32 216.120.187.67/32 216.120.187.68/32 204.89.148.64/32 204.89.148.65/32 204.89.148.66/32 204.89.148.67/32 204.89.148.68/32 |
- |
RTP media servers
| Regions | IP Addresses | Ports |
| San Jose, California, USA | 52.9.254.64/26 216.120.187.64/26 216.120.187.192/27 13.52.9.0/25 216.120.187.128/26 |
16384 - 32768 (UDP) 10000 - 30000 (UDP/TCP) |
| Ashburn, Virginia, USA | 3.93.158.128/25 52.205.63.192/26 204.89.148.64/26 204.89.148.192/27 18.214.109.128/25 18.215.142.0/26 204.89.148.128/26 |
16384 - 32768 (UDP) 10000 - 30000 (UDP/TCP) |
| Frankfurt, Germany | 52.58.255.224/27 52.59.63.224/27 3.120.121.128/26 |
16384 - 32768 (UDP) 10000 - 30000 (UDP/TCP) |
| São Paulo, Brazil | 54.233.255.192/27 54.233.191.0/27 18.228.70.64/26 |
16384 - 32768 (UDP) 10000 - 30000 (UDP/TCP) |
| Sydney, Australia | 52.65.191.160/27 52.65.127.160/27 13.238.202.192/26 |
16384 - 32768 (UDP) 10000 - 30000 (UDP/TCP) |
| Singapore | 52.220.63.128/26 18.136.1.128/26 204.89.149.64/27 204.89.149.128/27 |
16384 - 32768 (UDP) 10000 - 30000 (UDP/TCP) |
| Mumbai, India | 15.207.90.0/24 204.89.151.64/27 204.89.151.96/27 204.89.151.128/26 204.89.151.192/27 |
16384 - 32768 (UDP) 10000 - 30000 (UDP/TCP) |
API
Since we don’t support static IP address ranges for the API, you don’t need to whitelist IP addresses for Voice API communication. The domain to whitelist for Plivo APIs is api.plivo.com.
Browser SDK client and Call Insights
We don’t support static IP ranges for the Browser SDK client, Browser SDK fallback client, or Call Insights. You can whitelist their domains.
- client.plivo.com
- client-fb.plivo.com
- insights.plivo.com
STUN servers for Browser SDK
The Plivo Browser SDK utilizes the listed STUN servers to initiate WebRTC media communications. The STUN server aids in identifying a device’s public IP address and port number for communication.
- stun:stun.plivo.com:3478
- stun:stun.l.google.com:19302
Protocol Whitelisting
When using the browser and mobile SDK for calls, please ensure the protocols - SIP, RTP, STUN, and DTLS are allowed by your firewall and ISP.
Callbacks from Plivo
Some Plivo APIs and XML elements support callback events. To make sure those callbacks are not blocked, allow traffic from these Plivo IP addresses to your web applications (ports defined by you; for HTTPS, default is 443, for HTTP it’s 80).
These IP addresses are NAT gateway IPs associated with our HTTP(s) OutProxy instance.
- 3.7.220.174/32
- 3.7.4.233/32
- 18.228.96.85/32
- 18.228.143.199/32
- 3.120.80.110/32
- 35.157.59.132/32
- 52.62.46.143/32
- 13.238.88.135/32
- 52.220.250.27/32
- 18.136.128.252/32
- 13.56.175.187/32
- 13.57.139.231/32
- 18.211.27.222/32
- 18.211.55.148/32
Subscribe to updates
