3.1 MMI Managed Objects for TIF Support
MMI information associated with TIF support is accessed from a DSR NOAM or SOAM from .
Once the MMI API Guide displays, use the application navigation to locate specific vSTP managed object information.
The following table lists the managed objects and operations supported for vSTP TIF Support feature:
Table 3-1 vSTP TIF Support Managed Objects and Supported Operations
| Managed Object Name | Supported Operations |
|---|---|
| Generic Name | Insert, Update, Delete |
| Linksets | Insert, Update, Delete |
| MtpScreeningRules | Insert, Update, Delete |
| NppActionSet | Insert, Update, Delete |
| NppServiceRuleSet | Insert, Update, Delete |
| NppServices | Display, Update |
| RemoteSignalingPoints | Insert, Update, Delete |
| TIFOptions | Display, Update |
genericname - Insert, Update, Delete
Using Generic name, you can block messages with specific generic name on certain linkset.
Example output for Display:
{
"gname": "gname1",
"settype": "Both"
}linkset - Insert, Update, Delete
A Link Set is a logical element representing link attributes assigned to a Link (/vstp/links) and a far-end point assigned to a Route (/vstp/routes).
Example output for Display:
{
"asNotification": true,
"asls8": false,
"cgGtmod": false,
"cgpnblSet": "None",
"configurationLevel": "16",
"enableBroadcastException": false,
"gnameset": "Both",
"gttmode": "Sysdflt",
"islsrsb": 1,
"ituTransferRestricted": false,
"l2TimerSetName": "Default",
"l3TimerSetName": "Default",
"linksetAccMeasOption": "No",
"localSignalingPointName": "LSP2",
"maximumLinkTransactionsPerSecond": 4000,
"name": "LS01",
"numberSignalingLinkAllowedThreshold": 1,
"numberSignalingLinkProhibitedThreshold": 1,
"randsls": "Off",
"remoteSignalingPointName": "RSP2",
"reservedLinkTransactionsPerSecond": 4000,
"rsls8": false,
"securityLogging": "Off",
"slsci": false,
"slsrsb": 1,
"smsProxy": "Off",
"type": "M3ua"
}MtpScreeningRules - Insert, Update, Delete
Sample JSON to configure MTPScreeningRules named mtpscrule:
/vstp/mtpscreeningrules –v POST –r mtpscrule.json
{
"networkIndicatorCode": "0-2",
"nsfi": "Stop",
"ruleName": "rule1",
"priority": "2",
"scrRuleGroupType": "Sio",
"scrRuleGroupName": "scr2",
"serviceIndicator": "5",
"actionIsup": "Tif_Ruleset_2",
"actionSccp": false
}
Execute following command on Active SOAM to insert:
/vstp/mtpscreeningrules –v POST –r mtpscrule.jsonNppActionSet - Insert, Update, Delete
A Numbering Plan Processor (NPP) Action Set is a collection of Conditioning Actions (CAs), Service Actions (SAs), and Formatting Actions (FAs).
{
"actSetName": "as2",
"caList": [
"Cc2",
"Ac2",
"Snx"
],
"faList": [
"Cc",
"Ac"
],
"fascrcg": [
"Dlmb",
"Dlma"
],
"ofnai": "Inc",
"sa1dgts": "ab",
"sa1val": [
10,
40
],
"saList": [
"Selscr"
]
}
/vstp/nppactionsets –v POST –r <filename>.json
Example Output:
{
"actSetName": "as2",
"caList": [
"Cc2",
"Ac2",
"Snx"
],
"faList": [
"Cc",
"Ac"
],
"fascrcg": [
"Dlmb",
"Dlma"
],
"ofnai": "Inc",
"sa1dgts": "ab",
"sa1val": [
10,
40
],
"saList": [
"Selscr"
]
}
NppServiceRuleSet - Insert, Update, Delete
{
"asn": "as2",
"fdl": "12",
"fnai": "Intl",
"fpfx": "*",
"invkserv": "None",
"srvn": "Tif
}
/vstp/nppservicerulesets –v POST –r <Filename>.json
Example Output:
{
"asn": "as2",
"fdl": "12",
"fnai": "Intl",
"fpfx": "*",
"invkserv": "None",
"srvn": "Tif
}
NPP Services - Insert, Update, Delete
{
"dlma": "33",
"dlmb": "None",
"dlmc": "None",
"dlmd": "None",
"dlme": "None",
"dlmf": "None",
"dlmg": "None",
"dlmh": "None",
"dlmi": "None",
"dlmj": "None",
"dlmk": "None",
"dlml": "None",
"dlmm": "None",
"dlmn": "None",
"dlmo": "None",
"dlmp": "None",
"intl": "4",
"nai1": "1",
"nai2": "2",
"nai3": "3",
"natl": "3",
"ruleCount": 0,
"sdwcCount": 0,
"srvn": "Tif",
"status": "On",
"unkn": 0
}
/vstp/nppservices –v PUT –r <Filename>.json
Example Output:
{
"dlma": "33",
"dlmb": "None",
"dlmc": "None",
"dlmd": "None",
"dlme": "None",
"dlmf": "None",
"dlmg": "None",
"dlmh": "None",
"dlmi": "None",
"dlmj": "None",
"dlmk": "None",
"dlml": "None",
"dlmm": "None",
"dlmn": "None",
"dlmo": "None",
"dlmp": "None",
"intl": "4",
"nai1": "1",
"nai2": "2",
"nai3": "3",
"natl": "3",
"ruleCount": 0,
"sdwcCount": 0,
"srvn": "Tif",
"status": "On",
"unkn": 0
}
RemoteSignalingPoints - Insert, Update, Delete
{
"configurationLevel": "381",
"enableBroadcastException": true,
"mtpPointCode": "012-160-014",
"name": "rsp1",
"nprst": "On",
"rcause": "100",
"splitiam": "20",
"ss7DomainType": "Ansi"
}
/vstp/remotesignalingpoints –v POST –r <Filename>.json
Example Output:
{
"configurationLevel": "381",
"enableBroadcastException": true,
"mtpPointCode": "012-160-014",
"name": "rsp1",
"nprst": "On",
"rcause": "100",
"splitiam": "20",
"ss7DomainType": "Ansi"
}
TIFOptions - Display, Update
The Trigger less ISUP Framework (TIF) Options are those configuration values that govern the overall TIF Framework. There is a single instance of this resource, which contains each of the individual options that can be retrieved and set. Because there is no collection of instances, there is no collection GET action. No new TIF Options resource can be created, so there is no POST action, and the single instance cannot be removed, so there is no DELETE action. The single instance GET is used to retrieve the options, and PUT is used to update one or more values within the set of options. A name for this single, non-deletable instance is neither required nor expected.
/vstp/tifoptions –v PUT –r <Filename>.json
Example Output:
{
"condcgpn": "None",
"condrdn": "None",
"crprel": 31,
"dfltrn": "None",
"dlma": "None",
"dlmb": "None",
"dlmc": "None",
"iamcgpn": "Dn",
"matchseq": "Dn",
"npflag": "None",
"nptypecgpn": "Sprn",
"nptyperls": "Sprn",
"nptyperly": "Sprn",
"nsaddldata": "No",
"nspublic": 0,
"rcausenp": 0,
"rcausepfx": 0,
"rlcopc": "Off",
"rnrqd": "Yes",
"snscgpndflt": "None",
"spfill": "Off",
"splitiam": "None"
"subcdpn": "None"
}