Configuring the Provision Server to setup Polycom VVX devices to support Lync

Recently i got the opportunity to deal with Polycom VVX devices that need to be configured to work with Lync Server 2013. My first experience, I’ve noticed that the VVX devises are not really ready to be signed in with a Lync user account right out of the box. In fact, there were several tings that need to be addressed before the devices putting in to production. This includes,

  • Devices comes up with “Generic” profile other than “Lync” profile.
  • Dialed numbers and inbound CLI presentation shows up as the full SIP URI (
  • In the Directory, there are two different directories, “Contact Directory” and  “Lync Directory” which can be confusing

All those issues that i mentioned above can be addressed by using a Provisioning server. Provisioning will centrally control all devices and keep the configuration identical on all VVX devices that are running. I’m not going to cover the steps to deploy the Provisioning Server in this thread. Jeff Schertz has written a nice article explaining how to deploy the provisioning server ( To get started with the issue #1, The devices need to be configured so that when they plug in to the network, it has to come up with the “Pin Authentication” option so that a user can sign in using the extension and PIN Number. to do this, I’ve used the device.cfg file that comes with the Firmware bundleCapture

open up the device.cfg file using XML Editor and set the parameters as mentioned in below snapshot. device cfg

Save the configuration and copy the .cfg file from  “Configuration” folder to the FTP Root directoryFolder

then, open up the 00000000000.cfg file from XML Editor and set the CONFIG_FILES as mentioned in snapshot below. maser cfg file config

After that, reset the device to factory (so that it will revert the base profile configuration). When it boots up, it should come up with the Lync profile and ask to enter the phone number and the PIN.

And moving back to the issue #2, Most of the time the end users are willing to put up with this as they can actually see the “Number” showing up on the display and don’t really care that it’s in wired format. But if it’s a migration from a traditional PBX, users will notice this immediately and ask to fix it.

This is a feature that comes with the VVX device call “SIP URI Dialing” when it turned on, the inbound calls will looks like below,  

And the issue #3, This might not be an “Issue” but a preference for most of the users. The “Contact Directory” is there so that the end users can specify numbers locally on the device. but in lync, users can have local contacts maintain on Outlook and get Lync to dial out and this makes “Contact Directory”

To fix both of this “Issues”, i used the Features.cfg file form the “Config” folder. Open the file with XML Editor and set the parameters as mentioned in below snapshot. Delete the rest of the parameters from the file as they are not in use.Features cfg   Move the .cfg file in to the FTP root. Open up the Master configuration file (0000000000.cfg) and set the CONFIG_FILES as mentioned below in snapshot.maser cfg file config

Restart the device and go to the “Menu”. Select Settings>Status>Phone>xxxx and check if the configuration files are populated.

Make several test calls and see if the number presentation shows properly with just the Number and not the URI bits.

And check the “Directory” and verify that the “Contact Directory” is no longer there and only the “Lync Directory”, “Contacts” and “Recent Calls” are there.photo3

That’s about it. Good luck setting up the Provisioning server and post below, if there are any issues. Thanks.