In some cases it could be necessary that you need to maintain the Microsoft SQL database which DICENTIS is using to save participants, user, seats and settings.
In the next steps I will explain some of the basics commands.
The DetectDevices script was developed to give a fast feedback on connection problems or any other failure within the DICENTIS wired system. It will simulate a device and give out an advanced log file which can be used to track sporadic or normal connection problems. The technical support will provide this tool to get a deeper look into some issues if needed.
After upgrading to DICENTIS Conference system 3.60, TLS1.0 is disabled for security reasons, and TLS1.2 is enabled. Since the Multimedia device does not support TLS1.2, it does not show logo and participant images anymore.
The DICENTIS Server has a own log file system which is working in the back ground and is called LogDump.
If something went wrong during the operation it will be reported in there. In many times this is a good tool for error analysis as well as fault detection and will often requested by the Technical Support for pre-analysis.
In the next Step-by-step guide it will be shown how to extract the LogDump file form DICENTIS Conference System.
Product(s) affected: DCN-NG systems with master & slave CCU set-up
A DCN-NG system will be installed in a building which uses different VLANs for different floors in the building. They want to be able to have interpreters on one floor (in one VLAN) and the rest of the system on another floor (in another VLAN). To this end they have connected their Master CCU to another VLAN than their Slave CCU. This set-up does not work.
Question is; should this work and if not, why not?
This cannot work in a DCN-NG system because of the way the system is designed.
The communication between the CCU’s, at start-up of the system, uses broadcast messages which are not routed by network devices. These messages have a time-to-live (TTL) of 1, which means that once they attempt to cross into another (V)LAN, the messages are not propagated by the routing (L3) switch.
The reason is that the TTL of the packet is decreased every time it traverses from one network to another. When the TTL’s value reaches 0, the packet is dropped by the routing device.
Therefore, the broadcast packet will never reach the other CCU, resulting in error messages like “No Master CCU” on the Slave CCU.
Therefore the system should be installed on the same (V)LAN. This usually does not pose any technical problems as (V)LANs can be distributed over multiple network devices without issue, it’s just that the predictability of where a device is physically located is less in this instance.
Possible causes and solution(s)
The Dicentis does not need any additional encryption to be set via the OMNEO Firmware Upload Tool. (OFUT)
If you have set this by accident it could lead to that you can not see or update your units with the OFUT any more.
stop the Firmware Upload Tool
delete the following file C:\Program Files\Bosch\OMNEO\Firmware Upload Tool\FirmwareUploadHIConfig.ini
start the Firmware Upload Tool
Encrypted devices did not show up and you can not update them anymore. Do not set a password for default!
Open and delete this file C:\Program Files\Bosch\OMNEO\Firmware Upload Tool\FirmwareUploadHIConfig.ini
Open the OFUT and units will appear again.
In some cases the log file from the Dicentis Server become too big and it has to be cleared to reduce the size from time to time. The normal size is between 10MB and 50MB depending on the operation time but it should normally not grow over 100MB. If it does exceed, is most likely a fatal error within the DICENTIS system which produce a lot of logging each minute.
It could be possible that the driver of the Network Card (3rd party Server) to become intermittent and the log file to grow to 300MB. In the next steps we will show you how to clear the logging.
DICENTIS installation log files are needed for further analysis for Technical support team if the software update failed or later some errors occurred.
Below it is explained how you can extract DICENTIS installation log files.
In some cases, especially if you use a 3rd party PC as DICENTIS Server, it could be necessary to update your network driver.
For example, if discussion units show a red LED from time to time or your DICENTIS is dropping out it could be related to the network driver.
Be aware that a normal Windows Update will not refresh this driver and you have to update it manually!