fix: correct EU SIP allowlist docs#1068
Merged
Merged
Conversation
Contributor
|
🌿 Preview your docs: https://vapi-preview-62ab032b-7e96-4d73-9652-249db5a82aa4.docs.buildwithfern.com |
Contributor
|
🌿 Preview your docs: https://vapi-preview-40f4d927-b761-476b-b7b9-3d9bf28dfaf5.docs.buildwithfern.com |
dhruva-vapi
force-pushed
the
docs/eu-sip-allowlist
branch
from
187c329 to
55cb900
Compare
Contributor
|
🌿 Preview your docs: https://vapi-preview-4a728c28-88f8-4ebc-affe-c3ef4402ae85.docs.buildwithfern.com |
noahraynor-vapi
approved these changes
Jun 12, 2026
roshan-vapi
reviewed
Jun 13, 2026
roshan-vapi
reviewed
Jun 13, 2026
3 tasks
dhruva-vapi
added a commit
that referenced
this pull request
Jun 14, 2026
…1072) ## Description Problem: After #1068 merged, a reviewer pointed out two inaccuracies in the SIP networking docs. The docs implied TCP on port 5060 is EU-only, and the 403/404 FAQ referenced an `X-Reason: Invalid credentials` response header that Vapi does not send. This PR fixes both so the SIP networking page is accurate. - Port `5060` now shows UDP/TCP for both US and EU. Both regions accept UDP and TCP, so the previous "EU only" framing could have led US customers to think TCP was unavailable to them. - The "What do SIP 403 and 404 responses mean?" FAQ no longer mentions the non-existent `X-Reason: Invalid credentials` header. It keeps a plain explanation of what 403 and 404 mean and what to check. Follow-up to #1068, addressing post-merge review comments from @roshan-vapi. ## Testing Steps - [x] `fern check` passes (0 errors, 5 pre-existing warnings). - [x] No internal links or JSON examples changed. - [x] Confirmed TCP/5060 is region-agnostic and that no `X-Reason` header is emitted, by checking the SIP infrastructure and backend code.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Problem: The SIP docs mixed US-only allowlist/TLS guidance with EU SIP setup, so EU customers could configure the wrong host, IP, or port.
This PR updates the SIP networking reference and provider setup guides to describe region-specific SIP signalling, EU TLS on
5061, and EU static RTP media.fern/advanced/sip/sip-networking.mdxwith EU TLS on port5061, EU RTP media on63.182.83.170, and the US dynamic-RTP caveat.fern/advanced/sip/sip-trunk.mdxandfern/advanced/sip/troubleshoot-sip-trunk-credential-errors.mdxso allowlist guidance is region-aware.Testing Steps
fern check-- passes with 0 errors and 5 existing warnings.git diff --check-- no whitespace errors.sip.eu.vapi.airesolves to63.182.83.170, and TLS on port5061succeeds.