EX ULTRA Adminguide 1 3

Administrator’s Guide
Eocortex
Version 1.3
[email protected]
www.eocortex.com
© Satellite, LLC, 2017
Published on: 05.10.2017
2
Table of contents
Table of contents ........................................................................................................... 2
Introduction .................................................................................................................. 7
1. Eocortex Ultra features and products ....................................................................... 8
1.1. Eocortex Ultra licenses ....................................................................................... 8
1.1.1. USB-key protection ..................................................................................... 9
1.1.2. Software key protection ............................................................................... 9
1.2. Eocortex Ultra Specification .............................................................................. 10
1.2.1. Licensing features ..................................................................................... 10
1.2.2. Main features............................................................................................ 10
1.2.3. High reliability and failover ......................................................................... 11
1.2.4. Devices .................................................................................................... 11
1.2.5. PTZ camera management .......................................................................... 12
1.2.6. Client application ...................................................................................... 13
1.2.7. Screen profiles .......................................................................................... 13
1.2.8. Archive playback ....................................................................................... 14
1.2.9. Export and printout ................................................................................... 14
1.2.10. Object plans .......................................................................................... 15
1.2.11. User scenarios. Schedules ....................................................................... 15
1.2.12. Alarm management ................................................................................ 15
1.2.13. Storage optimization .............................................................................. 16
1.2.14. Centralized configuration and management ............................................... 17
1.2.15. Integration with other systems ................................................................ 18
1.2.16. Video analytics (intelligent modules) ........................................................ 18
1.3. Contents of Package ........................................................................................ 19
2. How to install, update and remove Eocortex ........................................................... 21
2.1. Guidelines for choosing and configurating hardware platform ................................ 21
2.2. Guidelines for Windows settings ........................................................................ 21
2.3. Installing Eocortex Ultra software from a common installer ................................... 22
2.4. Installing Eocortex Ultra Client .......................................................................... 25
2.5. Updating Eocortex Ultra software ...................................................................... 25
2.6. Removing Eocortex Ultra software ..................................................................... 26
2.6.1. Remove software and save the settings ....................................................... 26
2.6.2. Complete removal of Eocortex Ultra products ............................................... 26
2.7. Installing and updating the license .................................................................... 27
2.7.1. USB key activation .................................................................................... 28
2.7.1.1. USB key offline activation .................................................................... 30
2.7.2. Software key activation.............................................................................. 32
2.7.2.1. Software key offline activation .............................................................. 34
2.7.3. License update.......................................................................................... 35
3. Eocortex Ultra Configurator .................................................................................. 36
3.1. Launching the Eocortex Ultra Configurator application .......................................... 36
3.2. Applying settings and controlling configuration .................................................... 40
3.3. Server settings ............................................................................................... 42
Eocortex Ultra
3
3.3.1. Connected servers..................................................................................... 43
3.3.1.1. Server addition to the system ............................................................... 44
3.3.1.2. Server setting ..................................................................................... 45
3.3.1.2.1. Selected server License parameters ............................................................................. 46
3.3.1.2.2. Archive location settings .............................................................................................. 46
3.3.1.2.3. Network server settings ............................................................................................... 48
3.3.1.2.4. Connection of the Mobile Devices ............................................................................... 49
3.3.1.2.5. Additional settings ........................................................................................................ 50
3.3.1.2.6. Client auto-update settings .......................................................................................... 51
3.3.1.2.7. Server information ....................................................................................................... 51
3.3.1.3. Troubleshooting of access to the main server ......................................... 51
3.3.1.4. Server recovery .................................................................................. 52
3.3.1.5. Setting as main server ......................................................................... 53
3.3.1.6. Disconnection of the server from the system .......................................... 53
3.3.1.7. Assignment of the server address ......................................................... 53
3.3.1.8. Server port assignment ....................................................................... 53
3.3.1.9. Centralized update of the server applications .......................................... 53
3.3.1.10. Server diagnostics ............................................................................... 55
3.3.1.11. Update the server license ..................................................................... 55
3.3.1.12. Replication server settings ................................................................... 56
3.3.2. Distribution of channels by servers .............................................................. 57
3.3.3. Eocortex System Healthcheck configuration .................................................. 58
3.3.4. Multicast channels ..................................................................................... 58
3.4. Camera settings .............................................................................................. 59
3.4.1. Camera auto search and connection ............................................................ 61
3.4.2. Channel connection settings ....................................................................... 62
3.4.2.1. Connecting video servers ..................................................................... 64
3.4.2.2. Connecting DVRs ................................................................................ 65
3.4.2.3. Configuring memory card access parameters .......................................... 65
3.4.2.4. Connecting panoramic cameras ............................................................ 66
3.4.3. Configuring data streams ........................................................................... 67
3.4.3.1. Using two streams .............................................................................. 69
3.4.4. Archiving settings...................................................................................... 70
3.4.5. Intelligence analysis system settings ........................................................... 72
3.4.5.1. Motion detector settings....................................................................... 72
3.4.5.2. Sound detector ................................................................................... 75
3.4.5.3. Perspective settings ............................................................................ 75
3.4.5.4. Configuring face detection module ........................................................ 76
3.4.5.5. Configuring Suspect search .................................................................. 76
3.4.5.6. Configuring external intelligent modules ................................................ 76
3.4.6. Patrolling ................................................................................................. 77
3.4.7. Scheduled tasks ........................................................................................ 77
3.4.8. Scenarios (response to system events) ........................................................ 80
Eocortex Ultra
4
3.4.8.1. Limit by start time condition ................................................................. 81
3.4.8.2. Movement event ................................................................................. 81
3.4.8.3. Loud sound event ............................................................................... 81
3.4.8.4. Lost connection with camera event ........................................................ 81
3.4.8.5. Established connection with camera event .............................................. 81
3.4.8.6. Face detection event ........................................................................... 81
3.4.8.7. Camera input signal event.................................................................... 82
3.4.8.8. No connected camera event ................................................................. 82
3.4.8.9. Analog camera connection fail event ...................................................... 82
3.4.8.10. Connecting to analog camera ............................................................... 83
3.4.8.11. User alarm event ................................................................................ 83
3.4.8.12. External alarm start event .................................................................... 83
3.4.8.13. End of external alarm event ................................................................. 83
3.4.8.14. Motion started event ........................................................................... 83
3.4.8.15. Motion stopped event .......................................................................... 83
3.4.8.16. Siemens DMS8000 event ..................................................................... 83
3.4.8.17. Moving objects tracking event .............................................................. 84
3.4.8.18. Smoke event ...................................................................................... 84
3.4.8.19. Fire event .......................................................................................... 84
3.4.8.20. Large number of people in the queue event ............................................ 84
3.4.8.21. Large crowd of people event ................................................................. 84
3.4.8.22. Recognized license plates event ............................................................ 84
3.4.8.23. Request to open gate event .................................................................. 85
3.4.8.24. Request to close gate event ................................................................. 85
3.4.8.25. Video surveillance sabotage event ......................................................... 85
3.4.8.26. Inactive zone event ............................................................................. 85
3.4.8.27. Lost luggage detected event ................................................................. 85
3.4.8.28. Add a record action ............................................................................. 85
3.4.8.29. Remove a record action ....................................................................... 86
3.4.8.30. Set a camera position action ................................................................ 86
3.4.8.31. Send an SMS notification action ............................................................ 87
3.4.8.32. Send an e-mail notification action ......................................................... 89
3.4.8.33. Send a signal to the camera output action.............................................. 90
3.4.8.34. Run external application on the server action ......................................... 91
3.4.8.35. Alarm generation action ....................................................................... 91
3.4.8.36. Save frame action ............................................................................... 91
3.4.8.37. Pause action ....................................................................................... 92
3.4.8.38. Enable camera AF mode action ............................................................. 92
3.4.8.39. Activate camera washer action ............................................................. 92
3.4.8.40. Disable frame skipping when recording to the archive action .................... 93
3.4.8.41. Barrier closed notification action ........................................................... 93
3.4.8.42. Barrier open notification action ............................................................. 93
3.4.9. Cloud broadcast settings ............................................................................ 94
3.4.10. Group settings ....................................................................................... 95
Eocortex Ultra
5
3.4.11. Indication of connected modules .............................................................. 96
3.5. User right settings ........................................................................................... 96
3.6. Object plans ................................................................................................... 98
3.7. Setting screen profiles .................................................................................... 102
3.8. Configuration of the categories of the archive bookmarks .................................... 104
4. Status Info utility, Eocortex Ultra Standalone control window, autorun Eocortex Ultra Client
105
4.1. Status Info utility ........................................................................................... 105
4.2. Eocortex Ultra Standalone control window ......................................................... 106
4.3. Autorun of Eocortex Ultra Client and Eocortex Ultra Standalone Viewer ................. 106
5. Intellectual modules ........................................................................................... 108
5.1. Sabotage detection module: ............................................................................ 108
5.2. Tracking module ............................................................................................ 109
5.2.1. Configuring the tracking module ................................................................ 109
5.2.1.1. Detector settings ............................................................................... 110
5.2.1.2. Alarm settings ................................................................................... 111
5.2.2. Camera position ....................................................................................... 113
5.3. People counting module .................................................................................. 114
5.3.1. Configuring the module ............................................................................. 114
5.4. License plate recognition module ...................................................................... 117
5.4.1. Module features ....................................................................................... 118
5.4.2. Licensing................................................................................................. 118
5.4.3. Installing and updating the module ............................................................ 120
5.4.3.1. Installation ........................................................................................ 121
5.4.3.2. Update ............................................................................................. 122
5.4.5. Requirements and recommendations .......................................................... 129
5.4.5.1. Choosing a camera ............................................................................. 129
5.4.5.2. Camera settings................................................................................. 129
5.4.5.3. Camera position and field of view ......................................................... 129
5.4.5.4. Requirements for obtained images of license plate ................................. 130
5.4.6. Eocortex Ultra barrier operation ................................................................. 132
5.4.6.1. Testing camera alarm outputs ............................................................. 132
5.4.6.2. Barrier control scenario ....................................................................... 133
5.4.7. Troubleshooting and replacing of license plate recognition module protection key
firmware 134
5.4.7.1. Troubleshooting ................................................................................. 134
5.4.7.2. HASP key driver ................................................................................. 135
5.4.7.3. License plate recognition module key options ........................................ 136
5.4.7.4. License plate recognition library efficiency ............................................. 137
5.4.7.5. Module operation ............................................................................... 138
5.4.7.6. HASP key firmware ............................................................................ 140
5.5. Crowd monitoring ........................................................................................... 141
Eocortex Ultra
6
5.5.2. Configuring cameras ................................................................................. 143
5.6. Heat map module ........................................................................................... 144
5.6.2. Camera position ....................................................................................... 145
5.7. Auto Zoom .................................................................................................... 147
5.7.1. Configuring the function ............................................................................ 147
5.8. Face recognition module ................................................................................. 148
5.8.1. Installing and licensing the module ............................................................. 148
5.8.3. Guidelines and requirements ..................................................................... 153
5.9. Abandoned object detector .............................................................................. 154
5.10. People counting in queue module .................................................................. 156
5.10.1. Configuring the module.......................................................................... 156
5.10.2. Camera position .................................................................................... 159
5.11. Fisheye cameras dewarping module .............................................................. 160
5.12. Activity monitoring module ........................................................................... 162
5.12.2. Camera position .................................................................................... 164
5.13. Smoke and fire detection ............................................................................. 164
5.14. Suspect tracking ......................................................................................... 166
6. Eocortex System Healthcheck .............................................................................. 167
6.1. Eocortex System Healthcheck configuration ....................................................... 168
6.2. Web-client ..................................................................................................... 169
6.2.1. Home page.............................................................................................. 170
6.2.2. Events Log page ...................................................................................... 171
6.2.3. Server's info pages ................................................................................... 171
6.2.4. Settings pages ......................................................................................... 176
7. Additional features ............................................................................................. 177
7.1. Driver package for cameras and devices (DevicePack) ........................................ 177
7.1.1.1. Installing DevicePack .......................................................................... 177
7.1.1.2. Removing DevicePack ......................................................................... 178
7.2. System log files ............................................................................................. 178
7.3. Viewing archives in case of failures ................................................................... 179
7.4. Optimal camera settings ................................................................................. 181
Eocortex Ultra
7
Introduction
This guide describes the operation process of the Eocortex Ultra software suite designed for
intelligent analysis, processing, archiving and display of video data, and one point to manage
cameras in a video surveillance system based on IP cameras.
The guide may contain screenshots of previous versions of Eocortex. In this case it is supposed
that the functionality described in these screenshots have not changed in the current version of
Eocortex.
After the release and publication of the next version of Eocortex Ultra software the manual can
be supplemented with changes not included in the version of the manual included in the Eocortex
Ultra software installation package. To receive up-to-date documentation, please check the
publication date of the Eocortex Ultra Administrator's Guide at www.eocortex.com and, if the
newer version is available, download it from the Support / Documentation page.
The documentation kit also includes the Eocortex Ultra User’s Guide describing the end-user
experience with Eocortex Ultra software.
Eocortex Ultra
8
1. Eocortex Ultra features and products
Eocortex Ultra is a software suite designed for intelligent analysis, processing, archiving and
display of video data and one point to manage cameras in video surveillance systems based on
IP cameras.
1.1. Eocortex Ultra licenses

One of the two measures used to protect license of Eocortex Ultra server software:
USB-key or software key. One server can be protected with only one type of key.
Licensing of Eocortex Ultra Client software is not required.
Eocortex Ultra licenses vary in type, bit depth, number of channels and additional features.
Product functionality is determined by the type of license and does not depend on the installation
method of Eocortex Ultra server software. Thus, when changing the type of license there is no
need to reinstall Eocortex Ultra server software — just reinstall the license file.
For more information on Eocortex Ultra features depending on the types of licenses see the
Eocortex Ultra Specification.
Eocortex Ultra
9
1.1.1. USB-key protection
License protection using USB-key consists of two components: a USB-key itself and a license file
(*.lic). The license file is installed on the same server with the USB-key. One server can use only
one Eocortex Ultra software protection USB-key.
Key series and number are marked on the edge of the
key (for example, 186Z 2B217205.)
The license file has an extension *.lic and should have
initial numbers matching with USB-key serial number:
number on the key must match the number in the license
file name.
The table shows the explanation of the license file name:
Nomenclature of a name of license file. for example: B217205_MC_ST_x64_c100_f100_
s100_a100_p10_fr10_apr10_pcnt10_tr100_crwdcnt10_heat10_queue10_abnd100_
dvr10.lic
Number of the key to be used with the file 2B217205
License type: ML / LS / ST ST
Bit depth: x64 — for 64-bit Eocortex Ultra licenses; 32-bit Eocortex Ultra license do not have x64
this parameter in the file name
The number of IP cameras (channels):
c — total cameras 100
f — with face detection support 100
s — with interactive search support 100
a — with sound support 100
p — with camera control support (PTZ) 10
fr — with face recognition support (using base) 10
apr — with license plates recognition support 10
pcnt — with people counting support 10
tr — with tracking moving objects support 100
crwdcnt — with people groups search support (crowd detector) 10
heat — with heat maps support 10
queue — with queue counting support 10
abnd — with left objects detector support 100
dvr — with DVR channel support (reserved) 10
If any of the quantitative parameters = 0, it is not included in the license file name
If you extend the license (increasing the number of channels, adding features), the USB-key
should not be replaced — just install a new license file.
USB-key is not assigned to a specific computer.
For example, to move a video server from computer A to computer B, you need to remove the
USB-key from the computer A and install it on the computer B — in this case the Eocortex Ultra
server software on your computer A will cease to operate.
1.1.2. Software key protection

License protection using a software key includes a request file associated to a specific computer.
After activation the key can not be moved to another computer.
The key is assigned to server hardware components (equipment):
On host machines the key is assigned to serial numbers of the system drive and the
motherboard.
On virtual machines the key is assigned to the MAC address, the CPU features and to the UUID
of the virtual machine (the system will run only if all three parameters match.)
Eocortex Ultra
10
1.2. Eocortex Ultra Specification
Eocortex Ultra is a global provider of an open platform video management software with the
strong intelligence of video analytics added. The software package is easy to layout, install, set
up, and service. Regular updates and technical support are provided for free.
1.2.1. Licensing features

Single Eocortex license permits the connection of one IP camera, client software, mobile
applications and Web-client are provided free of charge.
LICENSE KEY TYPE USB KEY SOFT KEY
USB security key, Soft key sent via email,

Distribution kit Software installation package Software installation package
(available at Eocortex.com) (available at Eocortex.com)
1.2.2. Main features
MAIN FEATURES DESCRIPTION
Cameras per one server Maximum number of cameras on one server
Servers in the system Maximum number of servers in the system
Remote workstations Maximum number of remote workstations

Windows 7 SP1 / 8 / 8.1 / 10 / Server 2008 R2 SP1 / Server
2012 / Server 2012 R2 (x86 and x64)
Operating Systems Windows Embedded (for Intel x86 and x64 with the full
functionality of abovementioned Windows versions)
Ubuntu 14.04 LTS (Linux)
Windows 32-bit (x86), 64-bit (x64);
Bitness Linux 64-bit (x64)
Video Stream Formats MJPEG, MPEG-4, H.264, H.265
PCM, G.711U, G.711A, G.722.1, G.726, G.729A, GSM-AMR,
Audio Stream Formats AAC
Sound transmission from the operator workstation to the
Duplex Audio Mode camera’s speaker or audio output
Centralized: all cameras from different geographical locations
stream to servers located at one place, Client application is
fetching from one server.
Centralized Or Distributed
Distributed: servers located at multiple places are unified in
Monitoring Solution one system, which allows cameras to be accessed via Client.
The cameras' streams are requested straight from the servers
they are connected to which happens in background.
Decode H.264 on GPU to reducing the CPU load during
CPU Load Reduction display. DXVA technology
Real-time and Archive Video Frame Export and Frame Saving
Export and Frame Saving (JPEG, PNG, BMP). Archive Video Export (AVI, MCM)
Place cameras, sensors and relays of the system on 2D object
plans (maps); Create custom object plans with In-built Graphic
Object Plans Tool within Eocortex Interface; Make changes to the existing
object plans
Eocortex Graphical user interface is intuitive for any user and
User-friendly GUI do not require any special administrator or programming skills
Make use of the largest variety of video analytic modules:
Suspect Search and Suspect Tracking, PTZ Camera Control,
Fisheye dewarping, License Plate Recognition, Audio stream
Advanced Video Analytics processing, Loud Sound Detection, Smoke and Fire Detection,
(Intelligent Modules) Tracking, People Counting, People Counting in Queue, Crowd
Monitoring, Face Detection, Face Recognition, Heat Map,
Abandoned Object Detection, Personnel Monitoring, Sabotage
Detection
Eocortex Ultra
11
MAIN FEATURES DESCRIPTION
English, French, Italian, Dutch, Polish, Portuguese, Russian,

Interface Languages Czech, Slovak, Spanish, Turkish
1.2.3. High reliability and failover

HIGH RELIABILITY
DESCRIPTION
AND FAILOVER
Additional Main Drives Scalable directly attached storage space.
In case the main drive breaks down or fails to do the recording,

Reserved Drives the channel will be recorded by the reserved drives
Ensures high flexibility of the system and resiliency of its
Multiserver Architecture components
In case of server failure, real-time broadcast of channels and
archive recording are performed by the reserved servers;
Hot Swap
Switching between failed and reserved servers takes up to 10
seconds
Cold Standby Cameras’ settings protection in case the server breaks down
Local Console Application used to notify a user about the
Status Info current system state, to run and stop Eocortex Server
Application, to run and stop Eocortex Configurator
Self-diagnosis is the function aimed at the automatic search for
Eocortex System the possible problems in a system. The users will receive the
Healthcheck notifications of problem detections and will be able to solve the
problems as soon as possible.
The replication of the databases is done automatically. If a
Increased stability and database is damaged, it will be automatically restored from the
safety of databases replication. Therefore, the Journal data is protected as well as
the results of Suspect Search and Suspect Tracking.
Set simultaneous recording of the video archive and the
Archive Mirroring (Backup
database both on the mirror and main drives of the single
Drives) server. Refer to ULTRA VMS for this functionality
1.2.4. Devices
DEVICES DESCRIPTION
ONVIF™ Compliant
Yes, Profile S
Devices
PSIA Compliant Devices Yes, version 1.2
Connection via IP network to IP video cameras, network video
IP Network Connection recorders, video servers, encoders
IP Camera Auto Search Yes, if the IP device supports ONVIF or UPnP
Perform camera IP-address setup, detect connectivity and
IP Camera Remote
functioning issues from Eocortex Configurator directly
Preview (without connecting to a camera web interface)
Configure IP camera settings remotely from Eocortex
IP Camera Remote Configurator: codec, resolution, frame rate, compression level;
Configuring Preview the video stream from this camera before applying
new settings
Camera Network Ports Specify camera network ports when using non-standard ports
Setup of cameras for video streaming
Copy settings of the devices and apply to the new ones:
Device Settings Transfer connection parameters, scenarios, schedules, video analytics
(intelligent modules) settings
Eocortex Ultra
12
DEVICES DESCRIPTION
Apply settings to the groups of devices: connection

Device Group Settings parameters, scenarios, schedules, video analytics (modules)
settings
Drag and Drop IP Camera Transfer IP camera from one server to another in a few
Transfer Between Servers seconds
Receives up to two video streams from IP camera, each

Two Video Streams
stream with customizable parameters: codec, frame rate,
Parameters resolution
IP Camera Motion
Employ in-built IP camera motion detector
Detector
Camera signal I/O
System management using I/O functionality of the camera
Functionality
Real-time broadcast and archiving of the video and audio
DVR, Video Server and streams received from IP and/or analog cameras connected
Video Decoder Support to video decoders, video recorders and video servers; Support
of PTZ functionality of such cameras
Archive viewing at DVRs (devices must support data transfer
Devices Internal Archive in MJPEG, MPEG-4 or H.264);
Support Access to the internal archives of DVR and IP Cameras placed
at SD-card, in-built HDD, etc.;
Support of various modes used in panoramic and multi-lens
Panoramic, Multi-Lens cameras, including broadcasting of video streams received
Camera Modes from different lenses on different channels (for certain camera
models only)
Real-time broadcasting and archiving of individual audio
IP Audio Encoders channels (for certain devices only)
Support of the two-way audio channel and access control
IP Intercom Support system (for certain devices only)
Provides backward compatibility of IP cameras and devices -
DriverPack Support after the Server Application upgrade
1.2.5. PTZ camera management

PTZ CAMERA
DESCRIPTION
MANAGEMENT
Control of PTZ cameras: camera rotation, zoom in/out (optical
zoom), focus, I/O ports, wiper; Employ joystick, PTZ control
PTZ Camera Interactive
panel, mouse or keyboard; Can be done manually with the
Control client interface and automatically upon a system event
(scenarios) or on a schedule
Manage with the help of virtual PTZ joystick with custom
Virtual PTZ Joystick rotation speed
Transition by Presets Transition by presets of PTZ camera
Create customized preset tours (routes of transition by
presets); Stop auto patrolling while operating manually;
Auto Patrolling (Tours)
Connect custom axes and buttons of PTZ joystick and PTZ
control panel to the presets and tours
PTZ Zoom of Selected Use zoom in/out functionality for the selected area in the frame
Area (zone)
PTZ Camera
Use PTZ camera management emulation for panoramic
Management for cameras
Panoramic Cameras
Support of the MultiDome function implemented in some
MultiDome cameras
Support of the AreaZoom function implemented in some
AreaZoom cameras
Eocortex Ultra
13
1.2.6. Client application
CLIENT APPLICATION DESCRIPTION
Operate in the video surveillance system with Eocortex Client

Application; Access all the video surveillance features in
Eocortex Client several clicks: video real-time and archive video, configure and
Application manage IP cameras, view events, employ video analytics
(intelligent modules); Set custom settings for a number of
parameters
Directly from a server; via remote workstation connected to a
Real-time Viewing Modes server; via remote workstation connect to a camera directly
Eocortex Graphical User Interface (GUI) is intuitive for any
User-friendly GUI user and do not require any special admin or programming
skills
Full-screen and Grid
Use full-screen and various grid modes
Modes
Multiple Monitor Support Use multiple monitors operating from a single remote
on a Single Workstation workstation
IPv4 and IPv6 Support Connecting cameras to IPv4 and IPv6 addresses,
including auto search for such cameras in a network
Send one single video stream from the camera, regardless of
Multicast Broadcasting the number of recipients
CPU Load Reduction with Decode H.264 on GPU to reducing the CPU load during
Decoding H.264 on GPU display. DXVA technology
Video Stream Proxy Use one of the servers to broadcast video streams to remote
Support workstations from other video servers
Video Stream Buffering Increases the smoothness of the display due to frames
buffering
Centralized update of all “Update the server” button allows to update all the servers in
the servers in a system one window. The servers can be updated from a remote
workstation as well as downgraded to the previous version.
The update should be downloaded only once.
1.2.7. Screen profiles

