Querying The Ad And Routing Priority - AudioCodes Mediant 1000B User Manual

Analog & digital voip media gateway enterprise session border controller gateway & e-sbc
Hide thumbs Also See for Mediant 1000B:
Table of Contents

Advertisement

15.3.11.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, Lync 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:
Parameter
MSLDAPPBXNumAttribute
Name
MSLDAPOCSNumAttribute
Name
MSLDAPMobileNumAttribu
teName
MSLDAPPrivateNumAttrib
uteName
MSLDAPPrimaryKey
MSLDAPSecondaryKey
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
configured):
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, PBX / IP PBX, private
(only if it equals Primary or Secondary key), and mobile.
User's Manual
Parameters for Configuring Query Attribute Key
Queried User Domain (Attribute) in AD
PBX or IP PBX number (e.g.,
"telephoneNumber" - default)
Mediation Server / Lync client number (e.g.,
"msRTCSIP-line")
Mobile number (e.g., "mobile")
Any attribute (e.g., "msRTCSIP-
PrivateLine")
Note: Used only if set to same value as
Primary or Secondary key.
Primary Key query search instead of PBX
key - can be any AD attribute
Secondary Key query key search if Primary
Key fails - can be any attribute
Mediant 1000B Gateway & SBC
220
Query or Query Result
Example
telephoneNumber=
+3233554447
msRTCSIP-
line=john.smith@compan
y.com
mobile=+3247647156
msRTCSIP-PrivateLine=
+3233554480
msRTCSIP-PrivateLine=
+3233554480
-
Document #: LTRT-27034

Advertisement

Table of Contents
loading

Table of Contents