Ad-Based Routing For Microsoft Skype For Business; Querying The Ad And Routing Priority - AudioCodes Mediant 800B User Manual

characters (such as spaces, hyphens and periods) separating the digits (e.g., 503-823 4567), the
LDAP query returns a failed result.
To enable the device to search the AD for numbers that may contain characters between its
digits, you need to specify the Attribute (up to five) for which you want to apply this functionality,
using the LDAPNumericAttributes parameter. For example, the telephoneNumber Attribute could
be defined in AD with the telephone number "503-823-4567" (i.e., hyphens), "503.823.4567" (i.e.,
periods) or "503 823 4567" (i.e., spaces). If the device performs an LDAP search on this Attribute
for the number 5038234567, the LDAP query will return results only if you configure the
LDAPNumericAttributes
LDAPNumericAttributes=telephoneNumber). To search for the number with characters, the
device inserts the asterisk (*) wildcard between all digits in the LDAP query (e.g.,
telephoneNumber = 5*0*3*8*2*3*4*5*6*7). As the AD server recognizes the * wildcard as
representing any character, it returns all possible results to the device. Note that the wildcard
represents only a character; a query result containing a digit in place of a wildcard is discarded
and the device performs another query for the same Attribute. For example, it may return the
numbers 533-823-4567 (second digit "3" and hyphens) and 503-823-4567. As the device discards
query results where the wildcard results in a digit, it selects 503-823-4567 as the result. The
correct query result is cached by the device for subsequent queries and/or in case of LDAP
server failure.

15.4.12 AD-based Routing for Microsoft Skype for Business

Typically, enterprises wishing to deploy the Microsoft® Skype for Business (formerly known as
Lync) are faced with a complex, call routing dial plan when migrating users from their existing
PBX or IP PBX to the Skype for Business 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:

Skype for Business client - users connected to Skype for Business through the Mediation
Server

PBX or IP PBX - users not yet migrated to Skype for Business

Mobile - mobile number

Private - private telephone line for Skype for Business users (in addition to the primary
telephone line)
15.4.12.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, Skype for Business 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:
Table 15-13: Parameters for Configuring Query Attribute Key
Parameter
MSLDAPPBXNumAttributeName
MSLDAPOCSNumAttributeName
MSLDAPMobileNumAttributeName
User's Manual
parameter with the
Queried User Domain (Attribute)
in AD
PBX or IP PBX number (e.g.,
"telephoneNumber" - default)
Mediation Server / Skype for
Business client number (e.g.,
"msRTCSIP-Line")
Mobile number (e.g., "mobile")
276
Mediant 800B Gateway & E-SBC
telephoneNumber Attribute
Query or Query Result
Example
telephoneNumber=
+3233554447
msRTCSIP-
line=john.smith@company.com
mobile=+3247647156
Document #: LTRT-10632
(e.g.,