94
6. 3. Index Channel File Structure
TORNADO allows flexible EPG and channel list management. The system allows EPG and channel list
generation either from the Content Management System (CMS) or from a text file located on a web server
that has the following format (‘ |’ delimited):
From Broadcaster the following URL can be used. This URL is generated using the Admin Interface of
the Broadcaster and implementing the following steps:
Log into the Admin Interface
Select “Channel Management”
Select “Index File Generate”. This will generate the index file that has the channel listing and
EPG.
The URL location will be the following: http://broadcaster_ip_address/web/cfg/uobjects.txt
To implement the Index File use the following steps on the STB:
Log into the Admin Interface
Select “Local media Server”
Enter the above URL into the “Media Config URL”. This will take the channel listing from the
URL location. Please, make sure that the “Streaming Services” section is disabled, because it has
higher priority and if the “Content Server IP Address” is defined the STB will try to pick up its
channel and EPG listing form the CMS server instead of the Media Config URL.
The “Media Config URL” file has the following structure:
NAME |FILE_TYPE |SIZE |LOCATION |DESCRIPTION |TIMER |INDEX |TYPE
|RECORDING_STATE |RATING |COST |IMAGE_URL |
NAME – channel name
FILE_TYPE – this is the file type such as AVI, MP3
SIZE – size of the file in kilobytes
LOCATION – this is URL of the channel. For dynamic files from a broadcaster, the URL has the
following format:
http://broadcaster_ip:8000/cgi-bin/strm.cgi?run=wsub&obj_id=46&p=5&mac=$MAC
The location can also have a format of:
udp:// -- used for TS multicast/udp and TS unicast/udp transport
rtp:// -- RTP packet format
rtsp:// - RTP format
rtmp:// - Flash format
mms:// -- Microsoft Format
Some format may not be fully properly supported based on codec, streaming, and packet specifics.
DESCRIPTION – this is the channel description