Implement LDAP-based Conditional Call Routing
It's recommended that you implement a third-party, LDAP server in your network for determining whether a call from a specific source is permitted to be routed to its destination. This setup uses Call Setup rules, configured in the Call Setup Rules table, to define a condition-based script that queries an LDAP server for the caller's number (for example) in a specific LDAP attribute. If the number exists, the device routes the call to the destination; otherwise, the call is dropped. The device executes a Call Setup rule upon the receipt of an incoming call (dialog) at call setup if a matching routing rule exists in the IP-to-IP Routing table, before the <device> routes the call to its destination.
➢ | To configure LDAP-based conditional routing: |
1. | For configuring LDAP, use the LDAP Settings page, LDAP Server Groups table, and LDAP Servers table (Setup menu > IP Network tab > AAA Servers folder). |
2. | For configuring Call Setup rules, use the Call Setup Rules table (Setup menu > Signaling & Media tab > SIP Definitions folder > Call Setup Rules). The below Call Setup rule example routes the incoming call only if the source number of the incoming call exists in the AD server. The device queries the AD server for the attribute record, "telephoneNumber" whose value is the same as the received source number (e.g., "telephoneNumber=4064"). If such an attribute is found, the device routes the call to the destination as specified in the IP-to-IP Routing table. If the query fails (i.e., source number doesn't exist in AD server), the device rejects the call. |
Call Setup Rule for Conditional LDAP-based Routing
Make sure that you implement secure LDAP communication, as discussed in Section Secure LDAP Communication.