Twilio Configuration - Oubound fine, Inbound not working

[ksargeant]

I'm reaching out for help as I'm struggling to get my PBX inbound connection configured with Twilio. After putting in several hours of work, I'm feeling quite frustrated.

Here’s a quick overview of what I've accomplished so far:

• The PBX setup is fine, and I've successfully configured the gateway to Twilio.
• I can make outbound test calls and I’m able to pass/receive audio without any issues.

However, I'm having trouble establishing the inbound connection from Twilio to the PBX. Here’s what I've tried:

1. Whitelisted all IPs from Twilio as per Twilio's IP Addresses documentation and added them to my ACL.
2. Ensured that the + prefix is present in the phone numbers.
3. Set the Origination URIs to various formats:
   • sip:serverip
   • sip:serverip:5060
   • sip:serverip:5080
   • sip:customdomain
   • sip:customdomain:5060
   • sip:customdomain:5080
4. Enabled Sofia global siptrace, but there's nothing appearing in the logs.

If anyone has insights or suggestions on what I might be missing or additional steps I should take, I would greatly appreciate it!

Thank you in advance for your help!

--

EDIT:

So my uri for origination it talking to my PBX, but my PBX is kicking it out despite setting iptables for Twilio IPs and whitelisting access on my ACLs...

Where am I going wrong please?

 

[voipBull]

@ksargeant So you created a new ACL 'Twilio' to define the Twilio IP's instead of using the existing ACL 'providers', which is fine, but did you then updated the sofia profile you're using for your Twilio gateway to reflect this change?

 

[ksargeant]

@ksargeant So you created a new ACL 'Twilio' to define the Twilio IP's instead of using the existing ACL 'providers', which is fine, but did you then updated the sofia profile you're using for your Twilio gateway to reflect this change?

Oh what a simple thing to overlook. Thank you so much @voipBull after a reboot it allowed the call in.