Cisco D9800 Reference Manual page 92

Output Status Command
URI Level 2 Parameter
value
status
ASI example on single-stream unit (for which ASI output was configured):
curl -k -H "X-SESSION-ID: $token" "https://192.168.0.1/ws/v2/status/output/asi/collision&js=1"
Expected output (values are for example purposes only):
{
"output": {
}
}
MOIP example on single-stream unit (for which MOIP output was configured):
curl -k -H "X-SESSION-ID: $token"
"https://192.168.0.1/ws/v2/status/output/moip/collision&js=1"
Expected output (values are for example purposes only):
{
"output": {
}
}
ASI Example on NTC multi-stream unit (for which ASI1 output was configured):
curl -k -H "X-SESSION-ID: $token"
"https://192.168.0.1/ws/v2/status/output/asi1/collision&js=1"
Expected output (values are for example purposes only):
{
"output": {
}
}
MOIP Example on NTC multi-stream unit (for which MOIP2 output was configured):
curl -k -H "X-SESSION-ID: $token"
"https://192.168.0.1/ws/v2/status/output/moip2/collision&js=1"
Cisco D9800 Network Transport Receiver Version 2.75 RESTful Web Services API Reference Guide
80
"asi": {
"collision": {
"status": "No Record in Dynamic Table"
}
}
"moip": {
"collision": {
"status": "No Record in Dynamic Table"
}
}
"asi1": {
"collision": {
"status": "No Record in Dynamic Table"
}
}
Description
Conflict Value
Type: Integer
Values: 0 ... 65535
Indicate the API output status
Type: String
Values: text to indicate the output status
DPM active collision is dynamic data. If
Note
there is no collision information in UIC
table, the "status" field will indicate the
reason.
API Definitions