Cisco Cisco TelePresence Video Communication Server Expressway 관리 매뉴얼
Device authentication
Field
Description
Usage tips
Alias
origin
origin
Determines how aliases are checked and
registered. The options are:
registered. The options are:
n
LDAP: for SIP registrations the AOR
presented by the endpoint is registered
providing it is listed in the LDAP database for
the endpoint's username.
For H.323 registrations:
presented by the endpoint is registered
providing it is listed in the LDAP database for
the endpoint's username.
For H.323 registrations:
l
At least one of the aliases presented by
the endpoint must be listed in the LDAP
database for that endpoint's username. If
none of the presented aliases are listed it
is not allowed to register.
the endpoint must be listed in the LDAP
database for that endpoint's username. If
none of the presented aliases are listed it
is not allowed to register.
l
The endpoint will register with all of the
aliases (up to a maximum of 20) listed in
the LDAP database. Aliases presented
by the endpoint that are not in the LDAP
database will not be registered.
aliases (up to a maximum of 20) listed in
the LDAP database. Aliases presented
by the endpoint that are not in the LDAP
database will not be registered.
l
If no aliases are listed in the LDAP
database, the endpoint will register with
all the aliases it presented.
database, the endpoint will register with
all the aliases it presented.
l
If no aliases are presented by the
endpoint, it will register with all the
aliases listed in the LDAP database for
its username.
endpoint, it will register with all the
aliases listed in the LDAP database for
its username.
n
Combined: the aliases presented by the
endpoint are used in addition to any listed in
the LDAP database for the endpoint’s
username. In other words, this is the same
as for LDAP, except that if an endpoint
presents an alias that is not in the LDAP
database, it will be allowed to register with
that alias.
endpoint are used in addition to any listed in
the LDAP database for the endpoint’s
username. In other words, this is the same
as for LDAP, except that if an endpoint
presents an alias that is not in the LDAP
database, it will be allowed to register with
that alias.
n
Endpoint: the aliases presented by the
endpoint are used; any in the LDAP database
are ignored. If no aliases are presented by
the endpoint, it is not allowed to register.
endpoint are used; any in the LDAP database
are ignored. If no aliases are presented by
the endpoint, it is not allowed to register.
The default is LDAP.
When Alias origin is LDAP,
MCUs are treated as a special
case. They register with the
presented aliases and ignore any
aliases in the LDAP database. (This
is to allow MCUs to additively
register aliases for conferences.)
MCUs are treated as a special
case. They register with the
presented aliases and ignore any
aliases in the LDAP database. (This
is to allow MCUs to additively
register aliases for conferences.)
The current status of the connection to the specified LDAP server is displayed at the bottom of the
page.
page.
Note that if you want to use an LDAP database for device authentication, you must also go to the
page and select a Database type of LDAP database.
Device LDAP schemas
The Device LDAP schemas page (
VCS configuration > Authentication > Devices > LDAP
schemas
) provides a set of .ldif files to be downloaded from the Cisco VCS and installed on the LDAP
server.
Cisco VCS Administrator Guide (X6)
Page 77 of 295