2.30.1.2 MMI Managed Objects for Proxy point code

MMI information associated with Proxy point code feature is accessed from a DSR NOAM or SOAM from Main Menu, and then MMI API Guide.

After 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 Proxy point code feature:

Table 2-41 Managed Objects

Managed Object Name	Operations Supported	URI
M3RL Options	GET/PUT	/vstp/m3rloptions
Remote Signaling Points	GET/POST/PUT/DELETE	vstp/remotesignalingpoint
Link Sets	GET/POST/PUT/DELETE	/vstp/linksets

M3rl Options - PUT

The Proxy Point Code Support parameter is used for turning on or off the proxy point code feature. Proxy Point Code Support parameter must be On to enable Proxy point code feature.

Create a file with following content. File name could be anything, for example test can be used as filename:

$ vim Test.json
{
    "Proxy Point Code Support": "On"   
}

Run the following command on Active SOAM to update the data:

/vstp/m3rloptions -v PUT -r /<Absolute Path>/<File Name>.json

Sample Output:
  {
    "data": true,
    "links": {},
    "messages": [],
    "status": true
  }

remotesignalingpoints

The Proxy Point Code Indicator parameter in remotesignalingpoint MO Indicates if Point code is to be used as a proxy point code.

POST

Create a file with following content. File name could be anything, for example option name can be used as filename:

{
 "enableBroadcastException": true, 
 "mtpPointCode": “1-2-1", 
 "name": "RSP1", 
 "nprst": "Off",
 “udtxudtcnv": "NOCONV", 
 "ProxyPointCodeIndicator": "Yes"
}

Run the following command on Active SOAM to insert the data:

/vstp/remotesignalingpoints –v POST –r .json

        
Sample Output:
  {
    "data": true,
    "links": {},
    "messages": [],
    "status": true
 }

GET

Run the following command on Active SOAM to display the content:

/vstp/remotesignalingpoints

Sample Output:

{
    "data": [
        {
            "configurationLevel": "5",
            "enableBroadcastException": true, 
            "mtpPointCode": "001-002-001", 
            "name": "RSP1", 
            "nprst": "Off", 
            "udtxudtcnv": "NOCONV", 
            "ProxyPointCodeIndicator ": "Yes"
        }
    ],
    "links": {},
    "messages": [],
    "status": true
}

Link Sets – POST

Proxy RSP Name parameter in Link Sets MO indicates Name of the Proxy Remote Signaling Point associated with this Link Set.

Create a file with following content. File name could be anything, for example linksetTest can be used as filename:

$ vim linksetTest.json
 {
   "asNotification": true,
    "configurationLevel": "0",
    "cgGtmod": false,
    "enableBroadcastException": true,
    "gttmode": "Fcd",
    "ituTransferRestricted": false,
    "reservedLinkTransactionsPerSecond": 100,
    "maximumLinkTransactionsPerSecond": 120,
    "localSignalingPointName": "TestItua",
    "mtpScrSetName": "scrSet1",
    "mtpScrTestMode": true,
    "mtpScrEventLog": true,
    "name": "Test",
    "numberSignalingLinkAllowedThreshold": 1,
    "numberSignalingLinkProhibitedThreshold": 1,
    "remoteSignalingPointName": "TestItub",
    "routingContext":
    "smsProxy": "Off",
    "type": "M2PA",
    "ProxyRSPName": "RSP1" 
}

Run the following command on Active SOAM to insert the data:

/vstp/linksets -v POST -r /<Absolute Path>/<File Name>.json

        
Sample Output:
  {
    "data": true,
    "links": {},
    "messages": [],
    "status": true