AudioCodes Mediant 800B User Manual page 390

Gateway & e-sbc
Hide thumbs Also See for Mediant 800B:
Table of Contents

Advertisement

Parameter
Search Key
attr-to-query
[CallSetupRules_AttributesToQuery]
Attributes To Get
attr-to-get
[CallSetupRules_AttributesToGet]
Row Role
row-role
[CallSetupRules_RowRole]
Condition
condition
[CallSetupRules_Condition]
User's Manual
To configure the search key, use the 'Search Key' parameter
(see below).
Note: The parameter is applicable only if the 'Query Type'
parameter is configured to any value other than None.
Defines the key to query. For LDAP queries, the key string is
queried in the specified LDAP server. For Dial Plan queries,
the key string is searched for in the specified Dial Plan.
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').
Examples:
To LDAP query the AD attribute "mobile" that has the value
of the destination user part of the incoming call:
'mobile=' + param.call.dst.user
To LDAP query the AD attribute "telephoneNumber" that
has a redirect number:
'telephoneNumber=' + param.call.redirect +
'*'
To query a Dial Plan for the source number:
param.call.src.user
Note: The parameter is applicable only if the 'Query Type'
parameter is configured to any value other than None.
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 parameter is applicable only if you configure the 'Query
Type' parameter to LDAP.
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.
Examples:
390
Mediant 800B Gateway & E-SBC
Description
Document #: LTRT-10298

Advertisement

Table of Contents
loading

Table of Contents