Problem description
The endpoint can't remain in the Sleep mode.
Analysis progress
1. Analyse the log from endpoint and found it is logged on SMC.
2. Checked the settings in SMC.
The auto-recovery configuration function of the manageable site is as follows: After the site is added to the SMC in an manageable mode, the SMC side can modify the configuration information. However, if the user skips the SMC, log in directly to the terminal side (the terminal's built-in web interface) to modify the configuration. This will result in different configuration information on the SMC side/device side. To keep the configuration information of the two devices consistent, configure the timing synchronization device on the SMC to periodically query the configuration on the device. If the configuration on the SMC is inconsistent with the SMC, the configuration information on the device is updated to the SMC. However, each time the H323/SIP password on the SMC side is sent to the device side by default. (The password information on the device side cannot be read because of the security red line problem. Therefore, the password information saved on the SMC side is taken as the standard and saved to the device side). If the configuration item is locked (the device applies a configuration template or a lock flag), the configuration item that is locked is delivered to the device side each time.
Root cause
SMC keeps on waking the endpoint.
Solution description
Disable the automatically restored defaults on the MCU sides and those endpoints can remain in Sleep mode.
