Solved New 3CX SIP Trunk Outbound Calling Fails

[Skavenger]

So I was following NetworkChuck and used the AWS stuff with 3CX to build a cloud phone system. I even set up the outbound calling to match what he did. It will not call out from my phone app at all. I receive inbound calls fine. Is there anyone willing to give me a hand with my settings? I made sure outbound/inbound calling was enabled and the outbound rules we set. Thanks in advance.

 

[Skavenger]

Note: Calling *777 and other extensions does work...just no true
outbound.

 

[Evolute IT]

Probably an issue with the outbound rules.

Screenshot of the rules please and what SIP provider are you using?

 

[Skavenger]

I am using Amazon Chime and see attached.

 

[Evolute IT]

I am using Amazon Chime and see attached.View attachment 22699

What number format are you dialing? The number sent to Amazon should be E164 (+ prefix), so your outbound rules must take the dialed numbers and format them accordingly.

https://www.3cx.com/docs/amazon-chime-voice-connector-sip-trunk/

 

[Skavenger]

So I have tried several iterations...from 1406XXXXXXX to just 406XXXXXX to just XXXXXXX...nothing works. I even added the +1 to Prepend. In all instances the App on my phone says Temp Unavailable and fast busy signal.

 

[Skavenger]

More info...

06/24/2021 6:34:52 PM - Call to T:Line:10000>>14065646205@[Dev:sip:[email protected];transport=TCP] from L:33.1[Extn:1000] failed, cause: Cause: 400 Invalid to number/INVITE from 99.77.253.10:5060

06/24/2021 6:34:52 PM - [CM503003]: Call(C:33): Call to <sip:[email protected]:0> has failed; Cause: 400 Invalid to number/INVITE from 99.77.253.10:5060

06/24/2021 6:34:33 PM - Call to T:Line:10000>>4065646205@[Dev:sip:[email protected];transport=TCP] from L:32.1[Extn:1000] failed, cause: Cause: 400 Invalid to number/INVITE from 99.77.253.10:5060

06/24/2021 6:34:33 PM - [CM503003]: Call(C:32): Call to <sip:[email protected]:0> has failed; Cause: 400 Invalid to number/INVITE from 99.77.253.10:5060

 

[Skavenger]

Got the rule figured but now getting "unauthorized" notices...

• Call or Registration to +14065646241@(Ln.10000@Amazon Chime Voice Connector) has failed. 99.77.253.1 replied: 401 Unauthorized; from IP:99.77.253.1:5060
  SIP Server ID: 12294 06/24/2021 7:03:34 PM
• Call or Registration to +14065646241@(Ln.10000@Amazon Chime Voice Connector) has failed. 99.77.253.1 replied: 401 Unauthorized; from IP:99.77.253.1:5060
  SIP Server ID: 12294 06/24/2021 7:02:14 PM

 

[YiannisH_3CX]

Hi @Skavenger

Start by going through our configuration guide and check if you missed something. https://www.3cx.com/docs/amazon-chime-voice-connector-sip-trunk/

I am sure it has to do something with the allowed list in the Chime configuration or the credentials you created for the trunk.

 

[Skavenger]

But would that still allow the *777 to work fine if the outbound allow was wrong? This is what is confusing me is the unauthorized part...cause inbound works and uses the same Creds?

 

[YiannisH_3CX]

But would that still allow the *777 to work fine if the outbound allow was wrong? This is what is confusing me is the unauthorized part...cause inbound works and uses the same Creds?

*777 is a call between the PBX and your phone. It never goes to the provider so the outbound rules do not matter. It is there to test that the communication between your device and the PBX is OK.
Chime is IP based so you do not need credentials for inbound calls. The credentials (if you chose to set them up) are used by Chime to identify outbound calls.

 

[Skavenger]

Ok thanks. I got it...I was so focused on the hardest things I missed the smallest. UserID is clearly case sensitive. It was spelled right but one letter was not capitalized. It is working now for outbound. Thanks for helping me get to the solution.

 

[YiannisH_3CX]

Glad I could assist and to see that everything now works