AudioCodes Mediant 500 E-SBC, User Manual

Page: 234 / 920

User's Manual 234 Document #: LTRT-10437
Mediant 500 E-SBC
Parameter Description
Attributes To Query
CLI: attr-to-query
[CallSetupRules_AttributesToQuery]
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.re '*' (searches
for the AD attribute, "telephoneNumber" that has a
redirect number)
Attributes To Get
CLI: attr-to-get
[CallSetupRules_AttributesToGet]
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.
Row Role
CLI: row-role
[CallSetupRules_RowRole]
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.
Condition
CLI: condition
[CallSetupRules_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)