Observer Admin Guide

5/24/2018 Observer Admin Guide

1/104

Observer

Admin Guide

Software Release 6.0

Copyright 2011 by Volicon, Inc.

Do not copy

All Rights Reserved

Volicon, Inc.

111 South Bedford Street

Suite 201

Burlington , Massachusetts 01803

www.volicon.com

email:[email protected]

Tel: 781-221-7400

Fax: 781-221-7407
http://www.volicon.com/http://www.volicon.com/mailto:[email protected]:[email protected]:[email protected]:[email protected]://www.volicon.com/


2/104

Observer Admin Guide 6.0 Do Not Copy 02/03/122

Introduction _____________________________________________________________________ 71.

Purpose and Scope ___________________________________________________________________ 71.1.

About the Observer __________________________________________________________________ 71.2.

Conventions used in the Manual ________________________________________________________ 71.3.

Mounting, Power, Basic Connections ____________________________________________________ 81.4.

Power ON, Shutdown _________________________________________________________________ 81.5.

Network Configuration ____________________________________________________________ 92.

Maintenance ___________________________________________________________________ 103.

User Management __________________________________________________________________ 103.1.

Group Management _________________________________________________________________ 103.2.Edit Group _______________________________________________________________________________ 113.2.1.

Edit User __________________________________________________________________________ 123.3.

Maintenance Settings ________________________________________________________________ 123.4. Observer Versions _________________________________________________________________________ 123.4.1.Session Timeout ___________________________________________________________________________ 123.4.2.System date format ________________________________________________________________________ 133.4.3.Global Keyword Alert Limits _________________________________________________________________ 133.4.4.

Default Login Settings _______________________________________________________________ 133.5.

Miscellaneous Settings _______________________________________________________________ 133.6.Hot Folders _______________________________________________________________________________ 133.6.1.Server Host (if NAT is used) __________________________________________________________________ 133.6.2.Web Server IP _____________________________________________________________________________ 133.6.3.Producer Settings __________________________________________________________________________ 143.6.4.CMM Settings _____________________________________________________________________________ 143.6.5. Expired Data Cleanup_______________________________________________________________________ 143.6.6.

Event Viewer _______________________________________________________________________ 153.7.

Stream Control _________________________________________________________________ 164.

Central Configuration ________________________________________________________________ 164.1.

Probe Groups ______________________________________________________________________ 164.2.

Probe Servers ______________________________________________________________________ 174.3.Add/Edit Probe ____________________________________________________________________________ 174.3.1.

Encoders __________________________________________________________________________ 184.4.Test Stream ______________________________________________________________________________ 194.4.1.

Transport Stream Media-Hub Interface ______________________________________________ 195.

Software Updates _______________________________________________________________ 206.

Central Server Installer Staging ________________________________________________________ 206.1.

Probe Release Selection and Automated Install ___________________________________________ 216.2.


3/104


Programs ______________________________________________________________________ 227.

As-Run Files ________________________________________________________________________ 237.2. Import Data ______________________________________________________________________________ 237.2.1. Import Profiles ____________________________________________________________________________ 257.2.2.

Hot Folders _______________________________________________________________________________ 267.2.3.Task Scheduling Example ____________________________________________________________________ 267.2.4.

Ratings ___________________________________________________________________________ 277.3.

Loudness Monitoring ____________________________________________________________ 298.Enable Audio Loudness Metering _____________________________________________________________ 298.1.1. Short Integrated Results ____________________________________________________________________ 308.1.2.

Observer Alerting _______________________________________________________________ 329.

Definition of Key Terms ______________________________________________________________ 329.1.

Encoder Stream Alerting _____________________________________________________________ 329.2.

Media Faults ______________________________________________________________________________ 329.2.1.Alert and Trap Generation ___________________________________________________________________ 329.2.2.Media Faults with Examples _________________________________________________________________ 339.2.3.

Capture Cards and Breakout Cables ________________________________________________ 3410.

Osprey450e card option _____________________________________________________________ 3410.1.Audio breakout 9 pin Mini-Din Pin-out ________________________________________________________ 3510.1.1.

Composite Video Interconnect diagram ________________________________________________ 3510.2.

HD/SD-SDI System Interconnect ___________________________________________________ 3611.

HD/SD-SDI Interface diagram ________________________________________________________ 3611.1.

Observer Enterprise Chassis Back-panel photo ___________________________________________ 3611.2.

Blackmagic Decklink SDI _____________________________________________________________ 3711.3.Decklink SDI Coax Connector Diagram ________________________________________________________ 3711.3.1.Dolby Digital 5.1 Support ___________________________________________________________________ 3711.3.2.Decklink SDI Channel features _______________________________________________________________ 3711.3.3.

Blackmagic Decklink Quad HD/SD-SDI _________________________________________________ 3811.4.Decklink Quad HD/SD-SDI Connector Diagram __________________________________________________ 3811.4.1.Breakout Cable BNC to Mini BNC Adapter _____________________________________________________ 3811.4.2.

BLACKMAGIC INTENSITY PRO ________________________________________________________ 3911.5.

Intensity Pro Configuration __________________________________________________________ 4011.6.

Alerts and Video Clip generation ______________________________________________________ 4111.7. Email Notification_________________________________________________________________________ 4111.7.1.Clip Video is NAT Configuration Dependent ____________________________________________________ 4111.7.2.Alert Delivery Test ________________________________________________________________________ 4111.7.3.

Stream Level Configuration ______________________________________________________ 4212.

Probe Manager ____________________________________________________________________ 4212.1.

Stream Detect Thresholds ___________________________________________________________ 4312.2.


4/104


Video Lost _______________________________________________________________________________ 4312.2.1.Black Screen _____________________________________________________________________________ 4412.2.2.Static Screen _____________________________________________________________________________ 4412.2.3.Low Audio and High Audio _________________________________________________________________ 4512.2.4.

Create Encoder ____________________________________________________________________ 4612.3.Encoder Rename Procedure __________________________________________________________ 4612.4.

Add/Edit Probe ___________________________________________________________________________ 4712.4.1.

Audio Profile Setup ________________________________________________________________ 4812.6.

Audio Profile Setup in Control Center __________________________________________________ 5012.7.

Audio Profile Configuration Rules _____________________________________________________ 5112.8.Dolby 5.1 Surround Sound __________________________________________________________________ 5112.8.1.

Example: Two Stereo Tracks in two languages ___________________________________________ 5212.9.Dolby 5.1 Surround Example ________________________________________________________________ 5212.9.1.Edit Encoder, Select Audio Profile ____________________________________________________________ 53 12.9.2.

IP Power Switch Setup _____________________________________________________________ 5412.10.

SNMP Notification ______________________________________________________________ 5513.

SNMP Trap Message Decoding _______________________________________________________ 5513.1.MIB Variables ____________________________________________________________________________ 5513.1.1.SNMP Destination Setup ___________________________________________________________________ 5513.1.2.SNMP Notification Variables - Audio Alert Example ______________________________________________ 5513.1.3.MIB Variables Table _______________________________________________________________________ 5613.1.4.SNMP Trap Variables Table _________________________________________________________________ 5713.1.5. SNMP Notification Signaling Table ___________________________________________________________ 5813.1.6.

What NOT to do on the server side ________________________________________________ 5914.

hMailServer Configuration on Web Server __________________________________________ 5915. SMTP configuration _______________________________________________________________________ 6015.1.1.

hMailServer configuration through Companys SMTP server _______________________________ 6015.2.

hMailServer Email Routing Log _______________________________________________________ 6215.3.

RAID Alert Notification __________________________________________________________ 6316.3Ware Configuration on Observer Servers _____________________________________________________ 6316.1.1.

Raid Maintenance _________________________________________________________________ 6416.2.

Antivirus Excluded Storage Areas / Services to Scan ___________________________________ 6517.

Active Directory (AD) Integration __________________________________________________ 6518.Prerequisites ____________________________________________________________________________ 6518.1.1.Turning on AD authentication: ______________________________________________________________ 6618.1.2.AD Operation ____________________________________________________________________________ 6618.1.3.Troubleshooting __________________________________________________________________________ 6618.1.4.

Closed Captions and Subtitles _____________________________________________________ 6719.

Closed Captions Metadata profile _____________________________________________________ 6719.1.


5/104


Database Automatic Cleanup _____________________________________________________ 6820.

Restoring the Task Credentials _______________________________________________________ 6820.1.

Typical Rack Layout and Interconnect with STBs ______________________________________ 6921.

