MMI Managed Objects for MTP Origin-Based Routing (MOBR)

2.36.1.2 MMI Managed Objects for MTP Origin-Based Routing (MOBR)

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

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 MOBR feature:

Table 2-60 MMI Managed Objects for MOBR

Managed Object Name	Supported Operations	URI
M3RL Options	GET, PUT	/vstp/m3rloptions
Remote Signaling Points	GET, POST, PUT, DELETE	/vstp/remotesignalingpoint
Remote Signaling Point Status	GET	/vstp/remotesignalingpointstatus
SCCP Options	GET, PUT	/vstp/sccpoptions
Rtx	GET, POST, PUT,DELETE	/vstp/rtx
Rtx Status	GET	/vstp/rtxstatus

M3rl Options

PUT

The MOBR parameter is used for turning on or off the MOBR feature. MOBR parameter must be On to enable the MOBR feature.

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


$ vim Test.json
{
    "mobrSupport": "On"  
}

Perform 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
  }

GET

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

/vstp/m3rloptions

Sample Output:


{
    "data": {
        "ProxyPcSupport": "Off",
        "cncfSupport": "Off",
        "cnvAInat": 1,
        "cnvCgda": false,
        "cnvCgdi": false,
        "cnvCgdn": false,
        "cnvCgdn24": false,
        "cnvClgItu": "Off",
        "gtCnvDflt": false,
        "islsbrEnabled": false,
        "m2paSctpRxbusyLink": "Off",
        "mobrSupport": "On",
        "pct": "Off",
        "performanceMeasurement": "Off",
        "randsls": "Off",
        "slsRotation": true,
        "slscnv": "Off",
        "slsocbEnabled": false,
        "slsreplace": false,
        "sparePCSupportEnabled": true,
        "ttMapSupport": "Off",
        "xListClusterThreshold": 90,
        "xListExpiryTimerDuration": 60
    },
    "links": {
        "update": {
            "action": "PUT",
            "description": "Update this item.",
            "href": "/mmi/dsr/v4.6/vstp/m3rloptions/",
            "type": "status"
        }
    },
    "messages": [],
    "status": true
}

Remote Signaling Points

The Exception Route Indicator parameter in Remote Signaling Point managed object indicates that the RSP contain Exception Route.

POST

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

{
            "groupCode": "ab",
            "mtpPointCode": "5-120-3",
            "name": "Itui_5_120_3",
            "rtx": "Yes",
            "ss7DomainType": "Itui"
        }

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

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

Sample Output:

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

GET

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

/vstp/remotesignalingpoints

Sample Output:

{
    "data": [       
{
            "configurationLevel": "4",
            "enableBroadcastException": false,
            "groupCode": "aa",
            "mtpPointCode": "5-120-3",
            "name": "Itui_5_120_3",
            "nprst": "Off",
            "prx": "No",
            "rcause": "None",
            "rtx": "Yes",
            "splitiam": "None",
            "ss7DomainType": "Itui",
            "udtxudtcnv": "NOCONV"
        }
    ],
    "links": {},
    "messages": [],
    "status": true
}

PUT

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

{
            "groupCode": "aa",
            "mtpPointCode": "5-120-3",
            "name": "Itui_5_120_3",
            "rtx": "Yes",
            "ss7DomainType": "Itui"
}

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

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

Sample Output:

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

Remote Signaling Point Status - GET

Perform the following command on Active SOAM to show the content:

/vstp/remotesignalingpointstatus

Sample Output:

"data": [
{
            "mpServerHostname": "<host-mp-name>",
            "name": "Itui_5_120_3",
            "operationalStatus": "Unavailable",
            "pointCode": "5-120-3",
            "routes": [
                {
                    "adjacentPC": "Itui_5_120_3",
                    "linksetName": "LS_ITUI_M3UA_01",
                    "routeAdjacentStatus": "Down",
                    "routeCost": 5,
                    "routeName": "RT_ITUI_01",
                    "routeRemoteStatus": "Available",
                    "routeStatus": "Unavailable"
                }
            ],
            "rspAdminState": "Enabled",
            "rtx": "Yes",
            "ss7DomainType": "Itui",
            "statusKnown": true,
            "timeOfLastUpdate": "2026-04-20T07:46:17-04:00"
        }
]

 "links": {},
    "messages": [],
    "status": true
}

SccpOptions

The MobrSccpOpc parameter in SccpOptions managed object indicates three possible OPC values that may be used within SCCP messaging. The OPC originally in the routing header, the vstp TPC, and the CGPA OPC (validated either through route-on-dpcssn or route-on-gt).

PUT

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

{
            "mobrsccpopc": "mtp"
}

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

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

Sample Output:

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

GET

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

/vstp/sccpoptions

Sample Output:

{
    "data": [
        {
            "allowedFirstSegLen": 0,
            "alwMsgDuringRsmblyErr": false,
            "cgpaGttOnResponseUdts": "On",
            "class1seq": "Disabled",
            "dfltfallback": false,
            "dfltgttmode": "Cd",
            "enableIntermediateGttact": "Off",
            "isSegXUDTfeatureEnable": false,
            "mobrsccpopc": "mtp",
            "mtprgtt": "Off",
            "mtprgttfallback": "Mtproute",
            "reassemblyTimerDurationAnsi": 5000,
            "reassemblyTimerDurationItu": 10000,
            "segmentedMSULength": 200,
            "sendVstpgenUdtsOnOpc": "Off",
            "smsDelivery": "Off",
            "smsOrigination": "Off",
            "smsTermination": "Off",
            "tcapErrorDiscard": "Off",
            "tgtt0": "None",
            "tgtt1": "None",
            "tgttudtkey": "Mtp",
            "tgttxudtkey": "Mtp",
            "travelVelocity": 700
        }
    ],
    "links": {},
    "messages": [],
    "status": true

RTX

GET

Perform the following command on Active SOAM to show the content:

/vstp/rtx

Sample Output:

{

    "data": [
        {
            "dpc": 16843011,
            "dpcStr": "001-001-003",
            "linksetId": 1,
            "linksetName": "LS_M3UA_ANSI_A",
            "opc": 16843009,
            "opcStr": "001-001-001",
            "routeCost": 15,
            "rspId": 1,
            "rtxId": 1,
            "rtxName": "RTX_ANSI_A"
        }
    ],

    "links": {},
    "messages": [],
    "status": true
}

POST

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

{
            "dpcStr": "1-1-3",
            "linksetName": "LS_M3UA_ANSI_A",
            "opcStr": "1-1-1",
            "routeCost": 15,
            "rtxName": "RTX_ANSI_A"
        }

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

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

Sample Output:

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

PUT

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

{
           "dpcStr": "1-1-3",
            "linksetName": "LS_M3UA_ANSI_A",
            "opcStr": "1-2-1",
            "routeCost": 15,
            "rtxName": "RTX_ANSI_A"
}

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

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

Sample Output:

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

RTX Status

GET

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

/vstp/rtxstatus

Sample Output:

{

    "data": [
        {
            "adjacentStatus": "Unavailable",
            "dpcStr": "001-001-003",
            "linksetName": "LS_ANSI_A",
            "mpServerHostname": "stik10314-so1mp1",
            "nonadjacentStatus": "Available",
            "routeCost": 15,
            "rtxId": 1,
            "rtxName": "RTX_ANSI_A",
            "rtxStatus": "Unavailable",
            "rtxStatusTimeStamp": "2026-04-22T08:24:30-04:00"
        }
    ],
    "links": {},
    "messages": [],
    "status": true
}