2x 3CX Systems 1x Asterisk System Unable to call an Extn

[Alan Smith]

We have 2 remote 3CX systems, on each system there is an extension being used to link to an Asterisk Server, on one system if the extension is rung it rings on the Asterisk server, it can be answered & a conversation had. On the other system when the extension is called the call goes straight to VM, both extensions are setup the same way on both of the 3CX systems & defined in the Asterisk Server the same. Calls can be made via the Asterisk Server to other extensions on each 3CX system without issue.

The only difference we can see is in the Register 200OK,

This is the extension that is failing it's running on 3CX 16.0.619

U 2020/07/21 09:28:00.522828 Asterisk_IP:5060 -> Failing_3CX:5060 #7110
REGISTER sip:Failing_3CX SIP/2.0.
Via: SIP/2.0/UDP Asterisk_IP:5060;branch=z9hG4bK585011dd;rport.
Max-Forwards: 70.
From: <sip:220@Failing_3CX>;tag=as1f997df5.
To: <sip:220@Failing_3CX>.
Call-ID: [email protected].
CSeq: 6508 REGISTER.
Supported: replaces, timer.
User-Agent: Asterisk PBX 16.11.0.
Authorization: Digest username="username", realm="3CXPhoneSystem", algorithm=MD5, uri="sip:Failing_3CX", nonce="414d53595f16a6a723:43bf8c3833acbc8338e4791dd036dd93", response="804f6646ed3e8763ae805ac997a4a0a7".
Expires: 120.
Contact: <sip:220@Asterisk_IP:5060>.
Content-Length: 0.
.

U 2020/07/21 09:28:00.573582 Failing_3CX:5060 -> Asterisk_IP:5060 #7111
SIP/2.0 407 Proxy Authentication Required.
Via: SIP/2.0/UDP Asterisk_IP:5060;branch=z9hG4bK585011dd;rport=5060.
Proxy-Authenticate: Digest nonce="414d53595f16a71024:ba2ed3cfc4132361e7f177bd5d539dd3",algorithm=MD5,realm="3CXPhoneSystem".
To: <sip:220@Failing_3CX>;tag=f9158160.
From: <sip:220@Failing_3CX>;tag=as1f997df5.
Call-ID: [email protected].
CSeq: 6508 REGISTER.
Content-Length: 0.
.

U 2020/07/21 09:28:00.651892 Asterisk_IP:5060 -> Failing_3CX:5060 #7112
REGISTER sip:Failing_3CX SIP/2.0.
Via: SIP/2.0/UDP Asterisk_IP:5060;branch=z9hG4bK658c37fe;rport.
Max-Forwards: 70.
From: <sip:220@Failing_3CX>;tag=as1f997df5.
To: <sip:220@Failing_3CX>.
Call-ID: [email protected].
CSeq: 6509 REGISTER.
Supported: replaces, timer.
User-Agent: Asterisk PBX 16.11.0.
Proxy-Authorization: Digest username="username", realm="3CXPhoneSystem", algorithm=MD5, uri="sip:Failing_3CX", nonce="414d53595f16a71024:ba2ed3cfc4132361e7f177bd5d539dd3", response="d3caa60d895e864367ec83949a25b9cb".
Expires: 120.
Contact: <sip:220@Asterisk_IP:5060>.
Content-Length: 0.
.

U 2020/07/21 09:28:00.702535 Failing_3CX:5060 -> Asterisk_IP:5060 #7113
SIP/2.0 200 OK.
Via: SIP/2.0/UDP Asterisk_IP:5060;branch=z9hG4bK658c37fe;rport=5060.
To: <sip:220@Failing_3CX>;tag=55f3341f.
From: <sip:220@Failing_3CX>;tag=as1f997df5.
Call-ID: [email protected].
CSeq: 6509 REGISTER.
User-Agent: 3CXPhoneSystem 16.0.5.619 (619).
Content-Length: 0.

This is the extension that is working it's running on 3CX 16.0.6.584

U 2020/07/21 09:27:49.114784 Asterisk_IP:5060 -> Working_3CX:5060 #1795
REGISTER sip:Working_3CX SIP/2.0.
Via: SIP/2.0/UDP Asterisk_IP:5060;branch=z9hG4bK7d18f0a0;rport.
Max-Forwards: 70.
From: <sip:6001@Working_3CX>;tag=as4bd56b7e.
To: <sip:6001@Working_3CX>.
Call-ID: [email protected].
CSeq: 6508 REGISTER.
Supported: replaces, timer.
User-Agent: Asterisk PBX 16.11.0.
Authorization: Digest username="username", realm="3CXPhoneSystem", algorithm=MD5, uri="sip:Working_3CX", nonce="414d53595f16a69b07:c5c8682af41925be6456f0365214eb94", response="8e358ff43e492588bf09354515b34d77".
Expires: 120.
Contact: <sip:6001@Asterisk_IP:5060>.
Content-Length: 0.
.


U 2020/07/21 09:27:49.165357 Working_3CX:5060 -> Asterisk_IP:5060 #1796
SIP/2.0 407 Proxy Authentication Required.
Via: SIP/2.0/UDP Asterisk_IP:5060;branch=z9hG4bK7d18f0a0;rport=5060.
Proxy-Authenticate: Digest nonce="414d53595f16a70519:47ee4bdd61b8c7105617f2f4cfcebd0d",algorithm=MD5,realm="3CXPhoneSystem".
To: <sip:6001@Working_3CX>;tag=03d96c74.
From: <sip:6001@Working_3CX>;tag=as4bd56b7e.
Call-ID: [email protected].
CSeq: 6508 REGISTER.
Content-Length: 0.
.


