Skip to content

fix: clarify hostname vs IP requirements for SIP trunk gateways#995

Open
sahilsuman933 wants to merge 1 commit into
mainfrom
tasker/VAP-12899-fix-sip-hostname-docs
Open

fix: clarify hostname vs IP requirements for SIP trunk gateways#995
sahilsuman933 wants to merge 1 commit into
mainfrom
tasker/VAP-12899-fix-sip-hostname-docs

Conversation

@sahilsuman933

@sahilsuman933 sahilsuman933 commented Mar 25, 2026

Copy link
Copy Markdown
Contributor

Description

  • Clarify that hostnames ARE supported for outbound-only SIP gateways (inboundEnabled: false), but NOT for inbound-enabled gateways
  • Update the "Using a hostname instead of an IP address" section with a new "How to check" subsection explaining the distinction between inbound and outbound hostname support
  • Add a <Note> component summarizing hostname support rules
  • Update the gateway configuration reference table's ip field description to reflect the nuanced hostname/IP behavior
  • Resolves VAP-12899

Testing Steps

  • Run the app locally using fern docs dev or navigate to preview deployment
  • Ensure that the changed pages and code snippets work
@sahilsuman933 @claude
fix: clarify hostname vs IP requirements for SIP trunk gateways
2e71cab 
Hostnames are supported for outbound-only SIP gateways but NOT for
inbound-enabled gateways. The previous docs incorrectly implied
hostnames never work. Updated the troubleshooting guide and gateway
config reference to accurately describe when hostnames are accepted.

VAP-12899

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@ghost ghost added the tasked-to-tasker label Mar 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tasked-to-tasker

1 participant

@sahilsuman933