Skip to content

fix: correct EU SIP TCP framing and 403/404 FAQ in networking docs #1072

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dhruva-vapi wants to merge 1 commit into
base: main
Choose a base branch
from
+5 −5
Open

fix: correct EU SIP TCP framing and 403/404 FAQ in networking docs #1072

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions fern/advanced/sip/sip-networking.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ 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 | US | `sip.vapi.ai` | `44.229.228.186`, `44.238.177.138` | `5060` | UDP/TCP | 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` | `63.182.83.170` | `5061` | TLS | Bidirectional |
Expand All @@ -48,7 +48,7 @@ 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. |
| **5060** | UDP/TCP | Default SIP signalling. UDP and TCP are both supported in US and EU. |
| **5061** | TLS | SIP over TLS (SIPS) signalling. |

Use port **5060** unless your provider or security requirements mandate encrypted signalling. For TLS/SIPS in either region, use port **5061** with TLS.
Expand Down Expand Up @@ -102,7 +102,7 @@ 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 | US | `44.229.228.186`, `44.238.177.138` | Your SIP server | `5060` | UDP/TCP |
| 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 | `63.182.83.170` | Your SIP server | `5061` | TLS |
Expand All @@ -115,7 +115,7 @@ 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 | US | Your SIP server | `44.229.228.186`, `44.238.177.138` | `5060` | UDP/TCP |
| 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 | `63.182.83.170` | `5061` | TLS |
Expand All @@ -142,7 +142,7 @@ Allow these if your firewall restricts outbound connections:
Vapi supports TLS for SIP signalling on port 5061 in both US and EU regions. 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.
</Accordion>
<Accordion title="What do SIP 403 and 404 responses mean?">
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.
These are standard SIP response codes. A `403 Forbidden` usually means your request was refused, most often because IP allowlisting or authentication failed. A `404 Not Found` usually means the request could not be matched to an account or called number. If you receive a `403`, confirm that your region's signalling IP addresses are allowlisted. If you receive a `404`, confirm the called number is configured in Vapi.
</Accordion>
</AccordionGroup>

Expand Down
Loading