Different ways to integrate with Omnicast

Security Center Omnicast is an open video surveillance solution. This post gives an overview of the most common ways to customize or integrate third-party systems with Omnicast.

Event and action

Omnicast has a powerful engine that allows administrators to configure how the system should react after a precise event. Here are only a few examples of the system being deployed without any programming:

  • Displaying one or many cameras in the Live Viewer when your shipping door opens
  • Starting the recording on a camera when another camera detects motion
  • Moving a dome to a specific preset when an IR motion sensor detects something
  • Sending an email when a specific user logs on the system
  • Creating a very complex chain of action by creating a macro

Macros

The Omnicast virtual matrix allows the user to create a custom script that will be executed by the system on schedule or when a particular event happens. The config tool includes a Macro Wizard that can be used to create simple macros. In fact, the wizard generates code in the background and if you want more flexibility, you can start editing the generated code from the config tool. The Omnicast Macro SDK comes with a series of function calls that allow you to do many things with our application. However, since these macros are pure VB Script or JavaScript, you can easily integrate with another system. Just a few examples of Macros that can be created:

  • Displaying cameras when specific characters a serial port are detected (POS/ATM machine)
  • Moving the dome to a specific preset after x seconds of inactivity on the dome
  • Saving a snapshot of a camera in a folder every x seconds
  • Creating an Omnicast alarm when we receive an alert of a TCP/IP protocol

Map engine (Web-based)

A map engine is a powerful tool that allows you to run your own code within our Live Viewer application. The Live Viewer supports displaying any web pages compatible with Internet Explorer. We also publish an API that allows the web page designer to interact with the current Live Viewer. The API offers a drag and drop functionality from the web page to the application. The Omnicast map designer takes advantage of the drag and drop to generate maps from a floor plan in JPEG/GIF format.

Any website designer can easily leverage the map engine to implement features such:

  • Displaying available cameras on Google maps or Virtual Earth
  • Showing motion detection alerts on a dynamic map
  • Showing a PTZ field of view on a floor plan
  • Opening/closing and showing status of car gate
  • Showing picture pop-ups and activity log from an access control product

Alarm Procedure

When an Omnicast alarm is raised, the Live Viewer user can display a procedure. The procedure is, in fact, an URL that will be displayed in the Live Viewer. Very similar to the map engine, Omnicast has an API that gives access to some alarm properties. This includes:

  • A simple HTML page or Word document that details the procedure for this alarm
  • An integration with case management tools and forces the user to enter a specific field
  • A page that captures some information and sends an SMS with info to a mobile agent.

Omnicast SDK

The SDK is a collection of ActiveX components and COM objects designed to build your own application with Visual Basic or C#. It contains every requirement to authenticate the system, receive and trigger alarms, event, display live or playback video, and modify configurations. 
It's the most flexible way to integrate with Omnicast but also the one that requires good programming skills. It allows you to:

  • Display an Omnicast camera (Live or playback) within your application
  • Add video capabilities to a web-based product
  • Query the Omnicast Archive database and export video in AVI or G64 format

Direct Show filter (DShow filter)

The DShow filter is a DirectX source filter that gives access to an uncompressed video stream (YUV or RGB). Its main purpose is for analytics company who need access to any cameras streamed by Omnicast. It's also used for transcoding. It requires a very good knowledge of Direct Show programming.

Genetec Protocol

The Genetec Protocol is designed for IP camera/encoder manufacturers that require support in Omnicast. It's an HTTP/CGI based protocol that supports MPEG-4, H.264 streaming over RTSP/RTP and JPEG over HTTP. As for Omnicast, it supports:

  • Video Configuration (Bitrate, framerate, resolutions...)
  • Events
  • Device Configuration (IP address, name)
  • Serial Port streaming and configurations
  • PTZ control
  • More features will be added in future releases

Learn more about our video management system here.

Previous Article
Shopping for a better retail investigation system?
Shopping for a better retail investigation system?

Today, many retailers are evaluating the use of digital evidence management systems. Here's 5 reasons why.

Next Article
Q&A with lieutenant Feig of the St. Louis PD
Q&A with lieutenant Feig of the St. Louis PD