EasyManuals Logo

AudioCodes Mediant 3000 User Manual

AudioCodes Mediant 3000
1070 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #267 background imageLoading...
Page #267 background image
Version 7.0 267 Mediant 3000
User's Manual 16. Services
Parameter Queried User Domain (Attribute) in AD
Query or Query Result
Example
eName
(e.g., "msRTCSIP-line")
line=john.smith@compan
y.com
MSLDAPMobileNumAttrib
uteName
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. 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 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:<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)

Table of Contents

Other manuals for AudioCodes Mediant 3000

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the AudioCodes Mediant 3000 and is the answer not in the manual?

AudioCodes Mediant 3000 Specifications

General IconGeneral
BrandAudioCodes
ModelMediant 3000
CategoryGateway
LanguageEnglish

Related product manuals