No outbound calls to Twillio sip trunk

Status
Not open for further replies.

bigmat

Free User
Basic Certified
Joined
Oct 3, 2021
Messages
1
Reaction score
0
Hi,

I'm new with 3CX, and I need to replace an hosted call center. I want to do this with AWS EC2 vm, and Twillio trunk.

I create my trunk on Twillio interface, configure that with the guide (https://www.3cx.com/docs/twilio-elastic-sip-trunking/) that I found on 3Cx documentation. I can receve inbound call in my trunk (dtmf, 2 way voice is OK) but I cant make outbound calls. I check and recheck my configuration, all seems good

Couple of points:

  1. I disable the E164 option.
  2. my outboud rules is correctly created (check and double check...)
  3. 3cx version 16.0.8.9, hosted on Windows server
  4. Firewall all green checked and activated
  5. My trunk with Twillio is up
    1. Registrar: xyz-ca.pstn.twillio.com
    2. Outbound proxy: xyz-ca.pstn.twillio.com
    3. type of auth: do not require Ip based (and auth is ok)
    4. Defaut caller id: my trunk DID on Twillio (+1818614xxxx)
  6. I can make outbound call to another trunk I've configured (with changes on outbound rules... )

In activity log, I see this when I try to make outbound call: 10/03/2021 1:37:27 AM - : Failed to create outbound lines to call 18194255555

And the most interresting is when I capture the trafic during call:

1633227173062.png

Why the source and destination IP is localhost??? Is there an option that I missed somewhere else???


Thanks!

Bigmat
 
Might be good to put system in verbose to see what is going on or what outbound rule it is using.

Since twilio is IP based you shouldn't see authentication required and it is odd that it shows localhost. Also, twilio requires E.164 so the call should show [email protected]
 
What you are looking at is the internal communication of the PBX to probably a 3CX client. That is why you see local host and authentication requests.

The first step is to check your outbound rules and see if everything is ok there and try to simplify them for testing. For example add only the extension you are using in the call from extensions and your trunk in route and leave everything else empty for testing.
 
Dear Mr.Bigmat,

If you are using a FREE BASIC plan & Twillio is a part of it from the 3cx then it won't work in 98% cases nor you can get support neither. That's why I configured own VOIP paid plan settings on 3cx then was able to make the calls easily.

If Twillio really needs Outbound proxy & Authen Type then only entered otherwise leave it blank


DISABLED SRTP & set Transport Protocol as ANY + ADD / DEL the CODECs which approved by SIP provider, then try below outbound rule, if successful then try to change SRTP & Transport protocol but be sure that your SIP really authorized/work on this.

For Outbound calls, you should make the Outbound rules simply then it would work, as you made it already so here I'm re-writing which maybe re-gain you if you missed something:-
1. Calls to numbers starting with prefix
- 00

2. Calls from extension(s) - MENTION THE EXTENSION OR if more then add with comma BUT NO SPACE

3. Calls to Numbers with a length of - EXACT LENGTH, IF MOBILE NUMBER IS "0091 1234567890" = 14DIGITS SO MUST MENTION 14, IF DIALING LANDLINE NUMBER OR ANY OTHER COUNTRY WHICH MAYBE 12 OR 16 OR MORE THEN MAKE A SEPARATE OUTBOUND RULE FOR EACH AS one rule for one type of dialing. Each Outbound rule will auto-detect, don't worry.

4. Calls from extension group(s) -
leave it OR if you made DEFAULT group & Want to give the access to all then add the same group.

5. Make outbound calls on - In the Route 1 choose SIP name then choose 0 in Strip Digits, leave Prepend blank, choose Outbound Caller ID

Dial like this 0091 1234567890 where 00 triggers the OUTBOUND RULE & as an International call + total 14digit trigger the exact length for this rule.

Save it & try...

B.regd
Mayank Gupta
 
Status
Not open for further replies.

Forum statistics

Threads
111,993
Messages
590,178
Members
164,933
Latest member
bunthoeun.may