AudioCodes Mediant 3000, User Manual

Page: 209 / 872

Version 6.6 209 Mediant 3000
User's Manual 14. Services
Parameters for Configuring Query Attribute Key
Parameter Queried User Domain (Attribute) in AD
Query or Query Result
Example
MSLDAPPBXNumAttribute
Name PBX or IP PBX number (e.g.,
"telephoneNumber" - default) telephoneNumber=
+3233554447
MSLDAPOCSNumAttribute
Name
Mediation Server / Lync client number (e.g.,
"msRTCSIP-line")
msRTCSIP-
line=john.smith@compan
y.com
MSLDAPMobileNumAttribu
teName
Mobile number (e.g., "mobile")
3247647156
MSLDAPPrivateNumAttrib
uteName 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 requests to query the following attributes (if
they’re not configured as an empty string):
•
MSLDAPPBXNumAttributeName
•
MSLDAPOCSNumAttributeName
•
MSLDAPMobileNumAttributeName
In addition, it queries the special attribute defined in
MSLDAPPrivateNumAttributeName, only if the query key (primary or secondary) is
equal to its value.
5. If the query is found: The AD returns up to four attributes - Lync / OCS, PBX / IP PBX,
private (only if it equals Primary or Secondary key), and mobile.
6. The device adds unique prefix keywords to the query results in order to identify the
query type (i.e., IP domain). These prefixes are used as the prefix destination number
value in the Outbound IP Routing table to denote the IP domains:
•
"PRIVATE" (PRIVATE:<private_number>): used to match a routing rule based on
query results of the private number (MSLDAPPrivateNumAttributeName)
•
"OCS" (OCS:<Lync_number>): used to match a routing rule based on query
results of the Lync client number (MSLDAPOCSNumAttributeName)