Skip to content

Fix inbound trunk calls rejected as external realm#145

Closed
yeoleobun wants to merge 1 commit intorestsend:mainfrom
yeoleobun:feature/issue-129-inbound-trunk-direction
Closed

Fix inbound trunk calls rejected as external realm#145
yeoleobun wants to merge 1 commit intorestsend:mainfrom
yeoleobun:feature/issue-129-inbound-trunk-direction

Conversation

@yeoleobun
Copy link
Collaborator

Fixes inbound trunk call direction detection when both caller and callee hosts appear external.

Changes included:

  • In src/proxy/call.rs, treat (caller_is_local=false, callee_is_local=false) as inbound when is_from_trunk is true
  • Avoid rejecting valid trunk-originated INVITEs with 403 in this scenario

Ref: #129

Trunk providers like Telnyx use internal IPs in the To header
(e.g. sip:DID@10.13.245.184 instead of sip:DID@our-ip). This caused
both caller and callee to appear external, triggering a 403 Forbidden.
When a call arrives from a recognized trunk, treat it as inbound
regardless of the To header's host.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@shenjinti
Copy link
Contributor

fixed in be7b278

@shenjinti shenjinti closed this Feb 27, 2026
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.

3 participants