IP control of your server

You are able to control the starting and stopping your TV Server recordings, and can query the appliance’s status, by calling a URL. You can create the URLs necessary to control your server by visiting the Automation URL builder in the web interface.
NOTE The HTTP remote control feature is only available in platform 3 and later appliances.
Browse to the appliance and tap the Advanced node on the left, then select Automation URLs from the menu beneath. Platform 3 users should choose Options then Automation URLs instead.
Channels
Lists all available inputs on your appliance. Select one or more channels that you wish to control by URL.
Operation
Select whether you wish to START, STOP, or report back STATUS on recording by choosing the appropriate entry from the drop-down list.
Username and Password
Provide the credentials of a user that has access to the appliance's web Interface.
Title*†
Provide the title of the new recording.
Description*†
Provide the description.
Folder*†
Provide the destination directory.
Do not include slide images with recording file*†
Omit captured image files from the final recording.
Duration (mins)*†
Provide the maximum length in minutes.
Publish*†
Set either to default, yes or no, this drop-down option determines whether the recording will be published after it is completed.
Publish format*†
Choose a quality setting for the published file.
Delete original after publish*†
When checked, the original recording is deleted once it has been published.
Return simple status*
When checked, status information is always returned in a simplified CSV format.
The Generated URL field shows a dynamically updating address that will automate the appliance using the parameters you set. You can copy the URL or click the ‘Test URL’ button to open a new web page and initiate the automated commands.

* optional parameter
† applicable only where Operation is START

Making a Direct HTTP Connection

To make a direct HTTP connection with the appliance, take the following steps:
  1. Make a TCP connection to the server on port 80.
  2. Send your commands in the following format:

    GET /<path> HTTP/1.0\n\n

    Where path has either been created using the Automation URL builder, or constructed in code using specified parameters.

  3. Disconnect.

Status

When the Operation is STATUS, and wherever a START or a STOP has been specified, the appliance will return status in a comma separated format.
An example of the appliance status is shown below:
Slides,1,00:20:28
Camera Input,1,00:20:28
The first field is the name of the channel. The second field denotes whether the channel is actively recording, and the third shows the duration of that recording.

Parameter Overview

If you are building the URLs programmatically, the following parameters can be used to provide data values.
NOTE The strings you build must be URL encoded. You can do this in code or by using a free online service such as www.url-encode-decode.com.
id
The source for the operation. This is in the format:
id=<name>
Where name is a string matching the name of the channel in question. Example: 
id=Camera
op
The operation to execute. This can be one of three string values:
op=<START|STOP|STATUS>
Where START begins recording, STOP ends it, and STATUS retrieves information on the status of recording. Example: 
op=STATUS
format
How the status response text should be formatted.
format=<csv | json>
This is a string value determining either comma separated (CSV) or JSON. Example: 
format=csv
username
The account of the user who will execute the operation.
username=<string>
This is a string value of the username in question. Example: 
username=admin
password
An MD5 hash.
password=<string>
This is the string hash of the password associated with username. Example: 
password=8409eb933e9f364ce2a7dbad59201f2f
NOTE You can either hash the password programmatically, or use a free online service such as www.md5hashgenerator.com
folder
The name of the folder in which to store the new recording.
folder=<string>
A string value of the subdirectory in question. Example: 
folder=Content+Folder
title
The title of the recording.
title=<string>
A string value representing the new recording’s title. Example: 
title=Sales+Department+Meeting
description
The description of the recording:
description=<string>
A string value representing the new recording’s description. Example: 
description=Monday+morning+sales+team+meeting
duration
The maximum length for the recording.
duration=< integer >
The length is expressed in minutes. Example: 
duration=60
noslides
Include or omit captured images with the recording.
noslides=< BOOLEAN>
To omit slides use a value of 1, and to include them a value of 0. Example: 
noslides=1
publish
Determined whether the recording should be published.
publish=<BOOLEAN>
To publish use a value of 1, and to not publish a value of 0. Example: 
publish=0
transspec
The name of the transcoding profile for publishing:
transspec=<string>
The string representing the profile name. Example: 
transspec=HIGH+(1.5Mbit)

Examples

Below are some examples of common automation URLs.
Start making a new recording entitled “My Recording” from source “Camera”: 
http://<server-ip>/admin/quickrecord.php?op=START&id=Camera&title=My+Recording&format=csv
Start recording on all channels, using default settings: 
http://<server-ip>/admin/quickrecord.php?op=START
Stop all recordings: 
http://<server-ip>/admin/quickrecord.php?op=STOP
Here, user ‘admin’ will start a recording from the source card “Slides” entitled “Morning Meeting” with a description of “Class morning meeting for students and teachers” and a maximum duration of 60 minutes. It will be stored in a folder “meetings” and will not include slides. It will be published using a 1.5Mbit transcoding profile, and status from the server will be returned in a comma-separated format. 
http://<server-ip>/admin/quickrecord.php?op=START&username=admin&folder=meetings&publish=1&title=Morning+Meeting&description=Class+morning+meeting+for+students+and+teachers&duration=60&noslides=1&transspec=HIGH+(1.5Mbit)&format=csv&password=21232f297a57a5a743894a0e4a801fc3&id=Slides
The status returned from the above URL will be as follows:
Slides,0,
Camera Input,1,00:00:00
This indicates that the channel defined as Camera Input has begun recording, whereas the channel defined as Slides remains idle.
A later status: 
http://<server-ip>/admin/quickrecord.php?op=STATUS&format=csv