AudioCodes Mediant 500L - Querying the AD and Routing Priority

User's Manual 270 Document #: LTRT-10532
Mediant 500L Gateway & E-SBC
 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
Queried User Domain
(Attribute) in AD
Query or Query Result
Example
MSLDAPPBXNumAttributeName
PBX or IP PBX number
(e.g., "telephoneNumber" -
default)
telephoneNumber=
+3233554447
MSLDAPOCSNumAttributeName
Mediation Server / Skype
for Business client number
(e.g., "msRTCSIP-Line")
msRTCSIP-
Line=john.smith@company.com
MSLDAPMobileNumAttributeName
Mobile number (e.g.,
"mobile")
mobile=+3247647156
MSLDAPPrivateNumAttributeName
Any attribute (e.g.,
"msRTCSIP-PrivateLine")
Note: Used only if set to
same value as Primary or
Secondary key.
msRTCSIP-PrivateLine=
+3233554480
MSLDAPPrimaryKey
Primary Key query search
instead of PBX key - can
be any AD attribute
msRTCSIP-PrivateLine=
+3233554480
MSLDAPSecondaryKey
Secondary Key query key
search if Primary Key fails -
can be any attribute
-
The process for querying the AD and subsequent routing based on the query results is as
follows:
1. If the Primary Key is configured, it uses the defined string as a primary key instead of
the one defined in MSLDAPPBXNumAttributeName. It requests the attributes which
are described below.
2. If the primary query is not found in the AD and the Secondary Key is configured, it
does a second query for the destination number using a second AD attribute key
name, configured by the MSLDAPSecondaryKey parameter.
3. If none of the queries are successful, it routes the call to the original dialed destination
number according to the routing rule matching the "LDAP_ERR" destination prefix
number value, or rejects the call with a SIP 404 "Not Found" response.
4. For each query (primary or secondary), it queries the following attributes (if