Phones cannot dial out

[Frank86]

I have a Grandstream GXW-4024 (LAN IP 192.168.10.64) that connects to our 3CX server's LAN IP (192.168.10.25) for extension 5203.
3CX activity log shows the error below: Credentials don't match. What credentials is it referring to?

The phones connected to the Grandstream device cannot dial out.

08/19/2020 7:00:22 AM - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 192.168.10.64:5106 tid=1343982059 Call-ID=414816194-5106-1:
REGISTER sip:192.168.10.25 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.64:5106;branch=z9hG4bK1343982059;rport=5106
Max-Forwards: 70
Route: <sip:192.168.10.25:5060;lr>
Contact: <sip:[email protected]:5106;user=phone>;reg-id=24;+sip.instance="<urn:uuid:00000000-0000-1000-8000-000B823BE42E>"
To: <sip:[email protected];user=phone>
From: <sip:[email protected];user=phone>;tag=609507070
Call-ID: 414816194-5106-1
CSeq: 18052 REGISTER
Expires: 3600
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE
Proxy-Authorization: Digest username="5203",realm="3CXPhoneSystem",nonce="414d535c154bacb921:fcb2db46103929cb53fb9d6330857b1c",uri="sip:192.168.10.25",response="5551ddfd4cd2771448075789d4fd7c53",algorithm=MD5 Supported: path
User-Agent: Grandstream GXW-4024 V0.4A 1.0.6.13 chip V2.2
Content-Length: 0 ;

Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

 

[leejor]

The "credentials", referred to, are explained in the last line of your post, the authorization ID and/or the password may be in error. How was the phone provisioned?

 

[Frank86]

Not sure. I just inherited the setup. The phone having the problem is a Bittel room phone connected via RJ11. This is for a small hotel. It has an extension set up in 3CX but no phone associated with it other than the 3CX app. I assume the phone was provisioned through the Grandstream device.

 

[cobaltit]

Not sure. I just inherited the setup. The phone having the problem is a Bittel room phone connected via RJ11. This is for a small hotel. It has an extension set up in 3CX but no phone associated with it other than the 3CX app. I assume the phone was provisioned through the Grandstream device.

You can't provision an analog phone. You provision the gateway, in this case the Grandstream

 

[leejor]

I would attempt to re-provision after a full reset.

 

[JohnS_3CX]

We Support the 4224 but not the 4024 so you might need to do some manual work.

It's probably a good idea to backup the config of the device in case you need to revert.

As a starting point, this may help you although compatibility cannot be guaranteed
https://www.3cx.com/voip-gateways/grandstream-gxw-fxs/

 

[Frank86]

We Support the 4224 but not the 4024 so you might need to do some manual work.

You are right. I was able to add the 4224 but I had to register the phones connected to the 4024 manually. Planning on replacing the 4024.

I was able to get the analog phones registered but they can only dial internal lines; they cannot dial out. I checked the outbound rules and they seem ok (all other IP phones can dial out just fine). Could it be something other than the outbound rules?

 

[leejor]

There is an extension option regarding outside calls. If that is set to allow, then look at the 3CX Activity Log for a reason the call does not complete.

 

[JohnS_3CX]

Yes, its a two part matter and generally speaking for any generic FXS it will be a bit like this:

1) The analog phones live behind the FXS and what call traffic happens between them can stay between them inside the FXS realm without the PBX being involved (i.e a type of standalone mode)

2) if they want to call outside they need a path from the FXS to the PBX (like old hybrid systems that needed a path to the outside world via an analog line). So from their perspective, calls to other legit 3CX VoIP extensions and trunk calls appear as external calls so to speak. The 3CX system configures your supported FXS accordingly so they act as normal extensions (as if they were VoIP phones)

You can look up all the parameters in the config files 3CX generates, and find equivalents to the device you use to make config a bit easier, but if you used a supported FXS all this will be taken care of via auto provisioning when you upload a 3CX-generated config XML to the device. I'm not sure whether the one you use now is fully compatible.