2.25.1.1 MMI Managed Objects for TPDA Based Filtering
MMI information associated with vSTP generated TPDA Based Filtering can be configured from a DSR NOAM or SOAM from
.Once the MMI API Guide gets opened, use the application navigation to locate specific vSTP managed object information.
The following table lists the managed objects and operations supported for TPDA Based Filtering functionality:
Managed Object Name | Supported Actions |
---|---|
gttsets | GET, PUT, POST, DELETE |
globaltitleaddresses | GET, PUT, POST, DELETE |
gttsets
The gttSetType parameter for TPDA must be set to MSISDN.
GET
Execute the following command to display the content:
/vstp/gttsets
Sample Output:
{
"domain": “Itu",
"gttSetType": “Msisdn",
"name": "set1"
}
globaltitleaddresses
The emapaddr and smapaddr parameters in globaltitleaddresses MO configures the a GTA with GTT Set having “Msisdn” gttSetType.
POST
{
"ccgt": false,
"cgGtmod": false,
"cgpcaction": "Dflt",
"emapaddr": "11223344",
"fallback": "Sysdflt",
"gttSetName": “set1",
"routingIndicator": “Gt",
"rspName": "rsp1",
"smapaddr": "11223344",
"translateIndicator": "Dpc“
}
Execute the following command on Active SOAM to create the data:
/vstp/globaltitleaddresses/ -v POST -r <filename>.json
Sample Output:
{
"data": true,
"links": {},
"messages": [],
"status": true
}
GET
Execute the following command to display the content:
/vstp/globaltitleaddresses
Sample Output:
{
"ccgt": false,
"cgGtmod": false,
"cgpcaction": "Dflt",
"configurationLevel": "402",
"emapaddr": "11223344",
"fallback": "Sysdflt",
"gttSetName": "set1",
"routingIndicator": “Gt",
"rspName": "rsp1",
"smapaddr": "11223344",
"translateIndicator": "Dpc",
"uniqueIdentifier": "e9f9edc0-1018-4169-a181-564ff616b4be"
}