Current Publication | x
Close

Configure Your Phone Management Settings

You can configure the following phone settings from the Endpoint > Phone Management > Phone Management Settings page:

Digest Password for CUCM Synced Phones: After you integrate with a Cisco Unified Communications Manager, the digest password for the phones is reset to the factory default unless you change this password. You can also customize the digest user passwords for the phones.

Provisioning Account Configuration: The HTTP or HTTPS service is used for the provisioning connection between the RealPresence Resource Manager system and the phones. By default, a system-generated user name and password are used by the phones during the process to get provisioning profiles and software updates from the RealPresence Resource Manager. Each phone uses the same HTTP or HTTPS service password. The default user name and password are both PlcmSpIp.

You can change this password at any time. After you change the password, you need to configure the phones to use the same HTTP or HTTPS password. Otherwise, the phones will not be able to connect to the RealPresence Resource Manager system to receive provisioning profiles and software updates.

.

 

If phone communicates with RealPresence Resource Manager via HTTPS, you should ensure that the phone(s) can validate the RealPresence Resource Manager system’s security certificate. For more information about certificates RealPresence Resource Manager system certificates, see Security Certificates.
For information about certificates for Polycom phones, see the respective UC Software Administrator Guide.

Phone Files Rotation Settings: You can control the disk space that the uploaded configuration and log files occupy in the RealPresence Resource Manager system. The default values rotate the log files every 1024 KB and keep up to five files for 15 days.

The logs are saved in the /var disk. When the /var disk 90% occupied, the system will clean the logs automatically. For example, if the Days to Retain Phone Files value is 15 days, when the /var disk 90% occupied, the system will clean the logs saved on the first day. If the /var disk still 80% occupied, the system will keep cleaning the logs saved on the second day.

Maximum Disk Space for Resource Files: You can set a upper limit to the size of the uploaded resource files. When the size of the uploaded resource files reaches the specified size, you will not able to upload more files. You need to remove some unused resource files first.

Upload Default XSD: The RealPresence Resource Manager system comes with a default XSD (Polycom RealPresence Trio 5.4.4.7609) file that contains phone configuration elements that you can use. You also can make your own XSD file to include more customized phone settings and upload the XSD file to the system to overwrite the default file.

See Polycom UC Software Administration Guide for details on XSD files and how to download XSD files.

To configure phone management settings:

1 Go to Endpoint > Phone Management > Phone Management Settings.

2 To change the digest password for phones synced from Cisco Unified Communications Manager:

a In the Digest Password for CUCM Synced Phones section, clear the Use System Auto Generated Password check box.

b Complete Password and Confirm Password fields.

3 In the Maximum Disk Space for Resource Files section, enter a maximum size and click Update.

The supported range of the maximum size is: 50MB - 250MB

4 In the Phone Files Rotation Settings section, change the settings as needed and click Update.

The range of the settings is:

Ø Log File Rotation Size: 512KB - 10240KB

Ø Number of Retaining Files (per name): 1 - 10

Ø Days to Retain Phone Files: 0 - 30

5 To configure the provisioning account, in the Provisioning Account Configuration section, edit the User Name or the Password.

6 To upload a XSD file, in the Upload Default XSD section, browse to the XSD file and click the Upload button.

7 Click Update.

Related Topics

Related Topics

Machine Translation

You are cautioned that the translation of this document is generated by a machine; therefore, the translated document may have errors and be inconsistent with the original English language version of the document.

The English language version of this document shall be considered the governing document related to the Polycom product.

If there is any contradiction between the English language version of the document and the translated version of the document, the English language version of the document shall take precedence.

The translation is provided for your convenience only. Neither Google nor Polycom shall be responsible for translated content or for the performance of the translation tool. If you require further assistance on non-translation issues, please contact Polycom support.

Translated documents are not available in PDF format.