Place is started on error - Device security mismatch |
|
| Standard > Use cases > Basic use cases samples > CuCM Secure Communication |
In this section, what happened when the SIP device is not configured to support TLS in the CuCM:
•Device is set to "IPTrade Profile EK - Standard SIP Non-Secure Profile"
"IPTrade Profile EK - Standard SIP Non-Secure Profile" is only support TCP and UDP
The context is the same as described in SIP Registration.
TPO logs and network analysis•When the place is starting, TLS handshake seems OK but the CuCM terminate the session.
•There is an error in the TPO log for the SIP registration <7632:2018.12.13-11.36.07:665:error:CCL: - CCL!E0008 [errCode][8] - [proxyDump][Domain:cucm12pub.iptrade.local IP: Protocol:TLS Port:5061 Transport:3 ] - [deviceId][SEP800000000009] - [reasonCode][0] - [errLine][857] - [registrarDump][sip:cucm12pub;transport=TLS] - [errFileName][CSIPBulkRegister.cpp] - [reason][] - [userDump][FROM: "" <sip:8900@cucm12pub> sip:8900@cucm12pub;transport=TLS contact: <sip:f3a8f41d-d7bc-cd28-ffc4-a0f73c3e0bba@10.10.7.7:5062;transport=TLS> sip:f3a8f41d-d7bc-cd28-ffc4-a0f73c3e0bba@10.10.7.7:5062;transport=TLS] - [warning][] >
•Changing the trace level of CCL to debug2 (trace.logger@ccl.eventlevel = debug2) shows the reason of the registration failure <9044:2018.12.13-11.39.26:960:debug2:CCL.SIP: - CCL!D0001 [msg][ --------------- SIP --------------- 10.10.7.7:5062 <-- 10.12.1.235:5061 SIP/2.0 403 Forbidden Via: SIP/2.0/TLS 10.10.7.7:5062;branch=z9hG4bK-664e9be7-794d-1d9d837-401ec9b0 From: ""<sip:8900@cucm12pub.iptrade.local>;tag=6558fc40-5f054dc9-794d-40d71740-7070a0a-13c4-759 To: ""<sip:8900@cucm12pub.iptrade.local>;tag=1190011488 Date: Thu, 13 Dec 2018 10:39:26 GMT Call-ID: 1959e1c8-37a3517a-794d-42fc0198-7070a0a-13c4-759 Server: Cisco-CUCM12.0 CSeq: 1 REGISTER Warning: 399 cucm12pub "Device security mismatch: expected TCP/UDP, received TLS" Content-Length: 0
] >
|