Yealink Forums
How exactly are -local.cfg files POSTed to server ? - Printable Version

+- Yealink Forums (
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: Auto Provisioning (/forumdisplay.php?fid=14)
+--- Thread: How exactly are -local.cfg files POSTed to server ? (/showthread.php?tid=41626)

How exactly are -local.cfg files POSTed to server ? - oliv - 03-19-2018 05:10 PM


I'm discovering Autop_Protect feature, enabling uploading of -local.cfg files to a provisioning server.

I'm evaluating this feature with T42S powered by firmware.

My settings are:
static.auto_provision.server.url =
static.auto_provision.custom.protect = 1
static.auto_provision.custom.sync = 1
static.auto_provision.custom.upload_method = 1
static.auto_provision.custom.sync.path =

When I change my Ringing tone using phone display and keys, I can see in my /var/log/apache2/access.log file lines such as: - - [19/Mar/2018:18:06:13 +0100] "POST /yealink/ HTTP/1.1" 404 526 "-" "Yealink SIP-T42S 00:15:65:bf:fd:fe"

I would expect "POST /yealink/001565bffdfe-local.cfg HTTP/1.1" 200 as my /yealink/001565bffdfe-local.cfg exists.

Thoughts ?
Can you reproduce this ?


RE: How exactly are -local.cfg files POSTed to server ? - oliv - 03-20-2018 08:02 AM

May I add to this thread the fact that changing static.auto_provision.custom.upload_method to 0, triggers in /var/log/apache2/access.log file, lines such as:
"PUT /yealink/001565bffdfe-local.cfg HTTP/1.1" 405

405 comes from the fact that my HTTP server (apache 2.4) is not configured to support PUT method yet.
So it seems PUT method uses URL such as <provisioning URL or sync.path URL> + <MAC>-local.cfg while POST uses <provisioning URL or sync.path URL>.

Thoughts ? Comments ?