Configure a Routing Query

To configure the Oracle Enterprise Communications Broker (OECB) to query an LDAP database for the purpose of obtaining a call's routing information, per the OECB processing sequence:

1. Access the LDAP Configuration object.
   Configuration tab, System Administration section, LDAP, LDAP Config.
2. On the LDAP Config page, expand Routing to expose the Routing parameters, and do the following:

   State	Select to enable the use of routing queries for your configured LDAP servers.
   Route Mode	Specify the route priority that the OECB uses in the route list that determines which routes to create, and the priority of the routes within the route list. Default: Match-only. Valid values: Match-Only | Attribute Order | Match First. Match-Only—When an exact match between the dialed telephone number and an LDAP attribute value in the search response entry occurs, a route is created corresponding to that LDAP attribute. When an exact match on multiple attributes occurs, the ordering of LDAP attributes in the LDAP configuration determines the priority for each route. For example, in an enterprise that uses the same phone number for both Lync and IPPBX phones, when the msRTCSIP-Line attribute is configured first, the corresponding next hop (Lync Server) is used to create the first route in the route list. Attribute Order— The ordering of LDAP attributes in the LDAP configuration determines the priority for each route. When the msRTCSIP-Line attribute is configured first, the corresponding next hop (Lync Server) is used to create the first route in the route list. If there is a valid value present in the search response entry for a LDAP attribute, a route is created corresponding to that LDAP attribute. Match First— If there is an exact match between the dialed telephone number and an LDAP attribute value in the search response entry, the corresponding route gets the highest priority in the route list. For the rest of the routes, the ordering of LDAP attributes in the LDAP configuration determines the priority for each route. So if the msRTCSIP-Line attribute is configured first, the corresponding next hop (Lync Server) would be used to create the second highest priority route in the route list. If there is a valid value present in the search response entry for an LDAP attribute, a route is created corresponding to that LDAP attribute. Note: The LDAP attribute must have a valid value in the response; a match is not necessary for that attribute. If an entry is returned in the search response, there must be a match on at least one other attribute. For example, the dialed telephone number could be [phone] (IP-PBX Phone#), and the msRTCSIP-Line in the response could be [phone] (Lync phone#). A route is created for the Lync phone#, even though the dialed telephone number is the PBX Phone#.
   From Header Replacement	Enter the name of the LDAP lookup query to use as the From Header replacement.

3. Click Add in the Lookup Query dialog, and do the following:
   Each element identifies a lookup number attribute and dialed pattern with which the OECB finds matches in the LDAP database and identifies contacts to which it builds routes. Multiple matches result in multiple targets to which the OECB creates routes for call forking.

   Lookup Number Attribute	Enter the Active Directory attribute name. Default: Telephone Number. Valid values: Alpha-numeric characters. Some examples of Active Directory attribute names include: ipPhone and msRTCSIP-Line for Lync phone number telephoneNumber for IP PBX phone number mobile for Mobile phone number
   Lookup Number Format Type	Select the expected attribute format from the drop down list. Default: None. Valid values: E164 | E614 No Plus | No Country Code | None | Pattern Only | Regular Expression.
   Lookup Number Regex Pattern	Enter the regular expression pattern used to break down the string of digits in the phone number extracted from the request URI and the FROM of the SIP request. The variables extracted from the phone number can be used in the attribute-value-format parameter. Default regex: "^\+?1?(\d{2})(\d{3})(\d{4})$" Valid values: Alpha-numeric characters. (The default value assumes that the phone number is a North American phone number specified in the E.164 format.) It extracts the following variables from the phone number: $1 is the area code. | $2 and $3 are the next 3 and 4 digits in the phone number. Note that the system queries only for the home agent of the FROM if it has not already found it. The setting applies only when you set Lookup number format type to regular-expression.
   Lookup Number Regex Result	Lookup number regex result—Enter the format for the attribute value. These format values are extracted from the phone number using the extraction-regex parameter. Default: "tel:+1$1$2$3". This value assumes that the phone number is a North American phone number specified in the E.164 format, and it recreates the phone number in E.164 format. Valid values: Alpha-numeric characters. In addition to the E.164 format, the OECB uses other formats as well to store the phone numbers. You can customize the value specified for this parameter to enable successful queries for phone numbers in other formats. The setting applies only when you set Lookup number format type to regular-expression.
   Home Agent Attribute	Enter the Active Directory attribute name for the agent field. Default: Blank. Valid values: Alpha-numeric characters. If created with the Oracle tools described in this document, the name would be orclAgentNameAttribute.
   Home Agent Regex Pattern	Enter the regular expression pattern used to break down the agent name. Default: Blank.
   Home Agent Regex Result	Enter the format of the regex result. Default: Blank.
   Default Home Agent	Enter the name of the home agent to use for routing if the query does not return one.

4. Click OK to save the routing query.
5. Save the configuration.