Skip to content

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

Open
dhruva-vapi wants to merge 1 commit into
mainfrom
dr/fix-eu-sip-tcp-and-403-404-docs
Open

fix: correct EU SIP TCP framing and 403/404 FAQ in networking docs#1072
dhruva-vapi wants to merge 1 commit into
mainfrom
dr/fix-eu-sip-tcp-and-403-404-docs

Conversation

@dhruva-vapi

@dhruva-vapi dhruva-vapi commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

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

  • fern check passes (0 errors, 5 pre-existing warnings).
  • No internal links or JSON examples changed.
  • Confirmed TCP/5060 is region-agnostic and that no X-Reason header is emitted, by checking the SIP infrastructure and backend code.

Copy link
Copy Markdown
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@github-actions

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants