Chaps,
we deploy a large number of W52ps and Ive just discovered that our tech's are having to configure the base stations manually because auto provision does not work.
T41's work ok.
firstly the factory default has
auto_provision.pnp_enable =1, which is inappropriate for most business network, rather than domestic deployments.
Using option 66 DHCP pushes the request to the Yealink RPS and the entry there returns the correct provision host according to the logs. However the base station is not updated with the server credentials and the provision fails.
If I enter the provision credentials correctly, URL, username and password - it works ok
I get the following from the logs: (server ip address redacted.)
3 17:17:40 LIBD[509]: DCMN<6+info > Connecting rps.yealink.com:443
Nov 3 17:17:41 LIBD[509]: DCMN<6+info > Connecting IP = 184.106.101.50, Port = 443
Nov 3 17:17:41 LIBD[509]: DCMN<6+info > SSL_connect (read done)
Nov 3 17:17:42 LIBD[509]: DCMN<6+info > SSL_connect (read done)
Nov 3 17:17:42 LIBD[509]: HTTP<5+notice> response code: 302
Nov 3 17:17:42 LIBD[509]: HTTP<6+info > Content-Length: 0
Nov 3 17:17:42 LIBD[509]: HTTP<5+notice> redirect to new url
Nov 3 17:17:42 LIBD[509]: DCMN<3+error > BAD_PORT_NUMBER
Nov 3 17:17:42 LIBD[509]: HTTP<5+notice> response process finish!
Nov 3 17:17:42 LIBD[509]: HTTP<3+error > handler response error
Nov 3 17:17:42 LIBD[509]: DCMN<5+notice> Init config! libdownload Ver:5.3.0.9
Nov 3 17:17:42 LIBD[509]: DANY<0+emerg > LIBD log :sys=1,cons=1,time=0,E=3,W=4,N=5,I=6,D=7
Nov 3 17:17:42 LIBD[509]: DANY<0+emerg > DANY=7
Nov 3 17:17:42 LIBD[509]: HTTP<5+notice> URL :
http://185.62.77.56/prov/y000000000025.cfg
Nov 3 17:17:42 LIBD[509]: DCMN<6+info > Connecting 1xx.62.77.56:80
Nov 3 17:17:42 LIBD[509]: DCMN<6+info > Connecting IP = 1xx.62.77.56, Port = 80
Nov 3 17:17:42 LIBD[509]: HTTP<6+info > Request Line: GET /prov/y000000000025.cfg HTTP/1.1^M
Nov 3 17:17:42 LIBD[509]: HTTP<6+info > Host: 1xx.62.77.56
Nov 3 17:17:42 LIBD[509]: HTTP<6+info > User-Agent: Yealink SIP-W52P 25.73.23.6 00:15:65:b1:62:82
Nov 3 17:17:42 LIBD[509]: HTTP<6+info > process response
Nov 3 17:17:42 LIBD[509]: HTTP<5+notice> response code: 404
Nov 3 17:17:42 LIBD[509]: HTTP<5+notice> response process finish!
Nov 3 17:17:42 LIBD[509]: HTTP<3+error > Client error
Nov 3 17:17:42 LIBD[509]: DCMN<5+notice> Init config! libdownload Ver:5.3.0.9
Nov 3 17:17:42 LIBD[509]: DANY<0+emerg > LIBD log :sys=1,cons=1,time=0,E=3,W=4,N=5,I=6,D=7
Nov 3 17:17:42 LIBD[509]: DANY<0+emerg > DANY=7
Nov 3 17:17:43 LIBD[509]: HTTP<5+notice> URL :
http://185.62.77.56/prov/001565b16282.cfg
Nov 3 17:17:43 LIBD[509]: DCMN<6+info > Connecting 1xx.62.77.56:80
Nov 3 17:17:43 LIBD[509]: DCMN<6+info > Connecting IP = 1xx.62.77.56, Port = 80
Nov 3 17:17:43 LIBD[509]: HTTP<6+info > Request Line: GET /prov/001565b16282.cfg HTTP/1.1^M
Nov 3 17:17:43 LIBD[509]: HTTP<6+info > Host: 1xx.62.77.56
Nov 3 17:17:43 LIBD[509]: HTTP<6+info > User-Agent: Yealink SIP-W52P 25.73.23.6 00:15:65:b1:62:82
Nov 3 17:17:43 LIBD[509]: HTTP<6+info > process response
Nov 3 17:17:43 LIBD[509]: HTTP<5+notice> response code: 401
Nov 3 17:17:43 LIBD[509]: HTTP<6+info > http auth type: 2,
Nov 3 17:17:43 LIBD[509]: HTTP<6+info > Reconnect 1xx.62.77.56:80
Nov 3 17:17:43 LIBD[509]: DCMN<6+info > Connecting 1xx.62.77.56:80
Nov 3 17:17:43 LIBD[509]: DCMN<6+info > Connecting IP = 185.62.77.56, Port = 80
Nov 3 17:17:43 LIBD[509]: HTTP<5+notice> response code: 200
Nov 3 17:17:43 LIBD[509]: HTTP<6+info > Content-Length: 8440
Nov 3 17:17:43 LIBD[509]: HTTP<5+notice> response process finish!
Nov 3 17:17:45 ATP [533]: ANY <0+emerg > ATP log :sys=1,cons=1,time=0,E=3,W=4,N=5,I=6,D=7
Nov 3 17:17:45 ATP [533]: ANY <0+emerg > ANY =3
Nov 3 17:17:45 LIBD[533]: DANY<0+emerg > LIBD log :sys=1,cons=0,time=0,E=3,W=4,N=5,I=6,D=7
Nov 3 17:17:45 LIBD[533]: DANY<0+emerg > LIBD log :sys=1,cons=1,time=0,E=3,W=4,N=5,I=6,D=7
Nov 3 17:17:45 LIBD[533]: DANY<0+emerg > DANY=3
Nov 3 17:17:45 LIBD[533]: DCMN<3+error > getaddrinfo: Name or service not known
Nov 3 17:17:45 LIBD[533]: HTTP<3+error > Connect Error
Nov 3 17:17:45 ATP [533]: ATP <3+error > http to file failed, code = -1, msg = Wrong host, retry = 1
The RPS recognises the target server 1xx.62.77.58 but the subsequent dialogues seem to fail in several places. The RPS holds the credentials for the auto provision name and password. equivalent to
auto_provision.server.username
auto_provision.server.password
Chris