General Interconnect Description _____________________________________________________ 6921.1.Media SD Video/ Audio and HDMI Interconnections _____________________________________________ 6921.1.1. IR Transmitter Interconnections _____________________________________________________________ 7021.1.2.

Optional Interfaces, Equipment ___________________________________________________ 7122.

GPI Interface ______________________________________________________________________ 7122.1.GPI Input Triggered Video Clip Generation _____________________________________________________ 7122.1.1.GPI Output ______________________________________________________________________________ 7222.1.2.

GPI Optional Equipment_____________________________________________________________ 7322.2.

IP Power 9258 _____________________________________________________________________ 7422.4.Power Control URLReboot STB ____________________________________________________________ 7422.4.1.

Time Base Corrector AVI 8710 ________________________________________________________ 7622.5.

Troubleshooting and Maintenance ________________________________________________ 7723. No Video Playing _________________________________________________________________________ 7723.1.1.Internet Explorer Issues due to Skype Add-ons _________________________________________________ 7723.1.2.Exporting Video Clips ______________________________________________________________________ 7723.1.3.Client machine not working properly _________________________________________________________ 7723.1.4.How to Remove Volicon Media Player from PC client ____________________________________________ 7723.1.5.License Problem Sources ___________________________________________________________________ 7823.1.6.Hard Disk Drive (HDD) Replacement __________________________________________________________ 7823.1.7.Hard Drive Outage ________________________________________________________________________ 7823.1.8.DVD Burner needs IMAPI2 service ___________________________________________________________ 7823.1.9.

Support Portal __________________________________________________________________________ 7823.1.10.

Appendix _____________________________________________________________________ 7924.

Examining Video Input with ViewCast__________________________________________________ 7924.1.Adjust Audio with Osprey Config ____________________________________________________________ 8024.1.1.

Control Center/Probe Manager ___________________________________________________ 8125.Remote Desktop Configuration ______________________________________________________________ 8125.1.1.Back-End Access __________________________________________________________________________ 8225.1.2.

Control Center General Properties _________________________________________________ 8326.

Menu-bar ________________________________________________________________________ 8326.1.

Server Menu _____________________________________________________________________________ 8426.1.1. Encoder Menu ___________________________________________________________________________ 8426.1.2.View Menu ______________________________________________________________________________ 8526.1.3. Logs Menu ______________________________________________________________________________ 8526.1.4.Tools Menu _____________________________________________________________________________ 8626.1.5. Help Menu ______________________________________________________________________________ 9026.1.6.

AFD - Active Format Description ______________________________________________________ 9126.2.

Control Center Localhost Properties ___________________________________________________ 9226.3.


6/104


General Settings tab ________________________________________________________________ 9226.4. Server properties _________________________________________________________________________ 9226.4.1.Streamer Properties _______________________________________________________________________ 9226.4.2.Time Server _____________________________________________________________________________ 9326.4.3.License ServerRegistration _______________________________________________________________ 9326.4.4.Observer MIB File Location _________________________________________________________________ 9426.4.5.

Services Tab ______________________________________________________________________ 9426.5. Services Status ___________________________________________________________________________ 9426.5.1.

Listener Tab ______________________________________________________________________ 9526.6. Configure Notification _____________________________________________________________________ 9526.6.1.

Control Center Encoder Properties _________________________________________________ 9627.

General Settings Tab _______________________________________________________________ 9627.1.Properties _______________________________________________________________________________ 9627.1.1. Input Settings ____________________________________________________________________________ 9627.1.2.Video QualityStandard ___________________________________________________________________ 9727.1.3.SD-SDI and HD-SDI Video Quality ____________________________________________________________ 9927.1.4.Closed Caption __________________________________________________________________________ 10027.1.5. Storage ________________________________________________________________________________ 10127.1.6. Alerting Tab ____________________________________________________________________________ 10227.1.7.Stream Alerts Control Table _______________________________________________________________ 10327.1.8.

Revision Change History ____________________________________________________________ 10427.2.


7/104


INTRODUCTION1.

PURPOSE ANDSCOPE1.1.

This manual is for system and network administrators responsible for setting up inputs from the video

networks, encoders, IP network, alerting threshold, users and other system related parameters in the

Observer. It is also useful for advanced users to gain further understanding of the system.

ABOUT THE OBSERVER1.2.

The Observer is a powerful tool for automated media monitoring, logging and quality assurance with

applications for broadcast and related networks:

Automated monitoring and diagnosis of multichannel broadcasts

Standards based loudness monitoring

Media logging and related features

Typically composed of a Central Server (CS) and a group of probe servers often spread out between

network management, operations centers and unmanned remote distribution points.

The system is preconfigured with default settings hence small installations can work right out of the box.

For larger installations, the probe servers and their streams need to be defined in the CS.

CONVENTIONS USED IN THE MANUAL1.3.

Type Classification

Boldface Denote names and labels in the Graphical User Interface (GUI)

Capitalization Denotes key words module names, components and signal labels

Denote push buttons and other similar user input devices

@Hyperlink Automatic links to other sections in the document, denoted by

boldface and the @prefix


8/104


MOUNTING,POWER,BASIC CONNECTIONS1.4.

Place the chassis in a standard 19-inch rack. Follow your rack manufacturers mounting instructions for

safe and stable mounting. If your power supply has a 110/220 switch, make sure to set it to the proper

voltage (120/220VAC, 50/60 Hz). Observer server power consumption specifications should be checked for

the particular systems used.

Attach dedicated keyboard, video, mouse, or a KVM and a network cable to the rear of the machine. See

the Observer Site Prep Guide for more details.

POWER ON,SHUTDOWN1.5.

After powering up the Observer server wait for the login screen to appear. When logging into the system

for the first time consult the Read Me First guide or contact the Volicon support team.After power-up, the Observers facilities run as services (configured by default) without necessitating input

from the system administrator.

To shutdown, use StartShutdown menu sequence. To restart use the StartRestart menu sequence.

Do not unplug the power cord so as not to impact the database. (Its re-indexing might require help from

Volicon support group). If for some reason the main Windows server console screen is not accessible, use

the front panel button to perform the shutdown or restart.

We recommend connecting the Observers systems to UPS or a similar high availability power supply.


9/104


NETWORK CONFIGURATION2.

In order to simplify network configuration, a static IP address is recommended for each Observer server:

If public IP access is used, provide a firewall

Provide sufficient bandwidth between server and the monitoring facilityminimum 10 Mbps network

connection bandwidth: 1.2-1.5 times the sum of viewed stream's bandwidth.

Additionally, insure that the following TCP ports are open through the firewall:

Observer Encoder servers:

Ports TCP 4504/5502 for content streaming (to client PCs)

Ports TCP 3306 for database updates

Port TCP 3389 or a VPN connection for support

Central/Web server:

Ports TCP 80 for the HTTP (Web Front-End and client PCs)

Port TCP 25 SMTP for Hmailserver email alerts

Port 943 and 4504 for Silverlight

See the Observer Site Prep Guide for details.


10/104


MAINTENANCE3.

USER MANAGEMENT3.1.

Access User Management through the Web client interface (see Observer User Manual for the login).

Select Maintenance User managementfrom the left menu. This is a flexible tool for controlling user and

group access to the Observer system. You can create multiple user groups while assigning different privileges

to each.

Figure: User Management

Administratorshave full privileges. It is recommended to create additional groups with selected privileges for

the regular users. button is located above, ,and buttons are located next to group names as shown in the figure above.

GROUP MANAGEMENT3.2.

Clicking the down/up arrows to the

left of group name reveals the users

in that group. Clicking the arrowsagain returns you to the previous

screen.

F

Figure: Group Management

Here new users can be added or the existing users edited or deleted. See , ,

in the figure above. button permanently deletes a user.


11/104


Edit Group3.2.1.

If a new group is added or an existing one edited, very

similar forms are used to edit the parameters. Edit the

Group Name and select the Permissions you wish togive to the members of the group. Press the

button to save the modifications.

View users Ability to View users but not modify their configuration

Manage users Add / edit user/ group names and their access. Require View users to be selected

Create/View/Delete/Edit clips Manipulate clips

Export clips From Observer to a Client PC

View Fault Clips Ability to View Fault Clips

Add/Delete/Edit programs Ability to Add/Delete/Edit programs

Manage channels Configure encoder-channels

Create CC Alerts Ability to create Closed Caption alert

Import data Ability to Import data such as stamps

View ratings Ability to View ratings (assuming the feature/option is available on the system)

Unlimited playback session Playback without timing out

View CMM Ability to view CMM (assuming the option is available)

