AudioCodes Mediant 3000 User Manual page 270
Media gateway & enterprise session border
controller (e-sbc)
Hide thumbs
Also See for Mediant 3000:
- User manual (984 pages) ,
- Installation manual (90 pages) ,
- Hardware installation manual (88 pages)
Table of Contents
Advertisement
a.
Open the Advanced Parameters page (Configuration tab > VoIP menu > SIP
Definitions > Advanced Parameters).
Figure 16-25: LDAP Parameters for Microsoft Lync Server 2010
b.
Configure the LDAP attribute names as desired.
3.
Gateway application: Configure AD-based Tel-to-IP routing rules:
a.
Open the Tel-to-IP Routing table (Configuration tab > VoIP menu > Gateway >
Routing > Tel to IP Routing). For more information, see Configuring Tel-to-IP
Routing Rules on page 496.
b.
Configure query-result routing rules for each IP domain (private, PBX / IP PBX,
Lync clients, and mobile), using the LDAP keywords (case-sensitive) for the
prefix destination number:
♦
♦
♦
♦
♦
c.
Configure a routing rule for routing the initial Tel call to the LDAP server, using
the value "LDAP" for denoting the IP address of the LDAP server.
d.
For alternative routing, enable the alternative routing mechanism and configure
corresponding SIP reasons for alternative routing. For this feature, alternative
routing starts from the table row located under the LDAP query row.
4.
SBC application: Configure AD-based IP-to-IP routing rules:
a.
Open the IP-to-IP Routing table (Configuration tab > VoIP menu > SBC > Routing
SBC > IP-to-IP Routing Table). For more information, see Configuring SBC IP-to-
IP Routing Rules on page 603.
b.
Configure query-result routing rules for each IP domain (private, PBX / IP PBX,
Lync clients, and mobile), using the LDAP keywords (case-sensitive) in the
Destination Username Prefix field:
♦
♦
♦
♦
♦
c.
Configure a routing rule for routing the initial call (LDAP query) to the LDAP
server, by setting the 'Destination Type' field to LDAP for denoting the IP address
of the LDAP server.
d.
For alternative routing, enable the alternative routing mechanism and configure
corresponding SIP reasons for alternative routing. For this feature, alternative
routing starts from the table row located under the LDAP query row.
The table below shows an example for configuring AD-based Tel-to-IP routing rules in the
Tel-to-IP Routing table:
User's Manual
PRIVATE: Private number
OCS: Lync client number
PBX: PBX / IP PBX number
MOBILE: Mobile number
LDAP_ERR: LDAP query failure
PRIVATE: Private number
OCS: Lync client number
PBX: PBX / IP PBX number
MOBILE: Mobile number
LDAP_ERR: LDAP query failure
270
Mediant 3000
Document #: LTRT-89730
Advertisement
Table of Contents
