Active Directory-Based Routing For Microsoft Lync; Querying The Ad And Routing Priority - AudioCodes Mediant 800B User Manual

User's Manual

15.4.11 Active Directory-based Routing for Microsoft Lync

Typically, enterprises wishing to deploy the Microsoft® Lync™ Server are faced with a
complex, call routing dial plan when migrating users from their existing PBX or IP PBX to
the Lync Server platform. As more and more end-users migrate to the new voice system,
dialing plan management and PBX link capacity can be adversely impacted. To resolve this
issue, enterprises can employ Microsoft's Active Directory (AD), which provides a central
database to manage and maintain information regarding user's availability, presence, and
location.
The device supports outbound IP call routing decisions based on information stored on the
AD. Based on queries sent to the AD, the device can route the call to one of the following
IP domains:

Lync client - users connected to Lync Server through the Mediation Server

PBX or IP PBX - users not yet migrated to Lync Server

Mobile - mobile number

Private - private telephone line for Lync users (in addition to the primary telephone
line)
15.4.11.1

Querying the AD and Routing Priority

The device queries the AD using the initial destination number (i.e., called number). The
query can return up to four user phone numbers, each pertaining to one of the IP domains
(i.e., private number, Lync number, PBX / IP PBX number, and mobile number). The
configuration parameters listed in the table below are used to configure the query attribute
keys that defines the AD attribute that you wish to query in the AD:
Parameter
MSLDAPPBXNumAttribute
Name
MSLDAPOCSNumAttribute
Name
MSLDAPMobileNumAttribu
teName
MSLDAPPrivateNumAttrib
uteName
MSLDAPPrimaryKey
MSLDAPSecondaryKey
Version 6.8
Parameters for Configuring Query Attribute Key
Queried User Domain (Attribute) in AD
PBX or IP PBX number (e.g.,
"telephoneNumber" - default)
Mediation Server / Lync client number (e.g.,
"msRTCSIP-line")
Mobile number (e.g., "mobile")
Any attribute (e.g., "msRTCSIP-
PrivateLine")
Note: Used only if set to same value as
Primary or Secondary key.
Primary Key query search instead of PBX
key - can be any AD attribute
Secondary Key query key search if Primary
Key fails - can be any attribute
233 Mediant 800B Gateway and E-SBC
15. Services
Query or Query Result
Example
telephoneNumber=
+3233554447
msRTCSIP-
line=john.smith@compan
y.com
mobile=+3247647156
msRTCSIP-PrivateLine=
+3233554480
msRTCSIP-PrivateLine=
+3233554480
-