Solved Can't Get Twilio Outbound Connections Working

[Jon Edmiston]

I've spent hours reading through the guides and forum posts try to get Twilio outbound calls to work. Inbound calls work fine (two way voice). I have gone through the guide below several times:

https://www.3cx.com/docs/twilio-elastic-sip-trunking/

And read through all the forum posts with similar issues. I've done the firewall tests and they all pass. The error I get is:

Call or Registration to +1602819XXXX@(Ln.10000@Twilio) has failed. 54.172.60.1 replied: 504 Request timeout; from IP:54.172.60.1:5060

(XXXX - is redacted)

I'm not sure if this network setting is correct. This was the default after installing from the PBX Express.

 

[YiannisH_3CX]

Hello @Jon Edmiston

If the highlighted IP is your local IP then that is correct. If not then something went wrong during the installation.
If you are using the default 3CX provided template for Twilio and you have followed the guide then outbound calls should work. Pay special attention to the outbound rules so that the number is formatted correctly and that your domain is listed correctly under the Origination SIP URI.

 

[Jon Edmiston]

I have confirmed the Origination SIP URI. Here are my outbound rules.

 

[YiannisH_3CX]

Your outbound rules look correct so the next step is to tun a wireshark capture on the PBX machine and capture an outbound call attempt. This will let you know what the PBX is sending is sending and the providers reply.

 

[Jon Edmiston]

After digging through the Twilio logs it appears you need to set the caller id on the extension to be the phone number digits.

 

[YiannisH_3CX]

After applying this change is the issue now resolved?

 

[Jon Edmiston]

Yes, the change above fixed the issue.

 

[cobaltit]

Outbound Caller ID
For the operation of the trunks, the outbound caller ID of the trunk must be present. This will ensure that a call can still be placed in the event that no outbound caller ID is set for the extension.


Note: Twilio does not support Clip No Screening Calls (sending a number as the Caller ID which is not associated with the trunk). Individual caller IDs per extension shall be set within the extension itself.

So I assume you had already set the caller-id at the trunk level then and that wasn't working?

 

[YiannisH_3CX]

Glad to see the issue has been resolved.