Firmware MIC-7604-Z12BR

New Features:
N/A

Changes:
• Resolved an issue where valid MKI and encrypted SRTP packets were transmitted with delay, leading to ~30 seconds of video decoding lag. This fix was most noticeable when streaming through video management systems that rely on strict SRTP timing
• Some default image settings of AUTODOME 7100i 2MP, AUTODOME 7100i IR 2MP, AUTODOME 7100i IR 8MP, and MIC Inteox 7100i 8MP, have been updated to provide a better out-of-the-box experience for new customers. Existing users will not have their customized settings overwritten during the firmware update. However, users who wish to benefit from the new defaults can restore the image settings to the factory defaults via GUI or Configuration Manager.
• Fixed an issue causing frame duplication on CPP13 devices. This issue was primarily observed in scenes with high object movement when IVA was enabled, occasionally resulting in uneven video playback or repeated frames during streaming.
• To prevent misunderstandings and better reflect actual behavior, the “Maximum Bitrate” field has been renamed to “Target Bitrate.” This parameter indicates the bitrate the camera will attempt to maintain, bitrate variations may occur due to network conditions, client behavior, and scene complexity.

SHA256: F48AFEDD1CBC8B865B000B54DF1173ADB9ADDDC2214FD1FB7D4C525835DC15CF

New Features:
• General improvements on image quality tuning of:
• AUTODOME 7100i - 2MP
• AUTODOME 7100i IR - 2MP
• AUTODOME 7100i IR - 8MP

Changes:
• It was identified on FW 8.47.0030 a critical issue causing network drops on CPP13 cameras for some users. The issue was caused by a malfunction on the DSP (Digital Signal Processing) of our cameras resulting in a loss of network connection to the camera. This issue could only be fixed via a power cycle was completed. It is still unclear in which conditions the issue was reproduced, but there are strong indications that the following parameters influence on how often the issue is reproducible:
• Cameras recording into a Storage Management Device
• SD card inserted
• Camera using VCA busy scenes with multiple objects moving on the field of view
• Multiple alarms set At BOSCH, we strive to provide high-quality and reliable products to our customers. We have thoroughly investigated the reported network drop issue and have developed a solution in the form of this firmware update. We strongly encourage all users to install this firmware update as soon as possible to benefit
• The firmware 8.48.0017 fixes a malfunction causing the “Focal length” value to be wrongly displayed in clients what affected mainly the calibration of CPP13 cameras. This bug was not reproducible on other versions, being restricted to 8.47.0030.
• An issue is fixed where the secure element could be permanently damaged due to wear -out of its internal flash memory. This issue is only applicable if video authentication is enabled with default settings, using MD5, SHA1 or SHA256 as hashing algorithm. The error was introduced with FW 8.50 and affects all firmware versions since. For more details refer to our Security Advisory BOSCH-SA-435698-BT, published at our Security Advisory web page:
https://www.boschsecurity.com/xc/en/support/product-security/security-advisories.html or visit our PSIRT website at https://psirt.bosch.com.

SHA256: 8A3AAFE6EAB8AF55B374F39AFF584E7B6614F24A952D288D42799DF78A48F947

New Features:
• This release introduces the core functionality of the new INTEOX cameras - AUTODOME inteox 7100i.
• An IR intensity control via slider was introduced on the “Imaging” menu of the INTEOX fixed camera models.
• Certificates and Certificate Signing Requests (CSRs) with key length of 4096 bit can now be used on all the CPP13 camera models. For the CPP13 products which are equipped with the FIPS certified secure element the possibility of generating keys is limited to 3072 bit length; those with the standard secure element allow generation up to 4096 bit key length. Using hashing algorithm of up to SHA256, those certificates can be applied for HTTPS, EAP-TLS and user authentication usages.
• Since firmware version 8.40.0029, TLS 1.3 is supported, including the possibility to set either TLS 1.3 or TLS 1.2 as the minimum TLS version. An UI to support this selection on CPP13 camera models is now available via Configuration Manager and Web-UI.

