2.23.3.2 MMI Managed Objects for XUDT UDT Conversion
MMI information associated with vSTP generated XUDT UDT Conversion 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 XUDT UDT Conversion:
Managed Object Name | Supported Actions |
---|---|
GTT Sets | GET, PUT, POST, DELETE |
Remote Signaling Points | GET, PUT, POST, DELETE |
gttsets
The alwsegxudt parameter in gttsets of type OPCODE indicates if TOBR processing must be allowed on Segmented XUDT(S) message or not. The parameter supports the following values:
- NO: Specifies that no segmented XUDT message for TOBR processing must be allowed.
- YES: Allows segmented XUDT message for TOBR processing.
Note:
- The alwsegxudt parameter is configurable only when GTTSET type is OPCODE.
- The XUDT only decodes messages with maximum of two byte TCAP lengths. Therefore, TOBR is not applicable on Segmented XUDT messages if the TCAP message length takes more than 2 bytes.
- The ANSI TCAP segmented messages are not supported, although there are no restriction on the provisioning of SXUDT parameter in with ANSI opcode GTTSet type.
- This is applicable for first segment only.
POST
Create a file with following content to set value for the alwsegxudt parameter. File name could be anything, for example option name can be used as filename:
{
"alwsegxudt": "No",
"checkmulcomp": "No",
"domain": "Itu",
"gttSetType": "Opcode",
"name": "test1"
}
Execute the following command on Active SOAM to update the data:
/vstp/gttsets –v POST –r <filename>.json
Execute the following command to display the content:
vstp/gttsets
{
"configurationLevel": "1",
"domain": “Itu",
"gttSetType": “Skbcsm",
"name": "set1"
}
Sample Output:
{
"data": true,
"links": {},
"messages": [],
"status": true
}
GET
Execute the following command to display the content:
/vstp/gttsets
Sample Output:
{
"data": [
{
"alwsegxudt": "No",
"checkmulcomp": "No",
"domain": "Itu",
"gttSetType": "Opcode",
"name": "test1"
}
],
"links": {},
"messages": [],
"status": true
}
remotesignalingpoints
The udtxudtcnv parameter remotesignalingpoints MO indicates the type of conversion allowed for respective Remote Signaling Point (RSP). The parameter supports the following values:
- NOCONV: Specifies that no conversion must be performed for the destination.
- UDTTOXUDT: Specifies that UDT(S) messages must be converted to XUDT(S) messages.
- XUDTTOUDT: Specifies the following:
- Non-Segmented XUDT(S) messages must be converted to UDT(S) messages.
- Segmented XUDT(S) messages must not be converted to UDT(S) messages.
- SXUDTTOUDT: Specifies that both Segmented XUDT(S) and non-segmented XUDT messages must be converted to UDT(S) messages.
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",
"rcause": "None",
"udtxudtcnv": "SXUDTTOUDT",
"splitiam": "None",
"ss7DomainType": "Ansi“
}
Execute the following command on Active SOAM to update the data:
/vstp/remotesignalingpoints –v POST –r <filename>.json
Sample Output:
{
"data": true,
"links": {},
"messages": [],
"status": true
}
GET
Execute the following command to display the content:
/vstp/remotesignalingpoints
Sample Output:
{
"data": [
{
"configurationLevel": "5",
"enableBroadcastException": true,
"mtpPointCode": "001-002-001",
"name": "RSP1",
"nprst": "Off",
"rcause": "None",
"udtxudtcnv": "SXUDTTOUDT",
"splitiam": "None",
"ss7DomainType": "Ansi"
}
],
"links": {},
"messages": [],
"status": true
}