DCN-NG is set-up in a multi-PC environment, all required licenses are installed. When trying to connect to the server from the secondary PC, the Operator Application takes a long time to start and once it does, the screen is simply blank and the server icon mouse-over shows the application is disconnected. When pinging the server from the secondary PC, the ping goes through without issues.
There can be various causes for this, it is usually network related. Ping messages are coming through, but the connection messages are not. This could for example have to do with a firewall blocking messages.
In this case the problem was caused by the second Network Interface Card (NIC) in the server PC. The server would respond to ping, but when the DCN-NG operator tried to connect to the server, the server would respond out of the wrong interface.
The solution is to only enable one interface on the DCN-NG server, when this is done, the system works as expected.
... View more
Product(s) affected: DCN-NG systems including an INT-TX Integrus transmitter
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:
“Network Error” on the display of the transmitter
Static/crackling from the discussion devices (sometimes)
Discussion devices do not start (when the CCU2 is rebooted)
Network status on the CCU2 is either “Not connected” or “Not responding”, depending if a ring setup is made (former) or a direct connection (latter)
Network status on other devices in the MOST network will also show “Not responding”
The problem was caused by the default settings of the INT-TX transmitter. By default the device will act as a standalone device. However, for it to function in a DCN-NG system it needs to be configured as such.
In order to do so:
Go to the network mode menu item (menu 4B) on the Integrus Transmitter
For more information, see the Integrus Operation Manual chapter 7.2.3
The warning in the Integrus Operation manual also indicates possible problems as described above:
In case ‘Standalone’ is selected and the transmitter is connected to a DCN Next Generation or DCN wireless system, the audio in the system can be disrupted. In case ‘Enabled’ is selected, while no DCN Next Generation or DCN wireless system is connected, the transmitter will show the fault status “Network Error”. In case ‘Enabled’ is selected and the transmitter cannot connect to the optical network (e.g. because the control unit of the DCN Next Generation conference system is switched off), the emergency contact does not function.
... View more
Product(s) affected: DCN-NG & DCN-WAP
A DCN-NG system is installed with a DCN-WAP but needs to be expanded and an extra WAP needs to be added. Is this possible?
Explanation & solution:
Besides the fact that the DCN Wireless system is no longer available, the answer is ‘No’ due to limitations of the DCN-NG wireless system.
If another wireless system is required, it can be done in a separate DCN-NG system only.
The following is described in the old DCN-NG Wireless manual:
A multi-CCU system is necessary if there is no capacity to connect all required DCN units or if you want to couple multiple rooms. All CCUs need to be connected with an optical cable to each other and with an Ethernet cable (Cat5e or better) to the switch (100 Mbit/s or better).
The following can be connected to a multi-CCU system:
A maximum of 30 DCN-CCU2 devices (refer to Control capacity, page 78).
A maximum of 4000 delegate positions.
A maximum of 1 DCN-WAP.
... View more
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
... View more
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.
... View more