1. y000000000038.cfg (version 1) is uploaded to TFTP server. It contains a configuration for the time zone.
2. A phone with factory default settings is connected to the network and powered on. It successfully auto-provisions.
3. A change is made to the y000000000038.cfg file (version 2) and re-uploaded, replacing the original. It contains a different setting for the time zone than version 1 of the file.
4. I access the phone's web UI and manually trigger auto-provisioning.
5. The phone's time zone setting does not change. It is still the setting found in version 1 of the y000000000038.cfg file.

(11-04-2014 02:00 PM)Yealink_Coco Wrote:  Hello KKJ,

Could you please provide both two cfg files for me and then I can test in my side.
And could you please tell me what the firmware of your T38 ?

Thx

(11-08-2014 04:00 AM)lorn10 Wrote:  I have exactly the same problems regarding updating phone settings trough provisioning. I added the following parameters to the y0000000000$suffix.cfg config file, - but the phones doesn't "see" them. Is there an error in the syntax?

LocalTime.SummerTime = 1
LocalTime.dstTimeType = 1
LocalTime.StartTime = 3/5/7/1
LocalTime.EndTime = 10/5/7/2
LocalTime.OffsetTime = 60

All phones are T32G & T38G. OSS End Point Manager is used at FreePBX. Thanks for any hints!

Quote:Is it just those settings that are not updating? I fixed my problem by manually adding an entry for the auto-provision server's IP.

It seems that when the phones have default settings they will auto-provision based on the server you set with the DHCP option... but once they have been configured through that they ignore subsequent configuration changes unless they know the address of the server to auto-provision from [despite it being available to them through DHCP], so you must manually specify it in the original config or add it through the webUI and force it to provision.

(11-08-2014 04:47 PM)lorn10 Wrote:  

Quote:Is it just those settings that are not updating? I fixed my problem by manually adding an entry for the auto-provision server's IP.

It seems that when the phones have default settings they will auto-provision based on the server you set with the DHCP option... but once they have been configured through that they ignore subsequent configuration changes unless they know the address of the server to auto-provision from [despite it being available to them through DHCP], so you must manually specify it in the original config or add it through the webUI and force it to provision.

Thanks for your fast answer. Yes, these are the changes which are not updated to the phones. My full y0000000000$suffix.cfg config file looks very different from yours. Where I should add your two new entries?

Code:

[ cfg:/phone/config/system.ini,reboot=1 ]
LocalTime.TimeZone = {$timezone}
LocalTime.TimeServer1 = {$network_time_server}
LocalTime.TimeServer2 = pool.ntp.org
LocalTime.Interval = 1000
LocalTime.SummerTime = 1
LocalTime.dstTimeType = 1
LocalTime.StartTime = 3/5/7/1
LocalTime.EndTime = 10/5/7/2
LocalTime.OffsetTime = 60
LocalTime.TimeFormat = 1
LocalTime.DateFormat = 5

AutoProvision.bEnablePowerOn = 1
AutoProvision.bEnableWeekly = 0
AutoProvision.bEnableDHCPOption = 1
AutoProvision.listSystemOptions = 66,43
AutoProvision.strServerURL = tftp://{$server.ip.1}

telnet.telnet_enable = 0

[ cfg:/phone/config/system.ini,reboot=1]
Profile.CNG = 0
Profile.VAD = 1
Profile.Echo = 1
Profile.SIDE_TONE = -30

[ cfg:/phone/config/user.ini,reboot=1 ]
WatchDog.Time = 10
vpm_tone_Country.Country = {$tones_country}

AlertInfo0.Text = interal
AlertInfo0.Ringer = 2

AlertInfo1.Text = external
AlertInfo1.Ringer = 5

Emergency.Num = 000

PhoneSetting.BacklightTime = 120
PhoneSetting.DialNowDelay = {$dialnowdelay}
PhoneSetting.BackGrounds = {$uselogo}
PhoneSetting.BackLight = 6
PhoneSetting.UnusedBackLight = 0
PhoneSetting.ScreensaverTime = {$screensaverdelay}
PhoneSetting.Theme = {$theme}
PhoneSetting.Voicevolume = 5
PhoneSetting.Lock = 0

[ bin:/phone/config/DialNow.xml,reboot=0 ]
url=tftp://{$server.ip.1}/dialnow.xml

[ psw:/phone/config/.htpasswd ]
admin = {$adminpw}

[ rom:Firmware ]
url = {$firmware_name}

Supplement: Parameter auto_provision.server.url semms to be for firmware V71 and above, - not for V70 based like T38G & T32G are. Does this really works for you at T38G? In my (old) config, parameter AutoProvision.strServerURL seems the correct one. It works for firmware 32.70.0.185 & 38.70.0.185. However, daylight saving parameters are still completely ignored.

Quote:Here is the full config I use for all the T38's.

...

The majority of the phones we have use firmware version: 38.70.0.186, some of them are on 38.70.0.126. But they all work with this config.

I have not tried the auto-provision format you have in your post. As you said, it is for a different version of the firmware. My phones seem to like the new format though, despite not being on v71+. With this layout, I don't think the phone cares which order you have the statements in, or which heading you have them under. My assumption just from looking at the structure of the older format is that the phones would interpret them in a much more rigid manner. I think the most important thing is to have the "#!version:1.0.0.1" header at the top of document. Maybe try converting your config over to the new layout and try it on a test phone? Hope that helps.

Quote:Many thanks for all this information! Will try... Last thing, firmware 38.70.0.186 seems to be a special (UK) one, - right? I think it uses also M7 style template...