SCREEN PROFILES.
DESCRIPTION
VIDEO WALL
Perform centralized customization of the screen profiles in a
few clicks; Display a specific set of cameras placed on a grid
Screen Profiles template in multiscreen mode; Configure automatic grid
Configuring and change sequences with a custom period for display; Set
Automation default screen profiles; Create unlimited number of templates
and lists of profiles; Display up to 262 cameras on a single
screen
Drag and Drop IP Camera
Transfer IP camera from one screen profile to another in a few
Transfer Between Screen seconds
Profiles
Zoom in real-time and while viewing archive, expand selected
Digital Zoom Support area to the full-screen
Set various frame dimensions during display: dimensions by
Custom Frame default, stretching the cell size, automatic selection;
Dimensions
Set custom frame dimensions for each cell individually;
Camera HTML-page
Open HTML-page of the camera in browser
Support
Manual Recording Manual recording by operator for selected channels
Create a video wall of any number of monitors without any
In-built Video Wall external devices. Refer to ULTRA VMS for this functionality
Eocortex Ultra
14
1.2.8. Archive playback
ARCHIVE PLAYBACK DESCRIPTION
Independent Archive
Run independent archive playback in selected cells, while real-
Playback time broadcasting in the other cells simultaneously
in Selected Cells
Synchronized Archive
Playback of Multiple Run time-synchronized archive playback on a single monitor;
Cameras on a Single Supports up to 25 cameras simultaneously
Monitor
Customize the variety of control and navigation parameters:
timeline, calendar, playback speed, play / pause, forward /
Custom Control and back;
Navigation Parameters
Use timeline to define the presence of archive, move to the
certain archive fragment;
Use visual calendar to select archive recordings created at the
Archive Calendar particular date and time
Playback speed from x0.01 to x120. Key frame playback
Archive Playback Speed support
Digital Zoom Support Zoom in selected area of the frame, expand to full-screen
Archive viewing at certain DVRs (certain devices must support
Devices Internal Archive data transfer in MJPEG, MPEG-4 or H.264);
Support Access to the internal archives of DVR and IP Cameras placed
at SD-card, in-built HDD, etc.;
Enjoy smooth automatic switch between the archives located
Smooth Playback
on the server and the camera in case the archive
of Combined Archives is available on the camera only
Mark fragments with Archive Bookmarks, range bookmarks by
importance and categories, add comments to the bookmarks;
Archive Bookmarks Filter Archive Bookmarks in the Event Log based on date and
Support time, channels, importance and categories; Run archive
playback from the bookmark in preview window from the Event
Log, switch playback to the main window manually
Users can get a report on the archive depth showing the
archiving for particular days and cameras. The function will
Reports on archive depth help to monitor the problems with cameras and the network.
The report will be especially useful for large scale systems.
1.2.9. Export and printout

EXPORT AND
DESCRIPTION
PRINTOUT
Real-time and Archive Make a screenshot in real-time or archive video; Save the image
Video Frame Export and to the selected location;
Printout Print out the image or selected area of the frame
Frame Export Formats JPEG, PNG, BMP
Archive Video Export Export selected video fragments from archive
Video Export Formats AVI, MCM (proprietary Eocortex format); Export time-
synchronized video fragments from multiple channels (MCM
only)
Eocortex Ultra
15
1.2.10. Object plans
OBJECT PLANS DESCRIPTION
Place cameras, sensors and relays of the system on 2D object

Object Plans Support plans (maps); Define the cameras’ surveillance coverage; Bind
external sensors to camera signal inputs; Bind external
devices to camera signal outputs; add intelligent modules in
cameras’ surveillance coverage
Display field of view coverage of all the cameras of the system
at the single object plan; Display the frames received
Camera Video Stream
from the certain camera at the object plan; Display video
Display analytics data at the object plan; Display real-time video by
pointing the certain camera of the object plan
Object Plans Import
JPG, PNG, BMP
Formats
Create custom object plans within Eocortex Interface; Make
In-built Graphic Tool changes to the existing object plans
1.2.11. User scenarios. Schedules

USER SCENARIOS.
DESCRIPTION
SCHEDULES
Create automated action sequence in response to various
events: archiving management, notifications by e-mail and
User Scenarios SMS, signals to the outputs of IP cameras, launch of external
Configuring and application, etc. (more than 40 scenarios available);
Automation
Configure rules, parameters, filters, periods, and other
conditions for certain events and actions
Create single automatic action sequence based on a certain
date;
Schedules Configuring Create recurring automatic action sequence with a custom
and Automation period, months, dates, weekdays
Configure rules, parameters, filters, periods, and other
conditions for certain events and actions
1.2.12. Alarm management
ALARM MANAGEMENT DESCRIPTION
Process Alarm events (registration, generation, notification)

within scenarios and event log; Configure Client Application for
Enhanced Alarm
advanced signal and alarm management, including alarm
Management generation by operators; Develop your own signal and alarm
generation mechanisms with Eocortex API and SDK
Visual, Audible Alarm Notify the operators on the alert event instantly with visual and
Signaling audible alarm signaling system;
Set one of the monitors as an Alarm Monitor to display alarm

Alarm Monitor Configuring events; Exclude certain channels from the Alarm Monitor’s grid
and Automation when a specified period passes after the alarm; Configure and
display alarms on the Alarm monitor only
Use Alarm cells for certain channels to display alerts and
Alarm Cells Support alarms when the event is happening
In Guard mode, the user is notified (in Eocortex Client) if the
alarm has been generated; This certain channel switches to
Guard Mode Support the Alarm mode; Guard mode can run on schedule or
manually
Enable user alarm for certain channels with Alarm button;
Alarm Button Support Alarm button display is configured by the system administrator
Send emails, SMS and push-notifications to alert the recipients
Notifications about the alarms and other system events;
Send frames as email attachments
Eocortex Ultra
16
ALARM MANAGEMENT DESCRIPTION
Event Log called Journal provides data on Server Application

System And Alarm Event audit and users actions, data on camera connections, alarms
Log (including missed alarms), video analytics results and other
events
Search in Event Log by filters: events, user actions, actions,
Event Log Filters archive bookmark
1.2.13. Storage optimization

STORAGE
DESCRIPTION
OPTIMIZATION
Duplicate archive data received from the defined IP cameras
to a dedicated replication server;
Archive Replication
Set custom parameters for the archive stored at replication
server;
Browse using a separate channel; several channels
Archive Browsing Modes simultaneously; backward playback
Server archive is stored on the logical drives defined by the
Archive Storage Location
operating system: HDD and SSD, RAID-arrays, external disk
on Logical Drives storage, network drives and their combinations
Archive Storage Format In the format received from the IP camera
Speed of archive recording and display is limited by the
hardware resources only; Cyclic recording: the oldest records
are replaced when reaching the disk space overflow; Pre- and
Archive Recording post-recording periods can be set based on motion detection
Optimization event; When using multiple logical drives, the recording is
conducted on all available logical drives to enhance the
performance; Separate drives can be set for recording of video
archive and metadata base;
Continuous; at the operator's request; when motion is detected
by the camera; upon Eocortex motion detector; on a schedule;
Storage Modes Available upon a system event (scenario). Recording modes can be
combined
Size is limited only by the drive storage and operating system;
Various archive size limits can be set for each IP
camera/group of cameras; Storage limits can be set for the
each logical drive: maximum storage size, minimum allowable
free space;
Archive Size Optimization Frame skipping reduces the storage space when no motion is
happening; With H.264 reference frames can be chosen to be
archived when no motion is noticed; Switching of Archiving
from Alternate stream to the Mainstream allows to switch
archive recording from an alternative stream (low quality, small
archive volume) to the Mainstream (high quality, large archive
volume) when certain system events occur (or scheduled)
Synchronization of archives between IP camera and server.
Allows to import absent fragments from IP camera to the
Archive Synchronization server - to restore the server after a loss, to recover camera
connection, to store the archive received from standalone or
mobile camera on the server.
Eocortex Ultra
17
1.2.14. Centralized configuration and management
CENTRALIZED
CONFIGURATION AND DESCRIPTION
MANAGEMENT
Centralized: All cameras from different geographical locations
stream to servers located at one place, Client application is
Centralized Or fetching from one server.
Distributed Monitoring Distributed: Servers located at multiple places are unified in one
Solution system, which allows cameras to be accessed via Client.
Desired cameras' streams are requested straight from the
servers they are connected to, all this happens in background
Microsoft® Active Support for installation, start and authentication with Microsoft®
Directory Active Directory accounts
Configure automatic start of Eocortex application after the start

Applications Auto Start of operating system;
Configure automatic authentication after the application start
Compatibility of client software with server software of other
Versions Compatibility versions (other than the client software version)
Set automatic updates of client software when connected to a
Client Auto Update server
System Health Monitor the current state of the video surveillance system
Monitoring components
Monitor the current state of Eocortex server parameters:

accessibility, status, CPU usage, memory usage, analysis
system usage, archiving system usage, client-server system
Server Monitoring usage, network usage, hard drives status, connected cameras
status;
Monitor the current state of multiple servers simultaneously;
Customize alarms generated on the events: server out of reach,
excessive CPU usage, excessive memory usage, excessive
network usage, alarm status of camera digital inputs, camera
Monitoring Alarms failures;
Receive custom alarm notifications for the events by email, SMS
or SNMP trap
All configuration settings are made from the Eocortex
Centralized Setup Configurator Client with remote or local connection to the server
Individual Server Each server stores its own configuration parameters: archive
Settings settings, network settings, and mobile connection parameters
By default, one server in the system is assigned as the Main

Server, and the others are Reserved.
System configuration parameters are stored on the Main Server:
Main and Reserved user rights, roles of the servers, channel settings (including the
Servers connection parameters, scenarios, schedules and video
Individual Settings analytics parameters), channels distribution settings, backup
and archive replication settings, screen profiles, object plans;
Each Reserved Server stores the backup of system
configuration parameters
Perform centralized or distributed management of all User rights
in the system; Customize User rights for the variety of actions
available in the system; Differentiate user rights basing on the
groups of users; Customize User access rights to the certain IP
User Rights cameras in the system, Differentiate User rights for real-time
Management broadcasting and archive viewing for each IP camera; Support
of Users and User Groups in Microsoft® Active Directory; Main
server of the system provides centralized authentication and
user permissions checks; Cameras will not be displayed in the
Client Application, if the user does not have rights to view them
Internal Chat Exchange messages, screen profiles and certain settings
between the users. Refer to ULTRA VMS for this functionality
Eocortex Ultra
18
1.2.15. Integration with other systems
INTEGRATION
WITH OTHER DESCRIPTION
SYSTEMS
Contains a list of API, Json- and XML-requests, as well as
Open SDK for
examples in C #; allows integrating Eocortex with various
Developers applications
Flash-Component for Allows real-time audio and video broadcasting, as well as
Web-sites controlling PTZ cameras
Integrations Integrate Eocortex with Fire Alarm and Access Control systems
Broadcast video streams from a server to the cloud solution built
Cloud Broadcasting on Eocortex Cloud
1.2.16. Video analytics (intelligent modules)

VIDEO ANALYTICS
(INTELLIGENT DESCRIPTION
MODULES)
Detect movement in the frame by real-time video stream
analysis;
Set limiting dimensions of detected objects in the frame (Basic
Eocortex Motion Mode);
Detector Set several detection zones and limiting dimensions of detected
objects for each zone (Expert Mode);
Use Motion Detector metadata both to start the archiving and for
further video analysis;
Decrease the frame rate received from camera to reduce the
System Load Reduction system load
Computational Load Enable partial H.264 decoding to reducing the computational
Reduction with Partial load during motion detector usage for video streams
H.264 Decoding in H.264 (additional to MJPEG)
Interactive object search in archive by uploaded photograph

Suspect Search or by object’s characteristics: color, dimensions/size, position in
the frame, shape
Suspect Tracking Tracking moving objects in the field of view of multiple cameras
Control of PTZ cameras using the client interface: camera
PTZ Camera Control rotation, zoom in/out (optical zoom), focus, etc.
Expand a spherical image from the Fisheye camera in three
Fisheye dewarping ways: double panorama, in simulation PTZ mode, in 4x90 mode.
Expansion in real time and while playing archive
Available for 91 countries: detection of license plates in the
frame; events archive; maintaining a database of license plates
with different settings for each license plate; maintaining multiple
License Plate lists; interception of license plates by the list; barrier control by
Recognition the list or by an operator command; export to Excel; determining
the movement direction; output of license plates on bases of
different color, depending on groups; differentiation of access
rights; import of license plates databases using external files
Audio stream
Broadcasting and archiving of audio from IP cameras
processing
Detect an excessive audio level registered by the camera
Loud Sound Detection microphone
Smoke and Fire
Detect the presence (emergence) of smoke, fire
Detection
Eocortex Ultra
19
VIDEO ANALYTICS
(INTELLIGENT DESCRIPTION
MODULES)
Track moving objects in a camera's field of view. Alert
generation on intersecting lines and borders (one way or both
Tracking ways), entering the dedicated zone, prolonged stay in the zone,
alert search in archive; interactive archive search on intersecting
lines set by an operator
Count the number of entering and existing visitors — either
People Counting through one or several inputs; create customized reports
Count people in queues; if necessary — it notifies the operator
People Counting in
should the number of people exceed a preset limit in a given
Queue queue, allows building temporary reports
Notifies the operator should the quantity of people exceed an
Crowd Monitoring indicated limit
Face Detection Detect faces in the frame
Detect faces and compare it with person’s identification using
Face Recognition pre managed database
Heat Map Create heat maps based on traffic in different areas of the frame
Abandoned Object
Detect abandoned objects and highlights them up on the screen
Detection
Personnel Monitoring Perform remote monitoring of the staff activities at workstations
Detect camera defocusing, panning away from pre-defined view,
Sabotage Detection illumination and overlapping
Specified features may require additional licenses
1.3. Contents of Package

The latest version of Eocortex Ultra and its documentation are available
at www.eocortex.com.
Each computer with Eocortex Ultra server software installed requires the following:
either a separate USB-key or a software protection key with a corresponding license
file.
The software package with USB-key includes the following:

• Software protection USB-key;
• License file;
 CD with Eocortex Ultra software suite and documentation (optional).
Depending on the product delivery scheme the license file can be delivered in the following ways:
• On the CD with Eocortex Ultra software suite;
• On a separate medium;
• By email.
If the software protection key is selected, a customer receives only a key identifier while
purchasing a license — software and documentation are to be downloaded from eocortex.com
by the customer.
Software installation applications
Each installation package includes the basic software (with corresponding bit depth), as well as
additional components required for the operation.
Eocortex Ultra
20
 Eocortex Ultra Server — server software for a network video surveillance system used to
receive, analyze, process and archive video data from IP cameras. It is installed on a single
machine, where the data is processed and the archive is stored. Eocortex Ultra Server is a
Windows service; it is launched at computer startup and runs in the background. A computer
must be highly reliable and ensure trouble-free operation. The server requires a USB-key
and a license file (supplied) for operation or software protection key with corresponding
license file.
 Eocortex Ultra Client — network client of a video surveillance system that allows viewing
video in real time and from the archive, controlling cameras, audio and intelligent modules
by using Configurator. It is installed on the computers of operators, security chief and other
surveillance system users. Eocortex Ultra Client does not require a USB-key and a license
file for operation.
 Eocortex Ultra Standalone — software that combines the functions of a video surveillance
system server and client. It is installed on a single machine, where the data is processed,
the archive is stored and real-time video streams are viewed. Eocortex Ultra Standalone is
not a Windows service — it is separately launched software with window interface. A
computer must by highly reliable and ensure trouble-free operation. Eocortex Ultra
Standalone requires a USB-key and a license file (supplied) for operation or software
protection key with corresponding license file.
 Eocortex Ultra Configurator — software used to configure the Eocortex Ultra video
surveillance system.
 Eocortex Ultra Status Info — software used to notify a user about the current server
state.
 Eocortex System Heathcheck — application, meant to track the status of the components
of video surveillance distribution network system.
 Eocortex Ultra Player — software used for quick viewing of video files exported in the
proprietary Eocortex Ultra format (*.MCM).
 Archive local viewing and backup — software used to view and copy archived files.
 Log packing — a tool used to extract system logs related to Eocortex Ultra products and
record them in a single archive file.
 Enable/disable debug mode command — enable/disable debug mode that allows
recording more detailed information in system log files.
Eocortex Ultra
21
2. How to install, update and remove Eocortex
2.1. Guidelines for choosing and configurating hardware platform

You can calculate the minimum hardware platform requirements online on www.eocortex.com,
on the "Software for IP Cameras / Calculator" page.
While selecting the hardware platform consider, if necessary, the potential increase (near future
expansion plan) in the number of channels.
The drive subsystem must comply with the design load. It is recommended to use RAID to
increase system speed and reliability; take into account the performance in case of drive failure.
The server drive subsystem must also provide a certain reserve bandwidth (read rate) to allow
convenient archive search.
It is recommended to install two network interface controllers (NIC); configure one of them for
camera subnet and another for Eocortex Ultra Client requests. Benefits: camera isolation,
reduces network traffic in a public network.
If network storages (NAS, SAN) are used to store archives, we recommend installing an
additional NIC for these purposes.
Provide reserve computer resources in the amount of 3% of CPU load per connected client for
fast client request serving. The server drive subsystem must also provide a certain reserve
bandwidth (read rate) to allow convenient archive search.
When using the hot backup function consider that in case of failure of one of the servers, its load
is distributed on the others. For example, if there are only 2 servers, they work together and
"backup" each other; each must have a capacity sufficient to handle all video streams from all
cameras.
To achieve maximum performance disable processor power-saving technologies before
installing the OS: Cool'n'Quiet for AMD and SpeedStep or EIST for Intel (configured in BIOS,
usually in Advanced / CPU.) If you use SATA-drives, do not forget to set AHCI value for SATA
Mode (configured in BIOS, usually in Advanced / SATA; only for controllers that support this
mode.)
2.2. Guidelines for Windows settings

The computer must use one of Microsoft Windows operating systems provided in specification.
If RAM capacity is 4 GB or more, use a 64-bit operating system, as well as 64-bit

Eocortex Ultra license, since 32-bit operating systems cannot use more than 3 GB of
RAM and each process (program) can use no more than 1.3 GB of RAM.
64-bit operating systems support 32-bit Eocortex Ultra license but it should be borne in
mind that Eocortex Ultra Server and Eocortex Ultra Standalone will not be able to make
full use of CPU and RAM. Eocortex Ultra Client does not depend on the license type, so
we recommend installing the same version as your operating system.
Install all Windows updates and then turn off Auto-update.

