Cisco TelePresence Administrator's Manual page 115

The configurable options on the
Field Description
H.350 device Enables or disables the use of an H.350
authentication directory for device authentication.
Source of Determines how aliases are checked
aliases for and registered. See the section above
registration for a description of the settings.
Server The IP address or FQDN (or server
address address, if a DNS Domain name has
also been configured) of the LDAP
server.
FQDN Defines how the LDAP server address is
address resolved if it is specified as an FQDN.
resolution
Address record: DNS A or AAAA
n
record lookup.
SRV record: DNS SRV record lookup.
n
The default is Address record.
Port The IP port of the LDAP server.
Encryption Determines whether the connection to
the LDAP server is encrypted using
Transport Layer Security (TLS).
TLS: uses TLS encryption for the
n
connection to the LDAP server.
Off: no encryption is used.
n
The default is Off.
VCS bind DN The user distinguished name used by the
VCS when binding to the LDAP server.
VCS bind The password used by the VCS when
password binding to the LDAP server.
Base DN for The area of the directory on the LDAP
devices server to search for credential
information. This should be specified as
the Distinguished Name (DN) in the
LDAP directory under which the H.350
objects reside.
The current status of the connection to the specified LDAP server is displayed at the bottom of the page.
Cisco VCS Administrator Guide (X7.2)
Device authentication H.350 configuration page are:
Usage tips
The H.350 directory can be used in combination with
other authentication mechanisms.
When Source of aliases for registration is H.350
directory, MCUs are treated as a special case. They
register with the presented aliases and ignore any
aliases in the H.350 directory. (This is to allow MCUs
to additively register aliases for conferences.)
The LDAP server must have the H.350 schemas
installed.
DNS SRV lookups enable the VCS to authenticate
devices against multiple remote H.350 directory
servers. This provides a seamless redundancy
mechanism in the event of reachability problems to
an H.350 directory server.
The SRV lookup is for either _ldap._tcp or _ldap._tls
records, depending on whether Encryption is
enabled. If multiple servers are returned, the priority
and weight of each SRV record determines the
order in which the servers are used.
Typically, non-secure connections use 389 and
secure connections use 636.
When TLS is enabled, the LDAP server's certificate
must be signed by an authority within the VCS's
trusted CA certificates file.
Click Upload a CA certificate file for TLS
Related tasks section) to go to the
certificate page.
For example, uid=admin, ou=system
For example, ou=H350,dc=example,dc=com
Device authentication
(in the
Trusted CA
Page 115 of 498