Place is started on error - Wrong CA certificate

Top  Previous  Next
Standard > Use cases > Basic use cases samples > CuCM Secure Communication

In this section, what happened when the CA Certificate is not the good one.

The context is the same as described in SIP Registration.

 

TPO logs and network analysis

•When the place is starting, there is a TLS handshake error after a time:

<9952:2018.12.13-10.00.19:483:error:CCL.SIP: - CCL!E3095 [hAppConnection][] - [message][CmapCpp::AppTransportConnectionTlsStateChanged - TLS State changed to handshake failed] - [eState][3] - [hConn][0x000000001B7CD868] - [eReason][-1] >

 

TPO-Security_CuCM_NetworkTrace02

 

When the CA certificate is not present (or not the good one), the TLS handshake fails with error "Unknown CA".