Getting Started
UDM Pro Quick Start Guide
How to get up and running quickly with UDM Pro
1 Security
- Make sure you have changed the password on the admin account to something secure
- Create user accounts for the people who will be using UDM Pro
2 Settings
- Make sure Zero Touch Registration is enabled
- If you want your phones to be enabled and provisioning as soon as they connect to the bridge enable Zero Touch Approval. If this is not enabled new phones will go into the Unapproved Devices group and will need to be manually approved before full provisioning of the device.
3 Locations (groups of subnets)
Using locations to apply device configurations on a location by location basis can be a very powerful tool. If you intend to apply different configurations based on locations you can add some at this point for testing. A location can be a geogrqaphical site or something logical such as a floor in a building. Locations are best thought of as a group of subnets which you wish to use for provisioning.
- Add the Name of the site and any other descriptive information you require.
- If you enter the timezone of the site you can also enable the Auto-Set Timezone option which will create a device profile and apply it to the location.
- If you want to use the Location for applying device profiles ensure the Tag is enabled.
- Add the subnets for the Location either manual or by importing a test file with the subnet details. The subnet is entered in CIDR format xxx.xxx.xxx.xxx/yy E.g. 192.168.1.0/24
- During this initial stage do not enter anything in the other sections: Device Profiles Speed Dial etc
4 Install the provisioning bridge
Follow the instructions on UDM Pro Bridge Installation page
- Ensure it is present in the Bridges screen
- Status is approved
5 Software/Firmware
Upload the latest firmware you wish to use. This can take some time and as you shouldn't leave the window until it is complete you may want to do this at the beginning.
6 Optional: Upload resources
If you intend to using pictures or audio files in your configurations you should upload them now so they are available when you setup your Device Profiles in the next step.
7 Setup Device Profiles.
There are two extremes of setting up Device Profiles, Medium/Large global profile with some small override profiles or just using small single function profiles. For new users or for initial testing we recommend using the small override profiles as the basis of setting up your phones.
There are several preloaded device profiles and in a lot of cases you can use these for your small profile collection. A small number of the preloaded profiles may need some changes before using so check them before using them. For example if you want to integrate with Exchange you will need to edit the Polycom_exchange_Server profile. We would recommend you clone a copy of the file and use this. In this profile the exchange.server.url will need to be set to your Exchange server EWS URL. You may also want to enable or disable some of the features in the profile.
If you want to use an existing xml configuration file you have for most your phones. Create a new device profile and import this file. You can call this something like Global Profile.
8 Optional: Setup Speed Dials
If you want to use speed dials you can setup some speed dials at this time/
9 Tags
Tags are how we want the profiles to be applied to your devices. When you start if you enabled Zero Touch Registration then you will see at the top a Tag already on the system called Approved Devices. This Tag allows you to apply the Device Profiles you want to use for all your devices. If Zero Touch Registration was not enabled there is also a Tag called Unapproved Devices. The Unapproved Devices Tag is the only Tag that will be applied to devices that are in an unapproved status.
Some ideas of what to put in the tags:
If you are using the Unapproved tag we would suggest the following Device profiles:
Device Profile Name | Description |
Polycom_checksync_alwaysreboot_enabled | Enable the phone to be remotely rebooted by UDM Pro. Note on newer versions of the Polycom UC (skype) firmware this option no longer works. You will need to create a Device Profile to enable the REST API for rebooting only one value is required apps.restapi.enabled set to Yes (1). |
Polycom_webServer_enabled | Optional: Enable the Phone Web Server for remote access by an administrator through a web browser. |
Polycom_Security_AdminPassword | Change the phones Admin Password (Note: you will need to change the default password in the Device Profile to a new value up to 32 characters) You may also want to create a Device Profile to change the User Password on the phone as well. |
You can also create a new tag with a background image to indicate to users that the device is not currently setup for operation.
In the Approved tag we would suggest the following Device profiles:
Device Profile Name | Description |
Polycom_checksync_alwaysreboot_enabled | Enable the phone to be remotely rebooted by UDM Pro. Note on newer versions of the Polycom UC (skype) firmware this option no longer works. You will need to create a Device Profile to enable the REST API for rebooting only one value is required apps.restapi.enabled set to Yes (1). |
Polycom_webServer_enabled | Optional: Enable the Phone Web Server for remote access by an administrator through a web browser. |
Polycom_Security_AdminPassword | Change the phones Admin Password (Note: you will need to change the default password in the Device Profile to a new value up to 32 characters) You may also want to create a Device Profile to change the User Password on the phone as well. |
Polycom_Lync_baseprofile | Only Required if you are using the phone with Lync or Skype for Business |
Polycom_provisioningPolling_daily_enabled | This enables the phone to check for new configuration changes each night between 23:30 and 01:30. You can create a new Device Profile if you would like a different schedule. Once you have completed testing, in most cases in a stable environment once a week would be sufficient. |
For performance purposes disabling the sending of calls logs can be useful. These logs list the calls made, received or missed if you already record this information in your PBX/Skype system then you should setup a tag to disable this:
"feature.callList.enabled" set to No (0).
Minimizing phone logging can also improve performance by reducing the size and frequency of the log files being sent:
"log log.render.level" set to 6 (this logs critical errors only)
"log.render.file.upload.append.sizeLimit" set to 128
If you are looking for other options that may be of interest Greig Sheridan has an interesting blog post on some useful settings especially if you have offices outside of the USA. The settings are updated from time to time so worth checking back at https://greiginsydney.com/optimising-the-polycom-vvx-for-lync/
NOTE: If you are using Skype for Business Online or have enabled in-band phone settings for your Skype for Business server you will get the provisioning server options set back to FTP continually. This stops the phone from getting its configuration from UDM Pro. If this is the case we recommend creating a Device Profile with the following three parameters, then apply this to the All Devices and Approved Devices Tag in the Tags screen.
"lync.provisionDeviceParams.enabled" set to No (0).
"device.prov.lyncdeviceupdateenabled" set to No (0).
"device.prov.lyncdeviceupdateenabled.set" set to Yes (1).
"device.prov.upgradeServer.set" set to Yes(1)
"device.prov.upgradeServer" set to null/blank ""