A "thank you" to Yeastar for adding a "Template" function into the newest update of the Autoprovisioning App for the S-Series.
This makes it much easier and faster to deploy a custom configuration (button assignments for example) to a group of phones without having to manually program each button on each phone.
Thanks guys!
Yes, A big "thank you" to Yeastar team! Thanks guys!
But the current template is too simple, I believe Yeastar team will get template feature better in the future version of AUTO-P application.
Agreed - it is way too simple. Any idea how to auto provision various other phone features - one's that aren't in the template list..? Have any of you experimented with the "upload files" section under the autoprovisioning app. Is this meant to bridge that gap by uploading entire phones configuration files? Please help :)
I second all this. I want to tweak some non-GUI features but can't figure out how to create a config template or whether the template can even contain non-GUI items to load into phones.
I assume there is some SSH action required here, but I cannot SSH into my S412 with the suggested login. I've tried user/password combos suggested in a couple of spots: support/yeastar and support/iyeastar. (note "i") I'm guessing I can pull the file the auto-config uses and add stuff but I am a bit of a noob and guessing here!
I downloaded the actual Yealink config file for my phones from their website, but it is 5 or so files and I can't figure out how that relates to template-building. Kind of an amazing array of things contained in that. Is there a tool to help build auto-config files??? Not even sure how to put it back on the phone directly either.
Regarding how to generate the config file, I think you can follow guide from Yealink website(Below is an example download link for T52S, you may need to find other guide from Yealink website): http://download.support.yealink.com/download?path=upload%2Fattachment%2F2018-3-13%2F5%2F6eb0cdd1-ad6c-4d7f-b415-ffae939bbe90%2FYealink_SIP_Phones_AutoProvisioning_Template_V83.10.zip
After generate the cfg file(only one cfg file is required), you can follow below guide to upload the cfg file.
I believe through this way would be easier.
Oscar, thanks for the links! Here's another helpful thing I found: Their config generating tool.
Yealink Configuration Generator Tool_V81.zip
So when the phone is looking for a provisioning file, it goes to the tftp server on the pbx and it looks for its configuration file as named (phone mac address here).cfg. I keep seeing mac.cfg files and now realize they are saying "put the phone's mac here!".cfg. Correct? At least that is what Yealink phones are looking for.
Since the phone is looking for the one file, all the parameters I want to load into the phone must be merged into that one document. Right? It appears to be what the Generator tool results in.
The thing I'm not quite wrapping my head around at the moment: I look at the template you noted above. It contains multiple .cfg and XML files. Again, I'm not sure how they all actually get utilized.
So much to learn...
Joseph, yes, you are right. One IP phone need one mac.cfg file only. We put all the parameters in that file.
The other cfg or XML files you saw in the screenshot was for other phones.
I updated my S412 to the new firmware 30.7.0.27. I can no longer access the contents of the TFTPboot directory, either using SSH or FTP. I think it started being a problem after the upgrade; I could access it earlier this week. I'm logging in with support/iyeastar. It does log in, I can list directories, I just can't open and view TFTPboot.
Thoughts???
Same here.
I don't know if Yeastar monitors the forums closely, so I've opened a ticket about the tftpboot issue.