Changes:
• The settings of the feature “Sector and Preposition”, available on the INTEOX moving camera models, support now up to 40 characters as an input on the “titles” field.
• An enhancement on the “Privacy Mode” was introduced in order to improve the stability of the privacy masks, generated via object detection, on scenes with more than 30 objects. In that sense, we aim to prevent potential glitches on the masks generation even on complex scenes.
• A new mechanism for SD cards recording and management was introduced in order to fix undesired behaviours observed in previous versions of the firmware, specially when the cameras were set to the maximum of their streaming/recording capabilities.
• 4CIF aspect ratio is now a supported resolution (704x576).

SHA256: 44C5C171030C5A4658E9651292194F15C2C5515E5B7E3CB55E6F40C7171130D4

New Features:
• A mechanism to allow the IR leds of the fixed camera models to be either automatically set or permanently disabled was introduced. This functionality is initially available via Web Interface (image settings), but soon will be available as well via Configuration Manager, on an upcoming release of the software.
• In addition to the ONVIF Profile M support available since version 8.40.0029, the possibility to forward MQTT events is now enabled on CPP13 cameras. Currently the events covered by the implementation are restricted to events generated exclusively by the BOSCH Firmware like the VCA alarms. The MQTT configuration via Configuration Manager will be available from the Configuration Manager version 7.60 or higher, however, it is already possible to configurate the MQTT of the camera while using ONVIF tools to configure it. Initially this implementation doesn’t include support to forward MQTT events generated by 3rd party Apps. The support for this kind of event should be available on an upcoming release. Meanwhile the metadata forwarding options from data generated by Azena ’s 3rd party Apps is restricted to:
• ONVIF pull-point for events and notifications generated by Apps, to be configurated according to ONVIF tools capabilities.
• App message forwarding based on Azena’s “Message Broker” solution, which includes the possibility to share messages and data with 3rd party devices*. This service must be configurated via Azena’s Integration Assistant, and in case of trouble integrating the data Azena’s Tech support team should be contacted.
• In order to guarantee integrability via “Message broker”, it is necessary that the 3rd party App used allows the use of the functionality.

Changes:
• There was an enhancement on the Privacy Mask solution offered for the fixed camera models. geometrical nodes around the area they want to protect.
• Due to an increase on the security restrictions related to the most common web- browsers, the options to exchange BOSCH logo for a “Company logo” or “Device logo” were removed of our Web-Interface (Web Interface > Appearance Menu).

SHA256: 7D86F1C985CEBBAB318B44AA2C3BCFDCD28E001A7AA7DE998C0A7FA27BE0A957

New Features:
• A mechanism to allow the IR leds of the fixed camera models to be either automatically set or permanently disabled was introduced. This functionality is initially available via Web Interface (image settings), but soon will be available as well via Configuration Manager, on an upcoming release of the software.
• In addition to the ONVIF Profile M support available since version 8.40.0029, the possibility to forward MQTT events is now enabled on CPP13 cameras. Currently the events covered by the implementation are restricted to events generated exclusively by the BOSCH Firmware like the VCA alarms. The MQTT configuration via Configuration Manager will be available from the Configuration Manager version 7.60 or higher, however, it is already possible to configurate the MQTT of the camera while using ONVIF tools to configure it. Initially this implementation doesn’t include support to forward MQTT events generated by 3rd party Apps. The support for this kind of event should be available on an upcoming release. Meanwhile the metadata forwarding options from data generated by Azena ’s 3rd party Apps is restricted to:
• ONVIF pull-point for events and notifications generated by Apps, to be configurated according to ONVIF tools capabilities.
• App message forwarding based on Azena’s “Message Broker” solution, which includes the possibility to share messages and data with 3rd party devices*. This service must be configurated via Azena’s Integration Assistant, and in case of trouble integrating the data Azena’s Tech support team should be contacted.
• In order to guarantee integrability via “Message broker”, it is necessary that the 3rd party App used allows the use of the functionality.

