vSTP Screening MTP Messages Based On DPCs
(Doc ID 2651241.1)
Last updated on DECEMBER 21, 2021
Applies to:
Oracle Communications Diameter Signaling Router (DSR) - Version DSR 8.4.0 and laterTekelec
Goal
We are not able to configure the Default rule for BlkDpc type.
This is the scrrule2 file:
"zone":"*",
"area":"*",
"signalingPointId":"*",
"scrRuleGroupName": "scr2",
"nsfi": "Stop",
"ruleName": "rule2",
"scrRuleGroupType":"BlkOpc"
}
When Trying to add mtp screening rule:
/vstp/mtpscreeningrules -v POST -r /var/TKLC/db/filemgmt/scrrule2
{
"data": [],
"links": {},
"messages": [
{
"area": "vstp",
"message": "String does not match pattern for [root.zone]",
"severity": 3,
"timestamp": "2020-02-12T11:23:34-05:00"
}
],
"status": false
This is weird because in the mtpscreeningrule.json file, zone, area and sinalingPointId have the same properties.
"area": {
"description": "ITU international area. The area in the point code represented by zone-area-id.",
"maxLength": 7,
"pattern": "^((([0-1]?[0-9]?[0-9])|([2][0-4][0-9])|(25[0-5]))(-))?(([0-1]?[0-9]?[0-9])|([2][0-4][0-9])|(25[0-5]))$|^[*]$|^[D]$",
"type": "string"
},
"signalingPointId": {
"description": "ITU international ID. The ID in the point code represented by zone-area-id.",
"maxLength": 3,
"pattern": "^(([0-7])(-))?([0-7])$|^[*]$|^[D]$",
"type": "string"
},
"zone": {
"description": "ITU international zone. This parameter specifies the zone in the point code represented by zone-area-id.",
"maxLength": 3,
"pattern": "^(([0-7])(-))?([0-7])$|^[D]$",
"type": "string"
}
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |