EasyManuals Logo

AudioCodes Mediant 3000 User Manual

AudioCodes Mediant 3000
1070 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #291 background imageLoading...
Page #291 background image
Version 7.0 291 Mediant 3000
User's Manual 16. Services
'Rules Set ID': 1
'Attributes to Query': ‘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
Routing table configuration: A single routing rule is assigned the Call Setup
Rule Set ID.
Index 1:
'Call Setup Rules Set Id': 1
Example 2: This 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.
Call Setup Rules table configuration:
'Rules Set ID': 2
'Attributes to Query': ‘telephoneNumber=’ + param.call.src.user
'Attributes to Get': displayName
'Row Role': Use Current Condition
'Condition': ldap.attr. displayName exists
'Action Subject': param.call.src.name
'Action Type': Modify
'Action Value': ldap.attr. displayName
Routing table configuration: A single routing rule is assigned the Call Setup
Rule Set ID.
Index 1:
'Call Setup Rules Set Id': 2
Example 3: This example configures the device to route the incoming call according
to whether or not the source number of the incoming call also exists in the AD server.
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 is found, the device sends the call to the Lync server; if the query
fails, the device sends the call to the PBX.
Call Setup Rules table configuration:
'Rules Set ID': 3
'Attributes to Query': ‘telephoneNumber=’ + param.call.src.user
'Attributes to Get': telephoneNumber
'Row Role': Use Current Condition
'Condition': ldap.found !exists
'Action Subject': -
'Action Type': Exit
'Action Value': false
If the attribute record is found (i.e., condition is not met), the rule ends with a
default exit result of true and uses the first routing rule (Lync). If the attribute

Table of Contents

Other manuals for AudioCodes Mediant 3000

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the AudioCodes Mediant 3000 and is the answer not in the manual?

AudioCodes Mediant 3000 Specifications

General IconGeneral
BrandAudioCodes
ModelMediant 3000
CategoryGateway
LanguageEnglish

Related product manuals