GXW4104 Grandstream FXO Gateway Provisioning

[SMF Media]

V16.0.2.910
Enterprise License
Debian Linux

Grandstream GXW4104 with the latest Firmware (1.4.1.5)
I follow the directions here: https://www.3cx.com/voip-gateways/grandstream-fxo/

It will not provision. (Just spend an hour rebooting, Hard power down and power back up, looking at logs....)

If I go to the SIP Trunk then select the trunk and go to the Authentication Section on the General Tab and Select the Type of Authentication "Do not require - IP Based"
The FXO Gateway will then provision.

You can then go back in and change the Type of Authentication to "Register/Account based"


This may be a bug. I looked at other forum posts and found a few that reference this gateway and editing the nginx.conf file to listen on 5000. I checked it and it was listening on 5000.
Anyway that is what I found so I thought I would share and document the solution for myself and others.

 

[Evolute IT]

V16.0.2.910
Enterprise License
Debian Linux

Grandstream GXW4104 with the latest Firmware (1.4.1.5)
I follow the directions here: https://www.3cx.com/voip-gateways/grandstream-fxo/

It will not provision. (Just spend an hour rebooting, Hard power down and power back up, looking at logs....)

If I go to the SIP Trunk then select the trunk and go to the Authentication Section on the General Tab and Select the Type of Authentication "Do not require - IP Based"
The FXO Gateway will then provision.

You can then go back in and change the Type of Authentication to "Register/Account based"


This may be a bug. I looked at other forum posts and found a few that reference this gateway and editing the nginx.conf file to listen on 5000. I checked it and it was listening on 5000.
Anyway that is what I found so I thought I would share and document the solution for myself and others.

Did you follow the steps explained here: https://www.3cx.com/voip-gateways/grandstream-fxo/

 

[JohnS_3CX]

Note step 6 here on Authenticate Conf file. Was this set to NO ?

 

[SMF Media]

Yes. I followed the directions listed on the website.
Yes. The Authenticate Conf File was set to NO.

The device just would not apply the settings from provisioning on the 3cx server until I changed it to Do not require - IP Based

Once I did that the SIP server Address, SIP ID and SIP Password came over. I rebooted the Grandstream and changed 3cx Back to Authenticate and all is good now.

 

[Evolute IT]

Yes. I followed the directions listed on the website.
Yes. The Authenticate Conf File was set to NO.

The device just would not apply the settings from provisioning on the 3cx server until I changed it to Do not require - IP Based

Once I did that the SIP server Address, SIP ID and SIP Password came over. I rebooted the Grandstream and changed 3cx Back to Authenticate and all is good now.

Glad you got it to work.

 

[JohnS_3CX]

Hi @SMF Media

Thanks for reporting this. I will test this with the same model here and see if I can replicate the behavior.

 

[JohnS_3CX]

Ok after following the guide step by step, I can confirm that my GXW4104 with the same firmware as yours has been provisioned successfully.

It was not necessary to change the type of authentication on my management console and it worked as per the guide.

I think the issue must be something else in your case.