Manage CMM Ability to manage CMM (assuming the option is available)

View Producer Ability to view Producer (assuming the option is available)

Manage Producer Playback without timing out (assuming the option is available)

Scheduled Recording Ability to manage Scheduled Recordings (assuming the option is available)


12/104


Figure: Add/Edit User

EDIT USER3.3.

If a new user is added to a group or an existing one is edited, very

similar forms are used to edit the parameters. Add/edit the User

name, Passwordand select the streams of interest in the Access

to video section. Press the button to save the

modifications.

MAINTENANCESETTINGS3.4.

Observer Versions3.4.1.

Software versions can be seen at the upper left: Minimum Player Version

Installed Player

Front-end Version

Product Version

Depending on the configuration,

the following module versions

can also be listed:

Producer Version

CMM

CMM Client

Minimum Player Version-

required for the front-end, web

client PCs

Product Version- the back-end

portion of the Observer software

Session Timeout3.4.2.

Inactivity at the web client logs off the user automatically after Session timeout is exceeded. To disable

timeout, set it to zero.


13/104


System date format3.4.3.

It is a drop down list to select the system date format from (see above).

Global Keyword Alert Limits3.4.4.

The Global Keyword Alert Limits option has:

Force use of rate limitingenabling (checkbox) to limit the frequency of alerts

Minimum time between alertslimits alert frequency to selected period (minutes/hours/days)

DEFAULT LOGINSETTINGS3.5.

Setting default values enables convenient login into the Observer without the need to enter username /

password. Not recommended for most networks due to security considerations

MISCELLANEOUSSETTINGS3.6.

Hot Folders3.6.1.

Observer imports the as-run files periodically from a Hot Folderlocation configured in:

Maintenance SettingsHot Folder

Clicking the button next to the Hot Folder location creates a C:\HotFolder directory on the server

with subfolders using the names of each encoder channel. The software automatically imports the As-run logs

from these folders Import Profiles @Hot Folders

Hot Folders in the As-Run filessection.

Server Host (if NAT is used)3.6.2.

Email Alert has an embedded link with the Clip location string referencing the Observer server address andclip location on the server reachable from the Internet/LAN. The Server Hostname (if NAT is used)must be

valid and reachable from the outside world. In addition to explicit IP Address it can be a Hostname or a valid

DNS name (text string form)

Web Server IP3.6.3.

External Web server address which is accessed from the outside/Internet, it is a required parameter.


14/104


Producer Settings3.6.4.

The Producer sold as a separate module - used for repurposing media content enables leveraging

broadcast assets in the new media world where one program can be delivered to multiple portals:

broadcast, web clips, over-the-top TV and mobile video

CMM Settings3.6.5.

If the Content Matching (CMM) and

Producer optional modules were

purchased with the Observer software,

these can be configured in:

Maintenance Settings

Content Matching Module (CMM) is for

organizations that need to be notifiedwhen certain audiovisual assets are

broadcast. Fully integrated with the

Observer, the CMM is easy to set up and

can operate stand-alone or integrated

into other systems.

Hovering over the ? icons provides tool tips to help configure the various fields/text boxes. See the

Content Matching and Producer manuals for more details.

Expired Data Cleanup3.6.6.

Maintenance Settings Expired Data Cleanup

The selected items:

Events

Remove license expiration message

Channels

o Closed Captions

o Ratings

o Programs

o Clips (Including GPI)

The button clears the expired data right after it is pressed.

CC RETENTION Duration for storing the Closed Captions and Teletext on the system


15/104


EVENT VIEWER3.7.

Maintenance Event Viewerfrom the Left menu allows administrators to view a running log of events and

currently-logged-in users on the Observer system.

The upper table displays a list of the currently-logged-in users and the session expiration times. The X iconis

used to forcefully terminate a session, although this could cause loss of unsaved items.

The lower table shows a log of actions taken by the users in reverse-chronological order.


16/104


STREAM CONTROL4.

CENTRAL CONFIGURATION4.1.

Probes groups are defined in a hierarchy

A Probe group contains multiple probes that usually have some commonality, i.e., geographical

location

A Probe contains one or more Encoder/streams or channels

PROBE GROUPS4.2.

Probe groups, probes and encoders are managed through:

Central Config

Encoders

Probe Groups Listis accessed:

Figure: Probe Groups List

Clicking one of the group lines opens the group. The Xicon deletes the selected group.

button-creates a new group - provide the groups name.

The Editicon allows one to edit an existing group name.

A Probe group is accessed in Probe Group List clicking the group name directly (i.e., the COLO HD blue

rectangle in Figure: Probe Groups List above), displays the Probe listshown in figure below:


17/104


PROBESERVERS4.3.

Figure: Probes List

A Probe/Encoder server is accessed by clicking the probe name

directly, (i.e., the Probe65 in Figure: Probe List above) will

display the Encoder Probeform.

Add/Edit Probe4.3.1.

With the button, a new group is added or with the

Edit icon, an existing group is edited. To complete, press the

Updatekey.

After adding a probe, define its properties as follows:

Group Name From preconfigured groups

Probe Name Name or rename a probe. It should match the name in the probe server registry under

VoliconEMSPROBE_NAME

SW Version Displays probes current software version. Also a dropdown select higher SW

Version,(with brief pause in media recording marked with asterisk in front of the

version number, i.e., *6.0.25787). Then probe comes online automatically.

LAN IP Address within the LAN to reach the probe

LAN IP Port TCP port of the streaming server, configured by default to 4504

WAN IP and Port IP address of the CS/web server when NAT is used; this will populate the IP address in

the alerting email in the clip link, so that you can click on the link and pull up the clip

from the email

SNMP Svc Map Map for the SNMP triggered recording


18/104


ENCODERS4.4.

Figure: Encoders List and Edit Encoder form

Pressing the button or theEditicon brings up the Add/Edit Encoderpopup window. Then fillin/modify the following parameters:

Encoder Name of one of the encoders (usually out of four) Setup in the Control Center

Display Name Front-end, friendly name for this encoder-channel. See Encoder input list section

Color Helps users to distinguish between the encoder-channels, a user settable property

CC adjustment Time adjustment for CC, usually leave the default value

Amplification Adjustment of audio input amplification

Data Expires Enable data expiration checkbox

Expires After Define period for keeping video and CC data

CMM Monitoring CMM Monitoring language

Test Press button to insure the front-end connects to the back-end encoder and

the new settings are working properly before applying Add/Update modifications

Preview opens a display showing video streaming from encoder channel input

Add/Update Press / button to complete this modification


19/104


Test Stream4.4.1.

In Figure: Stream Settings above, click the button. The system will attempt to connect to theEncoder-Stream just configured and verify that it is working.

TRANSPORT STREAM MEDIA-HUB INTERFACE5.

Create encoders for the Transport Stream interface on the Media-Hub server and then connect the new

encoders to the Central Server:

1. Create Media-Hub encoders directly on the Media-Hub server (Probe manager utility) - see Create

Encoders, in Media-Hub Admin Guide

2. Then connect the new TS encoders to the Central Server by configuring the Probe Groups, Probes

and Encoders in the Stream Control section of this guide


20/104


SOFTWARE UPDATES6.

CENTRALSERVER INSTALLERSTAGING6.1.

Managed in conjunction with Volicon Support

Volicon Support will email SW release installer/s - ProbeSetup ####.msi

Customer Systems Admin will place one or more installers on the Central server using menu

o Central ConfigSW Updatesand the

o and the Installer buttons

The button is at first grayed out until the selected installer is verifies by the system. Then the

pressing button, the Central server will make the release available in its Probes.


21/104


PROBE RELEASESELECTION ANDAUTOMATED INSTALL6.2.

Newest releases are available for selection and install accessible from the Probes List page

Central Config > Encoders provides you with Probe Group Listthen

Click Group Name to access the Probes Listpage

Press the Edit icon on the probe (of interest) to open an Edit Probe popup window

The SW Version (dropdown box) displays the currently installed version. Selectthe desired SW Version

(located on Central server)

Click the button for automatic new version install on the selected probe


22/104


PROGRAMS7.

Selected from Left-menu, Programs allow you to organize video recording based on program name, channelname and time. Usually, the Observer user sets up programs for the Observer. Optionally, Electronic Program

Guide, (EPG) integration can be used to skip manual data entry.

Users can search for video footage of interest based on program search parameters. Selecting Programs from

the left menu, user will be provided with the screen above.

Defined period instead of anytimeenables you to search between the Fromand Totimes. In addition

