Incoming calls work. Outbound calls get busy signal.

Status
Not open for further replies.

yqhdmon

New User
Joined
Oct 25, 2022
Messages
7
Reaction score
0
I read through a few thread and could find no solution.
I went through setup but was too clear about my Authentication ID (aka SIP User ID) so I have been trying a few different things and nothing works. Thanks in advance for your help.
The below is from my activity log:

0806@[Dev:sip:[email protected];transport=TCP] from L:32.1[Extn:1000] failed, cause: Cause: 403 Forbidden/INVITE from 3.80.16.127:5060

So I know something on AWS side is not allowing it to pass through, or something like that. I am no expert, first go at this with 99 percent success with much more to do and learn if I can get past this patch.
 
Yes. I get lost here in this article...
  1. Enter SIP Trunk ID and Password
 
OK -- so I figure that out but still getting dial tone and Chime still not letting my calls through so I still cannot dial out.
I even changed the IP address and nothing.
 
Dial-tone comes from a local device, nothing to do with your SIP provider. My first two suspects would be, the dialed number format you are sending, or, possibly the caller ID you are sending. Confirm that both are in a format that your provider accepts.

Checking the 3CX Activity Log, in Verbose, should provide some clues.
 
Last edited:
I check and it shows no smoking gun but to say Reason: Forbidden.
AWS support says same thing as you, so I made sure cid number is E.164 compliant.
I check the IP and make sure that is correct also... still getting busy signal when trying to dial out from all extensions.
 
...and you've confirmed that you are not sending a "non-compliant" caller ID.
 
Absolutely. I have checked everything going to Chime... caller id format, user id and pw, ip address of all the instances that I have running and I still cannot get past the gatekeeper. I still getting the busy signal.
I have went over the installation instructions and the only difference I see is I have installed Debian 10 instead of 9. Besides that, I do not think I have missed anything.
 
The sound of a ringing phone has never sounded so sweetly. AWS support replied with the below text. By that time I had already deleted the system completely and started over, paying attention to the instructions, then trying the above, and still got the busy signal... all of the things that they replied with the try, I had already tried. Then miraculously, when I dialed out, the phone rang. My conclusion is that they made some change but did not state what they changed. But whatever it was, it fixed my issue.

"The service team has reviewed the pcap sent and identified the error being 401 - Unauthorized is thrown. More specially the auth failed to pass - Digest response is invalid.

Please check the encryption settings and try again. They have explained that this means the username/password provided is invalid.

Note: We have no visibility into the credentials that you have configured on your voice connector, we suggest creating a new credential pair.

Now looking at your most recent response you are getting a different error related to the incorrect number format being used. In your last response you are getting error 400 indicating that the \"To\" number is in the incorrect format

The \"TO\" and \"FROM\" header user part must contain a valid E.164 number."

This issue is now solved with the phone now ringing out.
I have begun work on the extensions such that the user will enter three digits instead of one, using Call Flow Designer. I wish there were more standard voice samples though. Other than that, I am very intrigued, restraining myself from not making it too complex.

Thanks to all who tried to help me here.;-)
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet