Configuring Ad-Based Routing Rules - AudioCodes Mediant 8000 Installation, Operation & Maintenance Manual

Installation & Operation Manual
Parameter
Name
LDAP Private String
NUM Attribute Default:
Name msRTCSIP-
PrivateLine
LDAP Private String
key Default:empty string
LDAP String
secondary key Default:empty string
40.15.4

Configuring AD-Based Routing Rules

The procedure below describes how to configure Tel-to-IP routing based on LDAP
queries.

To configure LDAP-based Tel-to-IP routing for Lync Server 2010:
1.
Configure the LDAP server parameters, as described in .'Configuring LDAP
Server Parameters' on page 640.
2.
Configure the AD attribute names used in the LDAP query.
a.
3.
For the Gateway/IP-to-IP application: Configure AD-based Tel-to-IP routing rules:
a.
b.
AD Object
PRIVATE
OCS
PBX
Version 6.6
Provisioning
Type
Configure the LDAP attribute names as desired.
Select the relevant VoIP board, and then open the Tel to IP routing table
GW/IP to IP
(SIP
Configure query-result routing rules for each IP domain (private, PBX / IP
PBX, Lync / OCS clients, and mobile), using the LDAP keywords (case-
sensitive) for the prefix destination number:
Table 40-26: Destination Username Prefixes
Private number
Lync / OCS client number
PBX / IP PBX number
Type
Instant This attribute msRTCSIP-PrivateLine
represents user private line number in
Active Directory.
Instant if the Primary Key is configured, it uses
the defined string as a primary key
instead of the one defined in
LDAPPBXNumAttributeName. It requests
the attributes which are described below.
Instant 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
LDAPSecondaryKey parameter
Routing Telephone to IP / Outbound).
Description
645
40. General SIP Configuration
Description
October 2014