Identify the Media You Are Trying to Test

This is frequently confused with the web page or media player location on your website.  The target of a streaming media task will not be the URL of a player or web page that contains the player, but the actual media resource path that is used by a player to play the file.

Once you have identified the location, check the media file type. What protocol does it use? (make sure to specify the protocol in the file path (such as rtmp:// or https://, for example).

Supported protocols include applehttp, concat, crypto, gopher, hls, http, httpproxy, mms, pipe, rtmp, rtp, tcp, udp, rtsp, https.

Creating a task

Stream URI

Enter the address of the actual media file you wish to monitor. Note that the URL must link directly to the media resource and not a web page that contains a media player. For example,

Completion Timeout (in seconds)

Enter the number of seconds the task should wait for a response from the web page before ending the task and returning an error. If this is left blank the default timeout for a task is 120 seconds.

Custom Script

Apart from media URL you can choose MediaEngine and ReportDetails by adding into the Custom Script field:

(Tasks[0] as Media).MediaEngine= “SMOOTH”;

(Tasks[0] as Media).ReportDetails = “FULL”;


Tasks[<sequential number of the task>] – specifies the sequential number of the task in the device. Note that the numbering of tasks in the device starts from 0. So to refer to the first task in the device you should provide Tasks[0].

MediaEngine  = ( “FLASH”, “GENERAL”, “SMOOTH”, “WMP”, “FLASH_FC”)

ReportDetails = (“STANDART”, “FULL”, “SHORT”)

In case of “FLASH_FC” engine should contain required MediaHost and MediaStream.


(Tasks[0] as Media).MediaHost = "rtmp://";    
(Tasks[0] as Media).MediaStream = "simulcast-flash-128k";
(Tasks[0] as Media).MediaEngine= " FLASH_FC";
(Tasks[0] as Media).ReportDetails = "Full";