Changes:
• There was an enhancement on the Privacy Mask solution offered for the fixed camera models. geometrical nodes around the area they want to protect.
• Due to an increase on the security restrictions related to the most common web- browsers, the options to exchange BOSCH logo for a “Company logo” or “Device logo” were removed of our Web-Interface (Web Interface > Appearance Menu).

SHA256: 02E44A4CCD3BE729E5D28C9659282112DF7B5F3A17808E21FE57BD783B715924

New Features:
• A mechanism to allow the IR leds of the fixed camera models to be either automatically set or permanently disabled was introduced. This functionality is initially available via Web Interface (image settings), but soon will be available as well via Configuration Manager, on an upcoming release of the software.
• In addition to the ONVIF Profile M support available since version 8.40.0029, the possibility to forward MQTT events is now enabled on CPP13 cameras. Currently the events covered by the implementation are restricted to events generated exclusively by the BOSCH Firmware like the VCA alarms. The MQTT configuration via Configuration Manager will be available from the Configuration Manager version 7.60 or higher, however, it is already possible to configurate the MQTT of the camera while using ONVIF tools to configure it. Initially this implementation doesn’t include support to forward MQTT events generated by 3rd party Apps. The support for this kind of event should be available on an upcoming release. Meanwhile the metadata forwarding options from data generated by Azena ’s 3rd party Apps is restricted to:
• ONVIF pull-point for events and notifications generated by Apps, to be configurated according to ONVIF tools capabilities.
• App message forwarding based on Azena’s “Message Broker” solution, which includes the possibility to share messages and data with 3rd party devices*. This service must be configurated via Azena’s Integration Assistant, and in case of trouble integrating the data Azena’s Tech support team should be contacted.
• In order to guarantee integrability via “Message broker”, it is necessary that the 3rd party App used allows the use of the functionality.

Changes:
• There was an enhancement on the Privacy Mask solution offered for the fixed camera models. geometrical nodes around the area they want to protect.
• Due to an increase on the security restrictions related to the most common web- browsers, the options to exchange BOSCH logo for a “Company logo” or “Device logo” were removed of our Web-Interface (Web Interface > Appearance Menu).

SHA256: 18321640CBB23D253D9695D354ECC198BB38D796DE6AC7F4147F063956572880

New Features:
• ONVIF Profile M is now supported by INTEOX cameras.
• Intelligent Tracking Introduced into CPP13 moving cameras. This feature allows the camera to automatically zoom-in and to follow a selected Intelligent Video Analytics object, as far as possible with the camera. Information on how to operate and configure this feature is available on the following link:
• How to configure Intelligent Tracking for Bosch cameras? (link)
• SNMPv1 and SNMPv3 are now included on the list of protocols supported by CPP13.
• NTCIP is now included on the list of protocols supported by CPP13. For moving cameras models most of the commands associated to this protocol are now fully supported, while for the fixed cameras the support for this protocol is still limited. It’s expected to enhance the support offered via this protocol in upcoming firmware releases. NTCIP must be activated on the cameras via a license.
• SD Card recording with the MIC inteox 7100i models is now enabled.
• Support for communication between the “MIC inteox 7100i – 8MP” and external Alarm I/O Box has been introduced.
• A framerate switch mechanism was introduced into this firmware version, in a way that now it is possible to change the video frame rate scale according to the options offered by the camera model used:
Camera Model Default framerate (fps) Other framerate scales available(fps) MIC inteox 7100i – 2MP 30 25 / 50 / 60 MIC inteox 7100i – 8MP 30 25 FLEXIDOME inteox 7100i IR 30 25 DINION inteox 7100i IR 30 25 AUTODOME inteox 7000i 30 - Notes:
• A video framerate change can be performed either via Web-UI or Configuration Manager (version 7.60 or higher).
• A system reboot will be enforced in order to confirm the selected video frame rate configuration.
• Before performing a firmware downgrade from version 8.40.0029 to 8.12.0005 or older version, its necessary to configurate the video frame rate to 30 fps in advance. When this condition is not fulfilled the camera may show no video after the re-start and, in order to bring the camera back to former operating status, a configuration reset would need to be performed – a factory default reset is not required.
• When using configuration upload option to change de video frame rate configuration, two enforced reboots may be required to get video.

