AudioCodes Mediant 500 MSBR, Руководство пользователя

Страница: 377 / 1248

Version 7.2 377 Mediant 500 MSBR
User's Manual 21. SIP Definitions
Parameter Description
(string element only).

[6] Remove Prefix = Removes value from the beginning of the
string (string element only).

[20] Run Rules Set = Performs a different Rule Set ID, specified in
the 'Action Value' parameter (see below)

[21] Exit = Stops the Rule Set ID and returns a result ("True" or
"False"). .
Action Value
action-value
[CallSetupRules_ActionVal
ue]
Defines a value that you want to use in the action.
The valid value is a string of up to 300 characters (case-insensitive).
Examples:

'+9723976'+ldap.attr.alternateNumber

'9764000'

ldap.attr.displayName

srctags

true (if the 'Action Type' is set to Exit )

false (if the 'Action Type' is set to Exit )
21.3.1 Call Setup Rule Examples
Below are configuration examples for using Call Setup Rules.

Example 1: The example configures the device to replace (manipulate) the incoming
call's source number with a number retrieved from the AD by an LDAP query. The
device queries the AD server for the attribute record, "telephoneNumber" whose value
is the same as the received source number (e.g., "telephoneNumber =4064"). If such
an Attribute exists, the device retrieves the number of the attribute record,
"alternateNumber" and uses this number as the source number.
•
Call Setup Rules table:
♦
'Rules Set ID': 1
♦
'Query Type': LDAP
♦
'Query Target': LDAP-DC-CORP
♦
'Search Key': ‘telephoneNumber=’ + param.call.src.user
♦
'Attributes to Get': alternateNumber
♦
'Row Role': Use Current Condition
♦
'Condition': ldap.attr. alternateNumber exists
♦
'Action Subject': param.call.src.user
♦
'Action Type': Modify
♦
'Action Value': ldap.attr. alternateNumber
•
IP-to-IP Routing table: A single routing rule is assigned the Call Setup Rule Set
ID.
♦
(Index 1) 'Call Setup Rules Set ID': 1

Example 2: The example configures the device to replace (manipulate) the incoming
call's calling name (caller ID) with a name retrieved from the AD by an LDAP query.
The device queries the AD server for the attribute record, "telephoneNumber" whose
value is the same as the received source number (e.g., "telephoneNumber =5098"). If
such an attribute is found, the device retrieves the name from the attribute record,
"displayName" and uses this as the calling name in the incoming call.