The objective of this short overview is to explain briefly how to setup a Poly RealPresence ResourceManager 10.1 or later to support Poly Phone provisioning.
A great video detailing this can be found => here <=
NOTE: Please contact your Poly reseller or Poly Sales Engineer for a proof of concept and access to any ISO’s or OVA files or licenses required to set this up!
The Poly RPRM supports Hyper-V or VMware or a physical Dell server.
If the password was changed from the above standard PlcmSpIp the DHCP option can also include the new password.
NOTE: If the password as an example contains an @ please replace this with %40 instead.
http://Username:%40123$@IP_Address or URL/phoneservice/configfiles/
The above would use @123$ as the password or the phone would interpret the @Symbol as the separator between the password and the IP Address or URL.
Note: In order to use HTTPS please add a certificate to the RPRM or disable Common Name Validation on the Phone end. Poly Phones out of the box automatically trust the Certificates listed in the Certificate Updates documents posted regularly => here <=. The phone could initially be provisioned via HTTP and then once it loads its configuration via the RPRM a certificate for HTTPS could be provisioned.
Devices can be imported and re-imported to change associated groups in bulk without changing other configurations.
Once the phone is connected to the RPRM provisioning Server the Web Interface or Admin Password for the Phone changes to 789.
This can be changed by browsing to Endpoint > Phone Management > Configuration Profile and copying the AdminPassword-ProvisioningDefault.
This would then be required to be assigned to a Global Configuration within Endpoint > Phone Management > Profiles Deployment.
Added phone(s) can now be found via Endpoint > Monitor View
Selecting an individual phone:
Will provide access and details to configuration used or log files:
Get or Set Configuration Parameters
Via Endpoint > Monitor View > More > Get/Set Parameters a device can be checked to what value a parameter has been set:
Using the above will store the value within the phones <PHONE_LOCAL section. This will appear as made locally on the phone as explained => here <=
Software Updates via RPRM
Via Endpoint > Phone Management > Upload Software Updates Software can be added.
Usually, you would select the Poly hosted Server and create a new configuration profile based on the software version as this allows you to assign this to an existing or new configuration profile via Endpoint > Phone Management > Configuration Profiles
Apply versus OK
Throughout the application you will see Apply and OK appear in regards to Configuration Profiles and Group Memberships.
Will save the changes and devices that are impacted of the changes will be notified at the next polling period for the affected devices.
Will Save the changes and immediately notify all devices that are reachable that there are changes that need to be applied immediately.A Pop-up notification is provided to confirm this action as it will generally always reboot the phone(s). Always be aware of your context when applying changes
As a factory default when provisioning a Poly phone from RPRM the Phone will check daily between 03:00 and 05:00 for any configuration changes.
In order to change this you would copy Provisioning-Polling-Daily-SpecificWindow within Endpoint > Phone Management > Configuration Profiles and change the time to suit your setup and then assign to a profile.
Endpoint Monitor – Device Status
Via Admin > Maintenance > Troubleshooting Utilities several Troubleshooting Options are available
Advanced Functions – Global/Model/Site
Reboot Phones – All phones within the selected scope will be rebooted as long as they are not isolated behind a NAT’d device.
Gathering Logs in order to supply Poly Support:
Navigate to Endpoint > Monitor View and select an Endpoint and click on "View Details"
As a result on the left side an overview of all the Device Details are listed and all files can be downloaded:
Or simply individual Log Files:
In addition the amount of log files and the individual size can be modified to cover a longer time period.
Endpoint > UC Management > UC Management Settings
Endpoint Monitoring and Alerts
Start out with setting the Alert > Alert Level Settings
In the above example, we set the Heartbeat Timeout, to critical.
Set a new Remote Alert Profile
and either enabled in General Info and set all Resource Manager alerts and send the trap assigned
Or instead set this for VVX, SoundStation, SoundPoint and Trio again for Minor, Major and Critical in device type
The next step is to assign this to a specific User > Users as an example:
Ensure the relevant User has a valid Email address within General Info.
and ensure to chose the Associated Alert Profile previously created
The final step is to ensure the SMTP Server is set up correctly via Admin > Server Settings > E-mail:
Note: The SMTP Mail Server must support to send emails without authentication!
Or set up SNMP via Admin > Server Settings > SNMP Settings instead:
More details can be found => here <=