U 2020/07/21 09:27:49.240665 Asterisk_IP:5060 -> Working_3CX:5060 #1797
REGISTER sip:Working_3CX SIP/2.0.
Via: SIP/2.0/UDP Asterisk_IP:5060;branch=z9hG4bK214e1840;rport.
Max-Forwards: 70.
From: <sip:6001@Working_3CX>;tag=as4bd56b7e.
To: <sip:6001@Working_3CX>.
Call-ID: [email protected].
CSeq: 6509 REGISTER.
Supported: replaces, timer.
User-Agent: Asterisk PBX 16.11.0.
Proxy-Authorization: Digest username="username", realm="3CXPhoneSystem", algorithm=MD5, uri="sip:Working_3CX", nonce="414d53595f16a70519:47ee4bdd61b8c7105617f2f4cfcebd0d", response="366f6a65ebd4f61690281c73fa215f3a".
Expires: 120.
Contact: <sip:6001@Asterisk_IP:5060>.
Content-Length: 0.
.


U 2020/07/21 09:27:49.294031 Working_3CX:5060 -> Asterisk_IP:5060 #1799
SIP/2.0 200 OK.
Via: SIP/2.0/UDP Asterisk_IP:5060;branch=z9hG4bK214e1840;rport=5060.
Contact: <sip:6001@Asterisk_IP:5060>;expires=120.
To: <sip:6001@Working_3CX>;tag=2d7dfb77.
From: <sip:6001@Working_3CX>;tag=as4bd56b7e.
Call-ID: [email protected].
CSeq: 6509 REGISTER.
User-Agent: 3CXPhoneSystem 16.0.6.584 (584).
Content-Length: 0.

If we replace the Asterisk Server with a hard phone then calls can be made both ways

Is it worth asking the 3CX hosting partner to update to the latest version?

 

[davide.bonavita]

Why don't you setup a SIP trunk?

 

[Alan Smith]

Why don't you setup a SIP trunk?

We could do that but that doesn't explain why one server works & the other doesn't we'd like to understand what the actual cause is, in case this is a bug which requires a fix, although it is the never server that works, so it may have already been addressed.

 

[leejor]

Just so I'm clear...You created an extension in each 3CX PBX, you've then created two trunks in the Asterisk PBX to register to each. If that is the case, does the failing extension show as registered (ext 220) in that PBX. Does it show as registered in Asterisk? Is that the issue (at this point), that it can't register? Does Asterisk have a log that shows an error, when attempting to register?

 

[Alan Smith]

Just so I'm clear...You created an extension in each 3CX PBX, you've then created two trunks in the Asterisk PBX to register to each.

Yes

If that is the case, does the failing extension show as registered (ext 220) in that PBX.

It shows up with a green circle at the side of the extension & calls can be sent from the extension into the 3CX PBX, TBH this is our first foray into 3CX

Does it show as registered in Asterisk? Is that the issue (at this point), that it can't register? Does Asterisk have a log that shows an error, when attempting to register?

I will check that one & get back to you, but when a call is originated on the failing 3CX system the call does not reach or even offered to the Asterisk system

 

[leejor]

Since the call goes direct to voicemail (I assume it is the 3CX voicemail for Ext 220) the 3CX log should show why that is...the extension cannot be reached for some reason, has DND set, not registered, etc.

 

[Alan Smith]

The issue appears to be that the 3CX system does not think the Asterisk Server is registered

07/22/2020 10:07:39 AM - L:439.1[Extn:219] failed to reach Extn:220, reason Not Registered

07/22/2020 10:07:39 AM - [CM503017]: Call(C:439): Target is not registered: Extn:220

07/22/2020 10:07:39 AM - [Flow] Call(C:439): has built target endpoint: Extn:220 for call from L:439.1[Extn:219]

07/22/2020 10:07:39 AM - [Flow] Target endpoint for 220 is Extn:220

But the Asterisk can make calls into the 3CX & thinks it is registered within the Asterisk CLI which brings me back to the only difference we can see is in the 200OK from the REGISTER or am I chasing a red herring?

U 2020/07/22 10:10:25.026425 Failing_3CX:5060 -> 10.17.0.5:5060 #2380185
SIP/2.0 200 OK.
Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK084543a2;rport=5060.
To: <sip:220@Failing_3CX>;tag=617f1201.
From: <sip:220@Failing_3CX>;tag=as1f997df5.
Call-ID: [email protected].
CSeq: 8267 REGISTER.
User-Agent: 3CXPhoneSystem 16.0.5.619 (619).
Content-Length: 0.

U 2020/07/22 10:11:54.266880 Working_3CX:5060 -> 10.17.0.5:5060 #2380284
SIP/2.0 200 OK.
Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK4808a128;rport=5060.
Contact: <sip:[email protected]:5060>;expires=120.
To: <sip:6001@Working_3CX>;tag=70699236.
From: <sip:6001@Working_3CX>;tag=as4bd56b7e.
Call-ID: [email protected].
CSeq: 8269 REGISTER.
User-Agent: 3CXPhoneSystem 16.0.6.584 (584).
Content-Length: 0.

The Contact line is missing from the failing one

 

[leejor]

In most cases, a device that is not actually registered, can still place calls, as long as the parameters (user, password, Admin, etc.) are accepted (valid) by the server. Registration tells the server how to contact the device, and lets it know that t is still there.

Obviously some setting, or network configuration , on the failing PBX is incorrect. I would compare with the working one. What is different between the two?