-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Poly Phones
- UC Platforms
- Re: VVX410 wont automatically provision/update firmware/conf...
Create an account on the HP Community to personalize your profile and ask a question
04-06-2016 11:23 AM
Hi,
I have deployed a FileZilla provisioning server. I have DHCP configured on my network. If I boot up a VVX500 or VVX600 it will boot up, automatically begin downloading new UC Software / Firmware if a newer version is available, pull the configuration file, everything works accordingly. When I boot up a VVX 410 in the same scenario, it doesn't seem to automatically provisionion. The phone will boot up successfully in it's default configuration. If I manually define a provisioning server the phone will reboot, pull new UCS Software / Firmware, do it's configuration, and everything is fine. What can I do to make it work by default? My hunch is i am missing something in my master configuration file.
Thanks
-Matt
Here is my master configuration file (000000000000.cfg)
<?xml version="1.0" encoding="utf-8" standalone="yes"?> <!-- Default Master SIP Configuration File--> <!-- For information on configuring Polycom VoIP phones please refer to the --> <!-- Configuration File Management white paper available from: --> <!-- http://www.polycom.com/common/documents/whitepapers/configuration_file_management_on_soundpoint_ip_phones.pdf --> <!-- $RCSfile$ $Revision: 135829 $ --> <APPLICATION APP_FILE_PATH="software/release/sip.ld" CONFIG_FILES="configuration.cfg, qos.cfg" MISC_FILES="" LOG_FILE_DIRECTORY="logs" OVERRIDES_DIRECTORY="overrides" CONTACTS_DIRECTORY="contacts" LICENSE_DIRECTORY="" USER_PROFILES_DIRECTORY="" CALL_LISTS_DIRECTORY="calls"> <APPLICATION_SPIP300 APP_FILE_PATH_SPIP300="sip_213.ld" CONFIG_FILES_SPIP300="phone1_213.cfg, sip_213.cfg" /> <APPLICATION_SPIP500 APP_FILE_PATH_SPIP500="sip_213.ld" CONFIG_FILES_SPIP500="phone1_213.cfg, sip_213.cfg" /> <APPLICATION_SPIP301 APP_FILE_PATH_SPIP301="sip_318.ld" CONFIG_FILES_SPIP301="phone1_318.cfg, sip_318.cfg" /> <APPLICATION_SPIP320 APP_FILE_PATH_SPIP320="sip_334.ld" CONFIG_FILES_SPIP320="" /> <APPLICATION_SPIP330 APP_FILE_PATH_SPIP330="sip_334.ld" CONFIG_FILES_SPIP330="" /> <APPLICATION_SPIP430 APP_FILE_PATH_SPIP430="sip_327.ld" CONFIG_FILES_SPIP430="phone1_327.cfg, sip_327.cfg" /> <APPLICATION_SPIP501 APP_FILE_PATH_SPIP501="sip_318.ld" CONFIG_FILES_SPIP501="phone1_318.cfg, sip_318.cfg" /> <APPLICATION_SPIP600 APP_FILE_PATH_SPIP600="sip_318.ld" CONFIG_FILES_SPIP600="phone1_318.cfg, sip_318.cfg" /> <APPLICATION_SPIP601 APP_FILE_PATH_SPIP601="sip_318.ld" CONFIG_FILES_SPIP601="phone1_318.cfg, sip_318.cfg" /> <APPLICATION_SPIP670 APP_FILE_PATH_SPIP670="sip_403.ld" CONFIG_FILES_SPIP670="" /> <APPLICATION_SSIP4000 APP_FILE_PATH_SSIP4000="sip_318.ld" CONFIG_FILES_SSIP4000="phone1_318.cfg, sip_318.cfg" /> <APPLICATION_SSIP6000 APP_FILE_PATH_SSIP6000="sip_404.ld" CONFIG_FILES_SSIP6000="" /> <APPLICATION_SSIP7000 APP_FILE_PATH_SSIP7000="sip_403.ld" CONFIG_FILES_SSIP7000="" /> </APPLICATION>
Solved! Go to Solution.
Accepted Solutions
04-07-2016 01:36 PM
Matt, all the VVX phones use the initial <APPLICATION> tag to find their configuration information so if it's working for one phone then it'll work the same for all models.
My best guess is that the 410 is not getting the provisioning server location due to it being a different SKU than the other phones which will look at a different custom DHCP Option for the provisioning server URL. You may be using DHCP Option 160 and the phone that is not working is looking at 161 bt default, or vice versa.
Take a look at the customer configuration on the phone to insure that the same customer value is configured on all phones.
04-07-2016 01:36 PM
Matt, all the VVX phones use the initial <APPLICATION> tag to find their configuration information so if it's working for one phone then it'll work the same for all models.
My best guess is that the 410 is not getting the provisioning server location due to it being a different SKU than the other phones which will look at a different custom DHCP Option for the provisioning server URL. You may be using DHCP Option 160 and the phone that is not working is looking at 161 bt default, or vice versa.
Take a look at the customer configuration on the phone to insure that the same customer value is configured on all phones.
07-29-2016 03:26 AM
Sorry but can you eplain me why our 200 & more old VVX500 automatically get the DHCP option 160 and the new ones we have just receive doesn't work ?
What I have to do if I don't want to set option 161 for new phones ?
07-29-2016 04:27 AM
Hello Doum,
welcome back to the Polycom Community.
The "original" Polycom provisioning method prior to introducing separate LYNC / Skype for Business Hardware was always Option 160 and then fall back to Option 66.
Since the introduction of the separate LYNC / Skype for Business Hardware we utilize Option 161 and then fall back to Option 66.
This ensures that customer using the VVX phones for SIP whilst moving to LYNC / Skype for Business can do this seamlessly.
In order to change this you need to pre-provision the phone using device.set parameters to change the DHCP Option.
device.set device.dhcp.bootSrvOpt.set="1" device.dhcp.bootSrvOpt="160"
Please remember that for the 200+ Phones you already use with LYNC / Skype that you require the relevant per phone Licenses from Polycom.
Your known Sales Engineer can be consulted for any follow up questions.
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
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
07-29-2016 05:42 AM
Hello Doum,
yes, simply copy the Option 160 and create a Option 161 as well.
Please ensure you have the relevant licenses for the phones not in LYNC SKU.
Best Regards
Steffen Baier
Polycom Global Services
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
Didn't find what you were looking for? Ask the community