to the ProgramName, you can filter for an A/V stream with the Channel drop down box option, or leave it

open with the Any Channel option, see above.

ADD/EDIT PROGRAM To add a program click the button, to edit click the Edit, (pencil)icon. After modifying, press the button.

DELETE PROGRAM To delete a program press the xicon to the right of a program


23/104


AS-RUN FILES7.2.

Searchable program guides allow you to organize and find video based on program name, channel and time.

Usually, the Observer administrator sets up the program information for the Observer in the form of as-run

files. As-run files contain the program scheduling information, which is converted to video clips stored in the

Observer system.

Import Data7.2.1.

Note: Observer supports the Daily - Ratings report. Prior to importing this data into Observer you need to

convert a provided file to a Text (Tab-delimited) format.

Note:Import ability may be restricted by the administrator and thus may not be available

After file conversion to supported format click MaintenanceImport Datain Web client

Click on button to open the converted *.txt file for importing and then click the button

On the next window from the list of provided channels select your corresponding channel(s), Source Time

Zoneif needed, and then click the button.


24/104


After successful import you can start importing another file or go to Main page in Programs toview the video.

For making Rating graph to be displayed, in Ratings choose the same Date and Time range as the imported

file, then click button to display the graph, see Ratings section below.


25/104


Import Profiles7.2.2.

Open Maintenance ImportProfiles in the Web client and set the time zone and Delay Offset of EncoderChannels to compensate for video delay between the desired time and the when the actual Observer video

was loaded to storage. This compensation results in accurate timing of Programs related to As-Run files.

Then save the profile. A green check mark should appear next to the profile name in the list.


26/104


Hot Folders7.2.3.

Observer imports the as-run files periodically from a Hot Folderlocation configured in:

Maintenance SettingsHot Folder

Clicking the button next to the Hot Folder location creates a C:\HotFolder directory on the server

with subfolders using the names of each encoder channel. The software automatically imports the As-run log

from these folders on a scheduled basis which is controlled by a task setup in windows scheduled tasks, see

Task Scheduling below. It is the responsibility of the customer administrator to deliver updated as-run files tothis location.

Task Scheduling Example7.2.4.

Consider the following only as an example

as the particular details will change with

different versions of the OS and Observer

release version:

To periodically convert As-run filesschedules to Observer Media Programs,

right click the Observer HotFolder file in

the C:\Window\Tasks directory and

select Properties and then the

Schedule tab.

To run the conversion immediately, right

click on the Observer HotFolder select

Run menu option. Be sure to set the

password correctly and activate the task in

the Security tab.


27/104


RATINGS7.3.

Note:Rating is an optional module and also may not be available to all users (restricted by administrator)

While viewing video programs, the ratings module facilitates efficient comparison of broadcasts at specific

times and for selected channels. This feature works both in real-time and during playback Click the

icon onthe player control-bar see below (and the Observer User Manual).

The Demographic Type for ratings can be selected from a corresponding drop down

window. These profile the human population characteristics for the selected geographical

areas where the ratings are sampled:

HOUSEHOLDS Profile the average Households

P12-17, P18-24 Populations between ages of 12 and 17 and 18 and 24

F18-24 Female population between ages of 18 and 24

M50+ Male population over the age of 50

The following Chart Typescan be selected: Rating

Gain Loss

Cumulative

For instruction on how to import Daily Ratings data, see Import Data section above.

Matching colors markings are used to link between rating graphs to the corresponding

video displays.


28/104


On the top right of the graph time scale, the timescale granularity can be selected. The graph color to channel

key is located to the right of the graph as shown below:

The vertical line can be used as a correspondence pointer between a select specific time on the ratings curves

and programs shown on the displays. Moving the line will display the correct video for the times trans-versed.


29/104


LOUDNESS MONITORING8.

With the loudness module, the Observer, Observer TS and Observer RPM can

Perform loudness and loudness range measurements (LRA)

With gating and without gating (-10 dB but adjustable) over

o Momentary( 400ms)

o Short term (3s)

o Short Form integrated (7 adjustable windows updated each second - e.g. 10s, 15s, 20s, 30s, 60s)

o Long Form Integrated (7 adjustable windows updated hourly - e.g. 1 hour, 6 hour, 1 day, 5 day)

intervals

Loudness meter averaging to meet the following standards EBU R 128, BS-1770-2, ATSC A/85 and EBU

Tech 3341/2/3

Figure: Enabling Loudness Metering

Enable Audio Loudness Metering8.1.1.

Open the Probe Manager then click on the right side of the enabling line to select Truefor loudness

metering.


30/104


Short Integrated Results8.1.2.

To edit any of the short term integrated measurements click the Short Integrated Results 1 line below and

then the ellipsis on the right of the line to bring up the Collection Editor. The default setting are shown below:

Figure: Loudness Metering Integration

After the Collection Editor opens select a Memberon the left to add/edit its value on the right and thus

determine its integrated period. When done with the Collection Editor press the button.

After completing any of the above changes save the results with the button in Figure:

Loudness Metering Integration.


31/104


For items in the table below see Figure: Loudness Metering Integration above.

Enable Audio Loudness

Measuring

See items in Figure: Loudness Metering Integration above

EBU Mode EBU mode to comply with the EBU R 128 standard

Enable LRA LRA denotes Loudness Range to quantify the variation in a time-varying

loudness measurement

Short Integrated Results See theShort Integrated Resultssection above

0 - 15 Set theShort Integrated Result 0to 15sec

1 - 30 Set theShort Integrated Result 0to 30sec

Long Integrated Results Has a similar structure to theShort Integrated Resultssection above howeverthe unit of measurements is in minutes

0 - 1440 Set theLong Integrated Result 0to 1440minutes, which is 1 day

1 - 7200 Set theLong Integrated Result 1to 7200minutes, which is 5 days

Input Adjustment Adjustment added to the input level for fine tuning, a floating point type value

Measurement persistence

folder

Folder for loudness measurement results


32/104


OBSERVERALERTING9.

DEFINITION OF KEY TERMS9.1.

Term Definition

Encoder/stream Observer hardware module that receives and processes Media

signals from one to four set-top boxes. Depending on the

context, the encoder is sometimes referred to as an

Encoder/stream

Media Fault When the incoming media: video, audio and Closed Captioning

crosses Observer defined level and duration threshold limits

for normal operating conditions

Channel/Service Networks media service content as perceived by the end user.

Typically a cable or broadcast channel or a specialty service

Alert A notification of a media fault generated when an encoder

detects a fault. In addition to storing a video clip, if enabled the

system issues email notification and a SNMP trap of the event

Trap A message sent to an external system after detecting an alert

and enabled with the channel notification control, usually

referring to a SNMP alert

ENCODERSTREAMALERTING9.2.

Media Faults9.2.1.

Media Faults such as Black Screen or Low audio detected in Encoder-Stream input usually exceed

certain level and duration thresholds. For more details see @Media Faults with Examples, 9.2.3.

Alert and Trap Generation9.2.2.

To configure the threshold in the Probe Manager see @Stream Level Configurationor in the Control Center

see @Alerting Tab.

After a media fault is detected, a fault clip will be cut. And if notification is also enabled, a SNMP trap and

alerting email will be sent.


33/104


Media Faults with Examples9.2.3.

Alert Types Fault/Alert Detection

AUDIOLOW Audio fault is detected when the incoming audio signal stays below the Low audio level threshold(default -40 dB; increase for noisy lines, e.g., -35 dB) for duration exceeding the Duration threshold of

10 sec Disable audio alert detection on some channels when long periods of silence frequently

appear such as on some Public Education Government (PEG), NASA channels...

AUDIOLOW Alert Example: Audio alert is configured on Stream A1

Durationthreshold = 30 sec; Low levelthreshold = -40 dB

Audio input signal detected = -69 dB (below Level threshold) for 35 sec and exceeding the Duration

threshold, therefore a Media fault is detected generating an audio alert and cutting a media clip. And if

notification is enabled, a SNMP trap and an email message describing the alert are sent.

AUDIOHIGH Audio fault is detected when the incoming audio signal level stays above the High level threshold (-1dB the default)for sufficient duration to exceed the audio Duration threshold of 10 sec

AUDIOHIGH Alert Example: Audio alert is configured on stream A1

Durationthreshold = 30 sec; High levelthreshold = 0 dB

Audio input signal detected = 2 dB (above Level threshold) for 35 sec and exceeding the Duration

threshold, then an alert is detected and the resulting fault clip is cut. When notification is enabled , a

SNMP trap and email message describing the alert are sent

