Conference & Discussion

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.

To use the software modules, the software needs to be licensed. In order to receive licenses for the software, the keys need to be registered online.

If the document with the license key for DCN-NG was lost, there is still a way to find the license key currently loaded in a DCN-CCU2, this article shows how.

In order to integrate 3 rd party software with the DCN-NG system, there are 3 different integration options: Open Interface (OI) Application Programming Interface (API) Streaming Meeting Data (SMD)

DCN-NG Database Backup Note the name of the database files that need to be backed up. To check what those files are called, open the “Bosch DCN Conference Software Server Console” from the Windows notification area and note the name of the active database. Shut down all DCN-NG-related programs like ‘DCN-SW Operator Application’ and ‘DCN-SW Configuration Application’. Stop the DCN-NG service; Press the Windows button and search for ‘Services’ Open the Windows Services window Select the service called ‘DCN-SW Server (DCNNG) Right click and choose ‘Stop’. Still in the Services window, stop the services ‘SQL Server (SQLEXPRESS)’ and ‘SQL Server VSS Writer’ in the same way as outlined above. Open the folder that contains the DCN-NG database. On Windows 7 and 10, it’s located by default at “C:\Program Files\Microsoft SQL Server\[MS SQL Express version]\MSSQL\data”. Replace the line between [] with the right name, this can change. Right now it’s ‘MSSQL10_50.SQLEXPRESS’ Make sure that the user that is logged in is able to read/write from/to this folder. If this is not the case, the following step will not work. It’s possible to change permissions to folders for users within Windows, but that’s outside the scope of this document. Logging in to the server with an administrator account should be sufficient. Copy the right files to a safe location – make sure to copy both the file with extension ‘mdf’ as well as with the extension ‘ldf’.   DCN-NG Database Recovery Short version: simply follow the backup steps, but copy the files back to the database folder. Shut down all DCN-NG-related programs like ‘DCN-SW Operator Application’ and ‘DCN-SW Configuration Application’. Stop the DCN-NG service; Press the Windows button and search for ‘Services’ Open the Windows Services window Select the service called ‘DCN-SW Server (DCNNG)’ Right-click and choose ‘Stop’. Still in the Services window, stop the services ‘SQL Server (SQLEXPRESS)’ and ‘SQL Server VSS Writer’ in the same way as outlined above. Open the folder that contains the DCN-NG database. On Windows 7 and 10, it’s located by default at “C:\Program Files\Microsoft SQL Server\[MS SQL Express version]\MSSQL\data”. Replace the line between [] with the right name, this can change. Right now it’s ‘MSSQL10_50.SQLEXPRESS’ Make sure that the user that is logged in is able to read/write from/to this folder. If this is not the case, the following step will not work. It’s possible to change permissions to folders for users within Windows, but that’s outside the scope of this document. Logging in to the server with an administrator account should be sufficient. Copy the right files back to the database folder  – make sure to copy both the file with extension ‘mdf’ as well as with the extension ‘ldf’. Start all services once more; ‘DCN-SW Server (DCNNG)’, ‘SQL Server (SQLEXPRESS)’ and ‘SQL Server VSS Writer’. Run the ‘Repair’ function from the DCN-SW installation package. The Repair Wizard will run through the procedure of creating a new database or selecting an already existing one. Choose the existing database; If the repair process is successful, the following window will be shown: The “Bosch DCN Conference Software Server Console” from the Windows notification area will show the system is running correctly:

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

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.

In order to add authorizations to an existing license, the current license key is required as well as the new authorization numbers. How to find this key is detailed in another article: How to find the license key loaded in a DCN-CCU2 Follow the next steps for adding the new authorizations: Go to https://license.boschsecurity.com Fill in the CCU's Serial Number and CHK: Enter the current license key (this is found on the license key document received after activating the previous authorization numbers). In the following windows the license information is shown and it's possible to add additional authorization numbers. If multiple authorization numbers need to be added, choose "Next Authorization" If all authorization numbers are added, choose "Finish register" Next window will give the opportunity to register a spare CCU if applicable. A last verification is done in the next window, if things need to be changed, the process goes back to step 4. The license key with all information is shown on the next page. Note that the Print button doesn't work in all browsers, for this refer to "Printing the License Key document to PDF" Upload the license key into your CCU or NCO. The Bosch ‘download and license tool’ is to be used to upload your license into a CCU2.

Question Can a CCU be used in the same DCN-NG system as a CCU2 or CCUB2? Answer No, this is not possible. Mixing CCUs and CCU2/CCUB2s in a DCN-NG system is not supported. It’s also not possible to use a CCU as a spare unit in case of failure of a CCU2/CCUB2 in a DCN-NG system.

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.

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 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?

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.