AudioCodes Mediant 4000 SBC User Manual page 486

CHAPTER 20 SIP Definitions
● Manipulation of call parameters such as source number, destination number, and redirect
number and SBC SIP messages, while using LDAP query results.
● Multiple LDAP queries.
■ Dial Plan queries: For SBC calls, you can use Call Setup rules to query the Dial Plan table (see
Configuring Dial
Dial Plan tag. Call Setup rules can also change (modify) the name of the obtained tag. The
device can then route the call using an IP-to-IP Routing rule (in the IP-to-IP Routing table) that
has a matching tag (source or destination). You can also associate a Call Setup rule with an IP
Group (in the IP Group table). Once the device classifies the incoming call to a source IP
Group, it processes the associated Call Setup rule and then uses the resultant tag to locate a
matching IP-to-IP Routing rule. You can also use Call Setup rules for complex routing
schemes by using multiple Dial Plan tags. This is typically required when the source and/or
destination of the call needs to be categorized with more than one characteristics. For
example, tags can be used to categorize calls by department (source user) within a company,
where only certain departments are allowed to place international calls.
■ ENUM queries: For SBC calls, you can use Call Setup rules to query an ENUM server and to
handle responses from the ENUM server. ENUM translates ordinary telephone numbers
(E.164 telephone numbers) into Internet addresses (SIP URIs), using the ENUM's DNS
NAPTR records. For example, if the device receives an INVITE message whose destination
number is in E.164 format, you can configure a Call Setup rule to query the ENUM server for
the corresponding URI address, which is then used in the INVITE's Request-URI.
■ HTTP requests (queries): You can use Call Setup rules to query or notify an HTTP/S server,
which is configured in the Remote Web Services table
page 247). If a response is expected from the server, the query is sent as an HTTP GET or
HTTP POST request (configurable). If no response is required from the server (i.e., to notify the
server of a specific condition), then an HTTP POST for notifications is sent (configurable).
■ Manipulation (similar to the Message Manipulations table) of call parameters (such as source
number, destination number, and redirect number) and SBC SIP messages.
■ Conditions for routing, for example, if the source number equals a specific value, then use the
call routing rule.
You configure multiple Call Setup rules and group them using a Set ID. This lets you apply multiple
Call Setup rules on the same call setup dialog. To use your Call Setup rule(s), you need to assign
the Set ID to one of the following, using the 'Call Setup Rules Set ID' field:
■ SBC IP-to-IP routing rules (see
■ SIP Interface rules (see
■ IP Groups (see
If assigned to an IP Group, the device processes the Call Setup rule for the classified source IP
Group immediately before the routing process. If assigned to a routing rule only, the device first
locates a matching routing rule for the incoming call, processes the assigned Call Setup Rules Set
ID, and then routes the call according to the destination configured for the routing rule. The device
uses the routing rule to route the call depending on the result of the Call Setup Rules Set ID:
■ Rule's condition is met: The device performs the rule's action and then runs the next rule in
the Set ID until the last rule or until a rule with an Exit Action Type. If the Exit rule is configured
with a "True" Action Value, the device uses the current routing rule. If the Exit rule is
configured with a "False" Action Value, the device moves to the next routing rule. If an Exit
Action Type is not configured and the device has run all the rules in the Set ID, the default
Action Value of the Set ID is "True" (i.e., use the current routing rule).
■ Rule's condition is not met: The device runs the next rule in the Set ID. When the device
reaches the end of the Set ID and no Exit was performed, the Set ID ends with a "True" result.
Plans) for a specified key in a specified Dial Plan to obtain the corresponding
Configuring SBC IP-to-IP Routing
Configuring SIP Interfaces
Configuring IP Groups)
- 453 -
Mediant 4000 SBC | User's Manual
(Configuring Remote Web Services
Rules)
on page 334)
on