AUDIO-OK Audio level returns to normal when the incoming signal returns between the audio Low level andHigh level thresholds. The recovery Duration configured for the Low and High Audio is system preset.

On the stream A1: Level persisting between Low -40 dB and High -1 dB thresholds for duration

greater than 10 sec. Then AUDIOHIGH alarm is cleared, AUDIO-OK fault clip track is added to the

AUDIOHIGH Fault clip. When notification is enabled, AUDIO-OK Email and SNMP trap are sent.

VIDEOLOST When video frame loss is detected and persists over the Video Duration threshold, the VIDEOLOSTAlert is generated. Only the Duration threshold is configurable.

VIDEOBLACK The percentage of pixels lacking all luminosity exceeds the Black Screen Certainty threshold (Default95%). As there is usually some noise, common ranges are 95% - 97%; 97% if the STBs output is very

stable. Duration threshold default is 10 sec.

VIDEOBLACK Alert Example Stream A1 variables are set as follows:

Duration threshold = 30 sec; Black screen Certainty threshold = 95%

Stream A1 video exceeds 96% Certainty threshold and persist for 6 min, an Alert is declared and Fault

Clip is cut. When Notification is enabled, SNMP Trap and email messages are sent.

VIDEOSTATIC The percentage of pixels with the same luminosity, color and frame location compared between apair of consecutive video frames exceeds the Static screen: Certainty threshold default is 95%,

Duration default 10 sec. Disable Video Static detection on music channels and some PEG channels.

VIDEOSTATIC Media fault Example Stream A1 variables are set as follows: Duration threshold = 30

sec; Certainty threshold = 95%.

When the pixel color and luminance matching between consecutive video frames exceed 96% of all

the screen area pixels for longer than 35 sec, Static videofault alert is declared and a fault clip is cut.

VIDEO-OK When video returns to normal framing and pixel characteristic: Recovery for video alerts: BlackScreen, Static Screen and Video Loss

TTLLOST "Teletext" data is absent

CCLOST Closed Captions data is absent. Duration default is 600 sec

CC-OK "Teletext" or "Closed captions are OK

See also See @SNMP Notification.


34/104


CAPTURE CARDS AND BREAKOUT CABLES10.

OSPREY450E CARD OPTION10.1.

Osprey-440/450e support 4 external

video inputs; all can be configured as

analog composite. Attach up to four BNC

composite video cables to the input

video connectors.

The breakout connector provided with

the Osprey card has 4 left/right,

unbalanced audio inputs.

Observer encoder channels are configured as follow:

Video Input A and Audio Left 1 / Right 1

Video Input B and Audio Left 2 / Right 2

Video Input C and Audio Left 3 / Right 3

Video Input D and Audio Left 4 / Right 4

Input A

(Video source 1)Input B

(Video source 2)Input C

(Video source 3) Input D

(Video source 4)

4 outputs for unbalanced

audio, each consisting of left

and a right connector labeled

Left 1/Right 1

Left 2/Right 2

Left 3/Right 3

Left 4/Right 4

9-pin Mini-DIN

Inline plug

9 pin Mini-DIN

Socket for audio

breakout cable


35/104


Audio breakout 9 pin Mini-Din Pin-out10.1.1.

Pin assignment for the Osprey 440 audio break out and internal pin configuration:

1. Audio input Left 1

2. Audio input Right 1







9. Ground Ground

COMPOSITE VIDEO INTERCONNECT DIAGRAM10.2.

Composite Video

Source

Composite Video (Y)

Audio Right (R)

Observer Server

Osprey 440/ 450e

Composite

Video

Audio In


36/104


HD/SD-SDISYSTEM INTERCONNECT11.

HD/SD-SDIINTERFACE DIAGRAM11.1.

Both SD-SDI and HD-SDI interfaces use the following BNC cable interconnections

Figure: SD-SDI and HD-SDI Interconnect Diagram

OBSERVER ENTERPRISE CHASSIS BACK-PANEL PHOTO11.2.

MainNetwork

RJ-45

SDI InENC1BNC

SDI InENC2

IPMIRJ-45

TapeBackupRJ-45

USB

SD-SDI / HD-SDI

Source

HD/SD-SDI

Output

Observer Server

Blackmagic Decklink

SDI

HD/SD-SDI

Input


37/104


BLACKMAGIC DECKLINKSDI11.3.

Decklink SDI Coax Connector Diagram11.3.1.

Connect SDI Source (from deck) with coax M to the Blackmagic Decklink SDI cardsHD/SD-SDI Input.

Dolby Digital 5.1 Support11.3.2.

Dolby digital is supported in release 5.5 and above. Select the AC3 audio profile to setup Dolby digital on

the Blackmagic SD encoder card.

Decklink SDI Channel features11.3.3.

For SD-SDI and HD-SDI applications and configurable to NTSC and PAL, this card can be used both

standalone or in large facilities with SDI routers. The A10 bit SDI video card features a tri-sync reference

input, 8 channels of SDI embedded audio, 2 channels AES/EBU digital with sample rate converters and RS-

422 deck control. For generic shelf interconnect see section @Typical Rack Layout and Interconnect with

STBs .

SDI Source


38/104


BLACKMAGIC DECKLINK QUAD HD/SD-SDI11.4.

The card has Mini BNC SDI connectors, see the diagram below

for connection details.

Decklink Quad HD/SD-SDI Connector Diagram11.4.1.

Connections are made to the SDI

inputs as follows:

Breakout Cable BNC to Mini BNC Adapter11.4.2.


39/104


BLACKMAGICINTENSITYPRO11.5.

The Intensity Pro is a high definition HDMI capture card. It is shown with its breakout cable in the figurebelow.

The Intensity Pro video card connectors for the Breakout cables and the HDMI cables are shown in the

diagrams below:

Figure: Consumer Breakout Cable

The Decklink SDI card uses a different set of drivers than the Intensity Pro card.


40/104


INTENSITY PRO CONFIGURATION11.6.

Open the Intensity Pro Preference Settings

Start Settings Control Panel Blackmagic Control Panel

Configure the card as follows:

Set output: HDMI & Y, R-Y, B-Y

Set Input NTSC/PAL (Y In) & Analog RCA Audio

Select At 7.5 IRE for use in the USA

Select Remove Field jitter when video is paused

When not playing video send: Black


41/104


ALERTS AND VIDEO CLIP GENERATION11.7.

Email Notification11.7.1.

After detecting a problem - in the media stream the Observer system generates an alert message and a

corresponding clip to describe the fault. This information can be conveniently shared with other users and

business partners or saved to your workstation for later review.

The email notification list consists of the following options:

Email address of the recipient

Video alerts

Audio alerts

CC / Teletext alerts (Classic Observer)

To add a new recipient, select Maintenance Alertsmenu then click the button

Clip Video is NAT Configuration Dependent11.7.2.

