"paten": "Yes"
}
}
Example 4: GET a specific MOIP tuning value for a specific MOIP stream
The following example assumes that the user has successfully logged onto the unit, received the session id
and set it to the variable token. In addition, it is assumed that the IP of the unit is 192.168.0.1. You must
change the IP to the specific unit IP in use. This example retrieves one specific parameter value from the
MOIP tuning settings for MOIP stream 1.
The user must always specify the stream number in the URI followed by the URI argument the user wishes
to retrieve.
Note
This example retrieves the freqmode from MOIP stream 1. In GET URIs only the stream argument must
contain a value for the stream, all other arguments do not contain values.
curl -X GET -i
-H "Accept: application/json" -H "X-SESSION-ID: $token" -k
"https://192.168.0.1/ws/v2/service_cfg/input/moip?stream=1&freqmode"
If successful, the return body will be:
"input": {
"moip": {
"stream": "1",
"freqmode": "NIT"
}
}
Example 5: GET multiple MOIP tuning value for a specific MOIP stream
The following example assumes that the user has successfully logged onto the unit, received the session id
and set it to the variable token. In addition, it is assumed that the IP of the unit is 192.168.0.1. You must
change the IP to the specific unit IP in use. This example retrieves multiple parameter value from the MOIP
tuning settings for MOIP stream 1.
The user must always specify the stream number in the URI followed by the URI arguments the user
wishes to retrieve.
Note
This example retrieves the freqmode, sdten, niten and paten values from MOIP stream 1. In GET URIs only
the stream argument must contain a value for the stream, all other arguments do not contain values.
curl -X GET -i -H "Accept: application/json" -H "X-SESSION-ID: $token" -k
"https://192.168.0.1/ws/v2/service_cfg/input/moip?stream=1&paten&sdten&freqmode&niten"
If successful, the return body will be:
"input": {
"moip": {
"stream": "1",
"freqmode": "NIT",
"niten": "Yes",
"paten": "Yes",
"sdten": "Yes"
}
}
Cisco D9800 Network Transport Receiver Version 2.75 RESTful Web Services API Reference Guide
155
API Definitions
Input Configuration Command