Specifications

PA-001011-03-04 Aastra July 2014
315
18 Appendix G: LDAP Directory
18.1 Introduction
This appendix describes how to provide access to the Corporate Directory (Active Directory) from
the Aastra SIP phones. As LDAP protocol is used to access Active Directory, this document is also
valid for any other LDAP enabled directory server. This document is solely about user initiated
directory lookup, it does not cover Corporate Directory based caller ID lookup for incoming or
outgoing calls.
There is no native LDAP client in the Aastra SIP phone, but the phone's inbuilt XML browser can
be used to access a XML Proxy Server which then communicates with the LDAP server. This
architecture offers more flexibility than a native LDAP client in the phone since the logic of the
LDAP directory application lies in the XML LDAP application (e.g. a PHP script) running on the
XML Proxy Server rather than in the LDAP client embedded in the phone's firmware. The following
features can be easily controlled by changing the XML LDAP application on the XML Proxy Server:
 Customized search fields on the phone (e.g. first name / last name / any name /
department / …)
 Customized LDAP-attributes to be included in the search result (such as title, department,
address)
 Number translation (digits to be removed from / added to the numbers found in the LDAP
before dialling – e.g. external prefix)
The following diagram shows a typical architecture for the LDAP directory access:
Figure 102: LDAP directory architecture