Skip to main content
  • What: IP ranges and ports to whitelist so Plivo voice traffic can reach your infrastructure.
  • When: Outbound flow (Plivo → your servers). API and SDK traffic has no static IPs — whitelist domains instead.
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.

​
Which IPs do I need?

​
SIP phones

​
External SIP endpoints

​
RTP media servers

​
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-fb.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.