Version 7.2 277 Mediant 800B Gateway & E-SBC
User's Manual 15. Services
Parameter
Queried User Domain (Attribute)
in AD
Query or Query Result
Example
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 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 - Skype for Business, 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
Tel-to-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:<Skype for Business_number>): used to match a routing rule based on
query results of the Skype for Business client number
(MSLDAPOCSNumAttributeName)
• "PBX" (PBX:<PBX_number>): used to match a routing rule based on query results of
the PBX / IP PBX number (MSLDAPPBXNumAttributeName)
• "MOBILE" (MOBILE:<mobile_number>): used to match a routing rule based on query
results of the mobile number (MSLDAPMobileNumAttributeName)
• "LDAP_ERR": used to match a routing rule based on a failed query result when no
attribute is found in the AD
To Next Page
Loading...
Need help?
General
