System setup with multiple cameras and a supported multiviewer:
Orange: Ethernet connections, red: audio or video connections, blue: HD-SDI
Follow the manuals for the multi-viewers. They can be found at their manufacturer’s websites:
TvOne Corio Matrix Mini User Manual
Kramer MV 6 User Manual
Make sure that to get this setup to work, both the multi-viewer and the CCS1000D Control Unit should be in the same VLAN/subnet. Also, use the correct port to connect to the multiviewer:
TvOne Corio Matrix Mini; port 10001, example: http://192.168.1.2:100001
Kramer MV 6; port 5000, example: http://192.168.1.2:5000
The RESTful API of the CCS1000D is used in order to get a clear view of the state of the discussion devices’ microphones (amongst other things). However, when a Priority call is made, the other speakers still show as active even though they are muted in reality.
This is actually as it' supposed to work. The reason the speakers still show as active is because they remain in the speaker list while the priority call comes through (in this case, the chairperson making an announcement overruling all other parties) is that in the system there’s a difference between speakers being muted and speakers being removed from the speaker list.
In this case, after the priority call ends, the speakers are unmuted and can resume the discussion.
It’s also possible to configure the system to stop all speakers and remove all waiting participants from the request list. If the system is setup in this way and the chairperson starts speaking, the system will indeed erase all other speakers and waiting speakers.
The API can be used to create a custom interface. This means that logic can be added so the preferred outcome is created. In this case it means that the custom interface needs to poll for the speakers list but also needs to take in account that when a priority call comes through (also pollable) this means the others are muted. Using these two givens can then be used to for example change the icons of the speakers to a ‘muted’ state in the custom interface.
In order to change the layout, the StyleSheet needs to be changed. Default it is located in C:\ProgramData\Bosch\DICENTIS\VotingResult.xslt, this file can be opened in any text editor, Notepad++ is recommended as it is very versatile.
When using a fixed IP addresses in a multi-subnet Dicentis system, certain settings need to be made for the system to function well. If the settings are not made correctly, the system can stop functioning & disconnect from the server.
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.
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.
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.
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.
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.
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.
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.
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.
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.