Amazon Chime outbound call not working?

Status
Not open for further replies.

warda.c

Free User
Joined
Nov 22, 2021
Messages
2
Reaction score
0
Hi Everyone,

I did setup my 3cx on amazon chime. Im not an expert in 3cx just followed one video from YouTube. After the setup inbound calls are working but not the outbound. I tried to find a solution but could not find any. I would highly appreciate if anyone can help me in this. Thanks.

My Outbound rules
outbound.png

My sip trunks
siptrunk.png
 
Can you post the error message you are getting in the 3CX? Activate Verbose logging and make an outbound call. If we can see the INVITE message and/or any errors before or after, that would be helpful.
 
Have a read abut the number format required...

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

Since you have an outbound rule for numbers beginning with 9, I have to assume that, to be correct, you are dialing "9+1NXXNXXXXXX", as Chime wants to see numbers in the E164 format (leading +, and country code)
 
  • Like
Reactions: ChrisC_3CX
Can you post the error message you are getting in the 3CX? Activate Verbose logging and make an outbound call. If we can see the INVITE message and/or any errors before or after, that would be helpful.
Sorry I did not know which part of the error to send you. So I copied the whole error.

Call or Registration to +13526006900@(Ln.10000@Amazon Chime Voice Connector) has failed. 3.80.16.105 replied: 401 Unauthorized; from IP:3.80.16.105:5060

Call or Registration to +1+13526006900@(Ln.10000@Amazon Chime Voice Connector) has failed. 3.80.16.105 replied: 400 Invalid to number; from IP:3.80.16.105:5060


