Installation & Operation Manual
642
Document # LTRT-92224
Mediant 8000
40.15.2
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 / OCS 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 define the AD attribute that you wish to query in the AD:
Table
40-24: Parameters for Configuring Query Attribute Key
Parameter
Queried User Domain (Attribute)
in AD
Query or Query Result
Example
LDAPPBXNumAttributeName
PBX or IP PBX number (e.g.,
"telephoneNumber" - default)
telephoneNumber=
+3233554447
LDAPOCSNumAttributeName
Mediation Server / Lync client
number (e.g., "msRTCSIP-line")
msRTCSIP-
line=john.smith@company.com
LDAPMobileNumAttributeName
Mobile number (e.g., "mobile")
3247647156
LDAPPrivateNumAttributeName
Any attribute (e.g., "msRTCSIP-
PrivateLine")
Note:
Used only if set to same
value as Primary or Secondary
key.
msRTCSIP-PrivateLine=
+3233554480
LDAPPrimaryKey
Primary Key query search instead
of PBX key - can be any AD
attribute
msRTCSIP-PrivateLine=
+3233554480
LDAPSecondaryKey
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 performs 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.
Summary of Contents for Mediant 8000
Page 2: ......
Page 33: ...Part I Hardware Overview This part describes the hardware overview of the Mediant 8000 chassis...
Page 34: ......
Page 90: ......
Page 158: ......
Page 264: ......
Page 546: ......
Page 775: ...Part VI Maintenance This part describes the Mediant 8000 maintenance procedures...
Page 776: ......
Page 834: ......
Page 879: ...Part VIII Appendices This part describes additional Mediant 8000 configuration procedures...
Page 880: ......
Page 924: ...Media Gateway Mediant 8000 www audiocodes com Installation Operation Maintenance Manual...
