Figure 17-5: LDAP Parameters for Microsoft Lync Server 2010
b. Configure the LDAP attribute names as desired.
3. For the Gateway/IP-to-IP application: Configure AD-based Tel-to-IP routing rules:
a. Open the Outbound IP Routing Table page (Configuration tab > VoIP menu >
GW and IP to IP submenu > Routing > Tel to IP Routing). For more information,
see Configuring Outbound IP Routing Table on page 327.
b. Configure query-result routing rules for each IP domain (private, PBX / IP PBX,
Lync / OCS clients, and mobile), using the LDAP keywords (case-sensitive) for
the prefix destination number:
♦ PRIVATE: Private number
♦ OCS: Lync / OCS client number
♦ PBX: PBX / IP PBX number
♦ MOBILE: Mobile number
♦ LDAP_ERR: LDAP query failure
c. Configure a routing rule for routing the initial Tel call to the LDAP server, using
the value "LDAP" for denoting the IP address of the LDAP server.
d. For alternative routing, enable the alternative routing mechanism and configure
corresponding SIP reasons for alternative routing. For this feature, alternative
routing starts from the table row located under the LDAP query row.
4. For the SBC application: Configure AD-based IP-to-IP routing rules:
a. Open the IP-to-IP Routing Table page (Configuration tab > VoIP menu > SBC
submenu > Routing SBC > IP to IP Routing Table). For more information, see
Configuring SBC IP-to-IP Routing on page 468.
b. Configure query-result routing rules for each IP domain (private, PBX / IP PBX,
Lync / OCS clients, and mobile), using the LDAP keywords (case-sensitive) in the
Destination Username Prefix field:
♦ PRIVATE: Private number
♦ OCS: Lync / OCS client number
♦ PBX: PBX / IP PBX number
♦ MOBILE: Mobile number
♦ LDAP_ERR: LDAP query failure
c. Configure a routing rule for routing the initial call (LDAP query) to the LDAP
server, by setting the 'Destination Type' field to LDAP for denoting the IP address
of the LDAP server.
d. For alternative routing, enable the alternative routing mechanism and configure
corresponding SIP reasons for alternative routing. For this feature, alternative
routing starts from the table row located under the LDAP query row.