Solved Twilio Sip Trunk Can't Make Outbound Calls

[August]

I've been reading various threads, followed the recommended instructions, and am no longer sure what else to do. I'm hosting my 3cx instance in Google Cloud and am using the Twilio Elastic SIP Trunk. I can receive inbound calls and have clear 2-way audio. However, whenever I try to make an outbound call I get this message in the Event log.

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

Any thoughts?

 

[craigreilly]

Did you use the Twilio template within 3cx setting up the Truck or Manual entry?

 

[August]

I used the Twilio template.

 

[craigreilly]

From Twilio:

The call fails with a ‘408 Request Timeout’ error or ‘504 Request Timeout’ error
Cause: Twilio is getting no response from your SIP infrastructure

• Confirm that the SIP URI you have configured for your Trunk’s Origination settings is correct.

1. ie: company.pstn.us2.twilio.com

• Check your firewall to be sure the Twilio IP addresses and ports are whitelisted

1. maybe not the issue since inbound is working. but - do ensure all RTP ports are open

• Check your PBX to be sure the Twilio IP addresses and ports are whitelisted

1. Little difficult to do sometimes since providers are using SRV Records.

Perhaps a Wireshark of an outbound call may give a little more information. Goto the Activity Tab. Click Capture. Make the Call. Wait until it fails, count to 10. Stop the Capture. Then open it in Wireshark.

Twilio is only my backup trunk but I just tested and it worked fine for outbound call.

 

[August]

Sorry for the late reply, and thank you for your tips. What it ended up being was a parsing error on Twilio's side. For some reason with 3CX I can only have a phone number in the caller ID field. In Asterisk, I am able to format a caller ID like "{name}"<{number}> and it handles that, but 3CX with Twilio wasn't quite so forgiving and would only work if I had just a number as the callerID.

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution.