AudioCodes Mediant 4000 SBC, User Manual

Page: 493 / 1037

CHAPTER 20 SIP Definitions
Mediant 4000 SBC | User's Manual
● 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.
● Call Setup Rules table:
◆
'Rules Set ID': 2
◆
'Request Type': LDAP
◆
'Request Target': LDAP-DC-CORP
◆
'Request Key': ‘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
● IP-to-IP Routing table: A single routing rule is assigned the Call Setup Rule Set ID.
◆
(Index 1) 'Call Setup Rules Set ID': 2
■ Example 3: The 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 Skype for Business; if the query fails, the device sends the call to the
PBX.
● Call Setup Rules table:
◆
'Rules Set ID': 3
◆
'Request Type': LDAP
◆
'Request Target': LDAP-DC-CORP
◆
'Request Key': ‘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 (Skype for Business). If the attribute record does
not exist (i.e., condition is met), the rule exits with a false result and uses the second
routing rule (PBX).
● IP-to-IP Routing table: Two routing rules are assigned with the same matching
characteristics. Only the main routing rule is assigned a Call Setup Rules Set ID.
◆
Index 1:
◆
'Call Setup Rules Set ID': 3
◆
'Destination IP Group ID': 3 (IP Group for Skype for Business)
◆
Index 2:
- 460 -