Ncast telepresenter reference manual – NCast Telepresenter M4 User Manual

Page 33

Advertising
background image

NCast Telepresenter Reference Manual

RT Set title information to "Weekly Performance Review"

Commands are case-sensitive and must be written exactly as shown. The commands are processed in the
order given.

The presenter and title information are stored by the Telepresenter in an XML file associated with archived
MPEG-4 file. This XML file will normally be uploaded to the content server and can be used to provide
additional details about the content for archiving and indexing.

The "Telepresenter Serial Interface Manual" lists all the commands available on the serial IP interface.
Please check that document for additional setup commands that might be issued.

At the end of the event period, the program issues the "End Session" command "PE". No other commands
are sent.

The scheduler program queries the calendar every few minutes. Changes to the schedule may be entered
prior to this query. Once an event has started the event can only be stopped by going directly to the Web in-
terface of the Telepresenter and stopping it manually or waiting for the scheduled stop.

The scheduler program does not check for conflicts or overlapping events. If times overlap for a given
Telepresenter the results will occur in the order scheduled

3.9.7. iCalendar Overview

There are many different calendar applications in use, both PC based and Web based. NCast provides a
facility to utilize these other calendar applications to generate schedules through a file interchange standard
known as “iCalendar”.

Another situation where use of an iCalendar file would be needed is when immediate access to Google
Calendar is not available. For example, if Telepresenters are being utilized to record a conference on a
closed network at a hotel without Internet access, the scheduler file can be created for all tracks of the
conference and used to run all machines during the event.

3.9.8. The iCalendar Standard

iCalendar is the name for an Internet industry standard from the Internet Engineering Task Force (IETF):

RFC 2445: Internet Calendaring and Scheduling Core Object

RFC 2446: iCalendar Transport-Independent Interoperability

These standards specify the format and contents of a file (usually a “.ics” file) which contains text strings
describing calendar events. The sample below is a small portion of a typical iCalendar file:

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:NCast Corporation
X-WR-TIMEZONE:America/Los_Angeles
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701025T020000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD

The iCalendar file interchange standards are not associated with the popular Macintosh program “iCal” or
any other specific calendar application. The files provide a standard way to export, import and exchange
calendar events, ToDo’s, meeting invitations and blog entries between different computer applications, and
indeed, many different programs now support this standard (including Google Calendar).

NCast Corporation

Revision 2.2

Page 33

Advertising
This manual is related to the following products: