Conference & Discussion

If RSTP is not enabled in an looped system packets will loop infinitely exhausting all available bandwidth and could cause an overflow of MAC address tables. In the end it will result in a broadcast storm and breakdown of the entire network.

Ping messages are coming through, but the connection messages are not. This could for example have to do with a firewall blocking messages.

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.

If you can't see the DICENTIS Server Console Item in the right tab anymore this article will help you to surface them again.

Details on the RS232 connector can be found in the installation and User Instructions manual since version 3.1x for example found in the DCN-NG software ISO under docs

This article explains step by step wow to enable web server configuration for PRA-ES8P2S.

If you are facing problems with the API to construct your own synoptic view you can take a look at the RESTful API test page as well as Synoptic control example.

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.

Symptoms: When a meeting is recorded and the recording software (either Meeting Recorder or Open Interface connection) is shut down, the microphone control mode switches to "Open", independent of what it was before.

A very common mistake is to to forget to update your Windows and other Microsoft products which are also used by the DICENTIS.

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.

For some reasons it could be necessary that the the Technical Support needs this logging to analyze what could cause the trouble. This guide will help you to get through . This topic can as well be found in the Configuration Manual of Dicentis wireless page 34. DICENTIS_Configuration_Manual   Preconditions:   You need at least a user with access right: Configure Logging export is not available for tablets. The log file can only store about 1200 lines! That means you need to extract the logging after the error or symptoms occurred before the system overrides the logging line.  It may be to late if you extract the logging after some days.  

The DICENTIS cannot handle more than one enabled NIC at the same time and this could lead that it choose the wrong NIC and interrupts the system. This will be specially important if you use your own Server. To solve this problem it is necessary to precisely define the DICENTIS NIC. These next few steps will show you how to do that.

This is a small instruction how to update the DICENTIS wireless. All settings and license will not be affected from the update and can be used like before again.  

To send or receive a multicast Dante stream for example from different languages it will require some DCNM-LDANTE licenses but if you only need it for import and export audio signals the DCNM-LSYS includes already one channel (floor).

Possible causes and solution(s) Causes   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.   Solution:   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.  

To back up your DICENTIS Server System is one of the most important maintenance task and it should be done on regular basis. Especially if you have to set up your Server for the first time it is highly recommended to do an backup to save your system, programs , settings and so on. The reason obviously for this is if a system crash occurred you should be prepared to set up or recover the Dicentis again. This will save you a lot of trouble if it is done properly beforehand. There are four main themes to perform for a 100% save back up which will be now explained how to do it.

The Conference protocol is a platform-independent protocol which is based on Web-Socket technology to enable scalability of the DICENTIS system and it connects with the DICENTIS web server. This is a small introduction to test if the web socket is basically working and if the connection is right.

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.

Downloading firmware over the serial cable can be tricky, this document gives further information on the required equipment and settings for the serial connection and the system.