
Dialogic® Diva® SIPcontrol™ Configuration
Page 47
LDAP
The Lightweight Directory Access Protocol (LDAP), is an application protocol that programs use for querying
information from a server. The protocol runs over TCP/IP. Deployments today tend to use Domain Name System
(DNS) names for structuring the topmost levels of the hierarchy. LDAP servers index all the data in their entries,
and "filters" can be used to select the person or group for which you are looking. LDAP is appropriate for any
kind of directory-like information, where fast lookups and less-frequent updates are the norm. For example,
when you use Microsoft
®
Outlook and search the address book for a colleague, you access the Microsoft
®
Active
Directory database via LDAP.
How to Use LDAP to Access Active Directory for Routing Calls via Diva SIPcontrol
You can enable LDAP functionality via Diva SIPcontrol web configuration. When LDAP is activated, Diva SIPcontrol
will query the server on startup and store the query results internally for a faster lookup. In a default configuration,
this internal storage will be updated once a day to reflect changes on the LDAP database. If you use LDAP, you
need to configure two routes for one LDAP call:
• One route should contain the LDAP destination.
• The other route should contain the final destination.
The order of the routes is irrelevant, but it is important to configure the first route with the conditions needed
to avoid recursion.
Authentication mode: Select how the server-client authentication should be handled:
• Mutual Authentication: MTLS is used by Microsoft
®
Office Communications
Server 2007 Server roles and by Microsoft
®
Exchange 2007 UM role to
communicate with each other. In this mode, both peers need to authenticate
each other and both client and server exchange certificates.
For connecting to Lync Server or Microsoft
®
Office Communications Server
2007 R2 Mediation Server via TLS, use Standard TLS authentication mode. For
a direct connection to Microsoft
®
Exchange 2007 UM role via TLS, use MTLS
authentication mode.
• Standard TLS Authentication: This is the normal authentication mode, in
which the client asks the server for authentication to ensure a secure
connection to the correct server.
• No Authentication: In this mode, neither the server nor the client needs to
prove its authentication.
The default setting is Standard TLS Authentication.
Certificate date
verification:
If enabled, the expiration date of the peer certificate is verified. If the certificate
is expired, an informational message is displayed and the call is aborted.
Kommentare zu diesen Handbüchern