User's Manual 218 Document #: LTRT-42060
Mediant 2600 E-SBC
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.
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)
• "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
Note: These prefixes are involved only in the routing and manipulation processes;
they are not used as the final destination number.
7. The device uses the Outbound IP Routing table to route the call based on the LDAP
query result. The device routes the call according to the following priority:
1. Private line: If the query is done for the private attribute and it's found, the device
routes the call according to this attribute.
2. Mediation Server SIP address (Lync): If the private attribute does not exist or is
not queried, the device routes the call to the Mediation Server (which then routes
the call to the Lync client).
3. PBX / IP PBX: If the Lync client is not found in the AD, it routes the call to the
PBX / IP PBX.
To Next Page
Loading...
