From d6e2924e57ab31d564f80c9ca09fa3e7853c2630 Mon Sep 17 00:00:00 2001 From: Dhruva Reddy Date: Wed, 10 Jun 2026 15:00:30 -0700 Subject: [PATCH 1/2] fix: correct EU SIP allowlist docs --- fern/advanced/sip/sip-networking.mdx | 31 +++++++++++++--------------- 1 file changed, 14 insertions(+), 17 deletions(-) diff --git a/fern/advanced/sip/sip-networking.mdx b/fern/advanced/sip/sip-networking.mdx index bb7620852..d6b9ae985 100644 --- a/fern/advanced/sip/sip-networking.mdx +++ b/fern/advanced/sip/sip-networking.mdx @@ -25,21 +25,20 @@ The table below summarizes every IP address, port, and protocol you need to allo | Traffic type | Region | Hostname | IP addresses | Ports | Protocol | Direction | | --- | --- | --- | --- | --- | --- | --- | | SIP signalling | US | `sip.vapi.ai` | `44.229.228.186`, `44.238.177.138` | `5060` | UDP | Bidirectional | -| SIP signalling | EU | `sip.eu.vapi.ai` | `44.233.34.47`, `44.233.34.48` | `5060` | UDP | Bidirectional | +| SIP signalling | EU | `sip.eu.vapi.ai` | `63.182.83.170` | `5060` | UDP/TCP | Bidirectional | | SIP signalling (TLS) | US | `sip.vapi.ai` | `44.229.228.186`, `44.238.177.138` | `5061` | TLS | Bidirectional | -| SIP signalling (TLS) | EU | `sip.eu.vapi.ai` | `44.233.34.47`, `44.233.34.48` | `5061` | TLS | Bidirectional | | RTP media | All regions | N/A | No static IPs (dynamic) | `40000`-`60000` | UDP | Bidirectional | -Use your region's SIP hostname when configuring SIP URIs or SIP peers. If your firewall or SIP provider requires IP-based allowlisting, add the signalling IP addresses for your region explicitly. +Use your region's SIP hostname when configuring SIP URIs or SIP peers. If your firewall or SIP provider requires IP-based allowlisting, add the signalling IP addresses for your region explicitly. For EU TLS/SIPS requirements, contact support before allowlisting port `5061`. ## SIP signalling -Vapi's SIP infrastructure uses two static IP addresses for signalling traffic in each region: +Vapi's SIP infrastructure uses static IP addresses for signalling traffic in each region: | Region | Hostname | IP addresses | | --- | --- | --- | | US | `sip.vapi.ai` | `44.229.228.186/32`, `44.238.177.138/32` | -| EU | `sip.eu.vapi.ai` | `44.233.34.47/32`, `44.233.34.48/32` | +| EU | `sip.eu.vapi.ai` | `63.182.83.170/32` | These are the public IPs of Vapi's SBC (Session Border Controller) nodes. All SIP `INVITE`, `REGISTER`, `BYE`, and other signalling messages originate from and are received at the addresses for your region. @@ -47,17 +46,17 @@ These are the public IPs of Vapi's SBC (Session Border Controller) nodes. All SI | Port | Protocol | Use case | | --- | --- | --- | -| **5060** | UDP | Default SIP signalling | -| **5061** | TLS | SIP over TLS (SIPS) for encrypted signalling | +| **5060** | UDP/TCP | Default SIP signalling. EU traffic may use TCP on this port. | +| **5061** | TLS | SIP over TLS (SIPS) for US signalling. Contact support before using TLS/SIPS in the EU. | -Use port **5060** unless your provider or security requirements mandate encrypted signalling, in which case use port **5061** with TLS. +Use port **5060** unless your provider or security requirements mandate encrypted signalling. For US TLS/SIPS, use port **5061** with TLS. For EU TLS/SIPS requirements, contact support before allowlisting port `5061`. ### Hostnames and allowlisting Configure your SIP client or PBX to point to the hostname for your region. For firewall rules and carrier allowlists, use the static signalling IP addresses listed for your region. - Allowlist both IP addresses for your region explicitly. DNS A records may not match every static signalling IP that Vapi can use for carrier or firewall allowlisting. + Allowlist every IP address for your region explicitly. DNS A records may not match every static signalling IP that Vapi can use for carrier or firewall allowlisting. ## SIP media (RTP) @@ -86,7 +85,7 @@ Vapi uses **UDP ports 40000 through 60000** for RTP media traffic. ## Firewall rules -Configure your firewall to allow the following traffic. Both SIP signalling IP addresses for your region must be allowlisted, as Vapi may use either one for any given call. For RTP media, allow traffic on the full port range without IP restrictions since Vapi uses dynamic IPs for media. +Configure your firewall to allow the following traffic. Every SIP signalling IP address for your region must be allowlisted. For RTP media, allow traffic on the full port range without IP restrictions since Vapi uses dynamic IPs for media. ### Inbound rules (traffic from Vapi to your network) @@ -95,9 +94,8 @@ Allow these if your SIP provider or PBX needs to receive traffic from Vapi: | Rule | Region | Source IP | Destination | Port(s) | Protocol | | --- | --- | --- | --- | --- | --- | | SIP signalling | US | `44.229.228.186`, `44.238.177.138` | Your SIP server | `5060` | UDP | -| SIP signalling | EU | `44.233.34.47`, `44.233.34.48` | Your SIP server | `5060` | UDP | +| SIP signalling | EU | `63.182.83.170` | Your SIP server | `5060` | UDP/TCP | | SIP signalling (TLS) | US | `44.229.228.186`, `44.238.177.138` | Your SIP server | `5061` | TLS | -| SIP signalling (TLS) | EU | `44.233.34.47`, `44.233.34.48` | Your SIP server | `5061` | TLS | | RTP media | All regions | Any (dynamic) | Your media server | `40000`-`60000` | UDP | ### Outbound rules (traffic from your network to Vapi) @@ -107,20 +105,19 @@ Allow these if your firewall restricts outbound connections: | Rule | Region | Source | Destination IP | Port(s) | Protocol | | --- | --- | --- | --- | --- | --- | | SIP signalling | US | Your SIP server | `44.229.228.186`, `44.238.177.138` | `5060` | UDP | -| SIP signalling | EU | Your SIP server | `44.233.34.47`, `44.233.34.48` | `5060` | UDP | +| SIP signalling | EU | Your SIP server | `63.182.83.170` | `5060` | UDP/TCP | | SIP signalling (TLS) | US | Your SIP server | `44.229.228.186`, `44.238.177.138` | `5061` | TLS | -| SIP signalling (TLS) | EU | Your SIP server | `44.233.34.47`, `44.233.34.48` | `5061` | TLS | | RTP media | All regions | Your media server | Any (dynamic) | `40000`-`60000` | UDP | - Both SIP signalling IP addresses for your region must be allowed in your firewall rules. Vapi may use either address for signalling on any given call. Missing one address can cause intermittent call failures. For RTP media, since Vapi uses dynamic IPs, configure your firewall to allow the full port range (`40000`-`60000` UDP) without restricting by source or destination IP. + Allow every SIP signalling IP address for your region in your firewall rules. For RTP media, since Vapi uses dynamic IPs, configure your firewall to allow the full port range (`40000`-`60000` UDP) without restricting by source or destination IP. Contact support if you need a stricter media firewall policy. ## FAQ - Use your region's hostname for SIP URI and peer configuration. For IP-based firewall rules, add both static signalling IP addresses for your region explicitly. DNS-based firewall rules depend on TTL and caching behavior, and DNS A records may not match every static signalling IP that Vapi can use for allowlisting. RTP media uses dynamic IPs that cannot be resolved via DNS. + Use your region's hostname for SIP URI and peer configuration. For IP-based firewall rules, add the static signalling IP addresses for your region explicitly. DNS-based firewall rules depend on TTL and caching behavior, and DNS A records may not match every static signalling IP that Vapi can use for allowlisting. RTP media uses dynamic IPs that cannot be resolved via DNS. Yes. Vapi's RTP stack dynamically allocates ports within this range for each call. You cannot predict which specific port a given call will use, so the entire range must be open for reliable media flow. @@ -129,7 +126,7 @@ Allow these if your firewall restricts outbound connections: No. Vapi's SIP signalling uses static IP addresses for each region, but RTP media does not use static IP addresses. Media source IPs are dynamically assigned and may vary between calls. - Vapi supports TLS for SIP signalling on port 5061. For encrypted media (SRTP), configure your SIP trunk gateway with the `tls/srtp` outbound protocol option. See the [gateway configuration reference](/advanced/sip/troubleshoot-sip-trunk-credential-errors#gateway-configuration-reference) for details. + Vapi supports TLS for US SIP signalling on port 5061. For EU TLS/SIPS requirements, contact support before allowlisting port `5061`. For encrypted media (SRTP), configure your SIP trunk gateway with the `tls/srtp` outbound protocol option. See the [gateway configuration reference](/advanced/sip/troubleshoot-sip-trunk-credential-errors#gateway-configuration-reference) for details. From 187c329469ef70a6269c5a5d52ae11520367d92d Mon Sep 17 00:00:00 2001 From: Dhruva Reddy Date: Wed, 10 Jun 2026 15:58:51 -0700 Subject: [PATCH 2/2] docs: clarify EU SIP and RTP allowlisting --- fern/advanced/sip/sip-networking.mdx | 45 ++++++++++++++++++---------- 1 file changed, 29 insertions(+), 16 deletions(-) diff --git a/fern/advanced/sip/sip-networking.mdx b/fern/advanced/sip/sip-networking.mdx index d6b9ae985..cbf10b7b1 100644 --- a/fern/advanced/sip/sip-networking.mdx +++ b/fern/advanced/sip/sip-networking.mdx @@ -11,7 +11,7 @@ When you integrate a SIP trunk with Vapi, your firewall and network infrastructu **In this reference, you'll find:** - All IP addresses and ports used by Vapi for SIP signalling -- RTP media port ranges, directionality details, and dynamic IP behavior +- RTP media port ranges, directionality details, and regional IP behavior - Recommended firewall rules for inbound and outbound traffic @@ -27,9 +27,10 @@ The table below summarizes every IP address, port, and protocol you need to allo | SIP signalling | US | `sip.vapi.ai` | `44.229.228.186`, `44.238.177.138` | `5060` | UDP | Bidirectional | | SIP signalling | EU | `sip.eu.vapi.ai` | `63.182.83.170` | `5060` | UDP/TCP | Bidirectional | | SIP signalling (TLS) | US | `sip.vapi.ai` | `44.229.228.186`, `44.238.177.138` | `5061` | TLS | Bidirectional | -| RTP media | All regions | N/A | No static IPs (dynamic) | `40000`-`60000` | UDP | Bidirectional | +| RTP media | US | N/A | No static IPs (dynamic) | `40000`-`60000` | UDP | Bidirectional | +| RTP media | EU | `sip.eu.vapi.ai` | `63.182.83.170` | `40000`-`60000` | UDP | Bidirectional | -Use your region's SIP hostname when configuring SIP URIs or SIP peers. If your firewall or SIP provider requires IP-based allowlisting, add the signalling IP addresses for your region explicitly. For EU TLS/SIPS requirements, contact support before allowlisting port `5061`. +Use your region's SIP hostname when configuring SIP URIs or SIP peers. If your firewall or SIP provider requires IP-based allowlisting, add the signalling and media IP addresses for your region explicitly. EU SIP over TLS on port `5061` is not currently configured. ## SIP signalling @@ -47,24 +48,31 @@ These are the public IPs of Vapi's SBC (Session Border Controller) nodes. All SI | Port | Protocol | Use case | | --- | --- | --- | | **5060** | UDP/TCP | Default SIP signalling. EU traffic may use TCP on this port. | -| **5061** | TLS | SIP over TLS (SIPS) for US signalling. Contact support before using TLS/SIPS in the EU. | +| **5061** | TLS | SIP over TLS (SIPS) for US signalling only. EU SIP over TLS is not currently configured. | -Use port **5060** unless your provider or security requirements mandate encrypted signalling. For US TLS/SIPS, use port **5061** with TLS. For EU TLS/SIPS requirements, contact support before allowlisting port `5061`. +Use port **5060** unless your provider or security requirements mandate encrypted signalling. For US TLS/SIPS, use port **5061** with TLS. Do not allowlist EU port `5061` for SIP signalling unless Vapi confirms TLS support for your deployment. ### Hostnames and allowlisting -Configure your SIP client or PBX to point to the hostname for your region. For firewall rules and carrier allowlists, use the static signalling IP addresses listed for your region. +Configure your SIP client or PBX to point to the hostname for your region. For firewall rules and carrier allowlists, use the static IP addresses listed for your region. In the EU, `sip.eu.vapi.ai` currently resolves to `63.182.83.170`. - Allowlist every IP address for your region explicitly. DNS A records may not match every static signalling IP that Vapi can use for carrier or firewall allowlisting. + Allowlist every IP address for your region explicitly. DNS A records may not match every static IP that Vapi can use for carrier or firewall allowlisting. + + Do not use `sip-web.eu.vapi.ai` for SIP signalling or media. It is used for portal and API traffic and resolves through Cloudflare/WAF, not to Vapi's SIP infrastructure. + + ## SIP media (RTP) -Vapi does not use static IP addresses for RTP media (voice audio). The media source IP addresses are dynamically assigned and may change between calls. Because of this, you should not rely on allowlisting specific IPs for RTP media traffic. +RTP media IP behavior depends on your region: + +- **US:** Vapi does not use static IP addresses for RTP media. Media source IPs are dynamically assigned and may change between calls. +- **EU:** RTP media uses the same static public IP as SIP signalling: `63.182.83.170`. - Unlike SIP signalling, RTP media does **not** originate from a fixed set of IP addresses. Your firewall rules for RTP media should allow traffic based on port ranges rather than specific source IPs. + For US RTP media, allow traffic based on port ranges rather than specific source IPs. For EU RTP media, allowlist `63.182.83.170` with the full UDP port range. ### Port range @@ -85,7 +93,7 @@ Vapi uses **UDP ports 40000 through 60000** for RTP media traffic. ## Firewall rules -Configure your firewall to allow the following traffic. Every SIP signalling IP address for your region must be allowlisted. For RTP media, allow traffic on the full port range without IP restrictions since Vapi uses dynamic IPs for media. +Configure your firewall to allow the following traffic. Every SIP signalling IP address for your region must be allowlisted. For RTP media, allow traffic on the full port range. US media uses dynamic IPs; EU media uses `63.182.83.170`. ### Inbound rules (traffic from Vapi to your network) @@ -96,7 +104,8 @@ Allow these if your SIP provider or PBX needs to receive traffic from Vapi: | SIP signalling | US | `44.229.228.186`, `44.238.177.138` | Your SIP server | `5060` | UDP | | SIP signalling | EU | `63.182.83.170` | Your SIP server | `5060` | UDP/TCP | | SIP signalling (TLS) | US | `44.229.228.186`, `44.238.177.138` | Your SIP server | `5061` | TLS | -| RTP media | All regions | Any (dynamic) | Your media server | `40000`-`60000` | UDP | +| RTP media | US | Any (dynamic) | Your media server | `40000`-`60000` | UDP | +| RTP media | EU | `63.182.83.170` | Your media server | `40000`-`60000` | UDP | ### Outbound rules (traffic from your network to Vapi) @@ -107,26 +116,30 @@ Allow these if your firewall restricts outbound connections: | SIP signalling | US | Your SIP server | `44.229.228.186`, `44.238.177.138` | `5060` | UDP | | SIP signalling | EU | Your SIP server | `63.182.83.170` | `5060` | UDP/TCP | | SIP signalling (TLS) | US | Your SIP server | `44.229.228.186`, `44.238.177.138` | `5061` | TLS | -| RTP media | All regions | Your media server | Any (dynamic) | `40000`-`60000` | UDP | +| RTP media | US | Your media server | Any (dynamic) | `40000`-`60000` | UDP | +| RTP media | EU | Your media server | `63.182.83.170` | `40000`-`60000` | UDP | - Allow every SIP signalling IP address for your region in your firewall rules. For RTP media, since Vapi uses dynamic IPs, configure your firewall to allow the full port range (`40000`-`60000` UDP) without restricting by source or destination IP. Contact support if you need a stricter media firewall policy. + Allow every SIP signalling IP address for your region in your firewall rules. For RTP media, configure your firewall to allow the full port range (`40000`-`60000` UDP). US RTP media uses dynamic IPs. EU RTP media uses `63.182.83.170`. Contact support if you need a stricter media firewall policy. ## FAQ - Use your region's hostname for SIP URI and peer configuration. For IP-based firewall rules, add the static signalling IP addresses for your region explicitly. DNS-based firewall rules depend on TTL and caching behavior, and DNS A records may not match every static signalling IP that Vapi can use for allowlisting. RTP media uses dynamic IPs that cannot be resolved via DNS. + Use your region's hostname for SIP URI and peer configuration. For IP-based firewall rules, add the static IP addresses for your region explicitly. DNS-based firewall rules depend on TTL and caching behavior, and DNS A records may not match every static IP that Vapi can use for allowlisting. US RTP media uses dynamic IPs that cannot be resolved via DNS. EU RTP media uses `63.182.83.170`. Yes. Vapi's RTP stack dynamically allocates ports within this range for each call. You cannot predict which specific port a given call will use, so the entire range must be open for reliable media flow. - No. Vapi's SIP signalling uses static IP addresses for each region, but RTP media does not use static IP addresses. Media source IPs are dynamically assigned and may vary between calls. + It depends on the region. In the EU, SIP signalling and RTP media both use `63.182.83.170`. In the US, SIP signalling uses static IP addresses, but RTP media source IPs are dynamically assigned and may vary between calls. - Vapi supports TLS for US SIP signalling on port 5061. For EU TLS/SIPS requirements, contact support before allowlisting port `5061`. For encrypted media (SRTP), configure your SIP trunk gateway with the `tls/srtp` outbound protocol option. See the [gateway configuration reference](/advanced/sip/troubleshoot-sip-trunk-credential-errors#gateway-configuration-reference) for details. + Vapi supports TLS for US SIP signalling on port 5061. EU SIP over TLS on port `5061` is not currently configured. For encrypted media (SRTP), configure your SIP trunk gateway with the `tls/srtp` outbound protocol option. See the [gateway configuration reference](/advanced/sip/troubleshoot-sip-trunk-credential-errors#gateway-configuration-reference) for details. + + + A `403 Forbidden` response with `X-Reason: Invalid credentials` usually means IP allowlisting or authentication failed. A `404 Not Found` response usually means Vapi could not find a matching account or called number for the request.