Stale configuration options in the phones!!!

viopnewbie
Posts: 132
Member Since:
2007-12-19

I noticed that once you set an option in the configuration of the grandstream phone via those cfg****** files, and later remove the option.... the option is NOT removed from the phone.

What i mean is, if you set:
P48 = 192.168.1.1

then remove it afterwards, the P48 will STILL keep its old value of "192.168.1.1".

in order to get rid of it, you need to set it to:
P48 =

Which means, any settings you've tweaked, changed or switched from their original value, once removed from your configuration will still keep their old value, even if you RE-CREATE the configuration... apparently when the phone loads the config, it just overrides the values it finds, but never resets old values to defaults.

No wonder so many people had problems...

Oh, and don't try to use the defalt "gxp_config-1.1.6.16.txt" just like that because your phone will lock and endlessly reboot.



mjoyner
Posts: 142
Member Since:
2007-06-11
WRONG! You *must* rebuild each individual config file...

WRONG! You *must* rebuild each individual config file by going into endpoint manager, selecting the phone in question, followed up by clicking "update" at the bottom!

The cfg you are editing is merely a TEMPLATE used in building the actual config file.



viopnewbie
Posts: 132
Member Since:
2007-12-19
Where exactly did you read

Where exactly did you read in my post that i'm using the endpoint manager? I'm not.

I'm using the java configuration tool to directly compile my cfg* files before copying them to /tftpboot.

I've done extensive testing and the above problem is perfectly valid. Once a setting is set then it doesn't take its default value when unset unless you manually set the previous default value.



joshpatten
Posts: 733
Member Since:
2007-01-20
From my experience, you do

From my experience, you do have to leave the PXXX value defined in the config file, whether it is blank or not, otherwise it will never reload that value. As far as the perpetual reboot goes, I had to remove the configuration file (cfg*) from the tftpboot folder, reboot the phone, then let the phone download the new firmware and ringers/misc stuff, (and optionally do a factory reset) then place the config file back in the folder and reboot the phone.

BTW what phone are you using? 2000, 2010, 2020?

I have been using 2020's and they haven't given me any trouble.



viopnewbie
Posts: 132
Member Since:
2007-12-19
We are using gxp 1200 and

We are using gxp 1200 and 2010 phones and they all have problems.



timborino
Posts: 9
Member Since:
2008-02-05
I also use the java tool to

I also use the java tool to encode the cfg files. I've noticed that if I leave a PXXX setting out of the cfg file, the existing setting will remain on the phone, whether it was put there by a previous cfg file, or by a user in the web GUI. The only way to reset *everything* is to do a factory reset on the phone and let it pull the new cfg.

I don't remember seeing this mentioned in the documentation, but I think it's working as Grandstream intended. I find the feature useful to allow end users to customize certain settings (just leave them out of the cfg) while forcing all the other ones. Rebooting/re-provisioning won't affect their custom settings.



joshpatten
Posts: 733
Member Since:
2007-01-20
timborino, I never saw it

timborino, I never saw it that way, but it makes sense. as an example, a user can choose their own ringer and the setting wont be wiped on reboot. Now if users could just set speeddials for themselves, that would make thing a bit easier too.



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.