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.
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).
Please note that on the DICENTIS Server is already running Dante Virtual Device and you can not install another virtual Dante device like Dante Virtual Sound Card.
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.
Rapid Spanning Tree Protocol (RSTP) is needed if you want to set up redundant cabling via loops.
By default it is disabled and even if you update your DICENTIS Conference Software it will be again disabled and has to be activated afterwards. Also third party switches must comply with IEEE802:1D-20- 04 and support RSTP.
Please also note that loops have a limited hops which are lower than 21 (devices). If you need more information regarding this please have a look in the installation manual.
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.
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.
If you are facing unknown problems with your DICENTIS wired system and you need advice from the technical support they will ask for a lot of different information.
For that reason this little program was created to make the extraction of all needed log files, system settings and other data more easily.
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.
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 Serve r . To solve this problem it is necessary to precisely define the DICENTIS NIC.
These next few steps will show you how to do that.
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!
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.
If something is not working well in the Microsoft Windows Server it will be recorded in the Event Viewer (log files) and can indicate where the error occurs.
This is a good tool for the Technical Support to figure out if there are considerable issues in the Windows and other programs.
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.
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.
There could happen some occurrence were you should return your Dicentis wired license.
Reasons can be for example a hardware error, Windows software problems or an Windows upgrade of the Dicentis server etc…
Dicentis can run on a server with multiple network cards, but 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.
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.
It is recommended not to use wireless connectivity for 3rd party REST API usage.
REST API data traffic will be distributed on the same channel as the audio.
It is preferable to use the long-polling method. Do not use the normal polling method as this generates a lot of traffic, which might decrease the performance of the wireless connection.