Supplying login and password via DHCP option 160 (or 66)

Occasional Visitor

Supplying login and password via DHCP option 160 (or 66)

Form the (official) document bellow it seems the following would be valid:

https://provisioning.server;USER=user; PASSWORD=password

http://support.polycom.com/global/documents/support/technical/products/voice/Optimizing_Boot_Speed_o...

 

What happens in reality, according to Polycom app log, is that it tries DNS lookup on entire string, obviosly failing:

"DNS lookup failed for https://provisioning.server;USER=user; PASSWORD=password"

 

We've also tried https://user:password@provisioning.server, similar to what is being proposed here:

http://www.voip-info.org/wiki/view/Database+driven+Polycom+provisioning+with+Asterisk+RealTime

admiteddly it talks about FTP, not HTTPS.

 

In this case phone does not even try DNS lookup, as it apparently can't parse this notation as a valid URL.

 

When only URL is supplied, without credentials, provisioning works as expected.

Tried with vvx 300.

 

Questions:

Can login and password be supplied via DHCP option 160 (or 66)?

What other valid secure provisioning methods exist?

https + login/password condireded good approach to provisioning?

 

Thank you.

 

Message 1 of 2
1 REPLY
Advisor

Re: Supplying login and password via DHCP option 160 (or 66)

In our environment, on our DHCP server we specified a Server Option (inside our phone scope) of 066 Boot Server Host Name and used a string value like this:

 

ftp://poly:poly123@192.168.1.10

 

On 192.168.1.10 we have an FTP server running with a user named poly and a password as poly123 with full access to our Polycom_UC_software folder.

 

Note accounts and IP's are generic examples only.  Can't say we've worked on other protocols but ftp satisfies our requirements.  I hope it help!

 

Message 2 of 2