When any of the Fault Clips are clicked but the video does not appear, ensure @Server Host (if NAT is

used,3.6.2is configured correctly.

Alert Delivery Test11.7.3.

Click the button to test alert delivery.


42/104


STREAM LEVEL CONFIGURATION12.

This section covers the configuration of Encoder/stream alerting properties through the back-end. Login

directly or through a remote desktop to the Observer console. See the Read Me First Guide shipped with

the system for login details contact the Volicon Support team.

PROBE MANAGER12.1.

At the desktop, access the encoder/stream properties through the Probe Manager (PM) icon:

To configure go to:

Encoder SettingstabOptionsAlerting DetailsDetector Details

Click on the Collectionellipsis as highlighted below:

Figure: Probe Manager Alerting Details


43/104


STREAM DETECT THRESHOLDS12.2.

After clicking the Collection ellipsis in Figure: Probe Manager Alerting Details, Detect Collection Editor

appears:

Video Lost12.2.1.

Figure: Detect Collection Editor, Type Video Lost

Video lost fault is detected when video framing loss (monitored every frame at 30 times per sec in the US) is

detected and persists over the Video Detection period threshold (3 sec default), a VIDEOLOST alert isgenerated. Then after the framing recovers and exceeds the Recovery duration, it will generate a VIDEO-

OK notification message. For Video Lost only the Duration threshold is configurable.

Type Certainty

threshold

Detect

duration

Recovery

duration

VideoLost NA 3 sec 1 sec

BlackScreen 95% 10 sec 10 sec

StaticScreen 95% 10 sec 10 sec

LowAudio -40 dB 10 sec 10 sec

HighAudio -1 dB 10 sec 10 sec

Generally the same Certainty threshold is applied both during the detection and the recovery phases.


44/104


Black Screen12.2.2.

Figure: Detect Editor, Black Screen

Black screen fault is detected when the percentage of displayed pixels (with low luminosity) exceeds the Black

Screen Certainty threshold and persists over the Black Screen Detect durationthreshold.

Static Screen12.2.3.

Figure: Detect Editor, Static Screen

Static screen fault is detected when the percentage of pixels with the same luminosity, color and frame coordinates

compared between pairs of consecutive video frames exceed the Static screen Certainty thresholdand persist over

the Static Screen Detect durationthreshold.

Type Certainty

threshold

Detect

duration

Recovery

duration

Black Screen 95% 10 sec 10 sec

Static Screen 95% 10 sec 10 sec

After the encoder video recovers over the Recoverythreshold duration, it is considered as recovered.


45/104


Low Audio and High Audio12.2.4.

Figure: Detect Editor, Type Low Audio

Figure: Detect Editor, Type High Audio

Audio Low fault is detected when the audio signal level stays below its certainty threshold and persists over the

Duration threshold. Audio High fault is detected when the audio signal level stays above its certainty threshold and

persists over the Duration threshold; audio level is measured in decibels.

Type Certainty

threshold

Detect

duration

Recovery

duration

Low Audio -40 dB 10 sec 10 sec

High Audio -1 dB 10 sec 10 sec

After audio recovers (audio level persists between the low and high thresholds) exceeding the Recovery

thresholdduration, it is considered as recovered.


46/104


CREATE ENCODER12.3.

While in Probe Manager, right click on Observer Encoder (see figure) and select Add Encoderfrom thepopup menu:

Figure: Add Encoder

ENCODER RENAME PROCEDURE12.4.

Expand Observer Encoder(see above) to display the list of encoders

Select the encoder that you want to rename (e.g., E1)

Double click the encoder name (highlighted) and enter the new name (see figure below)

o Press the enter button, once the new name is typed in

Press the Button at the bottom of the window

o You will notice that the name will change in the tree view to the left

Next from the Web client, go toCentral Config, see the Add/Edit Probesection


47/104


Select the Group and server to rename at the Encoder List, click on the Edit icon (pencil) of encoder

you wish to rename

Add/Edit Probe12.4.1.

When the Edit Encoderwindow opens, enter the new name in the Encoderfield (figure 1), then press

the button. Once you receive notification of a successful test (figure 2), press the button

(figure 3):

Figure: 1 Figure: 2 Figure: 3


48/104


AUDIO PROFILESETUP12.6.

Select Audio streams Devicethen select the ellipsis on the right to open the Audio Source Collection

Editor

Figure: Audio Settings


49/104


Figure: Audio Profile setup

SelectProfilethen click on the ellipsis on the right to open a folder on the server with audio profiles. Select

the desired Audio profile from the folder.

Figure: Audio Profile folder


50/104


AUDIO PROFILESETUP IN CONTROL CENTER12.7.

Figure: Control Center Audio Profile setup

The Audio profile graphically depicts the interconnection of a grouping such as mono or stereo and a

language such as English or Spanish at the output node. Language can be selected by right clicking the web

client player. Inputs are mapped in pairs for stereo or in a group of six for surround sound.

Figure: Audio Profile, Stereo

For the analog input (Osprey 440/450e cards), each of the

4 audio input pairs can be mapped as either a stereo or

two mono profiles - various audio profiles are built-in the

Audio profile manager which is accessed from the Toolsmenu of the Control Center. First determine the

correspondence between language name and language

identifier in the incoming video stream.

In Figure: Audio Profile, Stereo, encoder channel with two

audio inputs are configured to one stereo node. Draw the

desired configuration by left clicking and dragging the line

between the nodes.


51/104


Figure: Audio Profile, Mono

The adjacent figure illustrates an example of two mono

audio inputs, each associated with its own language.

Select and edit a profile using File; Load Profile menu.

Multiple audio input channels can carry multiple

languages.

AUDIO PROFILE CONFIGURATION RULES12.8.

A. Audio channel inputs can be in groups of:

One for mono

Two for stereo

Six for surround 5.1

B. Audio profile names need to be distinct for each of the several

encoders in the system. If the profile interconnection and

language are the same, copy and rename a profile files for the

other encoders.

Dolby 5.1 Surround Sound12.8.1.

For the Black Magic Deckling SDI, up to 12 audio

input channels are available for up to two

surround sound language groups. Some common

configurations for SD-SDI cards are:

One Stereo

Two Stereo

Four Mono

HD-SDI cards are usually grouped as shown in the

adjacent figure: F igu re : S te reo and Sur ro und 5 .1

Four Stereo or

Two Surround Dolby 5.1

Input Language

nodes

Mono 4 4

Stereo 4 2

Stereo 8 4

Surround 12 2


52/104


EXAMPLE:TWOSTEREO TRACKS IN TWO LANGUAGES12.9.

As an example to display two stereo tracks in two languages, which will display 4 loudness meters

simultaneously, load the surround.audprof file (on the system by default) and restart the Encoder Service. In

general, audio tracks in groups of 1, 2, or 6 (tracks) should map well to output nodes.

Figure: Dolby 5.1 and Loudness Meter

Dolby 5.1 Surround Example12.9.1.

In order to display multiple audio inputs

simultaneously, these need to be

available on the encoder card and

configured in the Back-End (Profile

Manager/Control Center). The

analog encoder cards have two audio

inputs available per encoder while the

SDI/HD cards have up to twelve.

Figure: Dolby 5.1 and Loudness Meter

user selected (in the Front-End display)

from the popup menus first Audio Track

along with the six loudness meters shown at the bottom of the display.

Figure: Stereo selection

The stereo sound is selected from the

second track of popup menu in Figure:

Stereo selection along with the two

loudness meters.

Figure: Edit Encoder, Select Audio

Profile illustrates where to configure

the audio profile in the Control Center.

For the example shown, a customer can

switch between the loudness meters

between the six output surround, 5.1and the two outputs Stereo


53/104


Edit Encoder, Select Audio Profile12.9.2.

Click Encoder

EditName

Edit Audio Device: Select

Audio Settings Profile

Click ellipsis

Select and load the new

audio profile


54/104


IPPOWERSWITCHSETUP12.10.

The Observer/RPM system interfaces with the IP Power 9258 (optional) switch to control and cold reboot

STBs remotely through individual power outlets. This way any remote STB can be rebooted either manually

(through R/C) or automatically in response to detecting Encoder/stream issues (e.g., STB unresponsive;persistent banner failure and black screen).

Supported IP power devices types:

1. Aviosys IP Power Switch 9258 (4 port switch)

2. Aviosys IP Power Switch 9258-DS (8 port switch)

Each port connects to a separate Encoder/stream. The interface is configured as follows:

Parameters:

Type One of the available IP Power types (dropdown box)

IP Power 9258 (4 port switch) IP Power 9258-DS (8 port switch)

Server IP address of the IP Power switch

User name Used during login to the switch

Password login password

Port Controls an individual device/STB. First, port 60; second port 61


55/104


SNMPNOTIFICATION13.

Observer signals SNMP notification to external systems (e.g. NMS) using the Alert Notification variablesshow @SNMP Notification Signaling Table. In addition the NMS IP addresses need to be setup, see

@SNMP Destination Setup below.

SNMPTRAP MESSAGE DECODING13.1.

MIB Variables13.1.1.

SNMP V2 MIB variables and their definitions are listed in the EncoderTraps_v2.mibfile or a similar *.mib

file, located on the Observer server Program Files\Volicon\docs directory. Though also listed in the

@MIB Variables Table below, the MIB file should be the primary reference for the most recentinformation.

The Observer RPM SNMP V2 trap messages consist of media related alerts that create fault clips and also

system critical events that do not generate clips.

SNMP Destination Setup13.1.2.

Configuration takes place on the Central Server in local.php file

// "host" ""127.0.0.1" works by default, define("SNMP_RECEIVERS", serialize(array(

array("protocol" "v2",

"community" "public",

"host" "localhost",

"port" 162),

array("protocol" "v2",

"community" "public",

"host" "192.168.10.3",

"port" 162))));

Insure the network and the NMS systems are compatible with:

Port 162

Community string public

Otherwise reconfigure these values and also at the firewall as needed by the NMS.

SNMP Notification Variables - Audio Alert Example13.1.3.

Real-time traps were traced to build the MIB Variables Tablebelow; the Notification Variables in the

leftmost column. The last column illustrates examples to Setand Clear SNMP Alerts - @Alert

