Provisioning a RTX DECT 500/600-Multicell-System via a HTTP-Server (Export/Import of configurations data) Version: 11/202, firmware 05.30 B00022

These instructions are intended to restore an existing DECT multi-cell system, e.g. after a factory reset, or to PREPARE the configuration of a DECT multi-cell system for a first installation in order to be able to quickly distribute it automatically via HTTP server at the time of installation.

In addition, you will find information here on how to have certain configurations carried out automatically on a regular basis (e.g. adding or deleting users incl. user handset assignment).

ALL settings made in the WebUI of the DECT multi-cell system can be exported in the configuration menu of the bases and saved in a configuration file.
This configuration file can be edited and uploaded back to the base.

BUT NOT all settings that can be made in the configuration file are reflected in the WebUI.

e.g. %LDAP_VIRTUAL_LISTS%:0x00

It is also possible to distribute/upload individual configuration elements (e.g. only the LDAP configuration of the global telephone book) subsequently.

If you want to perform a new installation of an existing system after it has been set to the delivery state, the configurations of the primary bases must be exported BEFORE the factory reset.

The exported files can then be customised according to the following instructions, and a base-specific file created for each base, as well as a file for the multi-cell settings.

The personal telephone books of the handsets should also be exported, as it makes sense to reset the handsets as part of a new installation including a factory reset (master reset in the *service* menu).

If you want to carry out an initial installation, you can create the corresponding configuration files as described below and distribute/upload them to the bases.

Testscenario:

1 DECT 500 Base (8660 primary base)

Name: Dect500M-8660

MAC: 00087b0ae984

1 DECT 600 Base (8663 secondary base)

Name: Dect500S-8663

MAC: 00087B1573F8

1 Handset D510

IPEI : (02 77 94 3C 9E)

1 Handset D565

IPEI: (02 76 A9 EB DB)

A DECT 500 base cannot be added to an existing DECT 600 multi-cell system.

The DECT 500 base MUST be configured as a primary base, the DECT 600 as a secondary.
I.e. a DECT 600 base can only be added as a secondary base to an existing DECT 500 multi-cell system, but will be adapted to the DECT 500 multi-cell system in terms of functionality.

A corresponding warning/instruction is displayed in the WebUI.

1  IIS Server on which the files are stored

The mime type must be created/adapted for the file extension CFG to enable the download of the files (application/octet-stream).

The following file should then appear in the above-mentioned directory:

web.config
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<staticContent>
<mimeMap fileExtension=".cfg" mimeType="application/octet-stream" />
</staticContent>
</system.webServer>
</configuration>

Without adjustment, the CFG files will be displayed in the browser and not downloaded.
You can check whether the settings are correct by calling up the download page (e.g. http://192.168.1.14/D500Config/00087b0ae984.cfg) and clicking on a CFG file.
If it is displayed in the browser, the setting must be corrected.
If the file is offered for download, the configuration is correct.

Creating the configuration files

For EACH base of the multicell, ONE file is required which contains the base-specific information (e.g. name of the base, static IP address, ...).
The name of the file consists of the MAC address of the base and the extension CFG.

E.g.
00087b0ae984.cfg for the primary base
00087B1573F8.cfg for the secondary base

In addition, ONE configuration file is required, which contains the settings of the multi-cell (including user configuration, time settings, ...).
This file can be named as follows.

E.g.
MultiCell_99999.cfg, where 99999 is the multi-cell ID.

For a multi-cell system with 2 bases, 3 files are needed, one for each of the 2 bases and one for the multi-cell settings.
If there is only one base, one file is of course sufficient for the initial setup/restoration.

The base-specific files (e.g. 00087B1573F8.cfg) can either be uploaded manually to the respective base or distributed via HTTP server.

The multi-cell-specific file (e.g. MultiCell_99999.cfg) is ONLY uploaded to the PRIMARY BASE or distributed to the PRIMARY BASE via HTTP server.

Automatic, regular distribution of the configuration

(this screenshot shows the settings of the primary base. These are updated daily at 00:00. Distribution of the provisioning link is also possible via DHCP).

For further configuration options, please see the attached PDF, as well as the comment lines in the configuration files in the example.

After you have adapted the 3 files to your requirements, they can be uploaded manually.

1. Multicell spec. file on Primary

2. Primary spec. file on Primary

3. Secondary spec. file on Secondary

After adapting the following files, you can also upload the Primary_HTTPconfig.cfg or Secondary_HTTPconfig.cfg to the bases, to force them to download their settings from the HTTP server