Phones firmware 28.72.0.26.
We put the following in provisioning files:
Code:
ringtone.url = http://myProvisioningServer/yealink/myRingTone.wav
phone_setting.ring_type = myRingTone.wav
account.1.ringtone.ring_type = myRingTone.wav
What happens:
The wav file ist uploaded. Both settings can be seen in phones web.
Problem: New wav will not be enabled, the phone will play Ring1.wav instead.
Manual switching afterwards via web is working, then the phone will use myRingTone.wav as wanted.
Any ideas why this is not working by provisioning as expected?
you may want to verify that there are no duplicates in mac_.cfg and y000000000028.cfg files.
_barnabas
We put the following in provisioning files:
Code:
ringtone.url = http://myProvisioningServer/yealink/myRingTone.wav
phone_setting.ring_type = myRingTone.wav
account.1.ringtone.ring_type = myRingTone.wav
Thx. But no, already checked.
I named my file Ring9.wav and it works. Cold the name format be the problem?
_barnabas
Tried this, renamed file to "Ring9.wav". No, still not working. New file is downloaded, both setting can be seen in web of phone. But the used ringtone is Ring1.wav. As soon as I just click "Confirm" on web page "settings/preference" (nothing changed, juct click the button), the phone recognizes that choosen ringtone should be Ring9 and then plays this one.
Not enough, autoprovisioning of one of the build-in ringtones like Ring7.wav works as expected. How weird...
all your scripts look OK to me. I'd try one last thing:
1- rearrange to:
ringtone.url = http://myProvisioningServer/yealink/myRingTone.wav
account.1.ringtone.ring_type = myRingTone.wav
phone_setting.ring_type = myRingTone.wav
2- second, if that does not work:
remove the last line - phone_setting.ring_type = myRingTone.wav
3- Remove every other line and keep these few lines, but type them in manually (no copy)
Other than that I have no idea why it doesn't work.
-Barnabas
Yes， you are right, we can reproduce the issue in my side, will submit it to the R&D and let you know if any update about it.
8/27/2014
Any updated status on this problem?
We are experiencing the same problem with needing to click the <confirm> button to activate the uploaded custom ringtone.
Any updates on this? I just updated my firmware and have the same issue on my T26 phone. VERY annoying
My work around is to click confirm on all the phones after making changes to my .cfg file.