Configuring Call Setup Rules - AudioCodes Mediant 4000 SBC User Manual

Parameter
Malicious Signature
Malicious Signature Database
signature-db-enable
[MessagePolicy_UseMaliciousSignatureDB]
18.5

Configuring Call Setup Rules

The Call Setup Rules table lets you configure up to 40 Call Setup rules. Call Setup rules
define various sequences that are run upon the receipt of an incoming call (dialog) at call
setup, before the device routes the call to its destination. Call Setup rules provide you with
full flexibility in implementing simple or complex script-like rules that can be used for
Lightweight Directory Access Protocol (LDAP) based routing as well as other advanced
routing logic requirements such as manipulation. These Call Setup rules are assigned to
routing rules.
Below is a summary of functions for which you can employ Call Setup rules:

LDAP query rules: LDAP is used by the device to query Microsoft's Active Directory
(AD) server for specific user details for routing, for example, office extension number,
mobile number, private number, OCS (Skype for Business) address, and display
name. Call Setup rules provides full flexibility in AD-lookup configuration to suite just
about any customer deployment requirement:
•
Routing based on query results.
•
Queries based on any AD attribute.
•
Queries based on any attribute value (alphanumeric), including the use of the
asterisk (*) wildcard as well as the source number, destination number, redirect
number, and SBC SIP messages. For example, the following Call Setup rule
queries the attribute "proxyAddresses" for the record value "WOW:" followed by
source number: "proxyAddresses=WOW:12345*"
•
Conditional LDAP queries, for example, where the query is based on two
attributes (&(telephoneNumber=4064)(company=ABC)).
•
Conditions for checking LDAP query results.
•
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 Plans on page 495) for a specified search key in a
specified Dial Plan to obtain the corresponding 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
User's Manual
Description
rejected.

[1] Policy Whitelist = (Default) Only the specified
SIP body is allowed; the others are rejected.
Enables the use of the Malicious Signature database
(signature-based detection).

[0] Disable (default)

[1] Enable
To configure Malicious Signatures, see ''Configuring
Malicious Signatures'' on page 507.
366
Mediant 4000 SBC
Document #: LTRT-41729