SET/(CLEAR) Example .


56/104


MIB Variables Table13.1.4.

Alert Variables

(in MIB) OID Stings Description

volEncoder PREFIX =1.3.6.1.4.1.2352.1 Probe Server Name OID type and prefix for OIDs below

volEncoderName

Octet StringPREFIX.2 Name of encoder which detected the alert. (Names) configured

during installation and usually not changed by the user

volEncoderHostname

Octet StringPREFIX.3 Probe server Hostname, IP or DNS name. The Hostnames should

be unique within servers on the NMS monitored network

volAlertClipID Integer PREFIX.11.1 Generated with each new event (e.g., media defect) to identify

volAlertDescription

Octet String PREFIX.11.2

Textual description of the alert

volAlertClipRef Octet String

PREFIX.11.3

Alert clip ID and URL for its location on the web server e.g.,

http://rpm.cableTv.com/clip_view.php?id=158079

volStreamName Octet String PREFIX.11.4 Stream/scanner name to help identifying the link/STB location

volAlertEnum Integer

PREFIX.11.5

Grouping: event(0), test(10), service(20), encoder(30),

storage(40), license(50), audio(100), video(200), metadata(300)

power(400)

volAlertName Octet String PREFIX.11.6 E.g., AUDIOLOW, ENCODER STOPPED

volAlertTypeInteger PREFIX.11.7 Signals the NMS SET(0) or CLEAR(1) alert states, e.g. alert is SET

volCertainty Integer PREFIX.11.8 Degree of alert type percentage, e.g., 96 percent of Black Screen

volAudioLevel Integer PREFIX.11.9 Integer value of audio Level in dB

volAudioPin Integer32PREFIX.11.10

Audio Pin number, it is audio language pin. For now single

language is used, the Pin is always 0

volEventTime Octet String PREFIX.11.11 Time when the alert has occurred, e.g. 2010-10-31 20:57:21

rpmChannelID Octet String

PREFIX.11.12

Channel Number in the Lineup. It is stored in a string, such as

"124"

rpmChannelName OctetString PREFIX.11.13

Lineup Channel/Service name such as Fox

rpmChannelQAM Octet

String PREFIX.11.14

Channel group name for any group of channels logically related

volAlertSeverity Integer32PREFIX.11.15

Designates priority for a corresponding problem to get resolved

info(1), warning(2), minor(3), major(4), critical(5)

oidAlertLevelOctet String PREFIX.11.16Alert level (category) with one of the following possible values:

probe (1), group (2), system (3)

oidGroup (Octet String) PREFIX.11.17 Name of the affected probes group

oidProbe (Octet String) PREFIX.11.18 Name of affected probe machine

VolAlertName, VolAlertEnum, VolAlertType variables indicate when to set or clear NMS internal alarms.

System related traps (other than for media) though not used to set or clear alarms, provide important

information about the defect source such as volAudioLeveland volAlertSeverity.


57/104


SNMP Trap Variables Table13.1.5.

Notification

Variables OID Stings Description Alert SET/(CLEAR) Example

volEncoder PREFIX = 1.3.6.1.4.1.23522.1

Probe Server Name

OID prefix for OIDs below

trapEncAlerts

PREFIX.12 =

1.3.6.1.4.1.23522.1.12

ID identifying an Observer

trap. This variable binds all

other variables in it

volEncoderName

PREFIX.2 = 1.3.6.1.4.1.23522.1.2

Octet String (Size 0...32) Encoder Stream name Value: ENC1

volEncoderHostname

PREFIX.3

Octet String (Size 0...32)

Encoder hostname or IP

address Value: ObsRpmVa

volEncAlerts PREFIX.11 Object identifier

volAlertClipID PREFIX.11.1Integer32 Clip ID created on this alert Value: 6 (Value: 9)

volAlertDescription PREFIX.11.2 Octet String

Textual description of the

alert

Value: LOW AUDIO LEVEL /(AUDIO-

History Channel 66; Encoder: ENC1

Audio level: -69. (-34)Server time: 2010-09-29 18:52:41

volAlertClipRef PREFIX.11.3 Octet String

URL to the clip created for

this alert Value: IP Address

volStreamName

PREFIX.11.4 Octet String (Size

0...32)

Stream (scanner in RPM)

name Value: P1

volAlertEnum PREFIX.11.5 Integer [enumerate] Alerts enumeration See the following tableValue: 10

volAlertName

PREFIX.11.6 Octet String

(Size(32)) Alert nickname Value: AUDIOLOW

volAlertType PREFIX.11.7 Integer32 (0/1/2)

Type of alert: set (1),

clear(0), or warning (2) Value: 1

volCertainty PREFIX.11.8 Integer32 Certainty in percentage Value: 0

volAudioLevel PREFIX.11.9 Integer32 Audio level in dB units Value: -69 (-34)

volAudioPin PREFIX.11.10 Integer32 Audio Pin Value: 0

volEventTime


(Size(32))

Event time in format

2011/02/09 18:21:33 Value: 2010-09-29 18:52:41

rpmChannelID


(Size(32))

Lineup channel ID (usually a

channel number) Value: 66

rpmChannelName PREFIX.11.13 Octet String Lineup Service name Value: History Channel

rpmChannelQAM


(Size(32)) Lineup channel group Value: Westside

volAlertSeverity

PREFIX.11.15 Integer{ info (1),

warning (2), minor (3),

major (4), critical (5)}

The degree of priority to

correct the problem Value: 4

oidAlertLevel

PREFIX.11.16 Integer{ probe (1),

group (2), system (3)} Alert level

oidGroup


(Size(32))

Name of affected probe

group Value: Burlington News

oidProbe


(Size(32))

Name of affected probe

machine Value: Probe66

Variables in bold italicsin Table above specify the origin of the alert, e.g. volEncoderHostname,and the bold

underlineddetermine if an alert is Setor Cleared. The trap variables are described in @MIB Variables Table.


58/104


SNMP Notification Signaling Table13.1.6.

VolAlertName

Observer RPM Alerts (Fault Clips)

Set /Clear and Notify (w/o clear) alerts VolAlertEnum

VolAlert

Severity

VolAlert

Type

Set/

Clear

VIDEO-OK,

AUDIOLOW

Set AUDIOLOW Alarm for a specific

Media-Source 200 3 1 Set

VIDEO-OK,

AUDIOLOW

Clear AUDIOLOW Alarm for a specific

Media-Source 200 3 0 Clear

VIDEO-OK,

AUDIOHIGH Set AUDIOHIGH Alarm 200 3 1 SetVIDEO-OK,

AUDIOHIGH Clear AUDIOHIGH Alarm 2003

0 Clear

VIDEOLOST,

AUDIOLOW Set "Video Lost" Alarm 200(VIDEO)3

1 Set

VIDEOLOST,

AUDIOLOW Clear "Video Lost" Alarm 200(VIDEO)3

0 Clear

VIDEOBLACK,AUDIOLOW Set "Video Black" Alarm 200(VIDEO)

31 Set

VIDEOBLACK,

AUDIOLOW Clear "Video Black" Alarm 200(VIDEO)3

0 Clear

VIDEOSTATIC,

AUDIOLOW Set "Video Static" Alarm 200(VIDEO)3

1Set

VIDEOSTATIC,

AUDIOLOW Clear "Video Static" Alarm 200(VIDEO)3

0Clear

VIDEOMOTION Set "Video Motion Alarm 200(VIDEO) 3 1 Set

VIDEOMOTION Clear "Video Motion Alarm 200(VIDEO) 3 0 Clear

SCRIPTERROR System detected syntax error in the script 200 3 1 Set

TTLLOST Set "Teletext Lost" Alarm 300(METADATA) 3 1 Set

TTLLOST Clear "Teletext Lost" Alarm 300(METADATA) 3 0 Clear

CCLOST Set "closed captions Lost" Alarm 300(METADATA) 3 1 Set

CCLOST Clear "closed captions Lost" Alarm 300(METADATA) 3 0 ClearObserver Critical Events (no Clips)

Set/Clear and Notify(w/o clear)

POWER Toggle "STB Power" Event 400(POWER) 2 (warning) 2 Notify

TEST "Test" Event for a specific Encoder 10(SERVICE) 1 (info) 1 Notify

SERVICE STARTED Set "Service Started" Alarm 20(SERVICE) 2 1 Set

SERVICE STOPPED Clear "Service Stopped" Alarm 20(SERVICE) 3 0 Clear

Probe Down Alert Set "Probe Down Alert" 20(SERVICE) 4 (major) 1 Set

Probe Down Alert Clear "Probe Down Alert" 20(SERVICE) 4 0 Clear

ENCODER STARTED Set "Encoder Started " Alarm 30 (ENCODER) 2 (warning) 1 Set

ENCODER STOPPED Clear "Encoder Stopped" Alarm 30 (ENCODER) 5 (critical) 0 Clear

STORAGE LOST "Lack of Video Storage" Event 40(STORAGE LOST) 5 (critical) 2 Notify

STORAGE ERROR "HD file Error" Event 41(STORAGE ERROR) 5 (critical) 2 Notify

LICENSE "License expiration" Event 50(LICENSE) 5 (critical) 2 Notify


59/104


WHAT NOTTO DO ON THE SERVER SIDE14.

This section lists events and configurations that should not be applied to any of the Observer / RPM

servers.

1. Do not run a Web client application on the Observer Encoder or Web server2. Do not load/execute any additional applications on the server3. Do not install Antivirus software until checking with the Volicon Support group. In addition see

the @Antivirus Excluded Storage Areas / Services to Scan.

HMAILSERVER CONFIGURATION ON WEB SERVER15.

1. Launch the hMailServer Administrator in the Back End2. Login Username: hmailserver; Password hmailserver3. Select Setting IP Ranges Internet thenChange the IP Ranges settings:

a) In Allow connections section check the SMTP boxb) In Require Authentication for deliveries remove the check from To remote accountsc) In Allow deliveries from section check the External to externalaccountsd) Click the button

