This document describes a problem that is encountered when an automatic change occurs in the configuration of a Cisco TelePresence Endpoint after it is integrated with a Cisco TelePresence Management Server (TMS).
There are no specific requirements for this document.
The information in this document is based on a Cisco TelePresence endpoint that runs Cisco TelePresence Codec (TC) software or MXP and TMS.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any configuration.
The endpoints that are added to the TMS encounter a configuration reversion to unknown values every night or at random times. There can be multiple reasons for these configuration changes on the endpoint. The issue that occurs when the configuration reverts is due to either a codec reboot or a TMS reprovision of the endpoint.
You must verify whether the changes are made by the TMS or completed manually by the user.
This log snippet shows an output that can be observed when the change is made by the user admin:
ppc appl[2743]: 854597.29 CuilApp User admin(1001) successfully changed
configuration 'Config/H323/Profile[1]/CallSetup/Mode' to 'Direct'
from 64.X.X.X.
As shown in the output:
It is important that you verify the IP address. Refer to the sections that follow in order to troubleshoot the issue when the IP address is that of a TMS, which confirms that the TMS made the configuration change.
This section describes two possible causes for this issue.
For the examples that are described in this document, a change in the H323 call setup to the Gatekeeper on the endpoint is made manually; however, the backup on the TMS is set to Direct.
After you have determined the endpoint for which the configuration is reverted, go to the TMS web interface and navigate to the specific endpoint:
Here is an image for reference purposes:
The TMS restores the configuration on the endpoint when it restores the backup, which causes the issue.
Another possible reason for the configuration change can be some persistent configuration settings on the TMS for the endpoint.
Verify whether you have any configuration template that has been configured and applied to the endpoint as a persistent template.
Complete these steps in order to verify the configuration template:
If the endpoint is listed, then remove the persistent settings template or the configuration. You can also edit the persistent configuration as required.
This section provides solutions to the problem causes that are described in the previous sections.
In order to resolve this issue, you must back up the configuration on the TMS once the change on the endpoint is complete.
Complete these steps in order to take a backup on the TMS:
In order to resolve this issue, change the persistent template to No template, or you can change the persistent template configuration as required.
This image provides an example of the persistent settings on a configuration template:
Revision | Publish Date | Comments |
---|---|---|
1.0 |
23-Jul-2015 |
Initial Release |