Skip to content

Rewrite the firewall guide for SIP endpoint operators - #948

Draft
hey-august wants to merge 1 commit into
mainfrom
august-20261111-firewall-config
Draft

hey-august wants to merge 1 commit into
mainfrom
august-20261111-firewall-config

Conversation

@hey-august

Copy link
Copy Markdown
Collaborator

Summary

  • Rewrites "Allow SignalWire IPs through your firewall" as a how-to for SIP endpoint operators (PBX, session border controller, hosted SIP provider with an IP access list). Same slug; new title "Allow SignalWire SIP traffic through your firewall".
  • The guide now covers who needs it, signaling versus media, looking up the sip.signalwire.com A records, a re-runnable ipset sync script with a cron entry, hosted providers, and a verification section.
  • Drops the relay.signalwire.com and firewall.signalwire.com lookups. Both resolve to a single load balancer address, and nothing documents either as a source of traffic to customers.
  • Vapi guide: removes the 15 hardcoded IPs. The trunk-creation command builds the gateway list from a lookup at run time.
  • FusionPBX guide: trims "Access Control" and "fail2ban" to short paragraphs that link to the firewall guide.
  • Fax callback guide: replaces the "run a script to allow IPs" advice with signature verification and basic auth.

Closes #372. The issue proposed removing the page; this keeps and expands it, as discussed there.

Notes for reviewers

Draft until engineering confirms the claims below. Each is stated as fact in the pages.

  1. Complete list. The sip.signalwire.com A records are every address SignalWire sends SIP calls from, in every region, and one lookup returns all of them. The sync script replaces the whole set on each run, so a partial DNS answer would drop live addresses.
  2. Media. Call audio comes from unpredictable addresses, so media ports must be open to any source. Carried over from the old page's warning.
  3. Rotation. A new address the firewall doesn't know yet causes intermittent dropped calls. This is an inference. Is a new address published in DNS before it carries calls, and by how long?
  4. Refresh interval. The cron example runs hourly. That number is a placeholder pending the answer to 3.
  5. IPv4 only. The lookup and script handle A records only; the name has no AAAA records today.
  6. firewall.signalwire.com. Confirm no SIP customer needs it.
  7. 157.175.131.128. It was in the Vapi guide's list but is not in the current lookup, which returns 14 addresses. Is it retired?

Vapi guide, unverified against Vapi:

  • The warning says Vapi rejects calls from an address that isn't on the trunk.
  • It says to update the trunk's gateways without showing the call, because the update request wasn't verified.

Verification

  • yarn fern-md-check passes.
  • yarn fern-check reports only the redirects check, which needs FERN_TOKEN locally.
  • The sync script passes bash -n. It has not been run on a host with ipset and iptables.
  • The Vapi gateway construction was checked against simulated lookup output and produces valid JSON. It has not been run against Vapi's API or with a live dig.
  • Fax callbacks carrying X-SignalWire-Signature was confirmed against backend source.
  • Anchors checked by hand: #look-up-the-current-addresses, #keep-your-firewall-in-sync, #verify-webhook-signature.

Preview

  • /docs/platform/allow-signalwire-ips-through-your-firewall
  • /docs/platform/ai/vapi
  • /docs/platform/ FusionPBX guide (Platform → Integrations)
  • /docs/compatibility-api/guides/callback-for-inbound-fax

Scope the guide to allowing SignalWire SIP signaling, sourced from the
sip.signalwire.com A records, and replace the append-only iptables
one-liners with a re-runnable ipset sync script. Drop the
relay.signalwire.com and firewall.signalwire.com lookups.

Remove the hardcoded IP list from the Vapi guide in favor of a lookup at
run time, trim the FusionPBX access control advice to links, and point
the fax callback guide at signature verification and basic auth.

Closes #372
@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.

Rewrite: SignalWire Firewall Config adjustment/removal

1 participant