Plantronics + Polycom. Now together as Poly Logo

Polycom DHCP Options VVX600 and Infoblox option 66 or 161 Not working?

Occasional Contributor

Polycom DHCP Options VVX600 and Infoblox option 66 or 161 Not working?

Polycom Community,
                     Recently we have been manually configuring our polycom VVX600s and pointing them to our provisioning server. We are using Infoblox as our DHCP Server and putting in 

 

Option 66/161/160 ftp://pftp:Randompassword1234@10.0.0.0(ipaddress of FTP Server) the phones aren't seeing this

 

We have option 42 for our time server configured as our DC for time and the phones still don't have the correct time. 

 

 Option 3 we have the web server FQDN configured as the web internal fqdn but as hex  servername.domain.domain.com

 

Option 120 is our SBA converted into hexadecimal Servername.domain.domain.com

 

Option 4 web server port 443 converted

 

Option 5 /certprov/certprovisioningservice.svc converted to hex

 

Even after all of these configurations the phones aren't seeing the options. We have checked the firewall to make sure its not blocking FTP but that's not the case. The phones aren't even seeing the options. We have also checked inside of the phone in the web gui to see what option it's reading. We have moved and changed the options in the phones to see if they can read 161, 160, or 66 and none have seemed to work. Not sure what could be causing this. We have also each once checked the options over and have cleared and reboot the phones. When we manually provision the phones they reach the FTP server no problem. 

 

 UC Software Version 5.5.0.205556
Updater Version 5.7.18267

Lync 2013 

Sonus SBC 1000/2000

 

3 REPLIES 3
Polycom Employee & Community Manager

Re: Polycom DHCP Options VVX600 and Infoblox option 66 or 161 Not working?

Hello mekadaniels,

welcome to the Polycom Community.

It is always useful to include the currently used UC Software version as issues experienced or a question asked may already be addressed in a newer release.

Please also include if you are using a SIP server or a LYNC / Skype for Business server.

This also allows yourself and others to check against current software release notes, Administrator Guides or FAQ post’s.

The above is also stated in the "Read First"

Therefore the Polycom VoIP FAQ contains this post here:

Question: How can I find out my SIP or UC Software Version of my Phone?
Resolution: Please check here

 

Use a spanned / mirrored port and use this:

 

Aug 24, 2015 Question:What basic network data is send and received by a Polycom phone?

Resolution: Please check this post => here <=


Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services




<======== Signature / Disclaimer ========>
Please be aware:For questions about the type of support to expect please check here

Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's

Please remember, if you see a post that helped you , and it answers your question, please mark it as an "Accept as Solution".

The title Polycom Employee & Community Manager is an automatic setting within the community and any forum reply or post is based upon my personal experience and does not reflect the opinion or view of my employer.
Poly employee participation within this community is not mandatory and any post or FAQ article provided by myself is done either during my working hours or outside working hours, in my private time, and maybe answered on weekends, bank holidays or personal holidays.
Message 2 of 4
Occasional Visitor

Re: Polycom DHCP Options VVX600 and Infoblox option 66 or 161 Not working?

Did you ever get a resolution to this issue?  We are haveing the same problem with VVX201 phones and Infoblox.

Message 3 of 4
Occasional Contributor

Re: Polycom DHCP Options VVX600 and Infoblox option 66 or 161 Not working?

Yes we were able to get this set up for us. We had the options put in infoblox but the Voice VLAN wasn't set up properly. Also checking if the ports are configured properly as well. - Meka

Message 4 of 4