Yealink Forums

Full Version: Support for Variables
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi Guys,

This is an issue that we come across almost daily basis. We're an ISP with over 400 PBX customers and majority of them uses Yealink handsets.

Let me put a few scenarios where this would help especially with customers with a large number of handsets.

* DHCP Host name issues.
-- Some customers have issues with DHCP when all the devices have the same host name.
-- Some customers want to be able to identify which extension is configured from the hostname.
-- It is not feasible to change 100s of MAC.cfg files to accommodate this as there's no auto generate tool for this feature.

For this situation if we had a global variable for the extension number (Ex. $USER - Cisco), we could have easily incorporated it to the hostname in the base config file: Ex. $USER-T46G

* Line key and account Label.
-- Some customers would like to see their name on the top left corner (Account Label) and the extension number next to the DSS key.
-- At the moment we have to amend each file by hand if we're to do this and is not feasible for large distributions.

If we had the variable $USER as above, we could it with the base config file for the line keys.

It would be great if you guys could implement it this way or if we're allowed to use like below:

linekey.1.label = account.1.user_name
Hello,

Thanks for your info.

We will collect this request.

In addition, if we add "DHCP hostname" to the CGT tool, it could meet your request?

http://download.support.yealink.com/down...20Tool.zip


BR

klaus
(05-05-2017 09:28 AM)Klaus Wrote: [ -> ]Hello,

Thanks for your info.

We will collect this request.

In addition, if we add "DHCP hostname" to the CGT tool, it could meet your request?

http://download.support.yealink.com/down...20Tool.zip


BR

klaus

Hi Klaus,

Yes, it would remedy the situation at the very beginning. However any changes to extension number (sometimes customers want swap handsets, new extensions etc) means we need to manually edit the config file and remember to update this value as well.

Having this as a variable in the base file would mean we would not have to worry about it as the phone would automatically apply the required settings upon just changing the extension/username.

Regards
Hi Asankag,

Just as an alternative/point of interest for you, if you guys are managing 400+ phones you should really look into doing dynamic config generation. We use this all the time even for our small customers and it makes setting up the phones and configuring them with auto provision fast and extremely easy, no need for manually editing files all the time.

If you want an example, take a look at the post I did here:
http://forum.yealink.com/forum/showthrea...2#pid59282

Essentially you use a server-side web programming language to generate the actual config files that the phone receives, in real time. That way you get all the benefits of a programming language (variables, loops etc) and have the ability to tie into databases and other sources of information.
Reference URL's