Yealink Forums

Full Version: Help With T48 Provision
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello,
Configure dhcp provision, it's go correct to tftp server.
Found from tftp logs:
T48 ask file MAC-ADDRESS.boot - that not exist
then ask - y000000000000.boot
then ask xxx.cfg file.
Why it's not ask MAC-ADDRESS.cfg file?
How i need to change y000000000000.boot that for every phone it's will ask MAC-ADDRESS.cfg file ?
My y000000000000.boot is:

#!version:1.0.0.1
## The header above must appear as-is in the first line

include:config <xxx.cfg>
include:config "xxx.cfg"

overwrite_mode = 1

Thank you.
I am struggling with this exact same issue...
(07-25-2017 01:07 PM)yivgeny Wrote: [ -> ]Hello,
Configure dhcp provision, it's go correct to tftp server.
Found from tftp logs:
T48 ask file MAC-ADDRESS.boot - that not exist
then ask - y000000000000.boot
then ask xxx.cfg file.
Why it's not ask MAC-ADDRESS.cfg file?
How i need to change y000000000000.boot that for every phone it's will ask MAC-ADDRESS.cfg file ?
My y000000000000.boot is:

#!version:1.0.0.1
## The header above must appear as-is in the first line

include:config <xxx.cfg>
include:config "xxx.cfg"

overwrite_mode = 1

Thank you.

Dear User,
It is decided by you to choose which config file to be loaded.
Please refer to auto provision guide linked below,
http://download.support.yealink.com/down...V81_70.pdf
Kind Regards
Samuel Wang
Thank you,

Can you please explain how to configure y000000000000.boot file that it will ask MAC-ADDRESS.cfg file and not xxx.cfg file ?
The existence of a .boot file will stop the phone from asking for legacy configuration. I believe you can point the phone to pull a legacy configuration. I don't think you can use a hybrid of .boot and .cfg though.
Hi,

I know that i can create MAC-ADDRESS.boot file per phone and on every file like this point it to MAC-ADDRESS.cfg (so i need 2 files per phone: MAC-ADDRESS.boot and MAC-ADDRESS.cfg) but i want to know if i can create general y000000000000.boot that will be in use for all phones and will point for every phone to his MAC-ADDRESS.cfg file.
(07-27-2017 07:07 AM)yivgeny Wrote: [ -> ]I know that i can create MAC-ADDRESS.boot file per phone and on every file like this point it to MAC-ADDRESS.cfg (so i need 2 files per phone: MAC-ADDRESS.boot and MAC-ADDRESS.cfg) but i want to know if i can create general y000000000000.boot that will be in use for all phones and will point for every phone to his MAC-ADDRESS.cfg file.

Ran into this exact same issue ourselves. In all the Yealink documentation for the new provisioning process, there is no mention of a special keyword or variable that can be used inside the boot file. I expect one does exist (i.e. $MAC or something like that), but since it's not documented anywhere seems impossible to guess at what the value might be.

In our case we solved the issue by not using .boot files at all. If you do not have either y000000000000.boot or MAC-ADDRESS.boot then the phone does what it used to do, and requests the y000000000xx.cfg followed by it's own mac.cfg.

I understand why they implemented the .boot system, but it seems very odd that Yealink does not provide a standard sample y000000000000.boot file which implements the old style by default (that way we can learn about the new .boot and play with it without having it absolutely break everything).
Its documented.... You just haven't read the right document yet.

My y000000000000.boot

#!version:1.0.0.1
## The header above must appear as-is in the first line

## include:config "yealink-logging.cfg"
## include:config "yealink-syslog.cfg"
include:config "$MAC.cfg"
include:config "yealink-reboot.cfg"
overwrite_mode = 1
(09-08-2017 01:19 AM)bflorin Wrote: [ -> ]Its documented.... You just haven't read the right document yet.

My y000000000000.boot

#!version:1.0.0.1
## The header above must appear as-is in the first line

## include:config "yealink-logging.cfg"
## include:config "yealink-syslog.cfg"
include:config "$MAC.cfg"
include:config "yealink-reboot.cfg"
overwrite_mode = 1

thanks for the $MAC.cfg i've been looking for the past 3 days for that.

also what is in your yealink-reboot.cfg

im guessing so you don't have to hit re provision twice?
Reference URL's