Repository navigation
Rewrite the firewall guide for SIP endpoint operators - #948
Draft
hey-august wants to merge 1 commit into
Draft
hey-august wants to merge 1 commit into
hey-august wants to merge 1 commit into
Conversation
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
Contributor
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
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.
Summary
sip.signalwire.comA records, a re-runnableipsetsync script with a cron entry, hosted providers, and a verification section.relay.signalwire.comandfirewall.signalwire.comlookups. Both resolve to a single load balancer address, and nothing documents either as a source of traffic to customers.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.
sip.signalwire.comA 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.firewall.signalwire.com. Confirm no SIP customer needs it.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:
Verification
yarn fern-md-checkpasses.yarn fern-checkreports only the redirects check, which needsFERN_TOKENlocally.bash -n. It has not been run on a host withipsetandiptables.dig.X-SignalWire-Signaturewas confirmed against backend source.#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