Ni file name in POST URLs [Was: How exactly are -local.cfg files POSTed to server ?]

[oliv]

(11-08-2018 04:18 PM)jolouis Wrote:  Try removing the line:
static.auto_provision.custom.sync.path

(You can tell the phone to set it to default after by doing a factory reset, or by changing the provisioning value to "=%NULL%")

From your provisioning server. The manual states:

Quote:If it is left blank, the IP phone will try to upload/download the <MAC>-local.cfg file to/from the provisioning server.

Since your provisioning server is the same as the path you were using, it should all just work.

I expect the issue is that the custom.sync.path expects a full path including filename. So if you wanted to specify it that way, you would need something like:

Code:

static.auto_provision.custom.sync.path= http://192.168.64.250/yealink/$MAC-local.cfg

That's just a guess, but it works for .boot files so might work in a normal provisioning one too. In any case it should be redundant, try leaving it undefined or set to %NULL% first and see if that fixes it.

I tried with 3 different procedures:
1. with full path static.auto_provision.custom.sync.path = http://192.168.64.250/yealink/$MAC-local.cfg
2. with static.auto_provision.custom.sync.path = %NULL%
3. with # static.auto_provision.custom.sync.path = http://192.168.64.250/yealink/$MAC-local.cfg (commenting the whole line)

Before each attempt, I did a factory reset. After phone restart, I changed Ring Tone using phone keys.

With each attempt, I saw two POST (one for initial setting, one after Ring Tone modification. Each POST looked like:
192.168.64.42 - - [08/Nov/2018:19:06:52 +0100] "POST /yealink/ HTTP/1.1" 404 470 "-" "Yealink SIP-T42S 66.84.0.10 00:15:65:bf:fd:fe"

So basically, it still does not work yet for me.