User's Manual 274 Document #: LTRT-10532
Mediant 500L Gateway & E-SBC
b. Configure query-result routing rules for each IP domain (private, PBX / IP PBX,
Skype for Business clients, and mobile), using the LDAP keywords (case-
sensitive) in the Destination Username Prefix field:
♦ PRIVATE: Private number
♦ OCS: Skype for Business client number
♦ PBX: PBX / IP PBX number
♦ MOBILE: Mobile number
♦ LDAP_ERR: LDAP query failure
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:
Table 15-14: AD-Based Tel-to-IP Routing Rule Configuration Examples
Index Destination Phone Prefix Destination IP Address
1 PRIVATE: 10.33.45.60
2 PBX: 10.33.45.65
3 OCS: 10.33.45.68
4 MOBILE: 10.33.45.100
5 LDAP_ERR 10.33.45.80
6 * LDAP
7 * 10.33.45.72
The table below shows an example for configuring AD-based SBC routing rules in the IP-
to-IP Routing Table:
Table 15-15: AD-Based SBC IP-to-IP Routing Rule Configuration Examples
Index
Destination Username
Prefix
Destination Type
Destination
Address
1 PRIVATE: Dest Address 10.33.45.60
2 PBX: Dest Address 10.33.45.65
3 OCS: Dest Address 10.33.45.68
4 MOBILE: Dest Address 10.33.45.100
5 LDAP_ERR Dest Address 10.33.45.80
6 * LDAP
7 * Dest Address 10.33.45.72
The configured routing rule example is explained below:
Rule 1: Sends call to private telephone line (at 10.33.45.60) upon successful AD
query result for the private attribute.
Rule 2: Sends call to IP PBX (at 10.33.45.65) upon successful AD query result for the
To Next Page
Loading...
