Solved Problem with inbound calls

[Vivaciti Ltd]

Hi,
I am having an issue with some inbound calls (new sip provider)
If a call is placed on the main number, it is received all OK, but if we place it to another number we get the following:

04/09/2020 12:40:49 PM - [CM102001]: Authentication failed for AuthFail Recv Req INVITE from x.x.x.x:5060 tid=43b35b79 Call-ID=[email protected]:5060: INVITE sip:[email protected] SIP/2.0 Via: SIP/2.0/UDP x.x.x.x.130:5060;branch=z9hG4bK43b35b79 Max-Forwards: 70 Contact: To: From: "07854xxxxxx" ;tag=as025ad805 Call-ID: [email protected]:5060 CSeq: 103 INVITE Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Content-Type: application/sdp Date: Thu, 09 Apr 2020 11:40:49 GMT Proxy-Authorization: Digest username="sipusername",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:[email protected]",nonce="414d53595e8f09c154:eb73513f1bfb9effd4d4439edef02c62",response="27e993591e38acca24d7c7783be697fd" Supported: replaces, timer User-Agent: UCRESELLER MERLINDC22P P-Asserted-Identity: "07854xxxxxx" Content-Length: 323 v=0 o=root 931310251 931310252 IN IP4 51.89.222.130 s=Asterisk PBX 13.32.0 c=IN IP4 x.x.x.x t=0 0 m=audio 15666 RTP/AVP 0 8 18 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=maxptime:150 a=sendrecv ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

If we change the main number to the other one thats having an issue, call goes through all OK, so it looks like the inbound rules.

I have deleted these and put them in again, I have even changed the number format incase.

The carrier says the problem it with 3CX, but I have now reinstalled this on a hyper-v vm, aws, and google all with the same issues.

Any help?

 

[JohnS_3CX]

It depends on whether the DIDs you add are in the correct format, so that the PBX can identify the call belonging to it. This is very likely the cause.

Try to run a capture from Activity Log > Capture

Then make a call (which will fail). Stop the capture and download it from the machine so you can analyze it in WireShark. You should probably see the PBX send a challenge to the provider, and then you will get credentials authentication failing

 

[Vivaciti Ltd]

Found the issue (well did not find the problem, but solved it) I had to remove the SIP trunk and re-add it, now all works, so must have been an issue with the template.
Wish I had tried that sooner, would have saved a number of re-installs.

 

[JohnS_3CX]

If it was a supported trunk, then yes. You hadn't mentioned a provider yet though, so wasn't sure. Glad to hear it was resolved