11/26/2021 11:44:41 PM - Updating device Dev(982306261):[sip:[email protected]:5063;rinstance=ec5660c5d85fedf3 / 110] by message: DevUpd Recv Req REGISTER from 127.0.0.1:5063 tid=03fa0a68606fc727 Call-ID=yFN_iqvzhY-ZWhlYEn0nRw..: REGISTER sip:127.0.0.1:5060 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5063;branch=z9hG4bK-524287-1---03fa0a68606fc727;rport=5063 Max-Forwards: 70 Contact: <sip:[email protected]:5063;rinstance=ec5660c5d85fedf3> To: <sip:[email protected]:5060> From: <sip:[email protected]:5060>;tag=36d33e5c Call-ID: yFN_iqvzhY-ZWhlYEn0nRw.. CSeq: 48 REGISTER Expires: 60 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE Proxy-Authorization: Digest username="SMOCG6IHEg",realm="3CXPhoneSystem",nonce="414d535961a1392938:1d5c3088450c33f3528d07bb5a2a2d1b",uri="sip:127.0.0.1:5060",response="f429e8880253655f09fc458cde1af95f",algorithm=MD5 Supported: replaces User-Agent: 3CX WebRTC proxy Content-Length: 0
11/26/2021 11:44:34 PM - Currently active calls [none]
11/26/2021 11:44:34 PM - Default best-route IP is determined as 172.31.20.229
11/26/2021 11:44:30 PM - Leg L:330.1[Extn:110] is terminated: Cause: BYE from PBX
11/26/2021 11:44:30 PM - Terminated from "Ali, Zahid"<sip:[email protected]>;tag=ed5f3e42 to <sip:[email protected]:5060>;tag=eec60e10; reason: Rejected
11/26/2021 11:44:30 PM - L:330.1[Extn:110] Sending: OnSendResp Send 404/INVITE from 0.0.0.0:0 tid=7d3d5f003575d515 Call-ID=m4g_Fdu6N2hA4J8ctmQUqw..: SIP/2.0 404 Not Found Via: SIP/2.0/UDP 127.0.0.1:5063;branch=z9hG4bK-524287-1---7d3d5f003575d515;rport=5063 To: <sip:[email protected]:5060>;tag=eec60e10 From: "Ali, Zahid"<sip:[email protected]>;tag=ed5f3e42 Call-ID: m4g_Fdu6N2hA4J8ctmQUqw.. CSeq: 2 INVITE Warning: 499 ip-172-31-20-229.us-east-2.compute.internal "Not found" Content-Length: 0
11/26/2021 11:44:30 PM - SendMsg from <sip:[email protected]:5060>;tag=eec60e10 to "Ali, Zahid"<sip:[email protected]>;tag=ed5f3e42
11/26/2021 11:44:30 PM - Call(C:330) is terminated
11/26/2021 11:44:30 PM - [CM503020]: Call(C:330): Normal call termination. Call originator: Extn:110. Reason: Not found
11/26/2021 11:44:30 PM - [CM503016]: Call(C:330): Attempt to reach <sip:[email protected]:5060> from Extn:110 has failed. Reason: Not Found
11/26/2021 11:44:30 PM - [CM503014]: Call(C:330): No known route from Extn:110 to target: <sip:[email protected]:5060/UDP>
11/26/2021 11:44:30 PM - Call(C:330): from Extn:110 to 93526009600 doesn't match any outbound rule. No outbound rule could be selected.
11/26/2021 11:44:30 PM - [Flow] Target endpoint for 93526009600 can not be built!
11/26/2021 11:44:30 PM - Selected prefix: 9
11/26/2021 11:44:30 PM - Looking for outbound rule: dialed = [93526009600], processed: [93526009600]; from-ext:
11/26/2021 11:44:30 PM - [Flow] Building target endpoint to 93526009600 from "Ali, Zahid" <sip:[email protected]:0>
11/26/2021 11:44:30 PM - [CM503010]: Call(C:330): Making route(s) from Extn:110 to <sip:[email protected]:5060/UDP>
11/26/2021 11:44:30 PM - Remote SDP is set for leg L:330.1[Extn:110]
11/26/2021 11:44:30 PM - [CM505001]: Endpoint Extn:110: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX WebRTC proxy] PBX contact: [sip:[email protected]:5060]
11/26/2021 11:44:30 PM - Inbound DID: ''; Phonebook Name: ''
11/26/2021 11:44:30 PM - [CM500002]: Call(C:330): Info on incoming INVITE from Extn:110: Invite-IN Recv Req INVITE from 127.0.0.1:5063 tid=7d3d5f003575d515 Call-ID=m4g_Fdu6N2hA4J8ctmQUqw..: INVITE sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5063;branch=z9hG4bK-524287-1---7d3d5f003575d515;rport=5063 Max-Forwards: 70 Contact: <sip:[email protected]:5063;rinstance=ec5660c5d85fedf3> To: <sip:[email protected]:5060> From: "Ali, Zahid"<sip:[email protected]>;tag=ed5f3e42 Call-ID: m4g_Fdu6N2hA4J8ctmQUqw.. CSeq: 2 INVITE Subject: Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE Content-Type: application/sdp Proxy-Authorization: Digest username="SMOCG6IHEg",realm="3CXPhoneSystem",nonce="414d535961a1391d24:7b27d9b311c0f71ceac881ae720cf269",uri="sip:[email protected]:5060",response="b6dc091a0450914c5d1efb18e82122b8",algorithm=MD5 Supported: replaces User-Agent: 3CX WebRTC proxy Content-Length: 652 v=0 o=3cxVCE 18446744073380696171 18446744071788364258 IN IP4 127.0.0.1 s=3cxVCE Audio Call c=IN IP4 127.0.0.1 t=0 0 m=audio 8890 RTP/AVP 111 63 103 104 9 0 8 106 105 13 110 112 113 126 a=rtpmap:111 opus/48000/2 a=fmtp:111 minptime=10;useinbandfec=1 a=rtpmap:63 red/48000/2 a=fmtp:63 111/111 a=rtpmap:103 ISAC/16000 a=rtpmap:104 ISAC/32000 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:106 CN/32000 a=rtpmap:105 CN/16000 a=rtpmap:13 CN/8000 a=rtpmap:110 telephone-event/48000 a=rtpmap:112 telephone-event/32000 a=rtpmap:113 telephone-event/16000 a=rtpmap:126 telephone-event/8000 a=ptime:20 a=sendrecv
11/26/2021 11:44:30 PM - [CM503001]: Call(C:330): Incoming call from Extn:110 to <sip:[email protected]:5060>
11/26/2021 11:44:30 PM - IncomingCall: C:330 from <sip:[email protected]:0/UDP> to <sip:[email protected]:5060/UDP>
11/26/2021 11:44:30 PM - Added leg L:C:330.1[No endpoint yet]
11/26/2021 11:44:30 PM - Call from "Ali, Zahid"<sip:[email protected]>;tag=ed5f3e42 to <sip:[email protected]:5060>;tag=eec60e10
 
Call or Registration to +1+13526006900@(Ln.10000@Amazon Chime Voice Connector) has failed. 3.80.16.105 replied: 400 Invalid to number; from IP:3.80.16.105:5060
This error is because the dialed number has +1 twice

Call or Registration to +13526006900@(Ln.10000@Amazon Chime Voice Connector) has failed. 3.80.16.105 replied: 401 Unauthorized; from IP:3.80.16.105:5060
This (401 unauthorized) usually means that the request requires user authentication, but you'd have to confirm that with Chime. There could very well be another reason. It may even be a sent caller ID problem.
 
  • Like
Reactions: NickD_3CX
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,083
Members
164,901
Latest member
Silent_Guru