Changes:
• At the last release, entitled 8.12.0005, it had been reported that releases of firmware related to INTEOX cameras would start providing customers with 3 different firmware files options, so tha t the users would need to choose which file to upload according to the type of camera to be updated:
• A file exclusive for fixed cameras.
• A file exclusive for moving cameras.
• A combined file valid for both fixed and moving cameras. However, due to a system upgrade, this change has been re

SHA256: 646F5A8C0C4776C30F8E16B367215BB6DDA7031119FDBC89064306E49EB4F9C9

New Features:
• ONVIF Profile M is now supported by INTEOX cameras.
• Intelligent Tracking Introduced into CPP13 moving cameras. This feature allows the camera to automatically zoom-in and to follow a selected Intelligent Video Analytics object, as far as possible with the camera. Information on how to operate and configure this feature is available on the following link:
• How to configure Intelligent Tracking for Bosch cameras? (link)
• SNMPv1 and SNMPv3 are now included on the list of protocols supported by CPP13.
• NTCIP is now included on the list of protocols supported by CPP13. For moving cameras models most of the commands associated to this protocol are now fully supported, while for the fixed cameras the support for this protocol is still limited. It’s expected to enhance the support offered via this protocol in upcoming firmware releases. NTCIP must be activated on the cameras via a license.
• SD Card recording with the MIC inteox 7100i models is now enabled.
• Support for communication between the “MIC inteox 7100i – 8MP” and external Alarm I/O Box has been introduced.
• A framerate switch mechanism was introduced into this firmware version, in a way that now it is possible to change the video frame rate scale according to the options offered by the camera model used:
Camera Model Default framerate (fps) Other framerate scales available(fps) MIC inteox 7100i – 2MP 30 25 / 50 / 60 MIC inteox 7100i – 8MP 30 25 FLEXIDOME inteox 7100i IR 30 25 DINION inteox 7100i IR 30 25 AUTODOME inteox 7000i 30 - Notes:
• A video framerate change can be performed either via Web-UI or Configuration Manager (version 7.60 or higher).
• A system reboot will be enforced in order to confirm the selected video frame rate configuration.
• Before performing a firmware downgrade from version 8.40.0029 to 8.12.0005 or older version, its necessary to configurate the video frame rate to 30 fps in advance. When this condition is not fulfilled the camera may show no video after the re-start and, in order to bring the camera back to former operating status, a configuration reset would need to be performed – a factory default reset is not required.
• When using configuration upload option to change de video frame rate configuration, two enforced reboots may be required to get video.

Changes:
• At the last release, entitled 8.12.0005, it had been reported that releases of firmware related to INTEOX cameras would start providing customers with 3 different firmware files options, so tha t the users would need to choose which file to upload according to the type of camera to be updated:
• A file exclusive for fixed cameras.
• A file exclusive for moving cameras.
• A combined file valid for both fixed and moving cameras. However, due to a system upgrade, this change has been re

SHA256: 8CF88B0420505D5F648DCFC65209D3D417C5B5B879D645C095CC782DB7602297

Changes:
A malfunction in one of the software components controlling the camera's heater of the AUTODOME inteox 7000i has been identified on FW version 8.12.0005. The malfunction only occurs when the camera is exposed to specific conditions. To eliminate any inconvenience to our customers, we are releasing 8.12.0010 as a new version of firmware which includes the fix for this malfunction. Just like the 8.12.0005 version, the version 8.12.0010 is a pre-requisite on the process of upgrading firmware versions lower than 8.10.0005 to firmware versions higher than 8.40.0029.

SHA256: 840536F181DCC72A15AC2518A9296EAB6A46178CB1091484CF4E80FC3D0649E6