Conference & Discussion

When upgrading from a previous DICENTIS version that supports DANTE (V2.20 – V3.00) to the latest version 3.10, the following problem will occur; The DICENTIS system is not visible anymore in the Audinate’s DANTE controller software, where it was visible before the upgrade.

Audio is disrupted in a multi-CCU system, most likely after first install, re-install or reset of a multi-CCU system.

The request was to integrate an AMX NX-2200 with the CCU2. The appropriate licenses were installed, but the devices cannot communicate through the serial connection.

Product(s) affected: DCN-NG systems with master & slave CCU set-up Version(s): all Problem description: 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? Solution: 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.

Description: 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. Solution: 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.

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.

Setting up a new system with a Integrus transmitter. As soon as the Integrus transmitter is connected to the system all kinds of problems start occurring:

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.

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.

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

Unexpected behavior or no reaction of DCN-SW.