Version 6.2
605
February 2011
SIP User's Manual
8. IP Telephony Capabilities
8.6
Routing Based on LDAP Active Directory Queries
The device supports Lightweight Directory Access Protocol (LDAP), allowing the device to
make call routing decisions based on information stored on a third-party LDAP server (or
Microsoft’s Active Directory-based enterprise directory server). This feature enables the
usage of one common, popular database to manage and maintain information regarding
user’s availability, presence, and location.
The LDAP feature can be configured using the
ini
file, Web interface, SNMP, and CLI (for
debugging only).
8.6.1
LDAP Overview
The basic LDAP mechanism is described below:
Connection:
The device connects and binds to the remote LDAP server either during
the service’s initialization (at device start-up) or whenever the LDAP server's IP
address and port is changed. Service makes 10 attempts to connect and bind to the
remote LDAP server with a timeout of 20 seconds between attempts. If connection
fails, the service remains in disconnected state until either the LDAP server's IP
address or port is changed.
If connection to the LDAP server later fails, the service attempts to reconnect, as
described previously. The SNMP alarm acLDAPLostConnection is sent when
connection is broken. Upon successful reconnection, the alarm is cleared.
Binding to the LDAP server can be anonymous or not. For anonymous binding, the
LDAPBindDN and LDAPPassword parameters must not be defined or set to an empty
string.
The address of the LDAP server can be a DNS name (using the LDAPServerName
parameter) or an IP address (using the LDAPServerIP parameter).
Search:
To run a search using the LDAP service, the path to the directory’s subtree
where the search is to be performed must be defined (using the LDAPSearchDN
parameter). In addition, the search key (known as “filter” in LDAP references), which
defines the exact DN to be found and one or more attributes whose values should be
returned, must be defined. The device supports up to 20 LDAP search requests.
If connection to the LDAP server is disrupted during the search, all search requests
are dropped and an alarm indicating a failed status is sent to client applications.
CLI:
The LDAP CLI is located in the directory IPNetworking\OpenLdap. The following
commands can be used:
•
LdapSTatus - displays connection status
•
LdapSearch - searches an LDAP server
•
LDapOpen - opens connection to the LDAP server using parameters provided in
configuration file
•
LDapSetDebugmode - sets the LdapDebugLevelMode parameter
•
LDapGetDebugmode – gets the LdapDebugLevelMode parameter value
Relevant parameters: LDAPServiceEnable; LDAPServerIP; LDAPServerDomainName;
LDAPServerPort; LDAPPassword; LDAPBindDN; LDAPSearchDN; LDAPDebugMode;
LDAPServerMaxRespondTime.
Summary of Contents for Mediant 800 MSBG
Page 2: ......
Page 366: ...SIP User s Manual 366 Document LTRT 12804 Mediant 800 MSBG Reader s Notes ...
Page 372: ...SIP User s Manual 372 Document LTRT 12804 Mediant 800 MSBG Reader s Notes ...
Page 390: ...SIP User s Manual 390 Document LTRT 12804 Mediant 800 MSBG Reader s Notes ...
Page 404: ...SIP User s Manual 404 Document LTRT 12804 Mediant 800 MSBG Reader s Notes ...
Page 616: ...SIP User s Manual 616 Document LTRT 12804 Mediant 800 MSBG Reader s Notes ...
Page 636: ...SIP User s Manual 636 Document LTRT 12804 Mediant 800 MSBG Reader s Notes ...
Page 652: ...SIP User s Manual 652 Document LTRT 12804 Mediant 800 MSBG Reader s Notes ...
Page 886: ...SIP User s Manual 886 Document LTRT 12804 Mediant 800 MSBG Reader s Notes ...