In project S in country Z, all conferences attended by telepresence sites must be encrypted. After a conference is initiated using the TP3206 telepresence touch panel, the TP3206 fails to join the conference. Attempts to join the conference from the SMU2.0 also fail. However, all called RP systems join the conference successfully.
Log in to the SMC2.0 and view ongoing conferences. It is found that the conference has been created successfully. Calling the TP3206 site on the SMC2.0 also fails. Check the conference parameters. It is found that the conference is not encrypted. After the encryption is disabled on the TP3206, it can join a conference successfully. This confirms that an encrypted terminal cannot join a non-encrypted conference. Enable the encryption for the TP3206 again. The TP3206 can successfully join a SiteCall conference initiated on the web page. Check the conference on the SMC2.0 again. The conference is encrypted. Therefore, the problem is narrowed down to the touch panel. Log in to the management page of the touch panel. It is found that forcible encryption is not enabled. As a result, all conferences initiated from the touch panel are not encrypted. The problem is solved after forcible encryption is enabled on the touch panel. To set conference encryption, choose Advanced Settings > Conference Settings and set the Conference security parameter to Secure media conference.
The conference encryption setting on the touch panel does not match that on the terminal.
Enable the forcible encryption option on the touch panel.
This is a product design problem. After forcible encryption is enabled on the terminal, this configuration is not synchronized to the touch panel, and no message is provided for user to change the encryption setting on the touch panel. This requires optimization of the product.