Rf Input Configuration Command - Cisco D9800 Reference Manual

Network transport receiver
Hide thumbs Also See for D9800:
Table of Contents

Advertisement

Input Configuration Command
The parameter list for the configuration APIs in this and following sections are compliant with the UIC
Note
tables in the D9800 software application, which may use some special characters that are non-compliant
with the allowed URL character set.
When using curl, URL strings that include arguments (the options after the ?) must be in quotes, as
discussed in
implicit.
However, when using a web browser, argument strings must be first converted to substitute URL safe
"escape" replacements for special, reserved characters (as discussed in rfc2396).
For example, in URL safe format, spaces that are embedded in the URL string would typically need to be
replaced by %20 (percent sign followed by the asci hex value equivalent of a space).
Since some parameters may have spaces or forward slashes or other reserved URL characters in them.
We recommend that the D9800 web GUI, and other similar implementations, pass the full URL string
through a safe-url character converter before issuing the command.
For more information about safe URL encoding, see http://www.ietf.org/rfc/rfc2396.txt, or
www.skorks.com/2010/05/what-every-developer-should-know-about-urls/.

RF Input Configuration Command

Table 134: Command Details
Command Detail
Command URL
Command Information
HTTP Methods
Access Type
Access Level
GET Syntax
POST Syntax
URI Parameters (extension to the Command URL separated by /): N/A
URI Query/Set Arguments (possible fields and values preceded by ? and separated by &):
Cisco D9800 Network Transport Receiver Version 2.75 RESTful Web Services API Reference Guide
138
HTTP Request Methods, on page
Description
https://192.168.0.1/ws/v2/service_cfg/input/rf
Allows RF tuning input settings to be read or configured.
GET, POST
Read/Write (with complex input data)
User, Admin
One of the following:
GET "https://192.168.0.1/ws/v2/service_cfg/input/rf",
GET "https://192.168.0.1/ws/v2/service_cfg/input/rf?port=1", or
GET "https://192.168.0.1/ws/v2/service_cfg/input/rf?port=1&dnlkfreq"
POST
"https://192.168.0.1/ws/v2/service_cfg/input/rf?port=[port#]&dnlkfreq=<Freq>..."
3. In this case, the conversion of special characters is
API Definitions
http://

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents