It would be so very nice if I could configure a single phone using the web interface, then click a button that would export working auto-provisioning files from the phone's existing configuration.
I think it would reduce support costs considerably if we didn't have to worry about making sure we had the right autoprovisioning template for the right phone, with the right firmware version, and so on. Just config the phone with the web interface, export the autoprovisioning files, copy them to the autoprovisioning server, and then customize the few bits that are different from phone to phone within the same organization.
Hi julesa,
It is a good idea and we will add this feature in futurre version. We have considered this feature and decided to do it.
(02-25-2014 04:39 PM)Yealink Support Wrote: [ -> ]Hi julesa,
It is a good idea and we will add this feature in futurre version. We have considered this feature and decided to do it.
Excellent!!! Thank you!
I just made a post to suggest just this... but then I saw this was the same suggestion and deleted it.
I think this is an awesome idea. It would save a ton of work, and you'd be making a difficult and time consuming process much much easier. This would add a ton of value to the phones.
For Yealink, I think this would be big for their resellers, and you'd end up selling a lot more phones because of ease of deployment.
This is an awesome idea...
(02-25-2014 04:39 PM)Yealink Support Wrote: [ -> ]Hi julesa,
It is a good idea and we will add this feature in futurre version. We have considered this feature and decided to do it.
Is there an ETA for an export of the config file from a T46G. I have just received 23 of them and would like to have this feature.
(04-02-2014 10:21 PM)Yealink Support Wrote: [ -> ]Hi We are test a Configuration Generation tool internally.
Do you want to have a try?
CGT tool 2.0.0.11
I'm playing with this tool now, it looks very useful. Just out of curiosity, which firmware revision is generated with this code? Is this v72 compatible?
Some suggestions to further improve this:
1) Integrate this with your documentation (tool tips would be helpful). Otherwise you have to search for the feature in your documentation every time you want to make a change.
2) Import .bin file from the phones export feature. I personally set up my phones manually, and got it working with a manual setup... then painstakingly reproduced it in the auto-config. Maybe others can chime in on how their initial setup went, but that is the way I did mine.
Hi nicknomo,
Thank you for your opinions.
This tool can generate below syntaxs. You can refer to more details in user guide.
->SIP - T28P, SIP - T26P, SIP - T22P, SIP - T21P, SIP - T20P, SIP - T19P, SIP - T48G, SIP - T46G, SIP - T42G
and SIP - T41P IP phones running firmware version 72 or later
->SIP - T38G, SIP - T32G and VP530 IP phones running firmware version 70 or later