> ## Documentation Index
> Fetch the complete documentation index at: https://plivo.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Firewall & Network Configuration

> Plivo IP ranges and ports to whitelist on your firewall for SIP signaling, RTP media, and callbacks

<Info title="TL;DR">
  * **What:** IP address ranges and ports to whitelist on your firewall so Plivo voice traffic (SIP signaling, RTP media, callbacks) can reach your infrastructure
  * **Direction:** Outbound (Plivo → your servers). You whitelist Plivo's IPs on your firewall
  * **Key ports:** SIP signaling on 5060/5061/5080; RTP media on 16384-32768 (UDP)
  * **Regions:** IP ranges vary by region (San Jose, Ashburn, Frankfurt, Sao Paulo, Sydney, Singapore, Mumbai)
  * **API/SDK:** No static IPs. Whitelist domains instead (`api.plivo.com`, `client.plivo.com`)
  * **Note:** This page is about allowing Plivo traffic through your firewall. To restrict which IPs can call Plivo's API, see [API Access Control](/account/concepts/ip-whitelisting/). For messaging callback IPs, see [Messaging: Firewall & Network Configuration](/messaging/concepts/firewall-network-configuration/)
</Info>

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](/voice/concepts/firewall-network-configuration/#subscription-section) 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 & app.plivo.com) | 52.9.254.123/32<br />52.9.254.127/32<br />216.120.187.64/32<br />216.120.187.65/32<br />216.120.187.66/32<br />216.120.187.67/32<br />216.120.187.68/32<br />204.89.148.64/32<br />204.89.148.65/32<br />204.89.148.66/32<br />204.89.148.67/32<br />204.89.148.68/32 | 5060, 5080 (UDP)<br />5060, 5061, 5063, 5080, 443 (TCP) |
| Mobile phones (mobile.phone.plivo.com)       | 2600:1f1c:4ad:2f02:ac95:55cc:9a28:3891/128                                                                                                                                                                                                                            | 5060, 5080 (UDP)<br />5060, 5061, 5063, 5080, 443 (TCP) |
| External SIP endpoints                       | 13.52.9.4/32<br />13.52.9.5/32<br />18.214.109.132/32<br />18.214.109.133/32<br />                                                                                                                                                                                    | 5060 (UDP)                                              |

## RTP media servers

<table>
  <tbody>
    <tr>
      <td>Regions</td>
      <td>IP Addresses</td>
      <td>Ports</td>
    </tr>

    <tr>
      <td>San Jose, California, USA</td>
      <td>216.120.187.64/26<br />216.120.187.128/26<br />216.120.187.192/27</td>
      <td>16384 - 32768 (UDP)<br />10000 - 30000 (UDP/TCP)</td>
    </tr>

    <tr>
      <td>Ashburn, Virginia, USA</td>
      <td>204.89.148.64/26<br />204.89.148.128/26<br />204.89.148.192/27</td>
      <td>16384 - 32768 (UDP)<br />10000 - 30000 (UDP/TCP)</td>
    </tr>

    <tr>
      <td>Frankfurt, Germany</td>
      <td>3.120.121.128/26</td>
      <td>16384 - 32768 (UDP)<br />10000 - 30000 (UDP/TCP)</td>
    </tr>

    <tr>
      <td>São Paulo, Brazil</td>
      <td>54.233.191.0/27<br />18.228.70.64/26</td>
      <td>16384 - 32768 (UDP)<br />10000 - 30000 (UDP/TCP)</td>
    </tr>

    <tr>
      <td>Sydney, Australia</td>
      <td>13.238.202.192/26</td>
      <td>16384 - 32768 (UDP)<br />10000 - 30000 (UDP/TCP)</td>
    </tr>

    <tr>
      <td>Singapore</td>
      <td>52.220.63.176/28<br />204.89.149.64/27<br />204.89.149.128/27</td>
      <td>16384 - 32768 (UDP)<br />10000 - 30000 (UDP/TCP)</td>
    </tr>

    <tr>
      <td>Mumbai, India</td>
      <td>204.89.151.64/26<br />204.89.151.128/25</td>
      <td>16384 - 32768 (UDP)<br />10000 - 30000 (UDP/TCP)</td>
    </tr>
  </tbody>
</table>

## 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.

<table>
  <tbody>
    <tr>
      <td>Regions</td>
      <td>IP Addresses</td>
    </tr>

    <tr>
      <td>San Jose, California, USA</td>
      <td>13.56.175.187/32<br />13.57.139.231/32</td>
    </tr>

    <tr>
      <td>Ashburn, Virginia, USA</td>
      <td>18.211.55.148/32<br />18.211.27.222/32<br />204.89.148.70/32</td>
    </tr>

    <tr>
      <td>Frankfurt, Germany</td>
      <td>3.120.80.110/32<br />35.157.59.132/32</td>
    </tr>

    <tr>
      <td>São Paulo, Brazil</td>
      <td>18.228.96.85/32<br />18.228.143.199/32</td>
    </tr>

    <tr>
      <td>Sydney, Australia</td>
      <td>13.238.88.135/32<br />52.62.46.143/32</td>
    </tr>

    <tr>
      <td>Singapore</td>
      <td>52.220.250.27/32<br />18.136.128.252/32</td>
    </tr>

    <tr>
      <td>Mumbai, India</td>
      <td>3.7.4.233/32<br />3.7.220.174/32</td>
    </tr>
  </tbody>
</table>

***

## Related

* [API Access Control (IP Whitelisting)](/account/concepts/ip-whitelisting/) — Restrict which IPs can make API requests to your Plivo account
* [Messaging: Firewall & Network Configuration](/messaging/concepts/firewall-network-configuration/) — Plivo IP ranges for messaging callbacks