[YMCS/YDMP Free Trial Program]Yealink would like to offer Free Trial Program of Yealink device management service for our current eligible customers. You can see the details below.
https://www.yealink.com/ydmp-freetrial-2020


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Ni file name in POST URLs [Was: How exactly are -local.cfg files POSTed to server ?]
Author Message
oliv Offline
Member
***

Posts: 63
Joined: Feb 2016
Reputation: 0
Post: #1
Ni file name in POST URLs [Was: How exactly are -local.cfg files POSTed to server ?]
Hello,

I'm testing latest 66.83.0.10 firmware's local settings uploading.
My phone config includes:
static.auto_provision.server.url = http://192.168.64.250/yealink
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 = http://192.168.64.250/yealink

When a phone boots, it tries to download a <MAC>-local.cfg file with request (as printed in /var/log/apache2/access.log file) such as:

192.168.64.42 - - [04/Apr/2018:10:46:01 +0200] "GET /yealink/001565bffdfe-local.cfg HTTP/1.1" 200 228 "-" "Yealink SIP-T42S 66.83.0.10 00:15:65:bf:fd:fe"

When I change a setting using phone keyboard, I can see the sending a POST request such as :

192.168.64.42 - - [04/Apr/2018:10:46:01 +0200] "POST /yealink/ HTTP/1.1" 404 470 "-" "Yealink SIP-T42S 66.83.0.10 00:15:65:bf:fd:fe"

I would expect my phone to POST to the same /yealink/001565bffdfe-local.cfg URL.

Are my expectations correct ?
Can you upload a <MAC>-local.cfg file to a simple Apache2-enabled HTTP server or do you have to back this server with something else (PHP, ...) ?

Best regards
04-04-2018 08:55 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Samuel_Yealink
Unregistered

 
Post: #2
RE: Ni file name in POST URLs
Hi Oliv,

Sorry for replying late, yes you are right, when you change the configuration, the changes will be posted to the same MAC-local.cfg file.

For auto provisioning, normally we can use a simple HTTP server, so your Apache-enabled HTTP server is OK.

KR
Samuel Wang
04-17-2018 02:52 AM
     Quote this message in a reply
oliv Offline
Member
***

Posts: 63
Joined: Feb 2016
Reputation: 0
Post: #3
RE: Ni file name in POST URLs
(04-17-2018 02:52 AM)Samuel_Yealink Wrote:  Hi Oliv,

Sorry for replying late, yes you are right, when you change the configuration, the changes will be posted to the same MAC-local.cfg file.

For auto provisioning, normally we can use a simple HTTP server, so your Apache-enabled HTTP server is OK.

KR
Samuel Wang
Thank you very much, Samuel, for replying.

So, would you say this is a bug and I should see, in my /var/log/apache2/access.log file something like:
192.168.64.42 - - [04/Apr/2018:10:46:01 +0200] "POST /yealink/001565bffdfe-local.cfg HTTP/1.1" 404 470 "-" "Yealink SIP-T42S 66.83.0.10 00:15:65:bf:fd:fe"

If positive, is there something more to be done, to have this issue tracked, and hopefully worked on ?

Best regards
04-19-2018 01:16 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Samuel_Yealink
Unregistered

 
Post: #4
RE: Ni file name in POST URLs
Hi Oliv,

I don't think it is a bug, because it doesn't affect the phone from doing the auto provisioning. Indeed it is a good question why the log of the POST doesn't include the specific path, I will check this with R&D later.

The whole process of auto provisioning is as linked below,

http://download.support.yealink.com/down...V83_10.pdf
04-20-2018 02:19 AM
     Quote this message in a reply
oliv Offline
Member
***

Posts: 63
Joined: Feb 2016
Reputation: 0
Post: #5
RE: Ni file name in POST URLs
(04-20-2018 02:19 AM)Samuel_Yealink Wrote:  I don't think it is a bug, because it doesn't affect the phone from doing the auto
Yes and no, Samuel.

As you may know, Apache2 server by itself, does not support PUT method. So, if I'm not mistaken, if you want save phones local settings on an Apache2-enabled provisioning server, you need phones to support saving local settings through POST method.

So, I would be very curious to ear about this from R&D or whoever is interested in this topic.
04-20-2018 06:51 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
oliv Offline
Member
***

Posts: 63
Joined: Feb 2016
Reputation: 0
Post: #6
RE: Ni file name in POST URLs
(04-20-2018 02:19 AM)Samuel_Yealink Wrote:  Hi Oliv,

I don't think it is a bug, because it doesn't affect the phone from doing the auto provisioning. Indeed it is a good question why the log of the POST doesn't include the specific path, I will check this with R&D later.

The whole process of auto provisioning is as linked below,

http://download.support.yealink.com/down...V83_10.pdf
Hi Samuel,

Any update on this one ?
Testing today with 84.10 firmware, I can still see lines with missing file name in URL such as:
192.168.64.42 - - [08/Nov/2018:13:32:43 +0100] "POST /yealink/ HTTP/1.1" 404 470 "-" "Yealink SIP-T42S 66.84.0.10 00:15:65:bf:fd:fe"
11-08-2018 12:37 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
jolouis Offline
Moderator
*****

Posts: 339
Joined: Oct 2013
Reputation: 5
Post: #7
RE: Ni file name in POST URLs
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.
11-08-2018 04:18 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
oliv Offline
Member
***

Posts: 63
Joined: Feb 2016
Reputation: 0
Post: #8
RE: Ni file name in POST URLs
(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.
11-08-2018 06:15 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
jolouis Offline
Moderator
*****

Posts: 339
Joined: Oct 2013
Reputation: 5
Post: #9
RE: Ni file name in POST URLs
Strange... I've got a T41S here, if I have time this afternoon I'll try to replicate and see what I get on this end.
11-09-2018 01:58 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Post Reply 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  Local Contacts Restore Problem ipcsolutions 0 51 07-28-2020 11:16 AM
Last Post: ipcsolutions
  Is it possible to set auto_provision.server.url via a servlet call? scully 2 602 05-01-2020 01:53 PM
Last Post: richardoux
  Remote configuration overwriting local configuration cdesbouche 1 658 04-11-2020 05:58 PM
Last Post: complex1
  [REQ] Translatable language files FrankDRNS 3 865 02-19-2020 08:31 AM
Last Post: complex1
  Push.xml to setup action urls via YealinkIPPhoneConfiguration? nSolvePaul 0 403 01-22-2020 01:47 PM
Last Post: nSolvePaul
  y000000000000.boot and encrypted config files kapetrosyan 6 1,482 01-17-2020 11:22 PM
Last Post: kapetrosyan
  Boot files and wildcards? starion 1 733 09-23-2019 04:03 PM
Last Post: jolouis
  need complete list of yealink rps server IP's for firewall DanH 1 1,510 07-26-2019 07:00 AM
Last Post: Ted_Yealink
  How to erase a parameter using autoprovision file Santi 1 1,195 06-21-2019 10:25 AM
Last Post: complex1
  Local Phonebook autoprovision Aber 6 3,692 06-11-2019 01:55 AM
Last Post: Aber

Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us   Yealink   Return to Top   Return to Content   Lite (Archive) Mode   RSS Syndication