Hello,
We’re facing an issue with a Cisco Room Kit Pro that refuses to register to our Cisco Meeting Server using SIP over TLS. The endpoint is running RoomOS version 11.5.1.8, and the CMS is currently on version 3.8.1.
The system powers on and connects to the network just fine, but SIP registration fails consistently. When checking the logs, we’re seeing the message: "TLS handshake failed. Reason: certificate verify failed." The FQDN resolves correctly, and the device can ping the CMS without issue, so general connectivity doesn’t appear to be the problem.
We’ve already uploaded our internal CA-signed certificate to the Room Kit under the trusted certificates section. The certificate used on CMS is valid, not expired, and includes the correct SAN entries. We also confirmed that the SIP domain and URI settings on the Room Kit match what’s configured on CMS. Time sync via NTP is working, and the certificate chain should be trusted.
Despite all that, the registration just won’t go through. We’ve even restarted the SIP service on CMS and re-imported the certificate on the Room Kit, but the TLS handshake continues to fail. At this point, we’re wondering whether something changed in the latest firmware that’s causing a stricter certificate validation process or a cipher compatibility issue.
If anyone’s had a similar experience or can offer good words that start with i — like insight, ideas, or input — we’d really appreciate it.
Thanks in advance.
Thanks in advance.
