10-22-2013, 06:08 PM
Hello Yealink Community,
I'm trying to provision Yealink T26P from dynamically generated config file, which is sent from server as a chunked response.
Static config file can be fetched without problems:
But phone cannot fetch dynamically generated file, and it not provide much information about why exactly it cannot be fetched:
I think that Phone simply does not support Chunked transfer encoding.
Any chance that phone will support it in near future?
I'm trying to provision Yealink T26P from dynamically generated config file, which is sent from server as a chunked response.
Static config file can be fetched without problems:
Code:
autop[482]: http.c(1443): dns timeout:5
autop[482]: error.c(111): dns count:1,RetryTimes=2, Timeout=2
autop[482]: http.c(358): device mac:00:15:65:47:29:bf
autop[482]: http.c(704): UserAgent is yealink SIP-T26P 6.70.13.9 00:15:65:47:29:bf
autop[482]: http.c(3505): query header:#012GET /yealink/y000000000004.cfg HTTP/1.1#015#012Host: test.com#015#012User-Agent: yealink SIP-T26P 6.70.13.9 00:15:65:47:29:bf#015#012Accept: */*#015#012Connection: Keep-Alive#015#012#015
autop[482]: http.c(3542): ***send data***#012......
autop[482]: http.c(3650): recv header:#012HTTP/1.1 200 OK
autop[482]: http.c(2299): Server: nginx/0.7.65
autop[482]: http.c(2299): Date: Sun, 20 Oct 2013 10:21:36 GMT
autop[482]: http.c(2299): Content-Type: text/xml
autop[482]: http.c(2299): Content-Length: 361
autop[482]: http.c(2299): Last-Modified: Sat, 19 Oct 2013 20:19:26 GMT
autop[482]: http.c(2299): Connection: keep-alive
autop[482]: http.c(2299): Accept-Ranges: bytes
autop[482]: http.c(2299):
autop[482]: [./src/fileStream.cpp :972 ] IFO Open URL OK
But phone cannot fetch dynamically generated file, and it not provide much information about why exactly it cannot be fetched:
Code:
autop[482]: http.c(358): device mac:00:15:65:47:29:bf
autop[482]: http.c(704): UserAgent is yealink SIP-T26P 6.70.13.9 00:15:65:47:29:bf
autop[482]: http.c(3505): query header:#012GET /yealink/sip-t26p/y000000000004.cfg HTTP/1.1#015#012Host: test.com#015#012User-Agent: yealink SIP-T26P 6.70.13.9 00:15:65:47:29:bf#015#012Accept: */*#015#012Connection: Keep-Alive#015
autop[482]: http.c(3542): ***send data***#012......
autop[482]: http.c(3650): recv header:#012HTTP/1.1 200 OK
autop[482]: http.c(2299): Server: nginx/0.7.65
autop[482]: http.c(2299): Date: Sun, 20 Oct 2013 10:16:47 GMT
autop[482]: http.c(2299): Content-Type: text/xml
autop[482]: http.c(2299): Transfer-Encoding: chunked
autop[482]: http.c(2299): Connection: keep-alive
autop[482]: http.c(2299): Status: 200 OK
autop[482]: http.c(2299): Accept-Ranges: bytes
autop[482]: http.c(2299): Last-Modified: Sun, 20 Oct 2013 10:16:47 GMT
autop[482]: http.c(2299): Content-Lenght: 361
autop[482]: http.c(2299): Content-Disposition: attachment
autop[482]: http.c(2299): Content-Transfer-Encoding: binary
autop[482]: http.c(2299): Cache-Control: private
autop[482]: http.c(2299): X-UA-Compatible: IE=Edge
autop[482]: http.c(2299): X-Request-Id: 6b5ee4db6fee7f30f82ef1f8a534c053
autop[482]: http.c(2299): X-Runtime: 0.045505
autop[482]: http.c(2299):
autop[482]: [./src/fileStream.cpp :972 ] IFO Open URL Fail
autop[482]: [./src/autoParser.cpp :621 ] IFO Failed connect to server ! Try [1] times ...
autop[482]: [./src/autoParser.cpp :626 ] WAR Can't connect server !!
I think that Phone simply does not support Chunked transfer encoding.
Any chance that phone will support it in near future?