- February 22, 2020 at 5:44 pm
With a VitalPBX PJSIP trunk configured against Twilio using Twilio Access Control List only (not Credential List), along with a PJSIP trunk Match list comprised of the Twilio signaling and media gateways, am able to make outbound calls okay, but none of the inbound works. The only way to get the inbound to work was to create a VitalPBX SIP trunk for each Twilio signaling gateway with VitalPBX settings such as:
Device for Outgoing Calls (Peer)
Local Username: twilio-va-0
Remote Host: 22.214.171.124
And the trunks will look like via ‘sip show peers’:
twilio-va-0 126.96.36.199 No No 5060 OK (1 ms) Twilio-VA-0
twilio-va-1 188.8.131.52 No No 5060 OK (1 ms) Twilio-VA-1
twilio-va-2 184.108.40.206 No No 5060 OK (1 ms) Twilio-VA-2
twilio-va-3 220.127.116.11 No No 5060 OK (1 ms) Twilio-VA-3
With this, cannot make outbound calls with the Twilio SIP trunks (‘Forbidden’).
So with this setup I create an Outbound Route to use the Twilio PJSIP trunk, and all of the inbound will be handled via the other SIP trunks configured to each and every Twilio signaling gateway.
It seems to me this should not be necessary. I don’t know the ramifications of having literally dozens of SIP registrations against Twilio – local system resources, getting blacklisted, or otherwise. This practice or method simply isn’t necessary on other competitive Asterisk-based products.
Has anyone been able to get inbound and outbound to work for a single VitalPBX PJSIP Twilio trunk using Twilio ACL and/or Credentials?0