PBX GUI - VoIP Innovations SIP Trunk setup

Publisher

Sangoma

URL

https://sangomakb.atlassian.net/wiki/spaces/PG/pages/39158404

Published

2026-04-22

Updated

unknown

Accessed

2026-09-25

HTTP status

200

License

Sangoma documentation; all rights reserved; no-redistribution; short excerpts and locators only

Source notes citing this source

• Sangoma's IP-authenticated trunk example puts an outbound route of type Emergency first, ahead of the general outbound route. in context
• The Firewall configures trunk peers automatically from the trunk definition, but an IP-authenticated carrier that sends calls from addresses other than the trunk's SIP Server may need those addresses trusted explicitly. inferred in context
• In Sangoma's VoIP Innovations example, inbound DIDs arrive in E.164 format (for example +13607464343) by default, so Inbound Route DIDs must be entered in that format. in context
• Sangoma's IP-authenticated trunk guide adds each carrier origination IP as trusted on the Firewall module's Networks tab. in context
• For an IP-authenticated carrier, the PJSIP trunk's Match (Permit) field lists every carrier signalling IP address that inbound calls may come from. in context
• For an IP-authenticated carrier, Sangoma's guide sets the PJSIP trunk's Authentication to none and Registration to none and enters the carrier's server IP as SIP Server. in context

Cite this source record

APA

WarmTransfer. (2026, April 22). PBX GUI - VoIP Innovations SIP Trunk setup. WarmTransfer. https://warmtransfer.net/knowledge/sources/sangoma-pbxgui-voip-innovations-trunk

BibTeX

@misc{warmtransfer-sangoma-pbxgui-voip-innovations-trunk,
  title  = {PBX GUI - VoIP Innovations SIP Trunk setup},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/sangoma-pbxgui-voip-innovations-trunk},
  note   = {Sangoma, accessed 2026-09-25}
}