Version: <=1.12 but also applicable to other older versions
The APS in question was running on v1.12 and needed to be upgraded to v2.60 and any firmware updates would continually fail (even other intermediate versions). The below procedure is not specific to this update and can also be used for updating from other older versions.
Install the 2.60 release on the Server PC and connect the PC to the APS directly (no network router or switch in-between).
Make sure nothing else is connected to the APS. Make sure the Dicentis services on the server PC are stopped.
When downloading the firmware to the APS it will fail the first time because of the change in name on the APS between version 1.12 and 2.60. Download the firmware again and then it will be fine.
If the update fails a second time, please check the LED behaviour of the APS:
Front LED should show alternating Green/Amber.
If not; switch the APS off and on again and re-try the update.
If the update keeps failing, the problem could also be caused by the PC used in the updating process, try a different PC and connecting cabling and follow the above steps once more.
... View more
A participant who uses a seat with Priority permissions set was not able to use the Priority button and interrupt other participants in the meeting.
The reason why this didn’t work as expected was because the system made use of the participant database in order to assign specific participants to seats.
When the system is used in this way, the permissions a participant has will overrule any seat permissions.
For example, a participant who has the Priority permissions, will have this permission at any seat where they are logged in (either by the system or for example using an NFC card). This is regardless of any permissions set on the seat.
A participant with Priority permission on a seat without Priority permission will have Priority.
A participant without Priority permission on a seat with Priority permission will not have Priority.
... View more
Dicentis can run on a server with multiple network cards, adding a variable that points to the network card that connects to the APS and other Dicentis equipment is required for it to work correctly.
Symptoms of a system that is not correctly configured:
The system would be working well for a few hours but at some point the Dicentis services no longer connect to the APS and the system stops working. Discussion devices show a red mic light and are disconnected; no audio. Rebooting the system or services will fix the problem temporarily, but it will return after 1-2 hours.
Dicentis needs a variable setting in Windows in order for it to choose the right network card. If this variable is not set and there are multiple network cards available, it may choose the wrong network connection. The discovery protocol can run out of another network connection which in turn makes it possible that Dicentis devices are discovered but the system cannot connect to the server.
From Dicentis version 2.70 onwards, a Windows environment variable can be added, this variable will persist through Dicentis software updates and it’s the preferred method if multiple NICs are required in the system.
Details taken from the Dicentis Software Manual, chapter 13.19:
Using the environment variable, DCNM_PREFERRED_NIC, the interface index can be set that you want to be used by DICENTIS .
Use "Route Print" from the command prompt to find out which Interface number is used by DICENTIS.
Create a new environment variable via:
"This PC" \ Properties \ Advanced system settings \ Environment
Variables \ System variables \ New
with variable name: DCNM_PREFERRED_NIC
with variable value: the interface number you retrieved via the “Route print” command.
Note: If there is only 1 network interface available in Windows, this will be used (regardless
the number that was set).
Note: If no environment variable, or an invalid number was set and there are several network
interfaces, the network interface that was found first will be used (current situation).
Alternative workarounds for previous software versions:
Disable all network interfaces apart from the interface that Dicentis is connected to.
Install Dicentis on a Virtual Machine which only has access to one network interface card. Make sure that the selected NIC receives a fixed MAC address from the VM software, otherwise licensing issues may occur when the MAC address changes.
... View more
Product(s) affected: Dicentis cabling Versions: all
Description: Trouble mixing and matching older & newer Dicentis cable assemblies (cables and connectors). The problem is usually that the cables and connectors do not fit together correctly or it's very hard to put them together.
Solution: In the past there were 2 types of connectors available and two types of cabling. The connectors and cabling could not be 'mixed and matched'.
DCNM-CBCON-I which were blue-tinted transparent connectors meant for DCNM-CB250-I (new product name) or DCNM-CB250 (old product name) solid core cabling.
DCNM-CBCON-N which were used with stranded cabling which was available as DCNM-CB250B installation cable or as a cabling assembly available with product number DCNM-CBxxB.
Now both connectors have been replaced by one common connector which can be used on both types of cabling; DCNM-CBCON (transparent, no colour).
All types of connectors can be used with the DCNM-CBTK tool.
It's advisable to use DCNM-CBxx-I cables for lengths over 5 metres as these cables are solid core which provides better performance for cable lengths over 5 meter.
DCNM-CBTK Toolkit for connectors and cables
Dicentis Cable Assemblies - stranded core
Dicentis Cable Assemblies - solid core
DCNM-CB250-I System installation cable 250m
... View more
How-to upgrade a Praesideo NCO-B system to include an NCO3
When adding an NCO3 to a system running on NCO-Bs, either to expand the system or to replace an NCO-B, there are certain things to keep in mind.
Upgrade all hardware to the latest versions (NCO-B to 3.6x and the NCO3 to the latest available version).
Update the PC call server and PC call stations to the latest available version.
Run a license upgrade.
The NCO-B’s will work with this software if they have version 3.4x or higher. However, it’s advised to upgrade to the latest available NCO-B version, which would be 3.6x.
The PC call station server and the clients need to be upgraded to the same version as the NCO3, it’s advised to upgrade to the latest available version from the Bosch website.
A system running on NCO-Bs most likely has version 3 licenses. In order for the NCO-3 to work correctly in the system, the licenses need to be converted to version 4 licenses.
Whether a license is a version 3 or 4 is not apparent until the below steps are taken, so it’s advised to follow this step when adding an NCO-3 to an NCO-B system:
Go to the license page (https://license.boschsecurity.com)
Click on ‘Praesideo’
Fill in the dongle number and click ‘ok’
Fill in the license number and click ‘ok’
Click on ‘finish’ and you will get an version 4 license.
... View more