Select the appropriate server time zone, specify the exact time in this time zone.
Guidelines on Windows settings (for Windows 7):
 Control Panel  Power Options: High Performance.
 Control Panel  User Accounts  User Account Control Settings: Never notify.
 Control Panel  Network  Web Networking  Adapter Properties: Disable IPv6(This
recommendation for earlier versions.
We recommend disabling the firewall on your computer. If the security policy does not allow
disabling the firewall, open a network port 8080 and — for camera connection — 80 (if RTSP
video stream is used — open port 554.)
Some cameras can receive control commands and transmit video streams using other
ports — in this case open the appropriate ports.
Eocortex Ultra
22
Installed anti-virus should not scan HTTP and RTSP traffic, including input video streams from
IP cameras, as this significantly reduces the system performance. Add Eocortex Ultra module
executable files to the list of trusted applications of anti-virus and firewall, as video stream
checking requires significant computing resources.
Some anti-virus software (such as NOD32) blocks video streams even when disabled,
since they "embed" their own components at the level of system drivers when installed.
Thus, to ensure correct operation and performance we recommend removing anti-virus
software from Eocortex Ultra video servers, if possible.
2.3. Installing Eocortex Ultra software from a common installer

Eocortex Ultra applications are installed from a common installer
(EocortexMainCommonUltra Installer.exe). This installer allows installation of the
following applications:
 Eocortex Ultra Server — server software for a network video surveillance system used to
receive, analyze, process and archive video data from IP cameras. It is installed on a single
machine, where the data is processed and the archive is stored. Eocortex Ultra Server is a
Windows service; it is launched at computer startup and runs in the background. A computer
must be highly reliable and ensure trouble-free operation. The server requires a USB-key
and a license file (supplied) for operation or software protection key with corresponding
license file.
 Eocortex Ultra Client — network client of a video surveillance system that allows viewing
video in real time and from the archive, controlling cameras, audio and intelligent modules
by using Configurator. It is installed on the computers of operators, security chief and other
surveillance system users. Eocortex Ultra Client does not require a USB-key and a license
file for operation.
 Eocortex Ultra Standalone — software that combines the functions of a video surveillance
system server and client. It is installed on a single machine, where the data is processed,
the archive is stored and real-time video streams are viewed. Eocortex Ultra Standalone is
not a Windows service — it is separately launched software with window interface. A
computer must by highly reliable and ensure trouble-free operation. Eocortex Ultra
Standalone requires a USB-key and a license file (supplied) for operation or software
protection key with corresponding license file.
 Eocortex System Heathcheck — application, meant to track the status of the components
of video surveillance distribution network system.
Within one installation procedure, you can install both separate applications and all included in
the installer. Eocortex Ultra Server and Eocortex Ultra Standalone are mutually exclusive
(you can install either Eocortex Ultra Server or Eocortex Ultra Standalone).
During the installation use the account that has full access rights to the local computer
on which Eocortex Ultra software is installed.
When using the multiserver configuration the version numbers of merged Eocortex
Ultra Server and/or Eocortex Ultra Standalone must match
If NAT is used to access Eocortex Ultra server via customizable network ports, specify
the external ports, i.e. ports for access from an external network. For example, if port
8080 is configured on a video server but it is displayed through port 60007 for an
external network, specify port 60007.
The problem of interaction between servers and Eocortex Ultra software located inside
the same LAN may arise since they will interact via specified external addresses. To
resolve this problem, set up SNAT so that when addressing to specific external
addresses (ports) components are connected to each other through a local network.
If you use a Eocortex Ultra USB-key, plug it into a server USB-port.
Eocortex Ultra
23
Close all Windows applications before installing Eocortex Ultra software; insert the disk with
Eocortex Ultra software suite in a CD/DVD-ROM — an installation package should run
automatically.
If it does not or the installation package was downloaded via the Internet, run the
EocortexMainCommon Ultra Installer.exe file located in the root directory of the package.
Select the installation language and click OK.
Setup wizard window will open. Follow the instructions:
Make the selection of application you want to install on the machine. Checking the option
Manually set installation path and bitness of application will allow you to define absolute
paths for each application and bit version that you may install.
Eocortex Ultra
24
When installation of the video server is finished, the application will start automatically:
Eocortex Ultra Server— as a Windows system service, Eocortex Ultra Standalone - as
a console application. At that, a root user with a blank password is created (by default) with
full rights (username and password are recommended to be changed).
When setup wizard is closed, Status Info window opens (for Eocortex Ultra Server) or
the Eocortex Ultra Standalone main window opens. When clicking the button
Configure or Install the license, Eocortex Ultra Configurator application will be
launched (after installation of the server application, you will be prompted to install the
license).
(Work with Eocortex Ultra Configurator is described in the section Eocortex Ultra
Configurator, installation and activation of the license - in the section Installing and updating
the license)
Eocortex Ultra
25
2.4. Installing Eocortex Ultra Client
Installation of Eocortex Ultra Client should be performed via the account of the user
by whom this application shall be used. If the application is to be used by several users
with different accounts, you should install the application for each of such user.
Close all Windows applications before installing Eocortex Ultra software; run the
EocortexMainCommonUltra Installer.exe file located in the installer root folder.
2.5. Updating Eocortex Ultra software

Eocortex Ultra software is updated by installing the newest version of the product "on top" of an
existing one (see Installing Eocortex Ultra software.) During the installation program files of the
previous version are removed but all settings, the archive and the license are saved. Thus, no
additional setup is required after update.
Eocortex Ultra
26
Only software with the same name and bit depth can be updated. For example, if you
previously installed Eocortex Ultra Server (32 bit), choose Eocortex Ultra Server
(32 bit) for update.
You can configure automatic update for Eocortex Ultra Client (see Client Autoupdate)
The latest versions of Eocortex Ultra software are available on the Eocortex Ultra
website in Support/Software Installation Packages, documentation — Support /
Documentation.
If you change the license but the product version and bit depth remain the same,
software update is not needed — just install a new license file or software key (see
License installation.)
2.6. Removing Eocortex Ultra software

Depending on the purpose, Eocortex Ultra software can be removed in one or two steps:
Step 1: Remove software and save the settings — only executable files and libraries are
removed; all settings, the license and the archive are saved. This procedure is used only if it is
planned to install Eocortex Ultra software with the same name and bit depth later (the same
procedure is performed automatically when you update your Eocortex Ultra software.)
Step 2: Complete removal of server products — all settings and the license are removed.
This procedure is used if it is planned to install Eocortex Ultra server software of another name
or bit depth later or completely remove it from the computer.
2.6.1. Remove software and save the settings

Open the Control Panel (Start / Control Panel.)
If the Category option is selected — change it to Large icons or Small icons. Open Programs
and Features.
Select the Eocortex Ultra product to be removed, right-click it and select Uninstall in the pop-
up menu.
2.6.2. Complete removal of Eocortex Ultra products
Complete removal of Eocortex Ultra server products can be performed only after
uninstalling the software and save the settings option was used.
Remove the Eocortex Ultra product installation folder from hard drive. The table below shows
the (default) location of software installation folders depending on bit depth of Windows and
Eocortex Ultra software:
Bit depth
Eocortex Default location of installation folder
Windows
Ultra
Eocortex Ultra Сервер
64-bit 64-bit C:\Program Files\Eocortex Server Ultra
64-bit 32-bit C:\Program Files (x86)\Eocortex Server Ultra
32-bit 32-bit C:\Program Files\Eocortex Server Ultra
Eocortex Ultra Standalone
64-bit 64-bit C:\Program Files\Eocortex Standalone Ultra
64-bit 32-bit C:\Program Files (x86)\Eocortex Standalone Ultra
32-bit 32-bit C:\Program Files\Eocortex Standalone Ultra
Eocortex Ultra
27
2.7. Installing and updating the license
Licensing of a Eocortex Ultra server requires installation of a software-key or USB-key and its
license file on the server.
To update the license of a previously activated key, activate the procedure for this key
again.
When transferring USB key to another computer, install and activate the license on
the new computer. For off-line activation, use the existing license file for this key.
Several different types of keys may be installed on the server - both multiple hardware
(USB) keys and one software key. Only one key can be activated. If you need to use
a license for another key on the server, you should run the license installation
procedure and activate that key.
To install and activate the software key, launch Eocortex Ultra Configurator
application on the computer on which the key is installed as the key installation and
activation utility collects information concerning the computer on which the utility is
launched.
It is prohibited to install more than one Eocortex Ultra software key on the server!
If you have installed another Eocortex Ultra software key on the server previously, you
should delete its certificate and restart Windows before installation.
When installing and upgrading the license, it's preferable to provide Internet
connection to the server, as the most convenient way of key activation its automatic
activation via the Internet. Generally, key installation and activation requires the
performance of the sequence of steps, offered by the wizard, which are predefined by
default.
To install, activate, or update a license, you must run the Eocortex Ultra Configurator. In the
opened authorization window, select the server, specify the account type, enter the user name
and password with configuration rights, and then click Connect.
If no license is installed and activated on the server, you will be prompted to install the license.
If accepted, the License Installation wizard will be launched.
The first window of the installation wizard depends on the existence of installed keys and their
activation status. Various installation and activation situations are described below, showing the
correct sequence of actions for every single situation and describing corresponding windows of
the installation wizard.
Eocortex Ultra
28
2.7.1. USB key activation
In order to install a USB key, it’s required to choose the corresponding variant on the Select
the installation type page and press Next.
The Select key page will appear, showing the list of keys connected to the server.
The Key ID column of the list indicates the number on a side of the USB key. If the user can’t
find the required key in the list, such key is not connected to a USB port of the server; in such
situation the user has to connect the required key to the server and press update, in a couple
of seconds the list will be updated. To continue the installation process the user has to choose
the required USB key and press Next.
The following step, i.e. key activation, depends on the availability of internet connection (if such
connection is not available, please see the USB key offline activation subsection).
Eocortex Ultra
29
If an internet connection is available, the Eocortex Ultra server will connect to a remote license
activation server and will try to activate the key in automatic mode in accordance with the licenses,
assigned to the key. The online activation of key page will be shown during the activation process.
In case of successful activation, The License has been successfully installed window will
appear. In order to exit the license installation wizard, the user has to press Finish.
In case if an error occurs during activation, the user will see the Failed to install the license
page. It’s required to finish the license installation process (press Finish), resolve the problem
and start the license installation process from the very beginning.
Eocortex Ultra
30
Possible online activation errors:

 connection with the activation server was interrupted during the activation
process; e.g. due to a connection problem, low speed of connection or due
to a problem with one of route elements
 the selected key has no assigned licenses. In such situation the user has to
contact the license supplier (seller)
2.7.1.1. USB key offline activation

If the user selects offline activation, the Offline key activation window will appear, where the
user has to select (using the Browse… button) the license file assigned to the selected USB
key, and press Next (more information about the license file can be found in the Hardware USB
key protection subsection).
In case of successful activation the Installation of license successfully completed page will
appear. Press Finish to exit the licensing wizard.
Eocortex Ultra
31
The most probable cause of the offline activation error is the inconsistency between
the license file and the USB key. License file sent by Eocortex Ultra bears a name
convention with USB key’s serial number as initial characters.
Eocortex Ultra
32
2.7.2. Software key activation
In order to install and activate a software key, the user has to obtain an activation
code, which looks like XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX, where X
can be hex digit (i.e., 0123456789abcdef). Here’s an example of the activation code:
a46a6d3e-17f6-416c-9da2-10cb4b80574e.
In order to install and activate a software key, the Eocortex Ultra Configurator has
to be launched on the server, where the Eocortex Ultra Server application is
installed. It’s not allowed to launch the Eocortex Ultra Configurator remotely to
perform the initial activation of the software key, because it may result in an incorrect
request creation, and installation of the software key can be performed with errors
(for example, when the user involves RDP in order to connect a remote desktop,
activation will be performed for a local computer, which is used by the user and not
for a remote machine).
The license software key can’t be transferred to any other computer, because it’s
linked to the computer during the activation process.
In order to install the license software key, the user has to select the corresponding menu item
on the Select the installation type page and press Next.
After pressing Next, the software key is being linked to the computer, thus it’s
going to be impossible to transfer it to any other machine. If the activation process
was launched mistakenly, the user has to press Back and close the License
installation window.
Next, the key activation code will be requested.
Eocortex Ultra
33
The next step is key activation. The program key activation process also includes two steps:
Step 1: creation and sending of the license request file.
The request file contains a unique “snapshot” of the server computer.
In order to create the request file, the user has to enter the activation code, received
from the Eocortex Ultra license supplier.
Step 2: receiving of the license file and key activation.
The license file contains information about the licenses assigned to the key. This file is
created by the activation server in automatic mode, after receiving the request file and
using the information about the previously issued activation code.
They key activation process depends on the availability of internet connection. If such connection
is not available, please see the Software key offline activation subsection.
In case of an existing internet connection, after entering the code and pressing Next, the Eocortex
Ultra server will connect to a remote license activation server and will try to perform automatic key
activation in accordance with the licenses assigned to such key.
The online activation of key page will be shown during the activation process.
In case of successful activation, a new Installation of license successfully completed

window will appear. In order to exit the licensing wizard, the user has to press Finish.
Eocortex Ultra
34
In case if an error occurs during activation, the user will see the Failed to install license page.
It’s required to finish the license installation process (press Finish), resolve the problem and
start the license installation process from the very beginning.
Possible online activation errors:

 connection with the license activation server was interrupted during the
activation process; e.g. due to a connection problem, low speed of connection
or due to a problem with one of route elements
 the selected key has no assigned licenses. In such situation the user has to
contact the license supplier (seller)
2.7.2.1. Software key offline activation

If user has chosen offline activation, Offline activation of software key window will be
opened, where you should Save the license request file to disk, and press Next.
After this step, you can close the wizard. In the course of next running you shall be
prompted to continue the installation from the step at which it was interrupted.
The created license request file (with *.McKeyRequest extension) has to be attached to an e-
mail and sent to [email protected]. An e-mail with a *.McKey license file will be sent in
response (keeping in mind that all answers are sent by the activation server in automatic mode,
waiting after sending the license request file will take minimum time).
After receiving the license file, you should continue installation from the step, at which the license
file is installed (with the extension * .McKey). License file is selected using Browse…button,
and then you should press Next.
Eocortex Ultra
35
In case of successful activation, a new installation of License successfully completed
window will appear. In order to exit the licensing wizard, the user has to press Finish.
The most probable cause of the offline activation error is the inconsistency between
the license file and the computer, which was used to create the request file (i.e.
activation on different computer).
2.7.3. License update

To update the license, open the Configurator, go to the tab 2. Servers, select a server from
the list of servers, for which you want to update license, and then click the Update license
button.
The License Installation wizard window opens, in which, depending on the license used on the
server, you shall be offered to update the software or USB key automatically. All actions are
similar to those ones, which are used when installing the license (see above).
Eocortex Ultra
36
3. Eocortex Ultra Configurator
The Eocortex Ultra video surveillance system is configured using the Eocortex Ultra
Configurator application: license management; parameters of the connected cameras;
functions, scripts, schedules and intelligent modules, used for cameras; parameters of video
servers; archive and backup settings; user authorities; plans of objects; screen profiles;
categories of archive bookmarks and other settings.
It is recommended to use a display with a resolution of at least 1024 × 768 in the

course of working with Eocortex Ultra Configurator, as the displays with smaller
resolution may cause problems with the displaying of the application.
Below is a list of procedures that must be performed after installing Eocortex Ultra Server (or
Eocortex Ultra Standalone) to start full-scale operation:
 Start Eocortex Ultra Configurator, enter IP-address and server network port (default
— 8080), user name and password (default — root with no password.)
On first launch you will be prompted to install a license.
 Configure server parameters.

 Set up video surveillance cameras (connection, archiving settings, intelligent functions,
etc.).
 If necessary, use Eocortex Ultra Configurator to configure system user accounts.
 Apply the configuration and close Eocortex Ultra Configurator.
 Install and run Eocortex Ultra Client, if necessary — adjust display settings on a client
workstation.
3.1. Launching the Eocortex Ultra Configurator application

Eocortex Ultra Configurator is included in all Eocortex Ultra video surveillance system
packages.
Launch video surveillance servers before starting the configurator.
For server configuration use Eocortex Ultra Configurator the same version as
Eocortex Ultra Server.
System configuration is stored on the Main Server. When the configuration is changed,
the Configurator automatically saves the configuration on the Main Server, and then
sends it to all available slave servers. Therefore, for the prevention of system conflicts,
you must connect the configurator either directly to the Main Server, or to the server
that currently has access to the Main Server.
There are several ways to run the application:
Eocortex Ultra
37
Method 1. Launch using the Start Menu or the desktop shortcut.
Go to Start / All Programs / Eocortex Ultra Server (or Client) / Eocortex Ultra
Configurator or run the program using the Eocortex Ultra Configurator shortcut on the
desktop. Enter address of the attached server in the opened authorization window (or select the
server from the drop-down list by clicking the button), specify the account type, enter
the user name and password with configuration rights, and then click Connect.
For Active Directory accounts, username shall be specified as:

username@domain; where domain is the domain name, username is the
username in the domain.
When you first install Eocortex Ultra Server, a default root user with no password
and full rights are created in the system (account type — Eocortex.) We recommend
changing this username and password when setting up user rights. Client connection
default port — 8080. If necessary, it can be changed in Eocortex Ultra
Configurator.
If you merge multiple servers into a single video surveillance system the configuration
becomes common to all servers, so connection to any of the system server is
considered as connection to the system.
When you connect to a server, you may use any one of its corresponding IP-
addresses. For example, if a server has two NICs — one with "internal" IP-address
for local network, another with "external" IP-address for the Internet, you can use
the "internal" IP-address when connecting through the local network, and the
"external" one when connecting via the Internet. If you start the configurator directly
on the server, you can use "local" IP-address 127.0.0.1.
Eocortex Ultra
38
Upon successful login the Eocortex Ultra Configurator Main window will open.
Method 2. Launch from the Eocortex Ultra Client application.

In the Control Panel of Eocortex Ultra Client click Settings and select Configurator.
Enter address of the attached server in the opened authorization window (or select the server
from the drop-down list by clicking the button), specify the account type, enter the user
name and password with configuration rights, and then click Connect.
Eocortex Ultra
39
Method 3. Launch from the Status Info window or from the Eocortex Ultra
Standalone initial window.
If you use Eocortex Ultra Server, select If you use Eocortex Ultra Standalone, select
Configurator in the Status Info window. Configurator in the initial window.
Specify the account type, enter the user name and password with configuration rights, and then
click Connect.
Eocortex Ultra
40
3.2. Applying settings and controlling configuration
After making any changes to the configuration make sure to apply the settings — only then the
new settings will take effect.
If you try to exit Eocortex Ultra Configurator without applying the changes a
warning window will appear.
Select No to go back and apply the settings, Yes — to exit without saving.
To apply the settings use the page that opens when clicking on the left part of the configurator
6. Apply settings.
To apply the settings, click Apply.
In case of incorrect configuration of modules or simultaneous usage of incompatible

modules on one channel, the Apply button is not active and the Configuration
checking results list contains the appropriate warning.
You can also use the controls located on this page to save settings to a separate file, check the
current state of servers and get a list of configurations of all channels.
Eocortex Ultra
41
To check the current status of servers, click Server check — the following window displays the
current status of each server in the system.
To get a list of configurations of all channels in the system settings, select Channel list -
the following window displays the configuration of each channel in the system.
To export the channel list to a CSV or XPS file, click Export...
Eocortex Ultra
42
3.3. Server settings
Server settings define which servers are connected to the system, network settings of these
servers, archive placement parameters on server hard drives and a number of other parameters.
To open the server settings page, select 2. Servers in the left panel.
This page contains several groups of settings:

Connected servers
Distribution of channels by servers
Multicast channels
Eocortex Ultra
43
3.3.1. Connected servers
This section of settings manages the composition of the multi-server system, as well as
configuration of the individual servers, including the licenses update.
List of the Connected Servers shows all the servers, included in the video surveillance system.
icon indicates the Main Server, icon indicate the Slave Servers.
Server renaming is performed by double clicking on its name; when the name is changed,
press Enter.
The following operations are available in this server configuration section:
Adding a server to the system
Configuring the server
Troubleshoot access to the main server
Server recovery
Set as main server
Disconnecting the server from the system
Assigning the server address
Server port assignment
Centralized update of server applications
Server diagnostics
Update the server license
Replication server settings
Eocortex Ultra
44
3.3.1.1. Server addition to the system
For the addition of the server to CCTV system, click the Add Server button in the configurator
on the 2. Servers tab. Enter the address of the server to be attached in the opened window,
then click the Next button.
An authorization window shall be opened, in which you should enter the name and password of
the user who has the rights to configure the to be attached server, and then click OK.
When the operation is completed, a message will be displayed concerning the result, and then
the configurator will be restarted.
Eocortex Ultra
45
3.3.1.2. Server setting
For the setting of the server, select the server in the Connected Servers list at the
2. Servers tab, and then click the Configure button. Warning window will be opened, then, if
approved, server settings window will be opened.
The server settings window contains several sections, which combine sections of related settings.
In order for the changes to take effect, you should Apply server settings.
Description of each of the sections is specified below:
Selected server License parameters
Archive location settings
Network server settings
Connecting Mobile Devices
Additional settings
Client auto-update settings
Server information
Eocortex Ultra
46
3.3.1.2.1. Selected server License parameters
The following information concerning the license parameters is displayed in this settings group:
Product type —ST Ultra;
IP camera licenses — number of IP cameras (channels), which may be connected to the
server (in case of usage of this server as the main server for cameras).
Audio stream processing modules— number of channels, processing the sound.
PTZ camera control modules — number of channels where PTZ cameras may be controlled.
64-bit support— indicates the use of the license for the 64-bit server application.
Video recorder channels— number of channels, which may be used as channels of the video
recorder. In case of presence of the video recorder channels, the number of the channels to
which individual cameras may be connected, is reduced by a given amount. At the same time,
"regular" channels may be used for the connection of the video recorder channels.
For example, a license is installed on the server with the following parameters: Licenses for IP-
cameras - 10; Number of video recorder channels is 4. In this case, no more than 6 separate
IP-cameras and 4 channels of the video recorder may be connected to the server; Or 2 separate
IP-cameras and 8 channels of the video recorder, etc.
Reserved channels — number of the channels of other servers which may be backed up on
this server. Number of the licenses for the reserved channels does not depend on the number
of licenses for IP cameras.
For example, the situation is allowed when you can connect to the server no more than one main
channel and 10 backup channels from the other servers.
Language — valid application language. For multilanguage license, the value of this parameter
is MULTI.
Besides all the intelligent modules, implemented in the application, are listed with specification
of the number of channels, where each module is allowed to be used.
3.3.1.2.2. Archive location settings
The following archive placement options are set in this section of settings:
Drive — is the logical name of the disk.
Eocortex Ultra
47
Disk mode — to specify how the disc will be used. The following options are available:
Option Main or backup Archive Database of events
Not used — — —
Archive only main yes —
Archive + database main yes yes
Backup archive backup yes —
main — for archive
Backup archive + database yes yes
backup — for database
Duplicate
Duplicate Archive yes yes
archive and database
Size (MB)— total disk size.
Free space (MB)— remaining free space at the disk.
Min. Free space (MB)— minimum free disk space, which shall be left when writing the archive.
To set the value of this parameter, you should double-click on the current value, enter a new
value and press Enter.
Max. archive size (MB)— maximum size of the archive. To set the value of this parameter,
you should double-click on the current value, enter a new value and press Enter.
Disc type— information concerning the type of disc: Local (HDD) or Network.
When the server is started for the first time, default server settings are automatically
created. At the same time, C:\ drive is attached to the archive. In the course of initial
setting, it is recommended to assign other disks to the archive, as placement of the
archive at the same physical disk, where Windows operating system is installed, may
cause the performance degradation or system crashes.
It is not recommended to host a database on the network drives.
The archive is stored on the server with the indication of the World Coordinated
Time (UTC). In this case, the client application displays the local time (including the
time zone) of the device from which the archive is viewed.
Example:
On the server with the time zone settings (UTC + 03: 00) Tallinn a fragment of the
archive from 12:00 to 12:05 Tallinn time is recorded.
If you view this fragment in the Eocortex Ultra Client running directly on the server,
it will be displayed a fragment from 12:00 to 12:05.
If you view a fragment from the computer with the time zone settings (UTC + 08:
00) Singapore— the fragment time will be from 17:00 to 17:05.
If you view a fragment from the computer with the time zone settings (UTC + 01:
00) Paris— the fragment time will be from 10:00 to 10:05.
Eocortex Ultra
48
Information concerning the archive:

The archive of each server stores video records of only those cameras, which are
attached to this server.
The archive has a ring structure. When all the place, allocated for archive is used, new
archival files begin to replace the oldest ones, trying to observe the limits of the
archive, set for each camera.
In case of usage of multiple discs, video archive is recorded simultaneously on all
available discs. When one of the disks becomes unavailable, recording of new data on
it is interrupted and redistributed to available disks. Similarly, if a previously
unavailable disk becomes available, recording of new data at it shall be resumed.
One or more disks can be assigned as backup ones. New data will be recorded on the
backup discs only when all the main disks are unavailable; At the same time, once
one of the main disks becomes available again, recording on the backup disks ceases.
One or more disks can be assigned as duplicates. New data is recorded on the On
duplicating discs in parallel with the recording on the main or backup discs.
The archive is located in the folder EocortexArchive, located in the root of each disk,
used for the storage of the archive.
3.3.1.2.3. Network server settings
The following parameters are set and displayed in this section of settings:
SSL server port— shows the port number that the SSL server connects to this server.
Open the Eocortex Ultra Server port automatically in Windows Firewall — allows
Eocortex Ultra Server automatic opening of the port in the Windows Firewall for external
incoming connections.
Allow UPnP Eocortex Ultra Server identification—allows network agents to find this server
in the network using UPnP.
Accept RTSP connections (tobroadcasts H.264)— allows to receive video stream and
service information by direct requests to the server via RTSP protocol.
RTSP/TCP port— the port, through which the client connections to the server shall be made
via the RTSP protocol.
Allow Mjpeg broadcasting via RTSP—allows MJPEG broadcasting via RTSP.
As RTSP protocol supports only MJPEG frames, encoded in the Baseline coding mode,
it is necessary to transcode them for the transmission of video streams, coded in other
modes; Which, in its turn, shall increase the load at the server. In addition, when
transcoding MJPEG, frame rate may be reduced (in comparison with the frame rate,
transmitted directly by the camera).
Allow multicast-broadcast on server —allows multicast-broadcast from the server for those
channels, which have the following option enabled. If more than one network adapter is installed
on the computer, then when this option is enabled, you may select the adapter in the drop-down
list, which shall be used for multicast-broadcasting.
Eocortex Ultra
49
3.3.1.2.4. Connection of the Mobile Devices
Service of video streams broadcasting to mobile devices and web clients is activated and
configured in this section of settings. This service is built into the Eocortex Ultra Server. To
enable the service, check the option ConnectingMobile Devices.
This service is also used for the arrangement of broadcasting to the site.
By clicking the Advanced Settings button, the advanced settings window shall be opened.
The following settings are available in the Advanced settings window:

Mode settings depending on the resolution of the mobile device or web browser, as well as on
the display mode:
Full screen settings— used for full screen mode.
Multi-screen settings—used for multi-screen mode.
Multi-screen settings (low-resolution)—used for low-resolution multi-screen mode.
Eocortex Ultra
50
For each mode, you may specify the following:
Resolution, which will be broadcast by default for each channel.
Transfer only anchor frames for H.264/MPEG-4— only the anchor frames will be transferred
for the specified video formats; This setting allows to reduce the amount of information,
transferred in networks with limited bandwidth.
Enable video transfer speed limitation— frequency of the transmitted frames will be limited
by the specified value; This setting allows to reduce the amount of information, transferred in
networks with limited bandwidth.
Other settings:
Mobile device server network port — allows to configure, via which port the connection to
the video streaming service for mobile devices will be available.
Connecting to a Mobile Devices server in proxy mode — enables broadcasting in the proxy
mode. When proxy mode is enabled in multi-server configurations, streaming of video streams
from all the servers to mobile devices, connected to this server, will be carried out via this server.
If the proxy mode is disabled in multi-server configurations, the mobile device will be
automatically connected to the servers, to which the requested cameras are assigned.
Limit CPU usage time consumption — allows to limit the consumption of the mobile
connection service processor time.
Allow the sending of push notifications — provides the ability to send various Push
notifications from the server to the mobile devices.
3.3.1.2.5. Additional settings
In this section of settings there is a button Network drives mount/unmount, when you click
on that, the corresponding window will open.
To mount a network drive, you should select the drive letter, to which you would like to add the
network drive, specify the path to the network drive, as well as the name and password of the
user, who has access to the network drive for reading, writing, and creating folders and files,
and then click Connect network drive and OK.
After clicking OK button, the server will be restarted and all the network drives, specified in the
list, will be added to the list of disks, displayed in the Archive location settings. Then network
drives can be configured in the same way as local drives.
For unmounting of the network drive, select the drive, which shall be unmounted from the list,
and then click Disconnect network drive and OK.
After clicking OK button, the server will be restarted and all network drives, not listed in the list,
will be excluded from the list of disks, displayed in the Archive location settings.
Eocortex Ultra
51
3.3.1.2.6. Client auto-update settings
Mechanism for automatic updating of the connected clients to the server version is configured
in this section of settings. This mechanism is built into the Eocortex Ultra Server.
To enable auto-update, check the option Allow client auto update and then apply server
settings. After restarting of the server, when clients connect to it, the following happens: if the
version of Eocortex Ultra Client does not coincide with the version of Eocortex Ultra Server
(or Eocortex Ultra Standalone), the client will be automatically updated to the server version.
3.3.1.2.7. Server information
This section of settings displays information concerning the current state of the server.
3.3.1.3. Troubleshooting of access to the main server

There are situations when the connection between the Main server and slave servers is lost. In
configurator, such servers will be displayed with a red indicator .
If you plan to disconnect the Main server, it is recommended that you first assign
the main one to the slave one by the server. After enabling, the original server may
be re-assigned as the primary server.
The typical causes of the loss of communication with the Main server are described below and
the recommended actions are as follows:
1. The Main server became unavailable (due to the failure, unplanned shutdown, disconnection
of the network connection, etc.). In this case, all slave servers will lose connection with the
Main server, but will continue to function with the last common configuration. In this case,
when the configurator is connected to any of the remaining servers, it will be suggested to
reassign the Main server (see 1.2).
1.1. If the Main server is scheduled to be returned to the system after a certain time and no
configuration is planned to be changed during this time, then it is recommended not to
perform any additional actions, because after turning on the Main server the connection
between it and the slave servers will be restored within 1 minute.
1.2 If the Main server is permanently deleted from the system or if it is required to configure
the system during its absence, it is recommended to assign one of the remaining servers as
the Main server. For this purpose you should connect the configurator to the slave server,
which will be assigned as the master one. In the opened window, select Assign the main
server ... and click Next, then follow the further instructions (it is recommended to perform
all the default actions by clicking the Next, Yes and OK" buttons).
Eocortex Ultra
52
After the assignment of one of the servers as the Main server, other servers will be
automatically notified of the change.
If you do not plan to use the previously Main server in this system, you should disconnect
it from the system.
If after reassignment of the Main server some of the functioning servers is marked with a
red indicator, it is necessary to recover these servers.
1.3. If, after the reassignment of Main server, the access to the previous Main server has been
recovered (for example, it was recovered after the failure), a collision takes place: the
system has two main servers. In this case, we recommend you to recover the servers that
are marked with a red indicator. The following should be taken into consideration:
 If the previous server is required to be used as a Main server, connect the configurator
to this server, and then perform a recovery operation for each of the slave servers.
 If newly assigned server is required to be left as the main one, connect the configurator
either to the "new" Main server, or to any of the slave servers, and then perform the
recovery operation for the "previous" Main server.
2. If the Main server is not available for the slave server for some reason (for example, the
slave server was turned off when the core server was reassigned), the slave server should be
recovered.
3.3.1.4. Server recovery

Recovery operation is performed when the Main server is not available for the slave server for
some reason. In the configurator, on the 2. Servers tab in the Connected Servers list, a red
indicator will be displayed on the slave server icon and the Server Status line shall specify
that the server has not been connected to the main server for a long time. In this case, you
should select the server in the list and click the Restore button: an information window will be
opened with the message, specifying that if there is a connection between the servers, the status
of this server will be changed after some time.
Red indicator on the server icon also appears in cases when the server is
unavailable from the configurator from this workstation (for example, the server is
turned off or located in an inaccessible subnet). For such servers, the Server Status
line will indicate that the server is unavailable. In this case, make sure that the server
is up and running and has access to the Main server (for example, by connection to
such a server by the configurator directly on the server itself). If necessary, you should
recover the information about the location of the Main server.
Eocortex Ultra
53
3.3.1.5. Setting as main server
If you would like to assign another server in the system as the main one, select this server in
the Connected Servers list in the configurator on the 2. Servers tab and click the Set as main
server button. A warning window will be opened: when you click Yes, the server will be
reassigned, and The configurator will be restarted.
3.3.1.6. Disconnection of the server from the system

To disconnect the server from the system, select this server in the Connected Servers list in
the configurator on the 2. Servers tab and click the Disconnect server button. The warning
windows for restarting of the configurator and disconnecting of the server will be opened in
successively: if you click Yes, the server will be disconnected. When the operation is completed,
a message will be displayed concerning the result, after which the configurator will be restarted.
3.3.1.7. Assignment of the server address

To change the server address, select this server in the Connected Servers list in the
configurator on the 2. Servers tab and click the Enter address button, enter new address in
the opened window and click Next. When the operation is completed, a message will be
displayed concerning the result, after which the configurator will be restarted.
3.3.1.8. Server port assignment

To change the server port, select this server in the Connected Servers list in the configurator
on the 2. Servers tab and click the Enter port number button, enter new port number in the
opened window and click Next. When the operation is completed, a message will be displayed
concerning the result, after which the configurator will be restarted.
3.3.1.9. Centralized update of the server applications

For a centralized upgrade of Eocortex Ultra server applications, select this server in the
Connected Servers list in the configurator on the 2. Servers tab and click the Update еру
server button.
The initial installation of server applications Eocortex Ultra is performed from the
common installer.
Centralized Server Update window will be opened.
Eocortex Ultra
54
If the package is not available, or the service pack version does not match to the required one,
download the package by clicking on the following button (with The package is empty or with
the version number of the package). In the opened window, select the file
EocortexMainCommon Installer.exe on the disk of the required version.
The latest version of Eocortex Ultra is available at www.eocortex.com.
Eocortex Ultra server applications may be updated not only to newer ones, but also
to older ones, as compared to the current version, but only if the first two numbers of
the version number are the same.
For example, if the current version installed on the server is 2.4.20, then the update
to version 2.4.10 is allowed, but it is not allowed - to 2.3.15. At the same time, if the
version 2.3.15 exists in the chain of previous updates, you may roll back to this version
successively.
Then you should wait for the package to load.
At the end of the loading, the button will be indicated with the version of the current service
package.
If the downloaded file is not a service package, an error message shall be appeared and the file
shall not be loaded.
Before the update of Eocortex Ultra Server version, you must download the service package
to this server. To download the service package to the server, select this server in the
Centralized servers update window and click the Download X.X.XX button (X.X.XX—
downloadable version number).
To install the version, downloaded to the server, click the Install X.X.XX button.
Beside the updating, you can ‘roll back’ the server application to the previous version by clicking
Roll to X.X.XX button. In this case, the server configuration also returns to the state, existed
at the time of the update. Thus, if changes were made to the server configuration after the
update, after the rollback, these changes will be canceled.
If the upgrading fails, an automatic rollback to the state before the update will be performed.
Eocortex Ultra
55
As the backup copies of server configurations and installation packages are stored on
the server's system disk, step-by-step sequential rollback of several updates is possible.
3.3.1.10. Server diagnostics

For the performance of the diagnostics of the server, select this server in the Connected
Servers list in the configurator on the 2. Servers tab and click the Diagnostics button — the
server diagnostics window will be opened.
The window displays a list of identified problems — both current and already solved.
By clicking on the line with the problem you can get its detailed description and recommendations
on its correction.
To remove a row from the list, press the button on the right side of the line.
3.3.1.11. Update the server license

To update the server license, you need to select this server in the Connected Servers list in
the configurator on the 2. Servers tab and click the Update license button — the license
installation window will be opened.
Eocortex Ultra
56
3.3.1.12. Replication server settings

You can assign the role of Replication servers to one or more servers in the system.
Replication server is a server that stores backup copies of archives from the other servers in
the system.
If the server is used for replication, it can’t be assigned as a main or backup channel
server.
Replication server requires USB or software key and the license for at least one channel
(of the same type as on the other servers).
To configure the replication server, select this server in the Connected Servers list in
configurator on the 2. Servers tab and check Replication server checkbox.
Next, in the Replication settings area below, set the replication depth limits, schedule, and
select the channels which shall be replicated to this server. For application of the specified
settings, you should apply the configuration.
Eocortex Ultra
57
In the replication server settings window, Replication settings group appears, which displays
the current replication status. There you can manually start or stop the replication process.
3.3.2. Distribution of channels by servers

Channels are distributed between the servers of the multi-server system in this group of settings,
If only one server is used in the system, Server channels distribution settings are
not displayed, as in this case all channels are automatically bound to a single server.
In a multi-server system, each channel may be attached to two servers. One server
in this case will be the main one, and the other will be the backup one. If the main
server fails, channel processing (connection to the camera, recording of the archive,
broadcasting of live video to clients) will be performed by the backup server. Thus,
the reliability of the video surveillance system is improved.
To use the channel backup, you need a separate license, which specifies the maximum
number of backup channels, which may be bound to this server.
Number of licenses for the channels with enabled backup does not depend on the
number of licenses for IP cameras. Thus, a situation is possible when, for example, no
more than one main channel and 10 backup channels from the other servers may be
connected to the server.
For the assignment of the channels to the server, select this server in the Connected Servers
list in configurator on the 2. Servers tab and. Next, in the Server channels distribution
settings" area, select Setting type: either Assert main Servers to channels or Assert
reserved Servers to channels. Then, using the button , move the required channels from
All system channels list to Server channels list. To save the changes, apply the configuration.
Automatic distribution of the channels to the servers is also available. For this purpose,
click the Auto distribution button.
Eocortex Ultra
58
Function of the automatic distribution of backup channels to the servers does not take
into account number of licenses for the backup channels. Thus, a situation is possible
when the backup channels, automatically tied to the serve, may exceed the number
of corresponding licenses. In this case, in the course of application of the configuration,
a warning appears and application of the configuration is not available.
Procedure for deallocation of the channels from the server is the same as the assignment
procedure. The channels are transferred from the Server channels list to All system channels
list.
Besides operation of deallocation of all the channels from the servers is available: for
this purpose, press Cancel button.
Backup of channels may be performed in two modes: standard and fast one. In case of standard
backup, time interval between server failure and the activation of the backup of its channels on
the other servers may reach 10 minutes. Fast backup is activated within 10 seconds from the
moment of loss of communication between the main server and the backup server. To enable
fast backup, select the server in the list of Connected Servers and check Enable Server
Backup (Hot Swap) checkbox below: in this case, after application of the configuration, fast
backup will be enabled for the main channels attached to this server.
In the systems in which periodic (including short-term) cuttings are possible in

communication between the servers, activation of a fast backup may cause false
activation of the channel backup.
3.3.3. Eocortex System Healthcheck configuration
The Eocortex System Healthcheck subsystem monitors the fail-safety and performance of
the components of the video surveillance system Eocortex (see Eocortex System Healthcheck).
3.3.4. Multicast channels

In this area of settings for the marked channels, multicast-broadcast from the server is turned on.
Eocortex Ultra
59
3.4. Camera settings
To open the camera settings page, select 1. Cameras. The channel settings tab will open on
the right and the channel list on the left.
Instead of the term CameraEocortex Ultrasystem uses a broader concept of Channel

because, in addition to cameras, video server and DVR channel may also be connected
to the system.
The hierarchical form of the channel list is easy to navigate, as it allows grouping
channels on basis of physical location of their respective cameras. Channels are
bound to security objects — grouping elements (for example, Building 1 or Corridor
of the 2nd floor.) Safety objects can also be bound to other security objects, which
allow creating a hierarchical structure of any nesting.
To add a security object, click .

To add a security object bound to another security object, select the object to which you
want to bind the new security object and click .
To add a channel, click .

To create a channel inside the security object, pre-select the object and then add the
channel.
To change the name of a channel or security object, double-click it or press F2; then enter the
new name and press Enter.
To delete a security object or a channel, select it and Click .
Eocortex Ultra
60
Features available to simplify channel hierarchy:

 drag security objects and channels from one security object to another using the
mouse;
 copy channels and security objects by holdingCtrl and dragging;
 move channels up and down with the arrow keys on the keyboard, while pressing
Ctrl;
 move and copy channels using the clipboard via the context menu or standard
keyboard shortcuts:
Ctrl+C — copy, Сtrl+X — cut, Ctrl+V — paste.
To save settings for all channels on disk, click .
To load settings for all channels from disk, click .
If you load channel settings from disk, all current channel settings are deleted and
replaced with the loaded ones. If you need to add settings from file to the existing ones,
save and load single security objects or channels via the context menu, as described
below.
All the above stepscan be performed from the context menu of channels and safety objects:
to do this, select a security object or a channel and then right-click it to open the context menu.
Besides, context menu commands provide additional options: save to disk and load from disk
the configuration of a single security object or channel.
To save the configuration of a single security object or channel to disk, select the security
object you want to merge with a previously saved object or channel, right-click it and select
Save.
To load the configuration of a single security object or channel from disk, select the
security object or channel, right-click it and select Save.
These procedures can be useful if it is not necessary to save and load the whole
configuration (for example, when merging servers — to configure channels of the
added server.)
To view video from a channel in browser, select a security object or channel, right-click to
open the context menu and select Open in browser.
Eocortex Ultra
61
To configure a specific channel, select it in the hierarchical list. Channel settings will be
displayed on the right:
3.4.1. Camera auto search and connection

To automatically search for cameras in a local network and add them to the configuration:
1. Click .
2. In the auto search window that opens, check the cameras you want to add.
3. Click Add devices.

4. Click Close to return to the main window of Configurator.
Eocortex Ultra
62
Not all cameras support features that allow users to automatically find them in a local
network.
After a camera has been automatically added do not forget to manually enter camera
administrator login and password and select the video format in data stream settings.
Some cameras are assigned with wrong manufacturers or models after automatic
search — in this case you may need to manually select the appropriate manufacturer
or model afterwards.
Configure addresses opens the camera IP-address settings window. You can change
the IP-address using Eocortex Ultra Configurator without opening the camera web
interface (this feature is currently available only for AXIS cameras.)
Auto configuration option allows you to automate the process of configuring channels if
your devices support ONVIF standard (preferably ONVIF Profile S.) For correct operation
of this function we recommend to disable ONVIF authorization on a device, if possible.
Auto configuration via ONVIF:
 if two channels are configured on a camera, the Use two channels option is
enabled;
 if a camera supports PTZ, the PTZ Camera option is enabled;
 if a camera supports audio reception, the Sound recording option is enabled
3.4.2. Channel connection settings

Channel connection settings are configured in the corresponding block.
Enter the IP-address or URL of the device that will receive video data (prefix http:// not
required.) In some cases, you may need to specify the device control/data port (for example,
192.168.1.55:8000).
If the camera is connected via IPv6, select Connect via IPv6.
Eocortex Ultra
63
To set ports other than the default; click Set network ports...; in the window that opens,
uncheck By default and set the required ports; click Save.
To set the manufacturer and model of the device that will receive video data, use the drop-
down lists for Brand and Device model.
If this device requires username and password, fill in the appropriate fields.
To enable sound recording from the camera, check Sound ON.
Not all models are supported
To enable sound transmission from the camera, check Sound transmission. To test sound
transmission, click Test and use the microphone connected to the computer. To select a
particular sound device (driver) used on this computer, click .

To enable PTZ camera control, select PTZ Camera.
To enable recording signals from camera inputs and sending signals to camera outputs,
check Event processing (I/O.)
Eocortex Ultra
64
To test the recording of signals from inputs and sending to outputs, click to the right
of the Event processing (I/O) field. The Ports I/O testing window will open: input signals
are marked with related green indicators on the Inputs line; to send output signals, click the
appropriate indicator in the Outputs line. By default, 8 input and output indicators are displayed;
to display more inputs or outputs, click located to the right.
Check Connect via server, if there is no direct network access to cameras from client
workstations. In this case, video data will be broadcast through the video surveillance system
server.
Some cameras have a limit on the number of concurrent connections. A number of

cameras reduce the frame rate if there are multiple simultaneous connections. Thus,
connection via the server allows you to provide only one connection to the camera for
any number of client workstations.
Check Narrow bandwidth channel, if you use a low bandwidth network. This setting allows
you to increase the camera signal time-out.
Check Disable channel, if you need to temporarily disable the channel.
3.4.2.1. Connecting video servers

Check Video server, if the source of video data is not a camera, but a video server or a DVR.
Enter the channel number in the appropriate field.
Numbering for different models starts with 0 or 1.
Eocortex Ultra
65
3.4.2.2. Connecting DVRs
For some DVRs the Video Recorder field is displayed instead of Video server. In this case you
can view the archive located on a DVR — select Use Video Recorder archive to enable this
function.
If you select Synchronize archive, then the archive for the periods of time when there was no
connection with a DVR or a server was idle will be downloaded to Eocortex Ultra server.
Some models of DVRs have the NVR license mode available. If you check this option, all
additional intelligence analysis modules and functions on this channel will be disabled.
3.4.2.3. Configuring memory card access parameters

The interaction settings for the archive on a memory card are placed in Channel connection
settings block.
To access the memory card, enable Use archive on memory card.

To synchronize the memory card with the archive on the server, enable Synchronize with main
archive. If you enable this function, then the archive for the periods of time when there was no
connection with a DVR will be downloaded to Eocortex Ultra server, if server is found to be idle.
Archive (or its part) for the required period may be unavailable on the camera's memory
card — for example, in the absence of movement, if a motion detector camera is used.
In this case the archive (or its part) on the server will remain empty.
Eocortex Ultra
66
3.4.2.4. Connecting panoramic cameras
Some models of panoramic cameras have the Panoramic camera option.
In this case you can use the Mode drop-down list to select different display modes available for
this model.
Individual modes are provided for each manufacturer. For example, for Axis: Zone
display, Overview, Panorama, Double Panorama, Quad View; only one mode is
available for Arecont Vision — Zone display, therefore the Mode drop-down list is
inactive.
If in the Device model field you select an option that relates not to an individual camera
model but to a model line, the Panoramic camera option will be available if at least
one model of the selected model line supports panoramic camera features — enable this
option only if the connected camera is indeed panoramic.
Eocortex Ultra
67
3.4.3. Configuring data streams
Channel data stream settings are configured in the corresponding block.
Eocortex Ultra
68
To set the data stream format to be used for the selected channel, select an option from the
Video format drop-down list.
To check the connection parameters, click Test. In the absence of errors, the video from the
configured channel will be displayed.
Test mode is enabled by default when you select a channel in the channel list.
Video image in the test section will only appear if the tested camera is accessible from
the computer with Configurator running. Thus, the situation may occur (for example,
when cameras are located on one subnet and Configurator is running on a remote
computer in another subnet) when the test image is not displayed but in fact the
server receives and processes the video stream correctly. In this case, to check the
correct connection of the channel, apply the configuration first, then run Eocortex
Ultra Client on this computer and select the required channel in the main window —
if the connection is correct, then video image from this camera will appear.
If the channel has not been tested and you select another channel or switch to another
tab Configurator will display a warning window. You can test the channel (click Yes)
or refuse to do it (click No.) If you want this window to no longer appear in the current
session, select Do not show again.
To abort the test connection, click Abort.

To view the camera connection event log, click Journal.
To view troubleshooting when connecting to the camera, click Help.
To change the volume level, move the slider to the desired position.
To specify additional data stream settings, click Additional settings beneath the video
format selection field — a data stream additional settings window will open.
The options available in Additional settings may differ depending on a camera model.
To set resolution, frame rate and compression level, select the desired values in the
appropriate fields. To use camera parameters for these values, check Use camera settings.
A limited number of camera models can be configured via Eocortex.
Eocortex Ultra
69
Please set data streams for all Axis cameras in Eocortex, since their own camera settings
may disrupt stream parameters.
To rotate the image from the camera, select the desired rotation type in the Rotate stream
field.
To specify custom connection parameters, type them in the Additional connection
parameters field. This option is rarely used with a limited number of devices.
To use an alternative decoder H.264/MPEG4 or decode H.264 on video card, check the
appropriate options. H.264 decoding on video card is used only to display video in Eocortex Ultra
Client. If this option is selected, Eocortex Ultra Client will decode this channel in H.264 on video
card; otherwiseEocortex Ultra Client will use CPU resources for decoding.
Use an alternative decoder H.264/MPEG-4 if camera image is not received, not

displayed or has artifacts.
Not all video cards can correctly handle H.264 streams with Use H.264 decoding on
video card selected.
3.4.3.1. Using two streams

Most modern IP cameras support two or more streams simultaneously. The use of two streams
allows recording high quality frames in the archive and displaying low quality frames in the client,
which can significantly reduce the equipment load.
If two streams are used Eocortex Ultra records the main stream to the archive by default.
If you want to use two streams, enable the Use two streams option.
When two streams are used, select the video format and, if necessary, configure additional
settings for each of the streams.
Eocortex Ultra
70
3.4.4. Archiving settings
Archiving of the selected channel is configured in the corresponding block.
To enable the recording of video to the archive, select Archiving.

To enable the recording of audio to the archive, select Sound recording.
To enable sound recording, select the Sound on option in the Channel connection
settings section.
To set the archive size for a camera, specify the required values in the fields Store an archive
not less than: days, hours (minimum size) and Store an archive not more than: days,
hours (maximum size.) Consider that if there is no free space left, the system will delete the
oldest records with a size more than the minimum for this channel.
In general, the system analyzes minimum and maximum sizes selected for each camera bound
to a server and tries to meet these limits. If it is impossible, then the oldest records for all
cameras will be deleted to free drive space.
If two streams are selected, you can choose which of the streams is to be recorded in the archive
in the Select recording stream field.
To select the recording mode, select the required field:
 Always on — permanent archiving.
 With detector + manual — archiving is conducted only when motion is detected in the
frame (if sound detector is on — when sound level is exceeded.) In addition, the operator
may enable/disable permanent archiving.
 Manual only — archiving is enabled/disabled only by the operator.
 Scheduled — allows flexible configuration of recording modes schedule.
To set a recording speed limit, select Enable recording speed limit and set the required
value in the Record speed field.
Record speed limit is only valid for the MJPEG codec. MPEG-4 and H.264 have the
Archive reference frames only option instead of this.
Recording speed limit affects the quality of archive playback and archive volume: video stream
played from the frame-skipped recording would be less smooth, thus saving disk
space.Sometimes there is a need to turn on recording in the original quality only at certain times
or as in a response to a certain event, while keeping the rest of video recording frame-skipped,
thus saving the disk space. In this case, one needs to configure Scheduled tasks or Scenarios
(response to system events), using Disable frame skipping when recording to the archive action.
The Re-recording parameter specifies the time interval during which the archiving must be
conducted before the occurrence of an event of motion detection and sound level exceeds.
Eocortex Ultra
71
The Post-recording parameter specifies the time interval during which the archiving must be
conducted after an event of motion detection and sound level exceed.
To schedule recording modes, select Scheduled and click to the right. The archiving
schedule window will open:vertical — days of the week, horizontal — time intervals.
Then choose one of the modes by clicking the appropriate box in the upper part of the window.
Then hold down the left mouse button and select time intervals for this mode — the gaps will be
painted appropriately.
To specify a single recording mode for a day or copy
the schedule from another day, click to the right
of a day of the week and select the required option.
When finished, click OK to save the changes.
The Frame skipping with time feature allows to reduce the size of the archive after a specified
time. Reduction of the disk space, occupied by the archive, is performed by the removal of some
stored frames. The frame skipping operation can execute in one or two stages: for example,
recording is performed with an original frequency of 30 fps; In 7 days it is resampled down to 6
fps; And in 30 days - down to 0.5 fps (1 frame per 2 seconds).
Frame skipping with time is started only if the current archive size has reached the
maximum specified value: i.e., only if it is necessary to free disk space; In this case
the oldest fragments of the archive are deleted.
For the MPEG-4, H.264 and H.265 codecs, only the reference frames will be recorded.
In case of playback of the archive in Eocortex Ultra Client, archive fragments, which
have been skipped with time, will be displayed by the shaded area on the timeline.
Eocortex Ultra
72
3.4.5. Intelligence analysis system settings
Intelligence video analysis settings are configured in the corresponding block.
3.4.5.1. Motion detector settings

To enable a motion detector, check the appropriate box.
To use a built-in motion detection, check the appropriate box. If the box is not checked, the
Eocortex Ultra software motion detectorwill be used.
If you select a built-in motion detector, intelligent modules become unavailable.
If the selected channel uses two streams, the Stream selection for analysis option is available
— you can choose either main or alternate channel (Alternateis selected by default.)
Recommendations for selecting a stream for analysis; if the main one has higher
resolution than the alternate one (e.g., main — 1920x1080, alternate — 640x480):
- Alternate — if no intelligence analysis modules except for Eocortex Ultra software
detector are used.
- Main — if at least one additional intelligence analysis modules, including external
modules, is used with Eocortex Ultra software detector.
To configure aEocortex Ultra software motion detector, select the required setting: simple
or expert.
Simple mode allows setting the minimum size of an object to be detected for the entire frame.
Analysis in this mode is carried out with the optimal frequency (see below.)
The minimum object size can be set in two ways:
 Interactively:
1. Click Set in interactive mode — a minimum object size window will open.
Eocortex Ultra
73
2. Hold down the left mouse button to select an area, which size corresponds to the
minimum object size.
3. Click OK.
 Use the sliders to specify the minimum width and height as a percentage of the frame
size.
Eocortex Ultra
74
Expert mode allows setting the detection zones and the motion detection speed.
To set the speed, select one of the options:

Detect by using optimum frequency — video analysis and motion detection will be carried
out at a frequency defined automatically according to the following rules:
- if at least one intelligent module is enabled for a channel (suspect search, face detection,
people counting, tracking), the analysis is performed at 10 frames/s;
- if no intelligence modules are enabled, the rate for MJPEG is 5 frames/s, for H.264 and
MPEG-4 the frequency is automatically selected from the range of 0.4–5 frames/s.
Use reference frames only — only reference frames will be checked for motion for H.264 and
MPEG-4.
Detect by using customized frequency — video analysis and motion detection will be carried
out at a customized frequency.
Detecting zone — an area of the frame used for motion detection. You can set several zones
for a single channel; minimum object size is customizable for each zone.
To add a new detecting zone, click , to remove it — .

Detecting zone in the Zone mask area is filled with yellow squares. To change a detecting zone,
use your mouse:
the left button is used to select;
the right button is used to deselect.
To select the entire zone, click Fill all.
Eocortex Ultra
75
Click Clear to deselect the entire zone at once.
Use the slider to change the selection brush size.
To check the operation of a motion detector, click Test...
3.4.5.2. Sound detector

Sound detector allows responding to the excessive sound level registered by a camera
microphone. To activate the detector, check Sound detector.
The activation controller and the logarithmic scale of sound level, which displays the level of
sound registered in real time, will become available. Use the Threshold slider to specify the
level at which the detector will activate.
3.4.5.3. Perspective settings

A number of intelligence analysis modules (suspect search; crowd detection module) should take
the frame perspective into account. The perspective settings block is used for these purposes.
To adjust the perspective, check the Set perspective settings option.
Then specify the size of people using two scale pieces ( ): use your mouse to move a piece
to a corresponding frame area and adjust its size so that its height coincides with the height of
people in this area:
- Move figure — click the middle part of a figure and drag it while holding the mouse
button.
- Change size — click the top or bottom of a figure and move the mouse up or down
while holding the mouse button.
Eocortex Ultra
76
3.4.5.4. Configuring face detection module
To enable the face detection module, enable Face Detection.
The face detection module quality settings will become available. The quality level affects
the system resource consumption (CPU and RAM usage) — the consumption rate is higher for
high quality.
3.4.5.5. Configuring Suspect search

To enable the Suspect search, select Suspect search. Also select Indexing of moving
objects by features.
Advanced settings will become available. Use the sliders or interactively set the minimum and
maximum size of indexed objects. For proportions search select the Enable proportion
classification option.
3.4.5.6. Configuring external intelligent modules

To enable external intelligent modules, check Use external intelligent modules. After that, a
list of available intelligent modules will open below.
The list contains only those modules that are available on this server under Eocortex
Ultra license.
Working procedure for external intelligent modules is given below — in the relevant
sections.
Eocortex Ultra
77
3.4.6. Patrolling
Terms:
Preset — a preset position of the camera, implemented in many PTZs.
Patrolling — automatic switching between presets, implemented in many PTZs.
Settings:
If your camera supports presets, you can create your own patrolling in Eocortex.
To add a new patrolling, click above the patrolling list, to remove it click .
To add a new preset, click above the preset list, to remove it click to the right.
To move a preset up or down in the list, use to the right.

You can use appropriate controls to customize the patrolling scenario — the delay between
switching, the behavior after a preset is interrupted by a user.
3.4.7. Scheduled tasks

Each channel can perform the following schedule tasks:
Add a record to the archive.
Remove a record from the archive.
Set a camera position (preset.)
Send an SMS notification.
Send an e-mail notification (with a frame attached, if necessary.)
Send a signal to the camera output;
Run external application on the server.
Save a frame to the drive.
Pause an action sequence.
Enable camera Auto Focus.
Activate camera washer.
Eocortex Ultra
78
Add an event to the client application log.
Send a notification if a barrier is lifted or lowered (if the license plates recognition module is
used.)
For more information on scheduled tasks see 3.4.8 on page 80.
Scheduled tasks are configured in the Scheduled tasks block.
To create a new task:
1. Click . A scheduled action wizard will open.

2. On the first step enter the task name in the Name field; you may also add its description to
the Description field; click Next.
3. On the second step select when do you want to run the task. If you want to run it more
often than 1 once a day, select Run by interval and specify the frequency. Click Next.
Eocortex Ultra
79
4. In the last step, add the actions to be performed:
 To add an action, click and select the desired task.
 To delete an action, select the required action in the Action list and click .
 To edit an action, select the required action in the Action list and click .
 To change the sequence, use to the right from the Action list.
5. Click Finish. The created task will appear in the list of scheduled tasks.
Most actions include special specific parameters. For more information on scheduled
tasks see 3.4.8 on page 80.
Eocortex Ultra
80
3.4.8. Scenarios (response to system events)
Scenarios are configured in the Scenarios block.
This setting allows you to specify the actions to be performed in response to video surveillance
system events.
To set an action for a specific event:
1. Select an event in the Event list;
2. Use the drop-down list to choose the action to be taken;
3. Click ;
4. Expand the drop-down list and configure the action.
To remove an action for a specific event:
1. Select an event in the Event list;
2. Select the action;
3. Click .
To change the action sequenceuse .

Most actions include special specific parameters. To configure action parameters, expand the
action description by clicking to the left of the action.
Action parameters may also include different conditions, depending on the type of event.
In this case, the settings panel includes the Runtime conditions line. To add a condition, click
(to the right), then adjust the conditions.
Below are the descriptions of current events and the settings of existing actions:
Eocortex Ultra
81
3.4.8.1. Limit by start time condition
This condition is applicable to all system events and for a predetermined interval of time allows
avoiding repeated execution of an action in response to similar events on the same channel.
3.4.8.2. Movement event

This event is generated if the software motion detector detects motion in the frame. You can
modify the Zone condition (zone name is selected from the motion detector settings); if it is not
specified, the event will be generated for every zone (according to the settings of that zone.)
3.4.8.3. Loud sound event

This event is generated if the software audio detector detects an excessive audio level registered
by the microphone.
3.4.8.4. Lost connection with camera event

This event is generated in case of camera connection failure.
Starting with version 1.9, we recommend using the No connected cameraevent

instead of it. Due to the features of networks (overloaded networks, networks with low
bandwidth or signal quality) or network interfaces frequent short breaks and
reconnection events may occur, which would lead to the generation of a large number
of such events.
3.4.8.5. Established connection with camera event

This event is generated in case of camera connection reactivation.
Starting with version 1.9, we recommend using the No connected cameraevent

instead of it. Due to the features of networks (overloaded networks, networks with low
bandwidth or signal quality) or network interfaces frequent short breaks and
reconnection events may occur, which would lead to the generation of a large number
of Camera connection reactivation events.
3.4.8.6. Face detection event

This event is generated if a face is detected on the channel with face detection enabled.
Eocortex Ultra
82
3.4.8.7. Camera input signal event
This event is generated if the signal (analog) camera input receives an electrical signal.
Eocortex Ultra software must also support signal inputs for this IP camera model. For
more information contact Eocortex Ultra technical support.
For this event you need to set the condition with mandatory attributes Input number and
Alarm availability.
3.4.8.8. No connected camera event

This event is generated if camera connection was not reactivated after a specified time period.
The event requires the attributes Stream type and Breakage duration (in seconds.)
Stream type can have the following values:

 Main video — no main stream.
 Alternate video — no alternate stream.
 Main sound — no main audio stream.
 Alternate sound — no alternate audio stream.
 Sound transmission — no sound transmission channels.
 Motion detection — no receiving channel from a camera motion detector.
 I/O — no communication channel with camera signal inputs/outputs.
 Archive video — no communication channel with the video archive.
 Archive sound — no communication channel with the audio archive.
If the Stream type attribute not specified, the communication failure by any stream type will
be registered.
Breakage duration (in seconds) is compulsory.
3.4.8.9. Analog camera connection fail event

This event occurs if the hybrid DVR or decoder channel loses communication with the analog
camera bound to this channel.
in case of camera connection reactivation
For this event you need to set the condition with mandatory attribute Channel number.
Eocortex Ultra
83
3.4.8.10. Connecting to analog camera
This event occurs if the hybrid DVR or decoder channel establishes a connection with the analog
camera bound to this channel.
For this event you need to set the condition with mandatory attribute Channel number.
3.4.8.11. User alarm event

This event occurs if a user presses the Alarm button in Eocortex Ultra Client.
3.4.8.12. External alarm start event

This event occurs if the external system sends the External alarm start event. It is used to
integrate external systems with Eocortex Ultra software.
3.4.8.13. End of external alarm event

This event occurs if the external system sends the End of external alarm event. It is used to
integrate external systems with Eocortex Ultra software.
3.4.8.14. Motion started event

This event is generated when the software motion detector has detected the beginning of motion
in the scene. For this event, you can set a Zone condition (zone name is selected from the motion
detector settings); If the Zone condition is not specified, the event will be generated for any
zone (according to the settings of this zone).
3.4.8.15. Motion stopped event

This event is generated when the software motion detector has stopped capturing motion in the
scene. For this event, you can set a Zone condition (zone name is selected from the motion
detector settings); If the Zone condition is not specified, the event will be generated for any
zone (according to the settings of this zone).
3.4.8.16. Siemens DMS8000 event

This event is generated if an event is received from Siemens DMS8000 .
For this event, you need to specify various attributes.
If any attribute is not used to generate the event, it is not required.
Eocortex Ultra
84
3.4.8.17. Moving objects tracking event
This event is generated if the tracking module is enabled, in one of the following cases:
 intersection of a set line by an object;
 entry into a set area;
 prolonged stay in a set area.
3.4.8.18. Smoke event

This event is generated if the smoke and fire detection module is enabled and smoke is detected.
3.4.8.19. Fire event

This event is generated if the smoke and fire detection module is enabled and fire is detected.
3.4.8.20. Large number of people in the queue event

This event is generated if the queue control module is enabled and the number of people in the
queue has exceeded the specified value (see 5.10.1 on page 156.) You can modify the Zone
attribute (zone name is selected from the module settings); if it is not specified, the event will
be generated for every zone (according to the settings of that zone.)
3.4.8.21. Large crowd of people event

This event is generated if the crowd detection module is enabled and the number of people has
reached or exceeded the maximum permissible level. You must modify the Zone attribute for
this event (value from 0 to 5) to be generated.
3.4.8.22. Recognized license plates event

This event is generated if a license plate is detected on the channel with license plate detection
enabled. For this event, you need to specify various attributes: for example, if one attribute is
added — License plate identified = Yes, the event will be generated if any plate is identified.
If any attribute is not used to generate the event, it is not required.
Eocortex Ultra
85
3.4.8.23. Request to open gate event
This event is generated in three cases:
 if the operator pressed Open barrier on the screen;
 if the license plate from the group Open barrier for cars in this group was
identified;
 if the Barrier open notification action was implemented.
3.4.8.24. Request to close gate event

This event is generated in two cases:
 if the operator pressed Close barrier on the screen;
 if the Barrier closed notification action was implemented.
3.4.8.25. Video surveillance sabotage event

This event is generated if the video surveillance sabotage module is enabled and of the sabotage
detectors activates:
 camera defocusing;
 camera turn away;
 camera illumination;
 camera overlap.
3.4.8.26. Inactive zone event

This event is generated if the personnel activity control module is enabled — if no activity in the
controlled zone. You can modify the Zone attribute (zone name is selected from the module
settings); if it is not specified, the event will be generated for every zone (according to the
settings of that zone.)
3.4.8.27. Lost luggage detected event

This event is generated if the lost luggage detection module is enabled — if a lost objects located
in the frame over a specified time period is found (see 5.9.1 on page 154.) You can modify the
Zone attribute (zone name is selected from the module settings); if it is not specified, the event
will be generated for every zone (according to the settings of that zone.)
3.4.8.28. Add a record action

It adds a video record to the archive. Action parameters:
Run in channels — defines the channels for which the action will be performed. Options
available for this parameter:
- current channel (by default);
- all channels;
- selectively (in this case, the channel selection window opens, where you need to mark
the required channels.)
Eocortex Ultra
86
Recording time (in seconds) — sets the time interval for archiving.
3.4.8.29. Remove a record action

It removes a video record from the archive. Action parameters:
- all channels;
3.4.8.30. Set a camera position action

Moves a PTZ camera to a preset position. However, this preset should be pre-specified in camera
settings.
Action parameters:
- all channels;
Eocortex Ultra
87
Preset order number — preset order number is specified.
3.4.8.31. Send an SMS notification action

Sends an SMS to the specified number using a GSM modem inserted into a server USB-port.
Before using the GSM modem in Eocortex Ultra software, install the drivers supplied with the
modem; test the modem by sending a test message — either by using the software provided or
the operating system.
Action parameters:
GSM modem — select the modem to be used to send an SMS. Initially this list is empty. To
add, delete and edit the modem settings use , respectively.
Below is a modem settings form: specify the actual values in this form (these values are set in
the proprietary modem software.)
Telephone number — phone number for SMS.
Eocortex Ultra
88
Message text — the text that will be sent to the specified number.
To test sending from Eocortex, click Send message — in this case an attempt will be made to
send an SMS via modem: depending on the result one of the two windows will appear: Message
sent successfully or Message not sent.
Eocortex Ultra
89
3.4.8.32. Send an e-mail notification action
Sends an e-mail from the server to the specified address.
Action parameters:
Mail server — specify the SMTP-server to be used to send a message. Initially this list is empty.
To add, delete and edit the server settings use , respectively.
Below is a mail server settings form: specify the actual server settings in this form (these settings
can be obtained from a system administrator or an organization maintaining the mail server.)
To — the e-mail address for messages.

From — the e-mail address, from which messages will be sent (in general, it will be the same
as the User Name field in the mail server settings window.)
Message text — the text that will be sent to the specified address.
Attach frame to email — allows you to attach the frame recorded at the time of sending.
Specify the Saved frame format: JPEG, PNG or BMP.
To test sending from Eocortex, click Send message — in this case an attempt will be made to
send a message via modem: depending on the result one of the two windows will appear:
Message sent successfully or Message not sent.
Eocortex Ultra
90
3.4.8.33. Send a signal to the camera output action
An electric signal is sent to the IP camera signal output.
Eocortex Ultra software must also support signal outputs for this IP camera model. For
more information contact Eocortex Ultra technical support.
Action parameters:
 current channel (by default);
 all channels;
 selectively (in this case, the channel selection window opens, where you need to mark
Output number — the number of the camera signal output.
A majority of cameras with a single output use 0 or 1 values.
Output value — alarm output status: 1 (enabled) / 0 (disabled.)
Depending on the circuit, the activation/deactivation of the alarm output may

correspond to different physical states of contacts: closed/open circuit,
presence/absence of voltage, etc.
As a rule, information on the wiring diagram can be found in the camera technical
documentation.
Eocortex Ultra
91
3.4.8.34. Run external application on the server action
Launches an external application on the server. Action parameters:
Path (on server) — the path to an application on the server. To select an application in Windows
Explorer, you can click .
Arguments — if an application must be launched with command line parameters, they are
specified in this field.
3.4.8.35. Alarm generation action

It generates an alarm for this channel.
3.4.8.36. Save frame action

Saves a frame on the server. Action parameters:
Folder (on the server) — the path to the folder used to store frames. To select a folder in
Windows Explorer, you can click .
Saved file format — allows you to select the image file format: JPEG or PNG.
File names will be formed as follows:

ChannelName DD_MM_YYYY hh.mm.ss.mmm.ext, where:
DD_MM_YYYY — day, month, year;
hh.mm.ss.mmm — hours, minutes, seconds, milliseconds
ext — jpg, png.
Eocortex Ultra
92
Restrict maximum size of the folder (MB) — allows you to set a maximum size of the folder:
after reaching the maximum size, the oldest files will be deleted.
3.4.8.37. Pause action

It allows setting a pause between actions within the scenario. Action parameter:
Pause interval (sec) — sets the duration of the pause.
3.4.8.38. Enable camera AF mode action

Focuses the camera assigned to this channel.
Eocortex Ultra software must also support AF control for this IP camera model. For more
information contact Eocortex Ultra technical support.
3.4.8.39. Activate camera washer action

It activates camera washer.
Eocortex Ultra software must also support camera washer control for this IP camera
model. For more information contact Eocortex Ultra technical support.
Action parameters:
 all channels;
Eocortex Ultra
93
3.4.8.40. Disable frame skipping when recording to the archive action

Disables frame skipping while recording to the archive during the specified time interval.
3.4.8.41. Barrier closed notification action

Generates the Barrier closed system event. Action parameter:
 all channels;
3.4.8.42. Barrier open notification action

Generates the Barrier open system event. Action parameter:
 all channels;
Eocortex Ultra
94
3.4.9. Cloud broadcast settings

Enabling Broadcast channel to the Cloud allows broadcasting the channel video stream to the
cloud on the basis ofEocortex Ultra Cloud. The broadcast will be made only with the appropriate
option enabled on Eocortex Ultra server.
Eocortex Ultra
95
3.4.10. Group settings
To simplify the setting procedure of many channels with the same parameters you can set the
parameters for all channels at once or for channels attached to a certain security object
(including underlying objects and attached cameras.)
To set the parameters for the channel group:

1 Select all channels by left-clicking an empty spot in the channel tree. Or choose channels
belonging to a security object by selecting this object;
2 Adjust the parameters in one of the blocks:
Channel connection settings (see 3.4.2);
Archiving (see 3.4.4);
Intelligent analysis system settings (see 3.4.5);
Scheduled tasks (see 3.4.7);
Scenarios (see 3.4.8);
6. Click Apply settings;
7. Repeat steps 2 and 3 for all required blocks.
Eocortex Ultra
96
3.4.11. Indication of connected modules
The channel tree contains icons that correspond to the functions used on the channel they are
related to.
— sound recording;
— sound transmission;
— PTZ management;
— face detection;
— interactive search in archive.
If none of the icons is displayed, the above mentioned functions are not enabled for this channel.
3.5. User right settings

In order to switch to user rights differentiation, click 3. Users and Groups. This will open the
edit page for groups, users and rights.
To add a new user group, click in the appropriate box, to remove it, click .
To select the available privilege for the selected group’s members, check the appropriate
boxes:
 Configuration.
 Configuring workplace.
 Close application.
 Observation mode change.
 PTZ Camera management.
 Archiving management.
 Archive expert mode access (simultaneous viewing of archives from multiple cameras)
 Access to the event log.
 Access to all users in the event log (if this option is disabled only events from the current
user are available).
 Received sound from camera.
 Broadcast sound to camera.
Eocortex Ultra
97
 Access to new added cameras (if the option is not enabled for a group, the newly added
cameras will not be available this group until they are clearly marked in access windows to
live video and archives).
 Connection via mobile devices and Web-Client.
 Receive push-notifications.
 Editing intelligent modules data (editing intelligent modules references).
 Receipt of the chat messages.
 Sending of the chat messages.
 Videowall management.
 Videowall configuration management.
 Access to screen profiles.
To select channels with group access to real-time video, select the required channels in
the Group access to real-time video list.
To select channels with group access to archive, select the required channels in the Group
access to video archive list.
To add a new user, click in the appropriate box, to remove it, click .
To change the name of a group or a user, double-click it, press F2 or right-click it to open
up a context menu and select Rename; then type a new name and press Enter.
The names of groups and users should only contain letters, numbers and underscores.
Spaces, punctuation, arithmetic and other special characters are not allowed.
To add a user to a group and set a user password:

 Select a user;
 Select a group in the Group drop-down menu on the right side of the block over Password.
 Fill in the Password field;
 Repeat the password in the Password confirmation field;
 Click Apply password.
Eocortex Ultra
98
3.6. Object plans
Working with object plans in Eocortex Ultra Client is described in the Eocortex Ultra User Guide.
To configure object plans, click 4. Object plans in the left half of Configurator. This will open
the edit page for object plans.
This page contains object plans with cameras, sensors, relays, as well camera fields of view.
The plan tree is at the top left of the page.
Plans have a hierarchical structure. The top-level node is named Plans, it can not be renamed,
moved or deleted under any circumstances.
To create a plan hierarchy based on a security object hierarchy, click .
To add a new plan, select a "parent" object for it and do one of the following: click
; press Ctrl+N; right-click to open a context menu and select Add plan.
To delete a plan, select an object you want to delete and do one of the following: click
; press Del; right-click to open a context menu and select Delete.
To rename a plan, select an object and press Ctrl+R or right-click to open a context menu and
select Rename; then enter a new name in the box and press Enter.
Eocortex Ultra
99
To move a plan from one parent element to the other, select a plan, hold the left mouse button
and drag it to another node.
The channel tree and sensor and relay addition buttons are located at the top right of the page.
Below is the drawing toolbar, which is located over the object plan.
The following drawing and editing tools are available:

Open image — Loads an image from a JPEG, PNG or BMP file. In this case all previously drawn
and arranged items are removed from the plan. After the image is opened you can use drawing
tools — hand-drawn elements will be placed on top of the image.
Draw from scratch — Erases all items drawn before, including opened image and arranged
elements.
Undo — Undoes the last action. If you press it again it deletes the previous one, etc. The
chain includes 20 actions. After applying the configuration the chain is reset.
Redo — Restores the last earlier undone action. If you press it again it restores the previous
one, etc. The chain includes 20 actions. After applying the configuration the chain is reset.
Object selection pointer — Enables the cursor selection mode for cameras, sensors,
relays and fields of view.
Select area — Selects objects (cameras, sensors, relays) in a rectangular area.
Set coordinate reference to another plan — Inserts (by pressing the left mouse button
on the plan) an icon referencing to another plan. The other plan must also contain an icon
referencing this plan. If you add an icon to the plan a menu to choose another plan appears; then
this second plan is opened; after you add a second icon a dialog box indicating the distance
between the plans in minutes appears. If the added icon is selected, right-click brings up a menu
allowing you to change the distance or the "paired" plan.
Pencil — Allows drawing (with the left mouse button pressed) arbitrary lines of color and
thickness specified in the Palette and Thickness fields.
Eraser — Allows erasing (in white, with left mouse button pressed) images on the plan,
including those loaded from a file. Its thickness in adjusted in the Thickness field.
Draw line — Allows drawing (with the left mouse button pressed) straight lines of color
and thickness specified in the Palette and Thickness fields.
Draw rectangular — Allows drawing (with the left mouse button pressed) rectangular
contours of color and thickness specified in the Palette and Thickness fields.
Eocortex Ultra
100
Draw ellipse — Allows drawing (with the left mouse button pressed) elliptic contours of
color and thickness specified in the Palette and Thickness fields.
Add text — Inserts (using the left mouse button) a text box for text. The text color is set
in the Palette field. The text size (height and width) is adjusted by selecting text and changing
(using the left mouse button) its size — the text fits into a rectangular area.
Palette — Allows selecting the line color.
Thickness — Allows selecting the line thickness.

Object length, m and Object width, m under the plan define the dimensions of the object to
be displayed on the image.
To place a camera on the plan, select it in the channel tree, hold the left mouse button and
drag-and-drop it to the plan.
When you select a camera with the Object selection pointer, you can:
- move a camera over the plan by holding the left mouse button;
- rotate a camera by clicking the green rotation node and moving the cursor with the left
mouse button pressed;
- remove a sensor (switch) from the plan by pressing Del;
- open a camera context menu by right-clicking.
This context menu includes the following commands:
Show video — displays real-time video from the camera (a rectangle with the video appears.)
You can move the video window over the plan with the left mouse button pressed.
Select channel — allows selecting (reassigning) the channel for this camera.
Set/delete field of view — displays the camera field of view.
Camera field of view is a rectangle of arbitrary shape. If you view the plan with set fields of
view in Eocortex Ultra Client, this fields display the image from the camera; if appropriate
settings are configured, the intelligent module data is also displayed on top of the field of view.
To change the size and orientation of the image in the field of view, select a camera using
Object selection pointer; use the left mouse button to move the corners of the field of view.
If you select a camera in the setting mode, the field of view displays real-time video — it allows
you to properly adjust the zone orientation.
You can also place sensors and relays on the plan.
Sensors — devices connected to camera signal inputs. If a sensor is triggered via the channel
connected to the camera the signal is sent to Eocortex Ultra system.
Relays (switches) — devices connected to camera signal outputs.
Relays allow the Eocortex Ultra system operator to send a signal to external devices connected
to the corresponding relays.
Eocortex Ultra
101
To add a sensor or a switch to the plan:
1. Click the appropriate button .
2. In the Binding relay to a channel window that opens, select the camera to connect a
sensor (switch) to; specify the Name that will appear on the plan for this sensor
(switch); specify the Alarm input (output) number to use with this sensor (switch); click
OK — the sensor (switch) will be added to the plan.
You can select only cameras with Event processing (I/O) enabled (seeChannel
connection settings)
When you select a sensor (switch) with the Object selection pointer, you can:
 move a sensor (switch) over the plan by holding the left mouse button;
 change binding parameters by opening the Binding relay to a channel window;
 remove a sensor (switch) from the plan by pressing Del.
Eocortex Ultra
102
3.7. Setting screen profiles
To configure the screen profiles click 5. Other setting and expand the Monitor profiles settings
group.
To create a screen profile, click .

To change the screen profile name, double-click it, press F2 or right-click it to open up a
context menu and select Rename; then type a new name and press Enter.
To delete a screen profile, click .

To adjust the location of grids in a profile, select one of the possible layouts in the Grid field.
To put a channel to a grid cell, drag the channel to the appropriate cell, or:
1. Select the cell;
2. Select the channel;
3. Click .
To remove a channel from a grid cell:
1. Select the cell;
2. Click .
In addition to profiles, Eocortex Ultra allows you to customize automatic grids switch
templates.
Eocortex Ultra
103
To create an automatic grids switch template, click .

To change the automatic grids switch template name, double-click it, press F2 or right-
click it to open up a context menu and select Rename; then type a new name and press Enter.
To delete an automatic grids switch template, click .

To add a profile to theautomatic grids switch template, select one of the existing profiles
from the drop-down list and click .
To delete a profile from an automatic grids switch template, click .
To change the sequence of profiles in a template, use .
Eocortex Ultra
104
3.8. Configuration of the categories of the archive bookmarks
Work with the categories of archive bookmarks in the Eocortex Ultra Client application
is described in the User's Guide.
To configure the categories of the archive bookmarks, go to the 5. Other settings tab and
expand the Categories of archive bookmarks section of settings.
To create a new category, click button, then enter the category name in the field on the
right and click the Save button.
To change the category name, select the category, then enter the new name in the field on the
right and click the Save button.
To delete a category, select the category, then press the button.
By default, the standard category Alarm is created in the configuration.

Editing and deletion of the standard categories is prohibited.
Eocortex Ultra
105
4. Status Info utility, Eocortex Ultra Standalone control window,
autorun Eocortex Ultra Client
This section describes the features of Status Info utility and of Eocortex Ultra Standalone
application, as well the configuration features for Eocortex Ultra Client autorun.
The operating procedures for Eocortex Ultra video surveillance system using Eocortex
Ultra Client, Eocortex Ultra Standalone viewer, as well as web and mobile
applications are described in the Eocortex Ultra User Guide.
4.1. Status Info utility

Status Info utility is used for the control and monitoring of Eocortex Ultra Server service. It
is activated automatically, when the operating system is started up, and is displayed in the
notification area on Desktop.
For opening of the Status Info window, click the utility icon, or right-click the context menu
and select Display. If you click Close in the context menu, the utility shall be closed, and
Eocortex Ultra Server service will continue to work.
Status Info window contains the following controls:

Run button launches the Eocortex Ultra Server service on the computer.
Stop button stops the Eocortex Ultra Server service on the computer. Before stopping, you
should enter the user name and password with the appropriate rights.
Configurator button launches the Eocortex Ultra Configurator application.
Bottom part of the window displays information concerning the current state of the server. In
the same area, notifications of problems on the server will be displayed. By clicking on the line
with the problem you shall obtain a detailed description and recommendations for its correction.
To delete a line from the list, press button on the right side.
Eocortex Ultra
106
4.2. Eocortex Ultra Standalone control window
Eocortex Ultra Standalone is not a Windows service — it is a separately launched application
with a window interface.
After the launch of Eocortex Ultra Standalone, application icon appears in the Windows
Desktop notification area.
To open the Eocortex Ultra Standalone control window, click on its icon, or right-click the
context menu and select Show.
If you select Stop and close in the context menu, the application shall be closed.
Control window Eocortex Ultra Standalone contains the following controls:
Viewing button launches the Eocortex Ultra Client viewing window.
System Setting button launches Eocortex Ultra Configurator application.
Bottom part of the window displays information about the current state of the server. In the
same area, notifications of the problems on the server will be displayed. By clicking on the line
with the problem you shall obtain the detailed description and recommendations for its
correction. To delete a line from the list, press button on the right side.
4.3. Autorun of Eocortex Ultra Client and Eocortex Ultra Standalone Viewer
Below are the examples of autorun that do not require entering an explicit username and
password in the login screen:
 autorun of Eocortex Ultra Client at computer startup;
 autorun of Eocortex Ultra Standalone viewer at computer startup;
 autorun of Eocortex Ultra Client from a desktop shortcut;
 autorun of Eocortex Ultra Standalone viewer from a desktop shortcut;
The following parameters are shown as examples:
Eocortex Ultra Client installation folder:
C:\Users\UserName\AppData\Local\Programs\Eocortex Ultra Client\
Eocortex Ultra Standalone installation folder:
C:\Program Files\Eocortex Ultra Standalone\
Server address: 192.168.0.100
Server port: 8081
Eocortex Ultra username: operator
Eocortex Ultra password: qwerty77
Windows username: UserName
Quotation marks in the full path to the file are required.
1. To configure Eocortex Ultra Client autorun at computer startup, go to the Windows

registry and create a record in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run:
"C:\Users\UserName\AppData\Local\Programs\Eocortex Ultra
Client\EocortexClient.exe" -server 192.168.0.100 -port 8081 -user operator -
password qwerty77
2. To configure Eocortex Ultra Standalone viewer autorun at computer startup, go to the
Windows registry and create a record in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run:
"C:\Program Files\Eocortex Ultra Standalone\Eocortex.exe" -server 192.168.0.100 -
port 8081 -user operator -password qwerty77
3. To configure Eocortex Ultra Client autorun from a desktop shortcut, select a shortcut, right-
click it, select Properties, go to the Shortcut tab and enter the following to Object:
"C:\Users\UserName\AppData\Local\Programs\Eocortex Ultra
Client\EocortexClient.exe" -server 192.168.0.100 -port 8081 -user operator -
password qwerty77
Eocortex Ultra
107
4. To configure Eocortex Ultra Standalone viewer autorun from a desktop shortcut, select a
shortcut, right-click it, select Properties, go to the Shortcut tab and enter the following to
Object:
"C:\Program Files\Eocortex Ultra Standalone\Eocortex.exe" -server 192.168.0.100 -
port 8081 -user operator -password qwerty77
Eocortex Ultra
108
5. Intellectual modules
5.1. Sabotage detection module:

The sabotage detection module allows detecting the following events:
 Camera defocusing.
 Camera panned to different direction.
 Camera illumination.
 Camera overlap,
For more information on working with this module in Eocortex Ultra Client and
Eocortex Ultra Standaloneviewer see the Eocortex Ultra User Guide.
To activate video surveillance sabotage detectors for the selected camera:

Run Eocortex Ultra Configurator, switch to the channel settings, Intelligence analysis system
settings, enable software motion detection as in 3.4.5.1 on page 72.
Mark Use external intelligent modules, the Sabotage detection module will become available.
Select the Sabotage detection module.

In the left pane of Configurator, click 6. Apply settings, click Apply on the opened page.
If you want the system to signal when the detectors are triggered, configure the
required actions in response for the Video surveillance sabotage event in scenario
settings.
Eocortex Ultra
109
5.2. Tracking module
The tracking module has the following features:
 Tracking of moving objects in the camera field of view.
 Generation of alarms for the following events:
 intersecting a line
 entering a zone
 Prolong stay of an object in a zone.
 Search in the alarm archive.
 Interactive search in archive by intersecting any set line.
The module is designed to monitor the territories without a dense stream of moving objects.
Its correctness depends on the number and relative position of objects in the frame: the
smaller objects are and the less they overlap each other, the better its result it.
Eocortex Ultra Standaloneviewersee the Eocortex Ultra User Guide.
For correct operation of the module you must position the camera correctly and set up the
Eocortex Ultra motion detector and the module itself.
5.2.1. Configuring the tracking module

For activation of the module, start Eocortex Ultra Configurator, go to 1. Cameras tab, select
the camera in the list (on the left), in the settings of the camera (on the right) in the Intelligent
analysis system settings section, enable and configure Motion detector, then enable the
option Use external intelligence modules, and then enable Moving object tracking module
in the list of available modules.
If this module is not on the list, it means that the server has no license for this module.
To purchase the license, please contact the direct seller of Eocortex Ultra licenses for
this server. The list of available licenses can be found in Configurator in 2. Servers tab
in the Selected server License parameters section.
When the module is activated, press button, placed to the right of the module name: the
module settings window shall be opened, containing two groups of settings — Detector settings
and Alarm settings (see below).
Eocortex Ultra
110
To save the module settings, click Save and exit button (or Exit without saving button to
discard the changes), then apply the configuration (go to the tab 6. Apply settings and click
Apply button).
5.2.1.1. Detector settings

In the detector settings, you should set the minimum size of the objects. Objects smaller than
the minimum size will be combined into the larger ones.
Eocortex Ultra
111
To set the minimum size of the object, click Set button, use the mouse to select the minimum
rectangle in the opened window, and then click "Set size" button.
5.2.1.2. Alarm settings

In the alarm settings, it is possible to configure three types of situations in which an alarm will
be generated:
 When crossing a given line;
 When an object hits a given zone;
 In case of long stay of the object in a given zone.
Eocortex Ultra
112
Intersection line
To specify the intersection line, press the button — a line will appear on the preview.
Line placement can be changed by dragging and dropping of the anchor points with the left
mouse button.
To specify the direction of operation, select the corresponding value in the Moving direction
drop-down list. Access to the values Both directions, First direction and Second direction
is available. If the first or the second direction is selected, arrows with Entering and Exiting
signs will be perpendicular to the line, and the alarm will be generated only when the objects
cross the line in the Entering direction.
You can also set the minimum and maximum sizes of objects. In this case, alarms will be
generated for this line only for those objects, which correspond to the specified range of sizes
(greater than the minimum and less than the maximum sizes).
Eocortex Ultra
113
Alarm in the zone
To set the control zone, press button — a rectangular zone shall appear on the preview.
The location of the zone may be changed by dragging and dropping of the anchor points with
the left mouse button. To add a new anchor point, click the left mouse button on the line. To
delete a reference point, you must right-click on this point.
If you select Alarm in the zone value in the Alarm type
drop-down list, the alarm will be generated every time, when
any moving object enters the zone.
If Lengthy presence is selected, the alarm will only be
generated if the object is in the zone, longer than specified
one in the Staying time ... seconds field.
You can also set the minimum and maximum sizes of objects.
In this case, alarms will be generated for this zone only for the
objects, which correspond to the specified range of sizes
(greater than the minimum and less than the maximum sizes).
To edit a line or zone, select this line (zone) in the list, and then start editing.
To delete a line or zone, select this line (zone) in the list, then press button.
To display all added lines and zones on the preview, press button.
5.2.2. Camera position

The camera should be positioned so that the objects in the frame avoid overlapping with each
other as much as possible. The camera is recommended to be placed as high as possible under
the most steep angle (recommended vertical deviation of no more than 30-40%). It is also
recommended to get rid of perspective distortion control zones.
Frame resolution should be at least 480x384 pixels. Optimum picture resolution for this module —
from 1280x960 pixels; it is desirable that the person took from one third to half of the frame.
Eocortex Ultra
114
5.3. People counting module
The people counting module has the following features:
 Counting the number of entering and exiting visitors in real time — either through one or
several (if multiple cameras are used) entrances/exits.
 Creating reports on entered, left and present visitors — over various periods of time (from
hours to years) for one or several cameras overseeing one area from different locations.
 Automatic and manual export of reports in CSV (supported, inter alia, by Microsoft Excel.)
 Counting of people in moving groups: i.e. few people moving as a group will be counted with
a minimum error.
The people counting module uses two mutually exclusive calculation methods: The method of
counting separately moving people and the method of counting people moving in groups. The
exact method to be used on a particular channel is determined when configuring this channel in
Eocortex Ultra Configurator.
Eocortex Ultra Standaloneviewersee the Eocortex Ultra User Guide.
5.3.1. Configuring the module

option Use external intelligence modules, and then enable People counting module in the
list of available modules.
this server. The list of available licenses can be found in Configurator in 2. Servers tab
in the Selected server License parameters section.
module settings window shall be opened.
Eocortex Ultra
115
Control elements of the module settings window:

The buttons Real time and Archive determine the mode of video broadcasting in the settings
window.
In the preview cell, you should configure the intersection line by dragging the ends of the line
with the mouse. All counted people must cross this line.
It is not recommended to have a line of intersection in close proximity to the doors

and other moving objects.
You also should adjust the direction of entrance and the average size of the object.
To change the direction, use the appropriate button. The arrow perpendicular to the intersection
line should correspond to the direction of the entrance.
To adjust the average size of the object, drag the corners of the rectangle with the mouse so
that the rectangle's dimensions correspond to the medium-sized object at the intersection of the
line. When counting, this size is taken into account: if the object is significantly larger than the
frame, it will be counted as several objects.
For the convenience of setting of the average size, it is recommended to use video from
the archive.
Eocortex Ultra
116
Average size rectangle can be in any part of the frame, it is not necessary to place it
on the intersection line.
Counting method allows to choose the method of counting depending on the operating
conditions of the module. The following values are available:
 Several people in a frame provides counting of both individuals moving separately and
groups of people. This method is recommended to be used in most cases, when the
operating conditions of the module are observed.
 Separately moving people in a frame is recommended to be used only in situations
when it is not possible to ensure all the operating conditions of the module (for example,
when the camera is set low or not vertically) and there are rarely more than one person
in the scene.
Show additional settings button opens
additional settings panel:
Counting options selects the data to be
calculated, stored in the archive and
displayed in the client application.
Automatic save data to csv-files activates
automatic saving of data.
People counting data period specifies a
scale: a single time interval for which the
counters data (one line of the CSV file) will be
summed.
Unload data every specifies how often the
CSV file is uploaded.
Path of files specifies the directory on the
server where the CSV files will be uploaded.
Select folder button (for interactive

selection) may be used only when the
Configurator is running on the server
to which the camera is bound.
The format of the CSV file name:

Counters_NameCameras_DDMMYYYY# hhmm.csv.
For example, if the autosave period is set to Hour for the camera named Camera 1,
the following files will be saved:
Counters_Camera 3_02022017#10.csv
Counters_Camera3_02022017#11.csv
Counters_Camera3_02022017#12.csv
An example of the contents of a CSV file:
time;in;out;inside;
02/02/2017 12:00:00;6;4;2;
02/02/2017 12:01:00;6;11;-5;
02/02/2017 12:02:00;10;6;4;
where time is the date/time of the start of the unit count interval;
in/out/inside is the number of the objects, entered, exited and remained
inside of the premise, within the given time interval, respectively.
Counter reset specifies the parameters for resetting of the counters to zero values.
 Start time is the date / time from which the reset intervals will be counted.
 Counter resetperiod is the frequency of resetting of the counters.
Eocortex Ultra
117
The settings below depend on the selected Counting method:
Settings for Several people in a frame:
Show the suggested size of the object enables the display of the object's automatically
calculated size.
Algorithm accuracy:
 Full frame analysis increases the accuracy of the calculation, but at the same time
increases the load on the processor.
 High Sensitivity increases the chances of detection of the objects, but at the same time
this increases the probability of false positives; low sensitivity increases the resistance to
noise, but this may reduce the accuracy of the calculation.
Settings for Separately moving people in a frame:
Show the trajectory of the movement enables the display of the trajectories of the objects.
To save the module settings, click Save and exit button (or Exit without saving button to
discard the changes), then apply the configuration (go to the tab 6. Apply settings and click
the Apply button).
The module will be "learning" for 10-15 seconds — counting data for this period will be
incorrect. Since this "learning" process includes the record of stationary background to
provide more accurate results, it is recommended to perform it with a minimum number
of moving and outside objects in the frame.
5.4. License plate recognition module

The license plate recognition module has the following features:
 Recognition of license plates of moving cars and archiving of information about the time and
date of recognition, the license plate, as well as the reference to the corresponding video
frame.
 Real-time interception of recognized license plates listed in a database.
 Support of the embedded database of license plates: adding and editing license plates,
additional information (color, owner, etc.) on vehicles.
 License plate groups, including groups for interception and automatic barrier opening; one
license plate can be assigned to one or more groups.
 Search of recognized license plates in the archive by time, date and details from a database.
 Export of the list of recognized license plates in Microsoft Excel or CSV formats.
 Barrier control.
Eocortex Ultra
118
The module is designed to detect license plates on moving vehicles: if a vehicle is not
moving a license plate is not recognized with high accuracy.
Users can export the list only in manual mode. To automate this process, use Eocortex
Ultra API features described in Eocortex Ultra SDK (submit a request for SDK to
[email protected]).
Eocortex Ultra controls barriers through output signals of IP cameras.
5.4.1. Module features

 Video stream processing at 6 or 25 fps (depending on the installed license.)
 Maximum vehicle speed for recognition: at 6 fps — up to 20 km/h, at 25 fps — up to 150
km/h.
 Maximum number of license plates simultaneously detected in the frame — up to 10
pcs. Detection at a vertical tilt angle up to 40°.
 Recognition at a horizontal tilt angle up to 30°.
 Recognition at a license plate tilt angle relative to the roadway — up to 10°.
 Recognition of license plates from the following countries: Abkhazia, Austria, Azerbaijan,
Albania, Algeria, Andorra, Angola, Argentina, Armenia, Belarus, Belgium, Bolivia, Bulgaria,
Bosnia and Herzegovina, Brazil, Vatican, Great Britain, Hungary, Venezuela, Vietnam,
Guatemala, Gibraltar, Honduras, Hong Kong, Grenada, Greece, Georgia, Denmark, Dominican
Republic, Israel, Jordan, Ireland, Iceland, Spain, Italy, Kazakhstan, Cameroon, Canada,
Cyprus, Kyrgyzstan, Colombia, Kosovo, Costa Rica, Cuba, Latvia, Lithuania, Luxembourg,
Macedonia Malta, Mexico, Moldova, Nigeria, the Netherlands, Nicaragua, New Zealand,
Norway, United Arab Emirates, Panama, Paraguay, Peru, Poland, Portugal, Transnistria,
Puerto Rico, Russia, Romania, Serbia, Slovakia, Slovenia, Taiwan, Tunisia, Turkey,
Turkmenistan, Uzbekistan, Ukraine, Uruguay, Philippines, Finland, France, Croatia,
Montenegro, Czech Republic, Chile, Sweden, Sri Lanka, Ecuador, Equatorial Guinea, Estonia,
South Africa; including special license plates — diplomatic, police, military, etc.
 Separate search zones for load reduction during recognition.
5.4.2. Licensing
License plate recognition module is licensed by license type and number of recognition channels.
In addition, when you purchase a license, please specify the list of countries to be supported by
the module.
License plate recognition module licenses
License type Description
Parking Allows recognizing license plates of vehicles moving at up to 20 km/h. The video
stream is analyzed at up to 6 fps, regardless of the received frame rate.
Highway Allows recognizing license plates of vehicles moving at up to 150 km/h. Analysis
is based on the actual received frame rate. We recommend using 25 fps to
recognize license plates of vehicles moving at high speed.
The list of supported countries:
Group 1: Abkhazia, Azerbaijan, Armenia, Azerbaijan, Belarus, Georgia, Kazakhstan, Kyrgyzstan,
Moldova, Transnistria, Russia, Tajikistan, Turkmenistan, Ukraine, Uzbekistan, South Ossetia.
Eocortex Ultra
119
Group 2: Australia, Austria, Albania, Andorra, Angola, Argentina, Belgium, Bolivia, Bulgaria,
Bosnia and Herzegovina, Brazil, Vatican, Great Britain, Hungary, Venezuela, Vietnam,
Guatemala, Germany, Gibraltar, Honduras, Hong Kong, Grenada, Greece, Denmark, Dominican
Republic, India, Israel, Jordan, Iran, Ireland, Iceland, Spain, Italy, Cameroon, Canada, Cyprus,
Colombia, Kosovo, Costa Rica, Cuba, Kuwait, Latvia, Lithuania, Luxembourg, Macedonia,
Malaysia, Malta, Mexico Mongolia, Nigeria, the Netherlands, Nicaragua, New Zealand, Norway,
the United Arab Emirates, Panama, Paraguay, Peru, Poland, Portugal, Puerto Rico, Romania,
Serbia, Singapore, Slovakia, Slovenia, Taiwan, Turkey, Uruguay, the Philippines, Finland, France,
Croatia, Montenegro, Czech Republic, Chile, Switzerland, Sweden, Sri Lanka, Ecuador, Equatorial
Guinea, Estonia, South Africa.
If you order a license that includes countries from Group 2, it may cost more — in this
case, please contact your Eocortex Ultra software vendor for the exact price.
The license plate recognition module uses libraries developed by a third party and requiring
separate licensing. Thus, this module technically requires two elements of license protection:
Eocortex Ultra protection key and license plate module protection key.
One license plate module protection key can support up to 20 countries.
Eocortex Ultra key

Name / Image Description
Guardant USB-key + license file
It allows using the license plate module with the

number of channels specified in the license file or
software key (also allows enabling the external license
plate recognition module in Configurator.) The license
Or file contains only the number of channels, not the
HASP software key license type (up to 20 or up to 150 km/h.)
License plate module protection key

Name / Image Description
It allows actually recognizing license plates on the
HASP USB-key
number of channels specified in the USB-key
firmware. The USB-key firmware also contains the
license type ("parking" or "highway"), the number of
channels and the list of countries.
The presence of two license protection elements is only a technical feature: you pay for
one license per each server; this license indicates the type ("parking" or "highway")
and the number of license plate recognition channels on this server.
The license plate recognition module requires the license plate module protection key to be
inserted in the Eocortex Ultra server with channels used for recognition. This server must also
have the Eocortex Ultra USB-key (or software key), the license file (or software key) that must
indicate that the license plate recognition module is supported.
One Eocortex Ultra server may have no more than one Eocortex Ultra USB-key (or software key)
and not more than one license plate module protection key.
One Eocortex Ultra server can run the module of only one type: "parking" or "highway".
The number of recognition channels can be increased: to do this, purchase additional licenses
from your Eocortex Ultra software vendor; then you will receive a new Eocortex Ultra license file
(or software key) and a new module protection key firmware.
Eocortex Ultra
120
License type of the license plate recognition module can be changed (from "parking" to
"highway"): to do this, purchase a license extension from your Eocortex Ultra software vendor;
then you will receive a new Eocortex Ultra license file (or software key) and a new module
protection key firmware: if the number of channels stays the same, you can keep an old Eocortex
Ultra license file (software key.)
When using the multiserver configuration, you can configure the license plate recognition on
channels assigned to different Eocortex Ultra server — in this case:
 each server must have a separate license plate recognition module protection key and
Eocortex Ultra licenses should support the corresponding number of modules;
 a single configuration will use a single database and the archive of recognized license
plates.
For example, if four servers are merged into a single configuration:

incl. license
License plate
Server plate Eocortex Ultra
Channels recognition module
name recognition license
license
channels
5 — up to 20 LS x64 for 10 IP
Server 1 10 5 "parking" channels
km/h cameras
Server 2 20 2 "highway" channels
km/h cameras
Server 3 30 1 "parking" channel
km/h cameras
LS x64 for 10 IP
Server 4 40 — —
cameras
You need to purchase the following licenses (by keys):
Eocortex Ultra LS software (64-bit (x64) version) for IP camera video surveillance
100 pcs.
systems.The license for processing the video stream from one IP camera.
"Auto parking" Eocortex Ultra module. License for 5 IP channels 1 pc.
"Auto highway" Eocortex Ultra module. License for 2 IP channels 1 pc.
"Auto parking" Eocortex Ultra module. License for 1 IP channel 1 pc.
If Eocortex Ultra server has any third-party software that uses HASP license
protection keys installed, Eocortex Ultra software with the license plate recognition
module enabled may be unstable on this server.
5.4.3. Installing and updating the module

The license plate recognition module is an external module: it is not included in the basic
Eocortex Ultra installation package and requires separate installation.
This module should be installed on both the computers with Eocortex Ultra Server or
Eocortex Ultra Standalone and on client computers with Eocortex Ultra Client used to
display license plate recognition channels.
Its version must match the version of Eocortex Ultra Server / Standalone / Client installed
on your computer. The latest version of the installation package is available on Eocortex
Ultra website.
Installation files must be launched by an administrator.
Eocortex Ultra
121
Default installation folder of the license plate recognition module:

 Bit depth
 Default installation folder
 Windows  Eocortex
 32-bit  32-bit  C:\Program Files\EocortexAuto
 64-bit  64-bit  C:\Program Files\EocortexAuto
 C:\Program Files
 64-bit  32-bit
(x86)\EocortexAuto
5.4.3.1. Installation
To install the license plate recognition module, follow these steps:
1. Stop all running Eocortex Ultra applications on your computer: Eocortex Ultra Server,
Eocortex Ultra Standalone, Eocortex Ultra Client.
2. Insert the license plate recognition module protection key into a USB-port of the
computer.
3. Run installation file EocortexAuto Installer.exe, if 32-bit Eocortex Ultra Server /

Standalone / Clientis installed; or EocortexAuto Installer_x64.exe, if 64-bit Eocortex Ultra
Server / Standalone / Client is installed.
4. Choose the language.
5. Follow the steps of the installation wizard.
Eocortex Ultra
122
6. Start Eocortex Ultra Server / Standalone; run Eocortex Ultra Configurator and
configure the license plate recognition module.
5.4.3.2. Update
If you update the license plate recognition module from version 1.9.x or later, no settings
are lost. If version 1.8.x or earlier is used, all the settings are saved except for the
selected patterns of license plates.
To update the license plate recognition module, follow these steps:

1. Stop all running Eocortex Ultra applications on your computer: Eocortex Ultra Server,
Eocortex Ultra Standalone, Eocortex Ultra Client.
2. Run installation file EocortexAuto Installer.exe, if 32-bit Eocortex Ultra Server /
Standalone / Client is installed; or EocortexAuto Installer_x64.exe, if 64-bit Eocortex
Ultra Server / Standalone / Client is installed. A window saying that the license plate
recognition module is already installed will appear; click OK.
3. A window prompting you to remove the module will appear; click Yes. Next window will
ask you to confirm the removal; click Yes.
4. A window showing the removal process will open afterwards. After the module is removed
a corresponding window will open; click OK.
5. This opens the installation wizard; click Next and follow the wizard steps.
6. Start Eocortex Ultra Server / Standalone.
7. If you were upgrading from version 1.8.x or earlier, run Eocortex Ultra Configurator and
select templates of license plates to be recognized.
If license plates are no longer recognized after the update, reinstall Eocortex Ultra
Server / Standalone. You do not need to reinstall the recognition module.
Eocortex Ultra
123
option Use external intelligence modules, and then enable License plate recognition
module in the list of available modules.
For correct operation of the license plate recognition module you must position
the camera correctly (see below).
If this module is not on the list, it means that the server has no license for this
module. To purchase the license, please contact the direct seller of Eocortex
Ultra licenses for this server. The list of available licenses can be found in
Configurator in 2. Servers tab in the Selected server License parameters
section.
The minimum width and height of the object in the motion detector settings
should be less than the size of the vehicle.
When using the detector expert mode, we recommend to select the whole frame
for motion detection in order to improve the reliability of recognition.
Eocortex Ultra
124
After the settings are completed, to save them, you must click OK, or exit without
saving by clicking on the close window icon. Also, you can reset all the settings to the
default values by pressing By defaultbutton.
The upper left corner contains the version of the library (SDK) used for recognition.
If the module protection key is installed, the License plate recognition will be specified:
Parking (6 fps) or highway (25 fps).
License plate recognition activates the license plate recognition mode. If this option is not
enabled, recognition will not be performed; this may be used in cases when the module is used
only to control the barrier.
Barrier control activates the barrier control mode.
If you plan to use the module only for barrier control, the License recognition license
is not required (just as the license plate recognition module protection key); however,
due to technical reasons the Eocortex Ultra license file (or software key) must support
license plate recognition module for the appropriate number of channels — for this
purpose contact the organization that sold you a Eocortex Ultra license for this server.
Eocortex Ultra
125
Determine motion direction activates the motion direction recognition mode. After checking
of this option, click Set direction of entry, then select the arrow, indicating the required
direction: vehicles moving in the scene in the direction of the arrow will be considered as an
entering, in the opposite direction — as leaving.
The Database settings parameter indicates the location of a license plate database. If
recognition is performed on only one server, it is recommended to check Local. When using the
multiserver configuration, if recognition is performed on multiple servers, the database can be
stored on a single server: in this case select Local for the channel assigned to the database
server and enter the IP-address of this server for all other channels. Default database connection
port — 3050, username — SYSDBA, password — masterkey.
For example: You have "Server 1" (IP-address: 192.168.1.1) and "Server 2" (IP-address:
192.168.1.2) merged together; channels "Channel 1" and "Channel 2" are assigned to
"Server 1", "Channel 3" and "Channel 4" — to "Server 2"; all channels perform license
plate recognition. If you want to store the database on "Server 1", enter "Database
settings" = "192.168.1.1" for all channels of the license plate recognition module.
No matter which server will be used to store the database, license plate recognition
events (date/time of recognition; recognized at a specified date/time; frame with the
recognized license plate) will always be stored on the server, to which the channel with
this module is assigned.
If the Barrier control option is enabled, the following features are available:
 Manual control — allows the operator to open a barrier in Eocortex Ultra Client.
 Auto (by recognized license plate) — opens a barrier automatically if the
recognized license plate is included in the "white list" (i.e., a group for automatic
opening.)
If automatic barrier controlis enabled, the following features are available:
 Open barrier — if the "white list" license plate is recognized it generates a command
for opening a barrier.
 Open and close through — if the "white list" license plate is recognized it generates
a command for opening a barrier; then, after a specified number of seconds, it
generates a command for closing.
Most of the modern barriers close automatically if a single vehicles passes through —
simply choose Open barrier for such barriers.
If you select Open and close through, a barrier must have an operating safety block
(i.e., after the command for closing is received, it must check whether a vehicle is still
and the barrier closes only if there is no vehicle.)
Eocortex Ultra
126
Ignore repeated occurrences of the same number plate (sec)— the period within which
the previously recognized license plate is not recognized again.
This setting is useful, in particular, for automatic barrier opening: if a vehicle stops in
front of a barrier and starts to move later its license plate can be recognized again. Such
problem may also appear if a license plate was temporarily covered by some object.
To adjust autosave of frames with recognized plates on disk, select Save frames on disk and
click Configure autosave. In the window that opens, select the folder in which you want to
store the frames, set its maximum size in the Folder maximum size, MBfield and click Save.
If the amount of saved files exceeds the maximum specified size, the oldest files will be
overwritten with new ones.
If Folder maximum size, MB is 0, the size will not be limited.
We recommend to configure frame autosave directly on the server, because in case of

remote settings the folder selection window will show the remote computer with
Configurator launched.
If you use a remote computer, enter the folder path by hand. The specified folder must
already exist on the server.
To select countries and plate templates to be recognized by the module:

Use and to move the required countries from the Available Countries list to the
Selected Countries list. If a country is not in the Selected Countries list, its license plates
will not be recognized.
If the list is empty, activate the module protection key. In this case save module settings,
apply the configuration and close Eocortex Ultra Configurator. Reinstall and restart
Eocortex Ultra Server / Standalone, then run Eocortex Ultra Configurator and continue
to set up the module.
Arrange countries in the Selected Countries list in the order in which you want to analyze
plates: when a plate is recognized, it will first be compared with samples from the first country
in the list; if no match is found — with the second one, etc. You can change the order by dragging
countries up or down.
For each country, select plate templates that will be recognized. To do this, select the country
in the Selected Countries list and use and to put the required templates from the
Available Templates list to the Selected Templates list. If a template is not in the Selected
Templates list, license plates of its type will not be recognized.
The more countries and patterns you select, the higher the server load is. If over 80%
of CPU are used recognition accuracy may be reduced.
By clicking of Set the size of the number plate button, window for setting of the minimum
and maximum width of the recognize license plate shall be opened.
Eocortex Ultra
127
Real time video stream from the tunable camera shall be broadcast in this window. To stop the
broadcast, click the Pause button. Archive button switches to playback from the archive (this
mode is convenient as it allows frame-by-frame playback when the mouse wheel rotates).
Using the scales of the settings, set the minimum and maximum width of the recognized license
plates. Dragging and resizing of the scales is performed with the mouse beyond the left or right
circular marker, respectively.
When setting of the size is completed, click Save button.
By clicking Set search zones button, window for setting the zones shall be opened, in which
the license plates will be recognized.
Real time video stream from the tunable camera shall be broadcast in this window. To stop the
broadcasting, click the Pause button.
One zone of the size of the whole frame is set by default. To create a new zone, press the left
mouse button and, without releasing the button, select a rectangular area. Cumulative area,
which combines all the selected zones, shall be used for recognition. To delete a zone, click
icon in the upper right corner of the zone.
When setting of the zones is completed, click Save button.
Eocortex Ultra
128
Quality of recognition is the internal module's parameter, which determines how the module
should filter the data: the license plates, recognition accuracy of which is below the certain
threshold, will be automatically discarded. The value of this parameter should be tuned
experimentally: as the value increases, the reliability of the recognized license plates will be
higher, but their total number may be less; With the decreasing of the value, number of
recognized license plates may be more, but number of failed recognitions increased.
For the first test run, it is recommended to leave the default parameter Quality of
recognition — they can be set later in order to achieve optimal recognition results.
Maximum number of not recognized number plates — filters plates by the number of
recognized characters: license plates with the number of unrecognized characters more than
specified will be automatically rejected.
To save the module settings, click OK button, then apply the configuration (go to the tab
6. Apply settings and click Apply button).
In the camera settings, in the Scenariosissue, you can configure additional actions for
the events Recognized license plates, Request to open gate and Request to
close gate.
The plate in the frame will be recognized only if the following conditions are met:
 license plate height is within the range between the specified minimum and
maximum size
 license plate fits completely in the search zone
 Eocortex Ultra software motion detector has detected movement
 license plate corresponds to one of the standard templates selected in the
module settings (see 10.4.3 on page 194)
 all conditions and restrictions on the size of characters, tilt angles and camera
position are met
If the recognition module on the server was enabled for the first time (during the
previous start of Eocortex Ultra Server / Standalone the recognition was not enabled
for any of the channels), then stop and restart Eocortex Ultra / Standalone server after
configuring the module. In case you change the settings of the license plate recognition
module later, restart of Eocortex Ultra Server / Standalone is not required.
Eocortex Ultra
129
5.4.5. Requirements and recommendations
5.4.5.1. Choosing a camera

Consider the following recommendations when choosing a camera:
 Your camera must support the B/W mode.
 Preference should be given to CCD cameras, if possible, of large size — not less than
1/3".
 We recommend using cameras with IR illumination (you can also use external IR
illuminators.)
 Manual exposure and aperture settings are desirable.
 The camera should operate in a "day/night" mode; automatic switch to B/W mode is not
important but such cameras have built-in automatic ICR filters (IR Cut Filter Mechanically
Removable) that filter IR only in day mode (filtering is not performed at night.)
5.4.5.2. Camera settings

In most cases, the license plate recognition is provided by default camera settings. In some
cases, if recognition is inefficient, you can use the following recommendations:
 Fully open the aperture.
 Set short or manual exposure — no more than 1/500.
 Turn off the auto-focus; adjust the focus to the desired recognition area.
 Enable the B/W mode.
 Disable additional information displayed in the frame (time, etc.)
 Disable AGC (Automatic Gain Control), if any, as this feature adds interference.
 Disable BLC (Back Light Compensation); this feature automatically prolongs the
exposure.
 Disable DNR (Digital Noise Reduction.)
 Disable WDR (minimum level.)
5.4.5.3. Camera position and field of view

Standard camera position on the road — 6 meters above the center of the controlled lane; the
control zone center is 20 meters away from the installation location.
Standard camera position to monitor entrances and exits from security areas — 3 meters over
the edge of the lane; the control zone center is 11 meters away at the traffic lane.
When you configure the field of view, consider the following limitations:
Height of license plate characters (big digits) — not less than 15 pixels, line thickness — at
least 2 pixels.
Eocortex Ultra
130
Camera vertical tilt — up to 40°.
Camera horizontal tilt — up to 30°.
License plate tilt angle relative to the roadway — up to 10°.
5.4.5.4. Requirements for obtained images of license plate

Car number will be recognized only if its image is in contrast and placed in the frame entirely.
Examples of the license plates images, that could be accurately detected:
Eocortex Ultra
131
Examples of the license plates images that will not be recognized:

 with a low contrast
 with a low resolution
 uneven lighting
 overexposed
 smudged (due to inconsistency between exposure length and vehicle speed)
 distorted (due to improper camera installation)
 interlaced
 dirty
Eocortex Ultra
132
When the camera is installed on the street, visual difficulty occur due to unfavorable
weather conditions (rain, snow). To increase the recognition rate in such conditions, one
can decrease the sensitivity of the license plate recognition.
5.4.6. Eocortex Ultra barrier operation

Eocortex Ultra controls barriers through signal outputs of IP cameras: signal (analog) camera
output is connected to barrier signal input — schematic connection diagram depends on the
layout of camera and barrier contacts.
To connect a barrier Eocortex Ultra software must support signal outputs for this IP
camera model. For more information contact Eocortex Ultra technical support.
To control a barrier:
1. Connect camera signal output to barrier signal input.
2. Set the barrier control scenario in Configurator (see below.)
5.4.6.1. Testing camera alarm outputs

To check whether the signal reaches camera alarm outputs:
1. Follow the scheme provided in camera documentation to connect test load to the signal
output (for example, tester or LED.)
2. Start Eocortex Ultra Configurator, go to tab 1. Cameras; in the channel list (on the left)
select the tested channel (camera.)
3. In the Channel connection settings block enable Event processing (I/O.)
4. Click to the right of the Event Processing (I/O) button to open the digital
input/output testing window.
5. Select the corresponding outputs — signals will be transmitted to camera outputs, test
load should trigger. To disable the signal, click outputs again.
Eocortex Ultra
133
6. Click OK to close the testing window.
5.4.6.2. Barrier control scenario

A barrier can be opened in two modes — manual and automatic.
In the manual mode, the operator opens (closes) a barrier using the on-screen control interface.
If Open is pressed, the system generates the Request to open gate event. If Close is pressed
— Request to close gate.
In automatic mode, a barrier opens if the license plate with the Open barrier for cars in this
group indicator is recognized. In this case the system generates the Request to open gate
event; if Open and close through is also enabled, then after a specified number of seconds
the Request to close gate will be generated.
In order to send an electric signal to the camera output after the Request to close (open)
gate, configure the appropriate scenario.
The scenario will perform the following after the Request to close (open) gateis generated:
 signal camera input is activated;
 a short pause follow;
 signal camera input is deactivated;
To set up an opening scenario:
1. Start Eocortex Ultra Configurator, go to tab 1. Cameras; in the channel list (on the left)
select the tested channel (camera) with screen control interface.
2. Go to the Scenarios block; in the event list (on the left), select Request to open
gate; in the drop-down list (on the top right) Send signal to camera output; click
to add the action.
3. Expand the action description by clicking on the left and adjust action parameters:
Eocortex Ultra
134
 Run in channels — by default the current channel is selected. If signal outputs of
another camera are used to control a barrier, change the value in this field.
 Limit by start time — allows limiting the signal frequency to avoid conflict if the scenario
is run for successive recognition events (set at least 2 seconds.)
 Output number — specify the camera signal output number.
 Output value — choose: 1 (Activated).
Depending on the circuit, the activation/deactivation of the alarm output may

correspond to different physical states of contacts: closed/open circuit,
presence/absence of voltage, etc.
4. In the dropdown list select Pause; click to add the action; go to action settings and
enter 1in the Pause Interval (sec) field.
5. In the dropdown list select Send signal to camera output; click to add the
action; enter 0 (Deactivated) in the Output value field; add other parameters from
step 3.
6. In the left pane of Configurator, click 6. Apply settings, click Apply on the opened page.
5.4.7. Troubleshooting and replacing of license plate recognition module protection

key firmware
5.4.7.1. Troubleshooting
If the license plate recognition module does not work at all or does not work properly, use the
following troubleshooting procedure:
1. Check if a protection key driver was installed and is working properly.
2. Check whether its sessions start.
3. Check the module settings.
Eocortex Ultra
135
5.4.7.2. HASP key driver
You can check the installation procedure by typing the following in your browser:
http://127.0.0.1:1947/_int_/devices.html
the license plate recognition key must be inserted.
Type in the complete address, including "http://".
If you see a window similar to the one shown below, HASP driver is installed correctly. The Key
ID contains the key identification number — in case of problems send this ID to our technical
support service. Protection keys may have two Vendor values — 106763 (AAOTB series) and
107392 (EOAWT series.)
If the window does not open, try another browser.

If attempts in other browser are also unsuccessful, it is likely that HASP driver is not installed or
is installed incorrectly.
In this case, you can try to solve the issue in several ways:
Restart your computer, since sometimes a reboot is required after driver installation.
If the driver window does not appear again, reinstall Eocortex Ultra Server / Standalone — HASP
driver will also be reinstalled. Restart your computer after reinstalling Eocortex Ultra Server /
Standalone.
All installation files must be run by an administrator.
You can install HASP driver separately: To do this, go to Eocortex Ultra installation package —
\Packages\Externals\HaspDrivers — and run haspdinst.exe installation file.
Eocortex Ultra
136
5.4.7.3. License plate recognition module key options
You can access options through the HASP driver web interface in your browser (Features tab)
or follow the following link: http://127.0.0.1:1947/_int_/features.html
The table below lists the available options.
Code Meaning Code Meaning Code Meaning
1 Highway 1 channel 214 Parking 14 channels 4026 Lithuania
2 Highway 2 channels 215 Parking 15 channels 4027 France
3 Highway 3 channels 216 Parking 16 channels 4028 Slovenia
Recognition module
4, 44 Highway 4 channels 4000 core, required 4029 Croatia
option
5 Highway 5 channels 4001 Ukraine 4030 Georgia
6 Highway 6 channels 4002 Russia 4031 Puerto-Rico
7 Highway 7 channels 4003 USSR 4032 Argentina
8 Highway 8 channels 4004 Bulgaria 4033 Germany
9 Highway 9 channels 4005 Colombia 4034 Spain
Highway 10
10 4006 Belarus 4035 Canada
channels
11, Highway 11
4007 Mexico 4036 Belgium
21 channels
Highway 12
12 4008 Italy 4038 Azerbaijan
channels
Highway 13 Bosnia and

13 4009 Finland 4039
channels Herzegovina
Highway 14
14 4010 Kazakhstan 4040 Hong Kong
channels
Highway 15
15 4011 Moldavia 4041 Denmark
channels
Eocortex Ultra
137
Code Meaning Code Meaning Code Meaning
Highway 16
16 4012 South Ossetia 4042 Macedonia
channels
201 Parking 1 channel 4013 Uzbekistan 4043 New Zealand
202 Parking 2 channels 4014 Turkey 4044 United Kingdom
203 Parking 3 channels 4015 Taiwan 4045 Singapore
204 Parking 4 channels 4016 Israel 4046 Netherlands
205 Parking 5 channels 4017 Hungary 4047 Switzerland
206 Parking 6 channels 4018 Romania 4051 Mongolia
207 Parking 7 channels 4019 Brazil 4052 Sweden
208 Parking 8 channels 4020 Transnistria 4053 Albania
209 Parking 9 channels 4021 Poland 4054 Japan
210 Parking 10 channels 4022 Slovakia 4055 Malaysia
211 Parking 11 channels 4023 Kyrgyzstan 4182 Nigeria
212 Parking 12 channels 4024 Czech Republic 4198 Portugal
213 Parking 13 channels 4025 Latvia 4249 Venezuela
Since the list of supported countries is constantly increasing, the table does not contain
all codes.
5.4.7.4. License plate recognition library efficiency

If Eocortex Ultra Server / Standalone is running and at least one channel is used for recognition,
then the Session field should have a non-zero value — this indicates that the license plate
recognition module is currently running. If the Session field is blank, it means that the module
is not running.
Possible causes and solutions:
Cause 1
None of the channels has license plate recognition enabled. The configuration was not applied
after enabling recognition. Eocortex Ultra was not restarted after applying the configuration.
Solution 1.1
Enable license plate recognition for at least one channel in Configurator. Apply configuration.
Restart Eocortex Ultra Server / Standalone.
Eocortex Ultra
138
Cause 2
Key license validity period has expired.
Solution 2.1
In some cases, a user may be given a testing protection key. The validity period for such keys
is limited. If the license has expired, open the key driver web interface, go to Features and
check Restrictions. It will say Expired.
Cause 3
HASP key conflict — license plate recognition module protection key conflicts with another HASP
key on your Eocortex Ultra server.
Solution 3.1
In order to make sure that Eocortex Ultra server does not use any other HASP keys for third-
party software, open the HASP driver web interface, go to Configuration, Access to Remote
License Managers (or follow the link: http://127.0.0.1:1947/_int_/config_to.html), deselect
all.
Then go to Sentinel Keys (http://127.0.0.1:1947/_int_/devices.html) and make sure there are

no other HASP keys used.
If other HASP keys are installed, remove them and leave only the license plate recognition
module protection key (Vendor — 106763 or 107392.) Restart Eocortex Ultra Server /
Standalone and check whether the module works.
If the module is working after other keys have been removed (Session contains a non-zero
value), reinstall Eocortex Ultra Server / Standalone or third-party software protected by HASP
keys to another computer.
5.4.7.5. Module operation

The following are typical problems that may arise during operation of the module, as well as the
solutions for them.
Eocortex Ultra
139
Problem 1
No license plates are recognized. License plates of a separate type or a particular country are
not recognized. Most of the plates in the frame are not recognized.
Solution 1.1
Customize license plate recognition templates. Change templates sequence in module’s settings.
Solution 1.2
Minimum and maximum plate sizes in the module settings may be incorrect. Set minimum and
maximum sizes so that they fit within the range between minimum and maximum limits.
Solution 1.3
Search zone in the module settings may be incorrect. Customize it so that the plates were inside
the zone. If multiple zones are used, then the license plate movement path in the frame should
not have gaps between zones. One simple rectangular zone is preferable to a complex zone
consisting of several smaller zones.
Solution 1.4
The software motion detector may be disabled or configured incorrectly. Enable and/or configure
the software motion detector and select motion detector in module setting.
Solution 1.5
Perhaps the image obtained from the camera does not allow in recognizing the number (for
example, it is not sharp enough, has interference or distorted fragments present.) Start Eocortex
Ultra Client, open the archive of the channel used for recognition and go to the frame containing
a license plate for recognition. Save this frame as TIFF or BMP; image resolution should match
the resolution of the frame received from the camera. Open the file in any image editor, in 1:1.
Image must be sufficiently sharp and distinguishable. If it is blurred or fragmented, configure
the camera to get a sharper picture (may require lens focusing or camera codec compression
rate adjustment.)
Solution 1.6
The camera position or the field of view may not comply with the recommendations set for LPR
module. Install the camera and adjust the field of view in accordance with these
recommendations.
Solution 1.7
If two streams are used by one camera, a high-resolution stream is required for recognition.
Open the channel settings in Configuration. If Use two streams option is enabled in Channel
data stream settings, make sure that Main is selected in the Stream selection for analysis
field in Intelligence analysis system settings.
Problem 2
Not all of the license plates in the frame are recognized. Some of the plates of the same type
and size and in the same zone are recognized and some are not.
Solution 2.1
See solutions 1.5 - 1.7 above.
Solution 2.2
Try to change the module settings: decrease threshold of reliability; increase the Number of
unrecognized characters, enable/disable Use auto scale and Use motion detector.
Solution 2.3
If the Parking license is used, recognition may not occur since vehicles move at a speed close
to or higher than 20 km/h.
In this case, if you want to increase the number of plates recognized, we recommend changing
the license type to Highway (note that the transition from Parking to Highway will significantly
increase the processing load on server CPU.)
Problem 3
Too many license plates are recognized incorrectly or incompletely (include asterisks "*".)
Solution 3.1
Try to change the module settings: increase The threshold of reliability; decrease the
Number of unrecognized characters.
Eocortex Ultra
140
Problem 4
When you select a recognized license plate in the Archive tab of the recognition window, an
empty frame or a frame with another plate is displayed.
Solution 4.1
Perhaps the camera uses two streams and the low-resolution (Alternate) stream was selected
for recognition (or archiving.) Open the channel settings in Configuration. If the Use two
streams option is enabled in Channel data stream settings:
- select Main in the Select recording stream field in Archiving settings (see 3.4.4 on
page 70);
- select Main in the Stream selection for analysis field in Intelligence analysis system
settings.
5.4.7.6. HASP key firmware

You may need to change the module protection key parameters. In this case, follow these steps:
1. Insert the key and open HASP driver web interface in browser, go to Sentinel Keys:
http://127.0.0.1:1947/_int_/devices.html. Record field values for Key ID and Vendor
and send them to the company you purchased Eocortex Ultra licenses from.
2. You will receive a utility (hasp_update.exe) to take a cast of your key:
each Vendor has its own utility but their user interface is the same.
3. Insert the key and run the utility, go to Collect Key Status Information, click Collect
Information and the file (*.c2v.) For convenience, we recommend naming it with the
value from Key ID.
4. Send the file (*.c2v) to the company you purchased Eocortex Ultra licenses from.
5. You will receive a firmware file with the extension *.v2c. Save it to your computer drive.
6. Insert the key and open HASP driver web interface in browser, go to Update/Attach:
http://127.0.0.1:1947/_int_/checkin.html. Click Browse and select the firmware file.
Click Apply File. The firmware will be changed in several seconds.
7. For the changes to take effect, restart Eocortex Ultra Server / Standalone
Eocortex Ultra
141
5.5. Crowd monitoring

The Crowd monitoring allows detecting crowds of people.
When configuring the module you have to specify the frame area to be monitored, as well as
two quantitative criteria (levels) — attention is required and allowable maximum levels. If the
number of people in specified frame areas exceeds one of these levels, an appropriate system
event will be generated. System events are used to configure scenarios, for example — for alarm
generation. Besides generating system events the module allows you to construct a graph
showing the number of people on a timeline.
The number of people is estimated analytically, on the basis of special-purpose

algorithms, so the estimate will be different from the actual one — degree of error may
amount up to 30%. One of the factors that affect the estimate is the speed of movement
of people in the frame: if people move fast enough — the estimated amount will be
higher than the actual; if people in the frame move very slowly or stand still — the
estimated amount will be lower than the actual.

analysis system settings section, enable and configure Motion detector and Perspective
settings, then enable the option Use external intelligence modules, and then enable Crowd
counting module in the list of available modules.
Eocortex Ultra
142
section.
Detection zones (no more than six), in which the number of people will be counted, are set in
this module:
To add a zone, click button (placed above the list of zones, on the left).
To delete a zone, select the zone in the list and press button.
To change the zone, select the zone in the list and execute one of the following actions:
• change the size of the zone — click on one of the square markers on the boundaries of the
zone and, while holding the mouse button, drag the border;
• move the zone — click the mouse inside the zone and, while holding the mouse button, drag
the zone.
Calculation of the people in each zone is performed independently, so the zones should
not overlap each other — otherwise people in the overlapped area will be counted twice.
To select the entire frame, click Select full frame button. When you activate the module
on a channel for the first time, such a full size zone is already created by default.
To facilitate adjustment, you may stop the video playback by clicking Pause button.
To avoid calculation errors on the boundaries of the zones, use (if possible) fewer zones.
Several zones are worth using, for example, in the following cases:
 if a road and a sidewalk is in the frame, controlled area should include only
the sidewalk;
 If a rest area, which is crossed with a path with intensive pedestrian traffic
is in the frame and it is required to avoid the crowd in the rest area, then the
controlled area should exclude the path.
For each zone, you should specify the limits for the number of people in the fields
Allowablemaximum ("Alert") and Attention is required ("Warning").
Eocortex Ultra
143
To save the module settings, click Save button (or Cancel button to discard the changes), then
apply the configuration (go to the tab 6. Apply settings and click the Apply button).
The module will be "learning" for 10-15 seconds — counting data for this period will be
incorrect. Since this "learning" process includes the record of stationary background to
provide more accurate results, it is recommended to perform it with a minimum number
of moving and outside objects in the frame.
5.5.2. Configuring cameras

For correct operation of the module it is recommended to install the camera as high as possible,
at such angle that, first, allows distinguishing human figures; second — so that figures of people
in the foreground do not overlap those in the background. Examples of correct camera images
for crowd counting are given below.
The minimum size should possibly eliminate or minimize false detector triggering (for example,
from shadows, glares or small objects that are not people.) If simple detector settings do not
eliminate false motion detector triggering, perform the expert setting in software motion
detector.
Eocortex Ultra
144
5.6. Heat map module
The heat map moduleis designed to visualize the traffic density in various areas of the frame.
A heat map is formed by summing up the time during which a movement was observed in a
certain point — as a result the areas where objects stay more often and for the longest time are
highlighted.
A color scale is used to visualize the traffic density: areas are overlaid with transparent color
stains according to the traffic density in a video image. For example, if you use a four-color
scale, red color denotes high density areas, blue — low density; green and yellow colors are
transient.
The heat map modulecan be used to determine the popularity of different places (racks,
cabinets) in a store, preferred routes for people or vehicles, as well as to analyze visit statistics
of various objects.
There are three options for using heat maps: real-time mode, scheduled report and camera field
of view overlaid on an object plan. In the real-time mode only areas with movement for the last
10 seconds are displayed in the frame. The scheduled report sets the interval of time used to
analyze traffic density in the frame. Camera field of view overlaid allows creating a heat map
not only in the frame but also on an object plan.

option Use external intelligence modules, and then enable Heat map module in the list of
available modules.
section.
If you want to save the heat maps, superimposed on the camera's view on the object's plan,
press button, placed to the right of the module name; enable the option Automatically
save plugin data on plan in the opened window, set Unload data every and Path of files,
then click Save button (or Cancel button to discard the changes).
Eocortex Ultra
145
To save data on a plan, create an object plan with this camera and its field of view
indicated (see Object plans).
After the activation of the module, you should apply the configuration (go to the tab 6. Apply
settings and click Apply button).

For correct operation of the module it is recommended to install the camera as high as possible
to minimize the effects of perspective — overlap of foreground objects on background. The ideal
position is on top, at a right angle to the horizon.
Eocortex Ultra
146
Eocortex Ultra
147
5.7. Auto Zoom
The Auto Zoom function displays a separate enlarged area with moving objects.
For more information on working with this function in Eocortex Ultra Client and
5.7.1. Configuring the function

option Use external intelligence modules, and then enable Heat map module in the list of
available modules.
Auto zoom does not require additional licensing.
When the function is activated, apply the configuration (go to the tab 6. Apply settings and
click Apply button).
Eocortex Ultra
148
5.8. Face recognition module
The face recognition module is designed for automatic identification of person by using the video
image. It recognizes faces captured by a face detector by comparing them with a previously
created database of reference images.
The face recognition module provides a high percentage of recognition and can be used in
conjunction with an access control system in order to improve the control of access to facilities
with high security requirements, such as banks or classified facilities. Another important
application field is the automation of face control in casinos, hotels, restaurants and other similar
facilities.
This module can be supplied in one of two versions: Expert and Basic. Each version uses its
own recognition engine (SDK) and database. However, the user interface and settings for each
version are not different.
If you want to implement joint verification based on access cards and video image, use
Eocortex Ultra in conjunction with one of the integrated third-party access control
systems.
The module is not designed to recognize individuals in a random stream of people — in

the streets, railway stations, supermarkets, etc.
5.8.1. Installing and licensing the module

The face recognition module is an external module: it is not included in the basic Eocortex Ultra
installation package and requires separate installation and license.
Face recognition module license protection is provided by means of a software HASP key.
When you apply a software key the license is assigned to a specific computer and can
not be reinstalled to another computer later. It is assigned to computer motherboard
and hard drive.
For the Basicversion, at least 2.6 GB of additional memory is required.
The license for the Basic version is very sensitive to changing the configuration of the
computer. For example, a connected USB drive triggers protection and the module
stops working.
The module must be installed only on the computer on which Eocortex Ultra Server or
Eocortex Ultra Standalone is installed. On computers on which Eocortex Ultra
Clientis installed and the recognition channels are being viewed, the module is not
required to be installed.
The version number of the module must match the version number of the Eocortex
Ultra Server / Standalone / Client installed on this computer.
Running the installation files must be performed under the administrator account.
If you need the installation package please contact Eocortex Ultra technical support.
Eocortex Ultra
149
To install the module, stop all running Eocortex Ultra applications on your computer and run
EocortexFace Installer_x64.exe (or EocortexFace Installer_x86.exe).
Select the installation language in the opened window and click OK:
Installation wizard shall be opened; click Next and follow the wizard steps.
Then select the version of the module (Expert or Basic), then either Generate the key
configuration file, or Skip and install without a license.
If you select Generate the key configuration file and click Next, the folders overview window
shall be opened, in which you should specify the folder for saving of the key configuration file
(file name, depending on the module — hardwarekey.cfg or face_sdk.lic).
After creation and saving of this file, a window with information about further actions shall be
opened.
Eocortex Ultra
150
Send the key configuration file to the organization, where you purchased the face recognition
module from. In response, the key activation file with the same name will be sent.
After receipt of the key activation file, run the module installation wizard, at the following step
select Activate the license and Install the key activation file, at the next step specify the
path to the key activation file and click Next.
When you run the installer with the selected version of the module for the first time, components
of this module will be installed on the server.
Eocortex Ultra
151

option Use external intelligence modules, and then enable Face recognition
module(Expert or Basic) in the list of available modules.
section.
One camera is allowed to use only one version of the face recognition module:
either Expert or Basic.
In the settings of the software motion detector, the minimum width and height
of the object should be smaller than a face.
When using the detector expert mode, we recommend to select the whole frame
for motion detection in order to improve the reliability of recognition.
Eocortex Ultra
152
 Minimum and Maximum size of the face — limits for recognized faces. Excludes too
distant or too close face from recognition. These parameters can be configured
interactively.
 Confidence coefficient — internal module parameter that filters faces by recognition
quality: if the quality is below a predetermined threshold, such face will be automatically
rejected. This parameter should be selected experimentally — if the value is too low some
faces can be recognized incorrectly; if it is too high — some faces may be not recognized
at all, since the system will mark them as poor quality ones. Note that the higher the value
is, the greater is the consumption of system resources (CPU, RAM used by the application.)
 Balance between accuracy and speed of identification — the module inner
parameter; it allows, depending on the available hardware resources, adjusting the balance
between speed and accuracy with regard to RAM and CPU usage during recognition.
 Card-file settings — specifies the location of a face database. If recognition is performed
on only one server, it is recommended to check Local. When using the multiserver
configuration, if recognition is performed on multiple servers, the database can be stored
on a single server: in this case select Local for the channel assigned to the database server
and enter the IP-address of this server for all other channels. By default: database
connection port — 3050, username — SYSDBA, password — masterkey.
Eocortex Ultra
153
 For example: You have "Server 1" (IP-address: 192.168.1.1) and "Server 2" (IP-address:
192.168.1.2) merged together; channels "Channel 1" and "Channel 2" are assigned to
"Server 1", "Channel 3" and "Channel 4" — to "Server 2"; all channels perform face
recognition. If you want to store the database on "Server 1", enter "Database settings" =
"192.168.1.1" for all channels of the face recognition module.
No matter which server will be used to store the database, face recognition events
(date/time of recognition; recognized at a specified date/time; frame with the
recognized face) will always be stored on the server, to which the channel with this
module is assigned.
To save the module settings, click OK button, then apply the configuration (go to the tab
6. Apply settings and click the Apply button).
5.8.3. Guidelines and requirements

Standard camera position — at the guard desk or at the door; at face level or at a slight angle
— to provide the best overview of faces.
Changes in lighting and facial expressions — as compared to the reference sample — can
significantly reduce the likelihood of detection, so you must ensure the following
recommendations:
 provide uniform and constant lighting of recognized faces;
 people must maintain a neutral expression during recognition.
Examples of the effect of lighting on the probability of recognition:
Glares Strong Strong

Additional side Strong
Parameter Original from overhead overhead
light daylight
glasses lights lights
Image
Probability 1 0.94 0.65 0.32 0.41 0.03
Eocortex Ultra
154
Examples of the effect of poses and facial expressions on the probability of recognition:
Camera
Face
databas
e
Recognition probability
The distance between the pupils of recognized faces in the frame should be at least 60 pixels.
5.9. Abandoned object detector

This intelligent module is designed to detect abandoned objects — if an object is left in the frame
for over the specified period of time, the operator receives a corresponding alarm and the object
itself is "highlighted" on the screen.

option Use external intelligence modules, and then enable Abandoned object detector in
the list of available modules.
Configurator in 2. Servers tab in the Selected server License parameters block.
Eocortex Ultra
155
Specify no more than three detection zones, in which to search for abandoned objects.
To add a new detecting zone, click , to remove it .

Detecting zone in the Zone mask area is filled with yellow squares. To change a detecting zone,
use your mouse: left button is used to fill a zone and right one to clear it.
To select the entire zone, click Fill all; click Clear to deselect the entire zone at once.
Use the slider to change the selection brush size.
Specify minimum and maximum object sizes for each zone in this module: To do this, select
a zone in the list and specify sizes — either by using sliders or interactively (Set in interactive
mode...).
Indicate detection time for each zone — the time interval after which an object will be
considered abandoned. The system provides two levels of notification:
Attention — an abandoned object is highlighted by an orange frame on the operator's screen.
If the operator reacts to this warning (clicks the mouse inside the frame), the alarm for this
object will not be generated.
Alert — an abandoned object is highlighted by a red frame; at the same time an alarm is
generated and the system creates a corresponding alarm event.
To set the detection time, select the appropriate zone in the list and then specify time periods
for Alert and Warning.
If Warningis not selected, this level will not be used for the corresponding zone.
Eocortex Ultra
156
apply the configuration (go to the tab 6. Apply settings and click the Apply button).
5.10. People counting in queue module

The module is designed to count people in queues in the field of view of IP cameras connected
to Eocortex Ultra servers.

option Use external intelligence modules, and then enable People counting in queue
module in the list of available modules.
this server. The list of available licenses can be found in Configurator in 2. Servers
tab in the Selected server License parameters section.
Eocortex Ultra
157
Specify no more than six detection zones, in which to count people.
To add a new detecting zone, click , to remove it .

To change a zone, select it in the list (to the left) and choose one of the following:
change zone size — click one of the square markers on the zone boundaries ( ), hold the
mouse button and drag it;
move zone — click the zone, hold the mouse button and drag the zone.
Set unified sized of counted objects (people) for all zone using the green rectangle — its
configuration is similar to zones.
The module works in one of two modes:
 counting people in the queue;
 long stay in the queue.
In the mode of counting people for each zone, in the Allowable maximum ("Alarm") field,
specify the limit on the number of people in the queue. If this value is exceeded, event A large
number of people in the queue will be generated.
If you enable the Long stay in the queue mode, specify the Delay time in the queue (sec).
If this value is exceeded, the event A large number of people in the queue will be generated.
The following settings are also available in this mode:
 Simple or Expert module operating methods. The expert method provides more accurate
operation of the module.
 Sensitivity of the algorithm. It is recommended to be used for fine tuning of the module in
those cases when the default value does not provide the required accuracy.
Eocortex Ultra
158
For the Long stay in the queue mode the control zone should be set to cover only
the intended end of the queue: it is implied that people will stay in this area only if the
queue is "full". In this case, people who quickly cross this zone will not be counted.
apply the configuration (go to the tab 6. Apply settings and click Apply button).
Eocortex Ultra
159
For correct operation of the module it is recommended to install the camera as high as possible
to minimize the effects of perspective — overlap of foreground objects on background. The ideal
position is on top, at a right angle to the horizon.
Eocortex Ultra
160
5.11. Fisheye cameras dewarping module

This intelligent module is designed to dewarp images from fisheye cameras.

For activation of the module, follow these steps:
Start Eocortex Ultra Configurator, go to tab 1. Cameras; in the channel list (on the left), select
the channel to be used for Fisheye camera module; in the channel settings (on the right) open
the Archiving settings block; select With detector + manual.
Open the Intelligence analysis system settings and enable software motion detector.
Select Use external intelligent modules in the Intelligence analysis system settings
block. The list of available modules will open, including Fisheye cameras dewarping module.
Select the Fisheye cameras dewarping module — the Settings button will appear.
Eocortex Ultra
161
Click to open the module settings window.
Specify the image radius and the direction of default view. To do this, click the image boundary:
circumscribed circle should match with the boundary of the image from the camera; the arrow
will point in the direction of default view.
Eocortex Ultra
162
5.12. Activity monitoring module

The module is designed to track the activity of employees at workplaces. Activity means
recording movement in the working area, including minor changes.

the channel to be used for Activity monitoring module; in the channel settings (on the right)
open the Archiving settings block; select With detector + manual.
block. The list of available modules will open, including Activity monitoring module.
Select Personnel monitoring module — will appear.
Eocortex Ultra
163
Specify no more than six detection zones, in which to observe activity.
To add a new monitoring zone, click , to remove it .

Detecting zone in the Zone mask area is filled with yellow squares. Use the mouse to change
monitoring zones: The left button is used to fill a zone and the right one to clear it.
Requirements for zones:

zones should not overlap;
only one employee should be inside each zone (subject to small movements — leaned
back, pulled back in a chair, etc.);
zones shall not include moving objects that do not depend on the activity of employees
— fans, conveyors, moving equipment parts, etc.
zones shall not include monitors.
Set inactive time for each zone — time period, after which the system will signal about
inactivity.
Eocortex Ultra
164
Inactivity does not mean an employee is absent — for example, a person can sit still
or fall asleep. Activity, in turn, does not mean an employee is present — it can be result
of, for example, other employees in the zone.

The camera must be fixed at a view. Most preferred position is a ceiling mount camera facing
downward — to visually isolate the workplace of each employee.
5.13. Smoke and fire detection

The module is designed to detect smoke and open flames in the frame.

the channel to be used for Smoke and fire module; in the channel settings (on the right) open
the Archiving settings block; select With detector + manual.
block. The list of available modules will open, including Smoke and fire detector.
Select the Smoke and fire detector — the Settings button will appear.
Eocortex Ultra
165
Select detection option: Smoke or fire, Only smoke or Only fire.

Eocortex Ultra
166
5.14. Suspect tracking
Suspect tracking allows to construct the trajectory of human movement between the cameras,
as well as to create a video or slide show on its basis.
Technique for work with the module in Eocortex Ultra Client and Eocortex Ultra
Standalone view window is described in the "Eocortex Ultra User's Guide".
Suspect tracking — it is not a single intelligent module, but a special functionality implemented
in Eocortex Ultra Client and using the built-in intellectual analysis options in Eocortex.
Below are the requirements and recommendations for configuring the channel on which the
Suspect tracking will be implemented.
Suspect tracking is performed only on the channels with the Suspect Search and Indexing of
moving objects by signs options included.
The minimum permissible parameters of the image, in which the search can work by signs are
the following: resolution - 640x480 pixels, frequency - 5 frames / sec. Image parameters
recommended for good performance of Suspect tracking: resolution - 1920х1080 pixels,
frequency - 25 frames / sec.
It is recommended to Set the perspective settings and Enable classification by proportions to
maximize the quality of Suspect tracking.
Eocortex Ultra
167
6. Eocortex System Healthcheck
The Eocortex System Healthcheck subsystem monitors the fail-safe and performance of the
components of Eocortex. video surveillance system
Parameters monitored by Eocortex Ultra Monitoring are the following:
 Availability of hosts (computers or virtual machines, where which Eocortex Ultra servers
are installed);
 CPU, RAM and network adapters utilization of Eocortex Ultra servers;
 Availability of cameras connected to Eocortex Ultra servers;
 State of the subsystems of recording to the archive of Eocortex Ultra servers;
 Client connections to Eocortex Ultra servers
Infrastructure of Eocortex System Healthcheck:
 Monitoring Server is a service (EocortexMonitoring), launching automatically, when
operating system is run on the server with installed Eocortex System Healthcheck
component. Functionality of the Monitoring Server:
 Collection of information on the status of the system components from the Monitoring
Agents;
 Sending of e-mail notifications about the critical events;
 Web-server, providing interaction with the Web-client.
 Monitoring Agent is a service (EocortexMonitoringAgent),launching automatically when
operating system is run on the server with Eocortex Ultra Server or Eocortex Ultra
Standalone installed. Monitoring Agent provides the Monitoring Server with the
information concerning the state of both the computer running the agent and the Eocortex
server and its components installed on this computer.
 Monitoring Web-client is the web-application, which is launched in the web-browser and
allows to monitor the current state of the components of the Eocortex Ultra system.
Eocortex System Healthcheck is installed from the common distributive when choosing the
appropriate option (see Installing Eocortex Ultra software from a common installer). It is possible
to install Eocortex System Healthcheck on the computer without installation of Eocortex
Ultra Server / Standalone.
Monitoring Agent is installed from the common installer automatically when installing
Eocortex Ultra Server / Standalone.
Eocortex Ultra
168
6.1. Eocortex System Healthcheck configuration
To configure Eocortex System Healthcheck, start the Eocortex Ultra Configurator and go
to 2. Servers tab, then in Eocortex System Healthcheck settings group check Enable
Eocortex System Healthcheck checkbox and press Configure Eocortex System
Healthcheck button.
Specify the settings of Eocortex System Healthcheck in the opened window. To save the
settings, click the Save button, then apply the configuration (go to the tab 6. Apply settings
and press Apply button).
Description of the settings is specified below:

System Healthcheck address is the IP address or URL of the computer which will be used as
a monitoring server.
System Healthcheck password is a password, providing access to the settings and viewing
of Healthcheck information. This password is set only in the Web-client, so already existing
password shall be specified here. Immediately after the component installation, the password is
blank by default, so in the course of first monitoring activation this field shall be left blank, but
when the password is changed in the Web-client, the value of this field need to be changed.
Interval between the data sent is the interval of time, in which the system status data shall
bel updated.
Servers controlled by System Healthcheck - monitored servers should be specified in this
group of settings.
If you need to send an e-mail notifications concerning the critical events, press Configure the
e-mail notifications button and set the sending options in the opened window.
Eocortex Ultra
169
6.2. Web-client
For activation of the Web-client page, enter the following:
http://address_or_name_of_monitoring_server:8889/in the address bar of the web-
browser.
(examples: http://192.168.200.161:8889/, http://eocortex-1.mycompany.com:8889/).
Specification of the port:8889/is mandatory. Port number cannot be changed.
Enter the System Healthcheck password in the opened authorization form and press the Login
button.
Immediately after component installation, System Healthcheck password is blank by

default.
If the login is successful, the System Healthcheck Home page opens (see below).
If System Healthcheck is not enabled in the configurator, or no servers are configured

in the System Healthcheck settings, Help page shall be opened.
Description of the Web-client pages is specified below.
Eocortex Ultra
170
6.2.1. Home page
Links Settings, Help and Logout are located in the upper right corner of the page, as well as
the language selection buttons. Working area of the page contains Servers list and Events Log
(digest).
To go from any page to the Home page, click on the logo in the upper left corner.
Page elements:
Servers list is a list with the names and addresses, number of bound cameras (where X/Y is
currently available/totally bound), and percentage of CPU utilization. By clicking on the server
line Main server's info page is opened (see below).
Events log (digest) is a short list with information concerning the last critical events:
date/time of the event, server on which the event is registered, and description of the event.
By clicking on the More Events link Events Log page is opened (see below).
Eocortex Ultra
171
6.2.2. Events Log page
List with information about the critical events is displayed on the right side of the page(in the
reverse chronological order): date/time of the event, server on which the event is registered,
and description of the event.
Filters bar, which allows filtering events by various parameters, is placed on the left side of the
page. For display of the filtered events, specify the conditions, and then press the Refresh
button.
6.2.3. Server's info pages
Eocortex Ultra
172
Eocortex Ultra
173
By clicking on the camera, the information page for this camera is opened:
Eocortex Ultra
174
Eocortex Ultra
175
By clicking on the name of the network interface, the information page for this interface is
opened.
Eocortex Ultra
176
6.2.4. Settings pages
Eocortex Ultra
177
7. Additional features
7.1. Driver package for cameras and devices (DevicePack)

Starting with version 12.0, a driver package for cameras and devices (DevicePack) is provided
separately along with the updates server and client Eocortex Ultra software. This package is
designed primarily for backward compatibility with earlier versions of Eocortex Ultra server
software. We do not recommend to use the package to operate new cameras and devices
(without updating the Eocortex Ultra Server / Client / Standalone executable package.)
DevicePack can only be used only for Eocortex Ultra software 1.12.* and more. Earlier
versions (up to 1.11.*) are not supported.
DevicePack is installed into a separate directory (by default — C:\Program Files\Eocortex

Ultra IP Device Pack.) Thus, it can always be removed without affecting other installed
Eocortex Ultra packages.
DevicePackis installed on the computer with Eocortex Ultra server software installed (for
multiserver configuration — on each server.) If certain channels have the Connect via server
option disabled, DevicePackis also installed on each computer used to view these channels in
Eocortex Ultra Client.
Eocortex Ultra software interacts with DevicePack as follows: At startup Eocortex Ultra
Server / Client / Standalone checks whether this computer has DevicePack installed; if yes,
plugins from the DevicePack folder are used to connect to cameras; if no, plugins from the
Eocortex Ultra Server / Client / Standalone installation folder are used.
7.1.1.1. Installing DevicePack

To install DevicePack, run the installation file EocortexIPDevicePack Installer_x64.exe if
you have 32-bitEocortex Ultra Server / Standalone / Client or EocortexIPDevicePack
Installer_x64.exe if you have 64-bitEocortex Ultra Server / Standalone / Client.
Eocortex Ultra
178
7.1.1.2. Removing DevicePack

You can remove DevicePack via Start / All Programs / Eocortex Ultra IP Device Pack /
Remove IP Device Pack or by using standard Programs and Features from Windows
Control Panel.
Restart Eocortex Ultra server software after removing DevicePack.
7.2. System log files

To fasten the technical support process we recommend you to send system log files to our
support service. To do this, use the Pack Logs tool. Below is the procedure for packing and
sending logs.
Start the program by going to Start / All Programs / Eocortex Ultra Server (Client,
Standalone) / Service Tools / Pack Logs. The program window opens:
To archive all logs at once, click Process logs archiving.... The warning (informational) window
will open, then the window where you will need to specify the destination folder and archive file
name. Wait for the archiving to complete.
To open a folder with logs and manually archive the required file, press Open logs folder.
Send saved file(s) by e-mail to our technical support service.
Eocortex Ultra
179
7.3. Viewing archives in case of failures
If you have problems viewing the archive in Eocortex Ultra Client, use the Local archive view
and archive backing up application:
1. Start the program by going to Start / All Programs / Eocortex Ultra Server (Client,
Standalone) / Service Tools / Local archive view and archive backing up. The
program window opens.
2. Click Active folders auto search to automatically find all folders in which the archive is
stored.
3. If folders are not found, click to manually select a folder, from where you want to copy
files.
To export one channel archive:
4. Select the channel type from the list in Filter by channel type.
5. Select the name of the channel you want to copy.
Click Archive export to export the archive in MCM or AVI. MCM file can be viewed in Eocortex
Ultra Player.
Additional parameters will allow you what all export file needs to include.
Eocortex Ultra
180
To back up multiple channels:
4. Click Backup.
5. In the window that opens, select channels, set the required time interval and the folder to
store the backup in. Click Start.
Eocortex Ultra
181
7.4. Optimal camera settings
Although Eocortex Ultra can operate with one or two streams from cameras of any resolutions,
note that the load on video servers greatly depends on parameters of streams received from the
cameras. It is also important to consider the configuration and operation process of Eocortex
Ultra software itself.
For most cameras, configure the video and audio parameters on the camera itself by means of
web interface. This does not relate to Axis cameras that can be configured in Configurator.
Software motion detector (Eocortex Ultra motion detector)
Software motion detector analyzes the video stream received from the camera and signals the
system if any motion is detected: the signal can mean, for example, start recording (e.g. motion
detector recording.)
Motion detector uses a certain amount of server system resources (CPU, RAM.) The usage rate
is linearly dependent on the resolution and frame rate. For example, CPU load when using motion
detector will be: about 6 times higher for 1920x1080 than for 640x480; for analysis at 25 fps
will be 4 times higher than for 6 fps.
At the same time, motion detector recording reduces the archive size since the stream is
recorded only if there is a movement detected. For a software motion detector to not trigger at
minor events (e.g., shaking leaves or birds), you can configure it to record moving objects of a
certain size.
In addition, it is used in all intelligent modules. Therefore, if intelligent modules are used,
software motion detector must always be enabled.
Many cameras have their own built-in motion detectors (in Eocortex Ultra terms — "camera
motion detector/ in-built motion detector.") System resources are almost not used if camera
motion detector is operating.
Recommendations for setting the motion detector:
If you need continuous recording and do not use intelligent modules, we do not recommend
enabling the detector. Instead, you can select a permanent archiving mode. This is possible, for
example, if objects move in the frame for 24 hours (continuous production, major railway
station, etc.)
If a camera has a built-in motion detector and intelligent modules are not used, it is
recommended to use a camera motion detector. Although it is sometimes preferable to use the
software motion detector: for example, if there is a large number of identical cameras and setting
motion detection on each camera requires a lot of effort (in Eocortex Ultra you can enable motion
detection for a group of cameras at once or set up one camera and then clone it by changing
the network address.)
If you use intelligent modules, software motion detector must always be enabled.
Besides, you can configure the combined archiving mode (in Eocortex Ultra terms — scheduled
mode.) For example, at the entrance to a shopping center constant movement is observed from
10:00 to 22:00 but at other times there should be no motion. Then you can adjust the schedule
as follows: from 10:00 to 22:00 — continuous recording (this will reduce server load); from
22:00 to 10:00 — motion recording (this reduces video archive size.)
Eocortex Ultra
182
In the software motion detector settings you can select two modes of operation: simple and
expert.
In simple mode, you can set the minimum object size for the entire frame. Analysis in this mode
is carried out with the optimal frequency (see below.)
In expert mode, you can set detection zones (minimum object sizes are defined separately for
each zone.) You can also specify the analysis frequency:
Detect by using optimum frequency — video analysis and motion detection will be carried out at
a frequency defined automatically according to the following rules:
- if at least one intelligent module is enabled for a channel (suspect search, face detection,
people counting, tracking), the analysis is performed at 10 frames/s;
- if no intelligence modules are enabled, the rate for MJPEG is 5 frames/s, for H.264 and
MPEG-4 the frequency is automatically selected from the range of 0.4–5 frames/s.
Detect by using customized frequency — video analysis and motion detection will be carried out
at a customized frequency.
Manual frequency makes sense if the optimal one is clearly above or below the value necessary
and sufficient for analysis or when you require fixed analysis frequency for H.264 and MPEG-4.
Recommended frequency for a particular intelligence module is given in the documentation for
each module.
Using two streams
Most modern IP cameras support two or more streams simultaneously. The use of two streams
allows recording high resolution frames in the archive and displaying low resolution frames in
the client, which can significantly reduce the equipment load.
In terms of Eocortex Ultrathe first stream is called main and the second is called alternate.
When the channel is configured to use two streams, the stream displayed in Eocortex Ultra Client
is selected which has resolution closest to the playback window size.
For example, there is a channel that receives two streams from the camera: 1920x1080 and
640x480. Client workstation is equipped with a 1920x1080 monitor. Then, in the multi-screen
mode (channel grid), with a 3x3 grid, the resolution of a single cell will be 640x360 (1920/3 =
640, 1080/3 = 360); therefore, the 640x480 stream will be used. If you maximize the channel
the 1920x1080 stream will be selected.
If two streams are used Eocortex Ultra records the main stream to the archive by default.
However, you can change this setting in Configurator and record the alternate stream.
When using the software motion detector you can choose which of the streams will be analyzed.
If, no intelligent modules except for software motion detector are used, we recommend selecting
a lower resolution channel, as this can significantly reduce server load.
However, if intelligent modules are used, a higher resolution stream should be used. This is due
to the following factors: intelligent modules record the coordinates of objects corresponding to
certain analysis parameters and record these coordinates to the archive; the alternate stream
resolution may not be sufficient for analysis; the aspect ratio (frame proportion) of main and
alternate stream may vary; streams of different resolutions sent by the camera often are not
synchronized precisely, in some cases stream can be out of sync for a second or more. Thus, if
you archive high-resolution stream and analyze low-resolution one, there can be a situation
when a frame that does not contain the desired object will be extracted from the archive (for
example, due to out of sync or different frame proportions.)
Eocortex Ultra defines a first stream as the main one and the second — as the alternate one.
We recommend selecting a high-resolution stream as the first (main) one and a low-resolution
as the alternate one. Thus, whenever possible, the frame rate of the main stream should be
sufficient. For example, if you record an office building and intelligent modules are not used, 6
fps is sufficient for a high-resolution archive (its size will be significantly lower than at 25
fps); low-resolution stream can be set at 12 or 25 fps.
Camera settings
Below is a list of terms that may be encountered in camera settings:
Stream
First (Main) stream
Second (Alternate, Sub) stream
Encode Mode, Codec
Eocortex Ultra
183
Eocortex Ultra supports the following compression formats: MJPEG, H.264 and MPEG-4.
MJPEG, compared with others, requires fewer resources (less load on server and client
computers.) On the other hand, MJPEG video stream has a substantially greater size: MJPEG
video requires several times more bandwidth and MJPEG video archive uses several times more
disk space than H.264 and MPEG-4 video with the same parameters (resolution and frame rate.)
H.264 is the most "economical" in terms of format but it requires large, compared to MJPEG,
computing costs for decoding.
MPEG-4 is similar to H.264 but has a lower compression ratio (i.e., MPEG-4 has a bigger channel
width and archive size than H.264 but much less than MJPEG.) In modern cameras MPEG-4 is
almost never used — it is replaced by a more advanced H.264.
Compression
All formats use such concept as the compression rate: the higher it is, the smaller is the video
size. The size is reducedat the cost of image quality. Depending on surveillance conditions and
camera hardware features, the acceptable compression rate may be from 30 to 60%, although
it can be from 0 (minimum compression) to 70% (maximum compression.) Except for percent,
the compression rate in camera settings can be defined (Compression Level), for example, from
0 to 12. Besides, quality is the reciprocal of the compression rate (in simple words, Compression
= 10% means to Quality = 90%). Set the compression rate based on the quality of received
image.
Resolution
Frame Rate(FPS)
In addition to the above mentioned, the H.264 stream settings can include the following
concepts:
Profile:
Baseline Profile,
Main Profile,
High Profile
Bit Rate Type
VBR, Variable Bit Rate. It provides set video stream parameters, the channel width may vary.
This mode is recommended in most cases, if there are no problems with network bandwidth.
CBR, Constant Bit Rate. It provides a set bandwidth but, depending on the camera model, may
change separate video stream parameters, the channel width may vary. This mode is
recommended only if you have problems with network bandwidth.
Bit Rate — Kbit/s, Mbit/s.
GOV(GOP group)
Specifies the number of frames in a group (distance between reference frames.) For example, if
GOV = 50, 50 transmitted frames will include one reference frame (i.e., there will be 49
intermediate frames); at 25 fps and GOV = 50 one reference frame is generated every 2 sec.
The higher the GOV is, the smaller is the video stream but the bigger is RAM and CPU usage,
because decoding of each successive frame requires a reference frame and all subsequent
intermediate frames up to the next reference frame to be stored in memory. When GOV = 1
H.264, in fact, is no different from MJPEG.
Eocortex Ultra

EX ULTRA Adminguide 1 3

Uploaded by

Copyright:

Available Formats

EX ULTRA Adminguide 1 3

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EX ULTRA Adminguide 1 3

Uploaded by

Copyright:

Available Formats

Administrator’s Guide

1.1. Eocortex Ultra licenses

1.1.2. Software key protection

1.2.1. Licensing features

USB security key, Soft key sent via email,

1.2.2. Main features

MAIN FEATURES DESCRIPTION

Cameras per one server Maximum number of cameras on one server

Servers in the system Maximum number of servers in the system

Remote workstations Maximum number of remote workstations

MAIN FEATURES DESCRIPTION

English, French, Italian, Dutch, Polish, Portuguese, Russian,

1.2.3. High reliability and failover

In case the main drive breaks down or fails to do the recording,

Apply settings to the groups of devices: connection

Receives up to two video streams from IP camera, each

1.2.5. PTZ camera management

CLIENT APPLICATION DESCRIPTION

Operate in the video surveillance system with Eocortex Client

1.2.7. Screen profiles

ARCHIVE PLAYBACK DESCRIPTION

1.2.9. Export and printout

Frame Export Formats JPEG, PNG, BMP

Archive Video Export Export selected video fragments from archive

OBJECT PLANS DESCRIPTION

Place cameras, sensors and relays of the system on 2D object

1.2.11. User scenarios. Schedules

1.2.12. Alarm management

ALARM MANAGEMENT DESCRIPTION

Process Alarm events (registration, generation, notification)

Set one of the monitors as an Alarm Monitor to display alarm

ALARM MANAGEMENT DESCRIPTION

Event Log called Journal provides data on Server Application

1.2.13. Storage optimization

Configure automatic start of Eocortex application after the start

Monitor the current state of Eocortex server parameters:

By default, one server in the system is assigned as the Main

1.2.16. Video analytics (intelligent modules)

Interactive object search in archive by uploaded photograph

Specified features may require additional licenses

1.3. Contents of Package

The software package with USB-key includes the following:

2.1. Guidelines for choosing and configurating hardware platform

2.2. Guidelines for Windows settings

If RAM capacity is 4 GB or more, use a 64-bit operating system, as well as 64-bit

Install all Windows updates and then turn off Auto-update.

2.3. Installing Eocortex Ultra software from a common installer

If you use a Eocortex Ultra USB-key, plug it into a server USB-port.

Setup wizard window will open. Follow the instructions:

Setup wizard window will open. Follow the instructions:

2.5. Updating Eocortex Ultra software

2.6. Removing Eocortex Ultra software

2.6.1. Remove software and save the settings

2.6.2. Complete removal of Eocortex Ultra products

Possible online activation errors:

2.7.1.1. USB key offline activation

Next, the key activation code will be requested.

In case of successful activation, a new Installation of license successfully completed

Possible online activation errors:

2.7.2.1. Software key offline activation