Core 1.3.11

The following Bouncy Castle libraries in the Key Manager are updated from version 1.64 to 1.68:

• bcprov-jdk15on
• bcpkix-jdk15on

Database 3.1.1003

SQLite is updated from version 3.33.0 to 3.35.5

OSGi 1.5.6

• Added a configurable timeout system property subscribe.time.out.cp in seconds for re-subscription to events from a device imported from the UPnP network through the UPnP Driver bundle. It configures the HTTP headers used.
• Exceptions thrown by ResolveContext#getWirings() were ignored, which was shadowing errors in framework resolver Util logic. Now errors are visible to the caller.

1

Framework 8.5.9

Framework storage,
Corrupted files

Framework was unable to start with ready storage when framework state, bundle state or startlevel state files were corrupted, unless that storage was explicitly deleted. Now it is possible to enable self-cleaning behavior in such cases, by setting system property mbs.storage.cleanIfCorrupted to true. Enabling this functionality means, that framework will clean its storage, if a corrupted storage file is detected, and then retry initialization.

9.3.0

2

Cameras 4.4.7

Camera Manager

Camera Manager was unable to get stream from a specific camera. Stream did not open using RTSP Proxy, when device supported both Digest and Basic authentication. That was caused by Authentication sequential problem. This is now fixed.

9.0.0

3

Cameras 4.4.6

Backup and Restore

There was an error when trying to remove device, which was registered with wrong address, host or port. That issue was affecting the restore operation. Now it is fixed.

9.0.0

4

Cameras 4.4.6

Device offline
behavior

The Functional Items were not unregistered, when device went into offline state, e.g. after changing camera's address to invalid value. This is now fixed and only the Configuration Functional Item remains registered. The fix does not affect the HDM usage.

9.0.0

5

OSGi 1.5.6

Metatype configuration
loader

There was a problem loading external configurations from а bundle in boot.ini. This has been fixed and now configurations are always available.

9.3.5

6

OSGi 1.5.6

Metatype configuration
loader, storage

Sometimes there was a problem updating external configurations upon a framework restart after metadata files were modified. The issue has been fixed and metadata is always scanned for changes, which are reflected accordingly in OSGi configurations.

9.3.5