Cisco Cisco TelePresence Video Communication Server Expressway
Server certificate requirements for Unified
Communications
Communications
Cisco Unified Communications Manager certificates
The two Cisco Unified Communications Manager certificates that are significant for Mobile and Remote
Access are the CallManager certificate and the tomcat certificate. These are automatically installed on the
Cisco Unified Communications Manager and by default they are self-signed and have the same common
name (CN).
Access are the CallManager certificate and the tomcat certificate. These are automatically installed on the
Cisco Unified Communications Manager and by default they are self-signed and have the same common
name (CN).
We recommend using externally-signed certificates for best end-to-end security between external endpoints
and internal endpoints. However, if you do use self-signed certificates, the two certificates must have
different common names. This is because the VCS does not allow two self-signed certificates with the same
CN. If the CallManager and tomcat self-signed certs have the same CN in the VCS's trusted CA list, then it
can only trust one of them. This means that either secure HTTP or secure SIP, between VCS Control and
Cisco Unified Communications Manager, will fail.
and internal endpoints. However, if you do use self-signed certificates, the two certificates must have
different common names. This is because the VCS does not allow two self-signed certificates with the same
CN. If the CallManager and tomcat self-signed certs have the same CN in the VCS's trusted CA list, then it
can only trust one of them. This means that either secure HTTP or secure SIP, between VCS Control and
Cisco Unified Communications Manager, will fail.
VCS certificates
The VCS certificate signing request (CSR) tool prompts for and incorporates the relevant subject alternate
name (SAN) entries as appropriate for the Unified Communications features that are supported on that VCS.
name (SAN) entries as appropriate for the Unified Communications features that are supported on that VCS.
The following table shows which CSR alternative name elements apply to which Unified Communications
features:
features:
CSR SAN element
Mobile and remote access
Jabber Guest
XMPP federation
Unified CM registrations domains
ü
(VCS Expressway only)
X
X
XMPP federation domains
X
X
ü
(VCS Expressway only)
IM and Presence chat node aliases
(federated group chat)
(federated group chat)
X
X
ü
Unified CM phone security profile names
ü
(VCS Control only)
X
X
Note:
n
A new VCS Control certificate may need to be produced for the VCS Control if chat node aliases are added
or renamed, such as when an IM and Presence node is added or renamed, or if new TLS phone security
profiles are added.
or renamed, such as when an IM and Presence node is added or renamed, or if new TLS phone security
profiles are added.
n
A new VCS Expressway certificate must be produced if new chat node aliases are added to the system, or
if the Unified CM or XMPP federation domains are modified.
if the Unified CM or XMPP federation domains are modified.
n
You must restart the VCS for any new uploaded server certificate to take effect.
More details about the individual feature requirements per VCS Control / VCS Expressway are described
below.
below.
Cisco TelePresence VCS Certificate Creation and Use Deployment Guide (X8.5.2)
Page 7 of 32
Server certificate requirements for Unified Communications