AudioCodes Mediant 600 - Page 177

Version 6.4 177 March 2012
SIP User's Manual 13. Services
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:
Parameters for Configuring Query Attribute Key
Parameter Queried User Domain (Attribute) in AD 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")
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. Queries the AD:
• If Primary Key is not configured: Queries AD for the destination number in the
"PBX" attribute name, configured by the MSLDAPPBXNumAttributeName
parameter.
• If Primary Key is configured:
♦ If Primary Key does not equal private attribute value: Queries AD for the
destination number in an AD attribute configured by the MSLDAPPrimaryKey
parameter. For example, if you set this parameter to "mobile", the query
searches for a user whose "mobile" attribute value equals the original dialed
destination number.
♦ If Primary Key or Secondary Key value equals the Private Key value:
Queries AD for the destination number in the private attribute name,
configured by the MSLDAPPrivateNumAttributeName parameter. (For
example, the private key will be used if both the
MSLDAPPrivateNumAttributeName and MSLDAPPrimaryKey parameters
are set to "msRTCSIP-PrivateLine").
2. If the query is not found:
• If Secondary Key is configured: Does a second query for the destination
number using a second AD attribute key name, configured by the
MSLDAPSecondaryKey parameter.
• If Secondary Key is not configured: 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.
3. 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.