DescriptionURI Argument
PE Action
Type: String
Values: "Drop", "Pass", "Map", "XCode"
action
Output PMT PID
Type: Integer
Values: 0..8191
pmtpid
Output Channel Number
Type: Integer
Values: 0..65535
outchan
To use this command properly, a level 1 parameter must be specified such as asi (asi1/asi2 on a NTC MS
unit) followed by a level 2 parameter which is pe followed by the peid argument that must be supplied
with a value, and only then can the remaining arguments (as below) be used for GET/POST. In-depth
CURL examples follow below.
Note
POST Examples:
All POST examples will apply to the DPM ASI PE settings, but the same examples can be applied to the
DPM MOIP PE settings, by simply replacing the ‘asi’ in the URI with ‘moip’
Note
Example 1: Set Various DPM ASI Parameters for a specific PE
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 changes both the PE action to Pass and Output
Channel Number to 105.
The asi/pe?peid=VAL must be provided before adding the specific arguments as seen in the curl command
below (due to having to place level 1 parameter followed by level 2 followed by peid followed by optional
arguments).
Note
curl -X POST -i -H "Accept: application/json" -H "X-SESSION-ID: $token" -k
"https://192.168.0.1/ws/v2/service_cfg/output/asi/pe?peid=1&action=Pass&outchan=105"
If successful, the return body will be:
"response": {
"code": "10",
"result": "success",
"message": ""
}
GET Examples:
Cisco D9800 Network Transport Receiver Version 2.75 RESTful Web Services API Reference Guide
195
API Definitions
Output Configuration Command