Specifications

6-45
Cisco TV CDS 2.5 ISA Software Configuration Guide
OL-24788-01
Chapter 6 System Reporting
Archived Data
Stream Activity Reports
The Stream Activity Reports archive contains all trick mode and play actions of all streams within the
given 24-hour period. Table 6-12 describes the fields that are exported to the CSV file.
mOperation Operation that was taking place when the stream failed. For example: createStream,
LSCP Command(), createServant, destroy. These are the measurement points or
transactional states of the system at the time of the failure. See Table 5-7 on
page 5-22 for more information.
mErrorCode Error code provides a description of the event that caused the error. See Table 5-7
on page 5-22 for more information.
mOperand Operand that was being operated on at the time of the failure, for example, the
StreamID is the operand if a stream was being created or controlled at the time of
failure.
mTask Failed task is the event category indicating the type of execution sequence that the
call stack was currently within at the time of the failure. See Table 5-7 on page 5-22
for more information.
1. Unix epoch time is 1970-01-01T00:00:00Z
Table 6-11 Stream Failure Report Archive Fields (continued)
Field Description
Table 6-12 Stream Activity Report Fields
Field Description
mSessionId Session ID of the stream.
mActionTime Timestamp when the stream activity occurred. The timestamp is represented in
seconds since the start of Unix epoch time.
1
1. Unix epoch time is 1970-01-01T00:00:00Z
mServerId Server ID of the Streamer that is providing the stream.
mOpState Operational state is not used and is always zero (0).
mStreamState Stream state is not used and is always zero (0).
mSpeed Speed direction is as follows:
• 1 means play
• 0 means not paused/stopped
• n means n times fast-forward
• –n means n times rewind
mNptOffset Current point in time (milliseconds) where the stream is on the set-top box,
based on from NPT and to NPT.
mDestroyedReason This field is only populated if the stream is destroyed by the CDS orphan
stream handler. The CDS orphan stream handler only destroys a stream for one
of the following two reasons:
• Orphan session is detected
• LSCP timeout maximum has been reached