Yealink Forums

I'm having a strange issue with repeated autoprovisioning. My configuration consists of y000000000000.boot, an included file, and a $MAC.cfg file. The initial two files are served via TFTP, and the final one is served via HTTP.

If I factory reset the phone, it will correctly download all three files - two via TFTP, and the final file via HTTP. However, the next time it autoprovisions (I set repeatedly = yes, and interval = 1 minute), the phone only downloads the TFTP files. It never requests the HTTP file. I have verified this using the PCAP diagnostic file.

y000000000000.boot:

Code:

#!version:1.0.0.1

## The header above must appear as-is in the first line

include:config <bh-provision.cfg>

overwrite_mode = 1

specific_model.excluded_mode = 0

bh-provision.cfg:

Code:

#!version:1.0.0.1

##File header "#!version:1.0.0.1" can not be edited or deleted, and must be placed in the first line.##

static.auto_provision.server.url = http://x.x.x.x:8088/phoneprov/$MAC.cfg

static.auto_provision.repeat.enable = 1

static.auto_provision.repeat.minutes = 1

$MAC.cfg (some lines removed, e.g. SIP registrations, passwords etc.)

Code:

#!version:1.0.0.1

##File header "#!version:1.0.0.1" can not be edited or deleted, and must be placed in the first line.##

local_time.date_format = 6

local_time.ntp_server1 = uk.pool.ntp.org

local_time.time_zone = 0

local_time.time_zone_name = United Kingdom(London)

push_xml.sip_notify = 1

static.network.dhcp_host_name = Reception

static.firmware.url = http://x.x.x.x:8088/phoneprov/T46S(T48S,T42S,T41S)-66.84.0.90.rom

static.auto_provision.custom.protect = 0

static.auto_provision.repeat.enable = 1

static.auto_provision.repeat.minutes = 1

Anyone have any ideas why this might be happening? It looks like a bug to me, especially since it works once after a factory reset. All ideas and suggestions gratefully received!

Strange I would have expected the opposite (i.e. the .boot and bh-provision served by TFTP would apply at boot time, the HTTP cfg would not be picked up until 1 minute later). I'm with you sounds like a bug, try opening a support ticket with Yealink as this is a specific case that you should be able to get a direct answer to.

In the meantime try setting your log level to 6, leaving the phone running for a few minutes, and poking around to see if there are any indications of it attempting the http and failing for some reason.

patrick_keys

jolouis