Poly Rove - DECT Handsets

Some links that have been useful for Poly Rove devices:

Firmware:

https://support.hp.com/au-en/deviceSearch?q=rove&origin=swd

Release Notes:

https://docs.poly.com/bundle/rove-rn-8-top/page/rove-8-rn.html

Teams Page for "Minimum" and "Approved" firmware versions

https://learn.microsoft.com/en-us/microsoftteams/devices/sip-gateway-plan

The screen shot (firmware version) above is the latest as of 7th November 2025

Migrate Poly VVX Phones from Skype/Teams to Zoom Phone

All Phones at once..

The process of migrating Poly VVX phones from Teams/Skype to Zoom Phone is a three (3) step process.

1. Configure the IP Phone within the Zoom Phone portal
2. Remove DHCP options that point to Teams/Skype provisioning server URL
3. Factory rest the IP phone, and it will complete via zero-touch provisioning

When using DHCP options to provide a provisioning server (DHCP option 160 or 161 - depending on the SKU that was used to purchase the phone).

If using DHCP options, the IP phone will pickup the provisioning server via specific option values.  If you are migrating all IP phones at once, you can just delete/clear the option within the DHCP scope/server, and factory rest the IP phones.

Staged Migration

If you are migrating phones in a phased approach, one (1) way to complete is via DHCP Policies.

Policy processing

Since you can configure multiple policies at both the scope level and server level, each policy is assigned a processing order. The processing order can also be modified, assuming more than a single policy exists. The following conditions exist:

1. When processing DHCP client requests, the DHCP server evaluates each client request against the conditions in all applicable policies, based on their processing order.

2. Scope level policies are processed first by the DHCP server, followed by server wide policies. Theoretically, a client can match the conditions of several scope policies and also several server policies.

3. If a client satisfies the conditions of more than 1 policy, it will get the combined settings from all policies that it matched. If the same option setting is provided in multiple policies, the client will use the setting from the first policy that is processed.

Poly Specific "Vendor Class Identifier"

Poly Product	Vendor Option Name
CCX350	Poly-CCX350
CCX400 (UC Software 6.2.11 or later)	Poly-CCX400
CCX500	Poly-CCX500
CCX505	Poly-CCX505
CCX600	Poly-CCX600
CCX700	Poly-CCX700
Edge E 100	Poly-EdgeE100
Edge E 220	Poly-EdgeE220
Edge E 300	Poly-EdgeE300
Edge E 320	Poly-EdgeE320
Edge E 350	Poly-EdgeE350
Edge E 400	Poly-EdgeE400
Edge E 450	Poly-EdgeE450
Edge E 500	Poly-EdgeE500
Edge E 550	Poly-EdgeE550
Edge B10	Poly Edge B10
Edge B30	Poly Edge B20
Edge B30	Poly Edge B30
VVX501	Polycom-VVX501
VVX601	Polycom-VVX601
VVX101	Polycom-VVX101
VVX150	Polycom-VVX150
VVX201	Polycom-VVX201
VVX250	Polycom-VVX250
VVX301	Polycom-VVX301
VVX311	Polycom-VVX311
VVX350	Polycom-VVX350
VVX401	Polycom-VVX401
VVX411	Polycom-VVX411
VVX450	Polycom-VVX450
VVX D230	Poly-VVX-D230
Poly Rove B DECT	IPDECT-V2/80.03.0009 (MAC=64167FF4C9ED; SER= 00000; HW=4)
Polycom Trio 8300	Poly-Trio8300
Polycom Trio 8800	Polycom-Trio8800
Polycom Trio 8500	Polycom-Trio8500
Polycom RealPresence Trio Visual+	Polycom-TrioVisualPlus
Polycom Trio C60	Poly-TrioC60
SoundStation IP 5000	Polycom-SSIP5000
SoundStation IP Duo	Polycom-SSDuo

A DHCP policy will need to be created that matches, both the MAC Address and the Vendor Specific option listed above.

The assisted provisioning server from Zoom outlines the value required for options 160 or 161.

Assisted provisioning URLs - Poly

Polycom VVX Timestamp

After some digging around today to try and find what the format of the time stamp from the Polycom VVX model IP Phones, so figured that I would do a quick post so that I can find it next time.

The time stamp is in the format MMDDHHMMSS

In my log file I have:
1008042609|cfg |*|00|Prov|Starting to provision

From the above format, this was written to the log on the 8th October at 4:26:09 AM

I found the details at the following site:
http://community.polycom.com/t5/VoIP/FAQ-How-can-change-Logging-Levels-or-use-Syslog/td-p/4741

Polycom VVX and Lync Server

So I have been playing around with the Polycom VVX IP Phones more and more lately and with the new features that are coming in the next few months I think this could become the go-to phone for Lync deployments that need IP Phones on the desk.

So of the features that I like include:

• Touch Screen for user authentication
• Ability to us Lync PIN number for authentication
• With UC Software release 4.1 or better the address book is downloaded to the phone, so no need to do anything with number normalisation/dial plans on the VVX phone
• Retrieve Lync server root certificate automatically using DHCP Option 43

Currently to upgrade the phone you can either do it manually (not a problem is you only have a few phones) or can use a provisioning server.  The provisioning server, from what I have found can be:

• FTP (Default)
• TFTP
• HTTP
• HTTPS
• FTPS 

To define the host for your provisioning server you can use DHCP option 66 (Boot Server Host Name) option 66 is a string value, by default the VVX phones will use FTP to download the configuration file and any firmware updates.

The default username and password for the VVX phones to use for the FTP session is defined within some of the Polycom support documents, OR you can use the same DHCP option 66 with the format "username:password@FTP Server IP/Hostname", without the quotes, this will allow you to define the username and password.  One word of warning this username and password is passed via clear text in the DHCP messages so it can easily be found.

Some Polycom pages that i found useful include:

• Deployment Guide for the Polycom VVX C Business Media Phone for CUCM (SIP)
• Technical Bulletin 54041
• Polycom ® UC Software/Polycom SIP Software Release Matrix