AudioCodes Mediant 4000 SBC - Configuring Call Setup Rules

CHAPTER20 SIP Definitions
Mediant 4000 SBC | User's Manual
You can load the User Information file using any of the following methods:
■ Web interface - User Information table (see Configuring SBC User Information Table through
Web Interface on page448)
■ CLI - sbc user-info-table import-csv-from (see Configuring SBC User Information Table
through CLI on page450)
■ Automatic Update mechanism - [SBCUserInfoFileUrl] parameter (see Automatic Update
Mechanism)
For backward compatibility only: When configuring a User Information file to load
through the Auxiliary Files page, use the following syntax:
[SBC]
FORMAT LocalUser,UserName,Password,IPGroupID
For example:
[SBC]
FORMAT LocalUser,UserName,Password,IPGroupID
John,johnd,2798,2
Sue,suep,1234,1
Configuring Call Setup Rules
The Call Setup Rules table lets you configure up to 64 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 queries: 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 suit 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.
- 452 -