Version 4.6.5 System Version 4.6.5 includes the following components: Avigilon VIEW Version 4.6.5 R-Series Version 4.6.5 Rialto Version 4.6.5 ICVR-HD Version 3.7.3 ICVR-SD Version 2.6.3 System Requirements for Avigilon VIEW Windows XP Professional (Service Pack 3) Windows 7 Windows 8 Minimum: CPU - 2 GHz, Core2 Duo 2 GB system memory 100 GB free disk space Recommended: CPU - 2.4 GHz, Quad Core 4 GB system memory 400 GB free disk space
IP Camera Compatibility Requirements (attaching an IP camera to a Rialto I4 or an R-Series IP Blade) 1. H.264 compression (High, Main or Baseline Profiles) a. MJPEG and MPEG4 video streams are NOT supported 2. RTSP streaming protocol 3. Resolution: 1920 x 1080 or lower Notes for first time users 1. When logging in to Avigilon View for the first time use the following credentials: Username: supervisor Password: supervisor 2. A user does not need to be a system administrator to run Avigilon VIEW. However, to install Avigilon VIEW, the user must be a system administrator. 3. Arecont multi-head IP cameras are not supported for attachment to a Rialto I4 or R-Series device. In addition, all other Arecont models have not been verified for attachment to Avigilon devices. Defects Resolved in System Version 4.6.5 1. Firmware upgrades have been implemented to protect against various threats such as the BASH vulnerability Shellshock and the SSL protocol vulnerability/ POODLE attack. 2. FLIR camera video streams were occasionally disconnecting from Rialto I4. 3. Short video gaps were found in Rialto recorded video. 4. 1080P camera streams, attached to a Rialto I4, would sometimes drop to 704 x 480 resolution. 5. VIEW would indicate that an ICVR HD or a Rialto device (e.g. blade) was stuck in initialization. The device was not actually in initialization mode. VIEW had not received a status update. 6. Unused and disabled Rialto channels generated video lost alarms when restarting VIEW. 7. VIEW would occasionally terminate when a user was acknowledging alarms. 8. Two 1080P camera streams, (configured at 30 fps and a high bit rate (e.g. > 10 Mbps)) attached to a Rialto I4, would sometimes result in a restart of the Rialto device. 9. When enabling audio input on a Rialto channel, the change was not implemented on the Low Bandwidth stream until the device was rebooted.
10. If the time zone was changed on a Rialto device that was using an NTP server, VIEW displayed a warning message about time being reset backwards or forward. This warning message should not be issued. New Features introduced in System Version 4.6.4 1. Additional Resolution Support for IP Camera Attachment All stream resolutions of 1920 x 1080 or lower are now supported. See above for additional camera compatibility requirements. Defects Resolved in System Version 4.6.4 1. IP Rialto and R-Series IP Blades Camera streams with 800 x 450 resolution could not be attached. 2. Rialto and R-Series When a Rialto device was discovered in Avigilon Control Center, the device s hardware model name was not available for display. 3. VIEW If an operator does not have permission to acknowledge alarms, the permission problem is now identified in the warning message that is generated when the operator attempts an acknowledgement. 4. ICVR HD Short video gaps were occasionally found in recorded video. 5. VIEW When a PTZ camera stream was attached to an IP Rialto and the video was displayed in full screen, VideoIQ Track could not be enabled. 6. VIEW, Rialto, and R-Series An NTP server can now be configured using a custom port. 7. Rialto and ICVR HD A new NTP client has been included on both device types. This resolves problems with inconsistent performance (i.e. not maintaining accurate time) on the previous client version. New Features introduced in System Version 4.6.3 1. Consolidation of FLIR and non-flir images There is now only one firmware image for FLIR (thermal) and non-flir modes. Previously, a separate firmware image was required for configuring a device to FLIR mode. This change applies to single channel encoders (2.6.3), IP and Analog Rialtos (4.6.3) and R-Series devices (4.6.3). 2. Additional Resolution Supported for IP Camera Attachment 1920 x 1072 is now supported Defects Resolved in System Version 4.6.3 1. VIEW allowed invalid Domain Name System (DNS) configuration settings.
2. Web UI - Auto-complete is disabled on all Web UI forms increased security. 3. Web UI Directories are not exposed through the Web interface increased security. 4. Rialto & R-Series Occasionally when a Rialto was connected to Avigilon Control Center, object bounding boxes were not displayed on the video. 5. VIEW If a leading 0 was used in an IP address octet (e.g. 192.168.086.101), when attaching a camera stream to an IP Rialto or R-Series blade, the attachment would fail. 6. R-Series The Network Attached Storage (NAS) device s time and date were not always correctly updated. 7. R-Series When replacing/swapping blades on a fully populated R-series (4 blades), the device would reboot and after the restart completed, the user would not be able to configure Common R-Series Settings. 8. IP Rialto and R-Series IP Blades ACTi IP camera video streams can now be attached to these devices 9. IP Rialto and R-Series IP Blades ACTi IP PTZ cameras can now be controlled (e.g. presets, zoom, etc.) by IP Rialto devices 10. Rialto & R-Series Occasionally when a Rialto was connected to Lenel s OnGuard System, video was not displayed. 11. Rialto & R-Series Audio talk down was not working with Genetec Security Center 5.2 SR6 New Features introduced in System Version 4.6.0 1. Additional Resolutions Supported for IP Camera Attachment Any resolution below 800 x 600 is now supported. 2. IP Camera Attachment: Three 720P (1280 x 720) Resolution Devices - Three 720P cameras can now be attached (simultaneously) to an IP Rialto or R-Series IP blade. 3. Extended Live View Opens Automatically Extended Live View will now open automatically if VIEW was closed with Extended Live View enabled Defects Resolved in System Version 4.6.0 1. VIEW had noticeably slower response times (in comparison to previous versions) when opening Live Video streams and editing rules. 2. ICVR SD, HD & Rialto When video retention was set to > 24 days, only 15 minutes of video was actually retained.
3. Rialto would occasionally generate alarms that were time stamped weeks into the future. 4. VIEW When backing up device settings to a file, VIEW would generate a warning message about changing device time. 5. ICVR HD & Rialto When an error occurred during transmission of an alarm clip to the cloud (Avigilon mobile events), a second attempt at transmission would not include the video clip. The event s video clip was therefore not available for playback. 6. IP Rialto & R-Series IP Blades Software upgrade introduced to reduce drops of attached camera streams to the IP Rialto devices. 7. IP Rialto & R-Series IP Blades When connecting an Avigilon PTZ IP camera to a Rialto device, VIEW control would result in erratic PTZ behavior. Known Issues 1. Teach by Example (TBE), on Rialto and R-Series, will occasionally not decrease False Alarms (i.e. there is no effect) This is currently under investigation. 2. Versions of VIEW, older than v4.3.0, can inadvertently disable all video channels and alarm notifications on Analog Rialto devices (RA4s) running firmware version 4.3.0 or greater. In this scenario, alarms on the Rialto devices will not be reported. Therefore it is critical to upgrade all workstations to VIEW version 4.4.1+, prior to upgrading the Rialto devices. If there are RA4 devices that have been disabled using View Version 4.2 re-enable the channels using these steps: a. Upgrade workstations to VIEW 4.4.1+ b. In View navigate to the Manage page c. Locate the Rialto A4 devices, double click on one of the cameras bringing up settings d. Navigate to the Encoder tab and check Enabled for each of the cameras. e. Press the OK button The RA4 cameras will now appear in the camera tree and report alarms. 3. Alarms that generate an email and provide an HTTPS link for the video clip, will not play with Internet Explorer and Windows Media Player. To work around this problem, either install QuickTime or switch to HTTP protocol.
4. When using the Teach By Example (TBE) function, alarms may be listed where the confidence level is below the threshold sensitivity configured in the associated rule. In this scenario, the listed confidence is incorrect. The alarm is valid the confidence level is not displayed correctly. 5. R-Series IP Blade and Rialto I4 If the unit is power cycled less than 5 minutes after a stream has been attached, all stream configuration information (for all streams on the device) is lost. Wait at least 5 minutes prior to removing power after attaching an IP camera. 6. When an R-Series is upgraded, VIEW reports that the process is complete, but a few additional minutes are required to finish the upgrade. The R-Series should not be power cycled until all upgraded R-Series blades are displayed as reconnected in VIEW s camera tree. Web-browser access to Avigilon (VideoIQ) cameras and appliances Web-browser access to cameras and appliances, currently supports IE 8 through IE 11. Other browsers may work however certain notes apply: Google Chrome Chrome appears to support the Windows Media Player plug-in without any modifications. Firefox Firefox does not natively support ActiveX. An extension is available that provides basic support for ActiveX however this support is not sufficient for Windows Media Player. It is recommended that this extension be uninstalled to prevent it from being used. A plug-in for live streaming is available from VLC (VideoLan). This plug-in will not decode or render detection boxes even when enabled by the Preferences setting. Safari on MAC The VLC plug-in for live streaming is also available for Safari. The limitation on detection boxes applies here as well.