AudioCodes Mediant 3000 User Manual page 289

User's Manual
Parameter
Index
[CallSetupRules_Index]
Rules Set ID
[CallSetupRules_RulesSetI
D]
Attributes To Query
[CallSetupRules_Attributes
ToQuery]
Attributes To Get
[CallSetupRules_Attributes
ToGet]
Row Role
[CallSetupRules_RowRole]
Condition
[CallSetupRules_Condition]
Version 7.0
Table 16-15: Call Setup Rules Parameter Descriptions
Defines an index number for the new table record.
Note: Each rule must be configured with a unique index.
Defines a Set ID for the rule. You can define the same Set ID for
multiple rules to create a group of rules. You can configure up to 10 Set
IDs, where each Set ID can include up to 10 rules. The Set ID is used to
assign the Call Setup rules to a routing rule in the routing table.
The valid value is 0 to 9. The default is 0.
Defines the query string that the device sends to the LDAP server.
The valid value is a string of up to 100 characters. Combined strings
and values can be configured like in the Message Manipulations table,
using the '+' operator. Single quotes (') can be used for specifying a
constant string (e.g., '12345').
For example:

'mobile=' + param.call.dst.user (searches for the AD attribute,
"mobile" that has the value of the destination user part of the
incoming call)

'telephoneNumber=' + param.call.redirect + '*' (searches for the AD
attribute, "telephoneNumber" that has a redirect number)
Defines the attributes of the queried LDAP record that the device must
handle (e.g., retrieve value).
The valid value is a string of up to 100 characters. Up to five attributes
can be defined, each separated by a comma (e.g., msRTCSIP-
PrivateLine,msRTCSIP-Line,mobile).
Note: The device saves the retrieved attributes' values for future use in
other rules, until the next LDAP query or until the call is connected.
Thus, the device does not need to re-query the same attributes.
Determines which condition must be met in order for this rule to be
performed.

[0] Use Current Condition = The Condition configured for this rule
must be matched in order to perform the configured action (default).

[1] Use Previous Condition = The Condition configured for the rule
located directly above this rule in the Call Setup table must be
matched in order to perform the configured action. This option lets
you configure multiple actions for the same Condition.
Defines the condition that must exist for the device to perform the
action.
The valid value is a string of up to 200 characters (case-insensitive).
Regular Expression (regex) can also be used, for example:

ldap.attr.mobile exists (attribute "mobile" exists in AD)

param.call.dst.user == ldap.attr.msRTCSIP-PrivateLine (called
number is the same as the number in the attribute "msRTCSIP-
PrivateLine")

ldap.found !exists (LDAP record not found)

ldap.err exists (LDAP error exists)
Description
289
16. Services
Mediant 3000