Hi Community members,
I'm wondering if anyone of you has some experience with clustering the conductors via TLS.
With this major update the TLS enforcement for the verification mode has been activated.
However, we used in the past IPSec for clust...
Hi,
I'm currently reading the latest deployment guide of the TMS PE (with CUCM).
On the first page stands:
Deployment Guide
Last Updated: February 2018
Cisco TMSPE 1.12
Cisco TMS 15.6.1
Cisco Unified CM 10.0 or 9.1
TelePresence Conductor XC 4.3
O...
Hi,
currently several users receive a prompt from Jabber with the message "Try again later or contact your system administrator" and a error code "CJ:1100:25"is written in the "show error notification" log.
When I lookup for the error codes (https:...
Hi Patrick,
I added a further value as CN entry -> the ip address of the device and repeated that for the 2nd peer.
With a signed certificate for mTLS I've benn able to cluster both systems.
I was just wondering that the clustering via FQDN obvious...
The keyword for clustering Conductors via TLS is: mTLS !
With mTLS it was working directly. Previously I was using a certificate for web server. As both are working as servers it can't work as they were expecting from the remote peer a certificate ...
Hi Patrick,
thanks for your reply. We're not using wildcards in the certificate(s).
Cisco described to work here with IP adresses. Therefore we requested a new certificate with an additional value for the IP adress.
The host name is identical to th...
Maybe as a short hint:The upgrade has been done according the guide lines. Long story short: Permissive mode is working. Enforce mode is not working. All certificates have been generated new and are valid. When in Permissive mode the comment appears ...