Populating The Corporate Directory; Configuring Auto Discovery - LifeSize Passport User Manual

Administrators maintain access to the local directory on the web administration interface
Directory page when the Local Directory preference is set to Disabled. For more
information about managing the local directory from the web administration interface, refer
to "Using Advanced Directory Features" on page 60.

Populating the Corporate Directory

Users can place calls from the directory by selecting a number to dial from a list of stored
numbers. The corporate directory is H.350 compliant and can store up to 1000 entries in
both an alphabetical and hierarchical format. All users can manage entries in the local
directory. Only administrators can manage entries in the corporate directory.
You can populate the corporate directory by configuring Auto Discovery preferences or
Lightweight Directory Access Protocol (LDAP) preferences in Administrator Preferences :
Directory. By default, auto discovery is enabled and LDAP is disabled. You can enable only
one of these methods. The system automatically disables the other method to prevent
duplicate entries from appearing in the corporate directory. The status of these methods,
either enabled or disabled, appears on the Administrator Preferences : Directory screen.
The connection status of the LDAP installation also appears on this page and on the
System Information page. The values that can appear for the connection status include the
following:
LDAP Connection Status
Unregistered
Registered
Unreachable
Unauthorized
Invalid Syntax
Failed

Configuring Auto Discovery

Auto discovery enables LifeSize systems on your network to pass address information to
other LifeSize systems automatically. By default, when a LifeSize system joins a network, it
sends a broadcast packet to the local subnet to announce its presence. Any LifeSize system
LifeSize Passport User Guide
Description
LDAP preferences are not configured.
LDAP preferences are configured. The last attempt by the LifeSize system to
contact the LDAP server and receive data was successful.
LDAP preferences are configured, but the LDAP hostname is invalid or the
service does not exist.
LDAP preferences are configured, but the username or password is invalid.
LDAP preferences are configured, but the base Distinguished Name (DN) is
invalid.
LDAP preferences are configured, but an unexpected failure occurred.
55