Solved Twilio SIP Having Issues with Specific Area Codes

[TaylorStevens23]

We recently ported our numbers over to Twilio and everything is working but I am getting a forbidden error when calling numbers with the area codes 470 and 904. All other calls are working outbound but I am having an issue dialing these out. I get a declined 603 error from 3CX and 21211 error for invalid "to" number in Twilio. I can imagine what is causing this issue but when I look at my failed twilio call logs its over 90% to these area codes.

Does anyone have an idea on where to begin here?

• 3CX Version, Professional Annual 18.0 Update 5 (Build 415)
• Server OS, Debian 10
• Is the 3CX Server Hosted and where? On Prem
• Provisioning Method: Local
• Trunk Provider or Gateway Make/Mode: Twilio
• Are custom Phone Templates being used: YES

 

[YiannisH_3CX]

Hello @TaylorStevens23

The first step is to determine who is rejecting the calls so check the activity log (in verbose) or run a packet capture and check if the calls are leaving 3CX. From your description the calls are reaching Twilio since you see them in the logs in Twilio but it is always good to look.
If the calls are being rejected by 3CX then my best guess is that you are being blocked by country codes.
If the calls are being rejected by Twilio then contact Twilio and ask why. You will need to probably dial the numbers in a different number.

 

[TaylorStevens23]

Hello @TaylorStevens23

The first step is to determine who is rejecting the calls so check the activity log (in verbose) or run a packet capture and check if the calls are leaving 3CX. From your description the calls are reaching Twilio since you see them in the logs in Twilio but it is always good to look.
If the calls are being rejected by 3CX then my best guess is that you are being blocked by country codes.
If the calls are being rejected by Twilio then contact Twilio and ask why. You will need to probably dial the numbers in a different number.

I was able to figure the issue out with Twilio, thanks!

 

[YiannisH_3CX]

Glad to see the issue has been resolved