4. Restart hMailServer service


60/104


SMTP configuration15.1.1.

When the Observer server needs to send alerts from the local machine to client emails, insure that in the

C:\PHP\PHP.inifile the SMTP server is set to localhost as follows:

SMTP = localhost

HMAILSERVER CONFIGURATION THROUGH COMPANYSSMTPSERVER15.2.

Sometimes it is necessary to change the way the Observer / RPM sends alerts. This is due to the increased

security configuration on some networks. Instead of the alerts being sent out directly from the Observer

server, they are sent from your companys SMTP server.

The following actions need to be taken to enable the Observer server to send alerts via the SMTP server.

IN OBSERVER CONTROL CENTER:

Change the Email from default value [email protected]@companyX.com

IN HMAILSERVER:

Change the Domains from the default setting ofobserver.volicon.comtocompanyX.com
mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]://observer.volicon.com/http://observer.volicon.com/http://observer.volicon.com/http://cablevision.com/http://cablevision.com/http://cablevision.com/http://cablevision.com/http://observer.volicon.com/mailto:[email protected]:[email protected]


61/104


Add SMTP relaywpmail.companyX.comunder the \Settings\SMTP in the Delivery of e-mail tab

IN PHP.INI:

In the section [mail function] please change the smtp= to companyX.comand

sendmail_from = [email protected]

Restart the hMailServer, Apache and Observer Encoder services and then rebooted the server
http://wpmail.cablevision.com/http://wpmail.cablevision.com/http://wpmail.cablevision.com/mailto:%20companyX.commailto:%20companyX.commailto:%20companyX.commailto:[email protected]:[email protected]:[email protected]:[email protected]:%20companyX.comhttp://wpmail.cablevision.com/


62/104


HMAILSERVER EMAIL ROUTING LOG15.3.

The hMailServer log helps during debugging of email alert routing issues. To enable it, see the figurebelow:

Figure: hMailServer log

To test the email delivery, select a specific encoder from the Control Center to send the test alert:

Tools Test alert deliveryTo analyze the results, open hMailServer\logs for the latest log file and check the message paths. The

email history can be further organized by importing it to an Excel spreadsheet.


63/104


RAIDALERT NOTIFICATION16.

To insure RAID array errors are attended to ASAP, configure its Alert Notification as follows:

3Ware Configuration on Observer Servers16.1.1.

1. Log on to the Webserver Back-End2. Click Start\All Programs\3ware\3DM2\3DM 2 Web Interface

3. Log in as Administrator, default password: 3ware4. Click on 3DM 2 Settings tab

5. Send E-Mail: Select ENABLED6. Notify on:Select level of notifications: Info (sends all info, warning and error email alerts);

Warning (sends warning and error email alerts); Error (sends only error email alerts)

7. Sender:[email protected]. Recipient(s):Enter email address to receive these email alerts9. Mail Server (name or IP): localhost10.Mail Server Login: hMailServer11.Mail Password: hMailServer12.Select 13.Select 14.Logout15.Repeat this section for each additional Encoder moduleif any
mailto:[email protected]:[email protected]:[email protected]:[email protected]


64/104


RAID MAINTENANCE16.2.

1. Log on to the Webserver Back-End2. Click Start\All Programs\3ware\3DM2\3DM 2 Web Interface (see section above)3. Select the Management Maintenancemenu item to go to the main screen

Notice: In this example we have the minimum number of three active drives and one spare.

If one of the drives gets degraded it will be moved automatically down to degraded; the system will

still be able to run flawlessly on the two remaining drives.

The system will move the spare drive up automatically to join the Raid5 array drives, and will be

Rebuilding it. You can also initiate the process with the button.

Note: Always use the Remove Drivelink to remove a drive before unplugging it physically.

The button scans the ports on the controller. Rescanning updates the list of the

available drives shown and updates the status of all the attached disks. If error conditions have been

fixed, the status is updated to reflect that.

The Rescanning process is useful in a variety of maintenance tasks. For example, if you physically plug in

a drive and want the controller to recognize it, the Rescanprocess will accomplish that


65/104


ANTIVIRUS EXCLUDED STORAGEAREAS /SERVICES TO SCAN17.

Ensure that the antivirus program does not interfere with the Observer Programs/services. This can use

system resources needed by the Observer services, causing these to hang or crash.

Certain directories need to be open and free for continuous system access. To do it - turn off the on

access scanning and ensure that the following folders are removed from scans:

C:\video (encoder servers)

C:\program files\observer (webserver and encoder server)

C:\program files\MySQL\Mysql Server 4.1\data\ (webserver only)

ACTIVE DIRECTORY (AD)INTEGRATION18.

Prerequisites18.1.1.

The following prerequisites need to be met for the AD integration to proceed:

Volicon needs to know the IP address or the Fully Qualified Domain Name (FQDN) of AD server;

as FQDN is more flexible, it is preferred

The Observer Web server must be added to the AD domain

A simple domain user should be created with non-expiring password and given to Volicon

We also need a list of customers Organizational Units (OUs) and their basic structure

All the Observer servers should be upgraded to the latest qualified build prior to integration

All client browsers should have the Web server address in the Intranet Zone or IE trusted zone


66/104


Turning on AD authentication:18.1.2.

The following Web server .../htdocs/include/local.php variables should be set as follows:

// LDAP section

$use_ldap_accounts = true;

$ldap_server = "ldap://ldappdc.broadcastdomain.com:389";

$auth_user_suffix = '@broadcastdomain.com';

$base_dn = "DC=broadcastDomain,DC=com";

$ldap_user = 'anyADUserName'.$auth_user_suffix;

$ldap_pass = 'somethingVerySecureAndNoThatObvious';

//End of LDAP section

AD Operation18.1.3.

After all prerequisites are met several groups must be defined in the Observer. To do so the system

administrator can still access the system with a non-AD password through URL http:///admin/.

When using AD integration, the user's set of permissions (including accessible channels and max. number

of concurrent channels played) is defined on the Observer groups (User Management section). Identical

group names as defined in Observer need also be created in the AD. Once completed, the administration

of users' access to Observer and their privileges will only be administered through the AD by adding or

removing users to be members of the different groups. One exception is the number of concurrent

channels; though by default there is no limit, if defined the Observer settings will be used. Furthermore, if

multiple groups define the number of concurrent channels, the highest number will be used even if it is

set to unlimited.Initially the user accesses the Observer system through a browser with only an IP or Domain Name. Then

the access to the Observer system is provided automatically according to his assigned group(s) in AD,

matching them by group name to the defined Observer groups. If the user is a member of several groups -

his effective permissions will be the sum of all permissions of those groups. His name is automatically

created internally within the Observer upon first logon; and is associated with the user generated content

in the Observer - clips, programs etc.

Troubleshooting18.1.4.

One common issue in large organizations is that sometimes users cannot access the Observer systemtransparently and username/password dialog pops up. This is caused when IE cannot determine correctly

which webserver is in the Intranet security zone (i.e. accessed by IP). The solution is either to access the

server by server name (FQDN) or by adding the acce

Documents

Observer Admin Guide