Page History

• An N670 with software 2.52 or higher, that supports up to 20 DECT handsets
• An N870(E) with software 2.52 or higher, that supports up to 20.000 DECT handsets
• An Gigaset PRO DECT handset
• A license per DECT handset that is used for Messaging and/or Location

As we are continuous improving the software and adding new AML features please install the latest official software release.

Go to the wiki page: Firmware N870(E)/N670/N610 to download the latest firmware.

In the web-interface go to: SETTINGS - System - Firmware

• Click Browse... and select the firmware file from your computer‘s file system.
• Click Upload to upload the firmware file.
• When ready, the pop-up "Press SET to start update schedule" will appear.
  The URL to the firmware file will change to the local storage: http://localhost/swupdate/<firmwarefile>
• Select Immediately if you want to start the update now.
• Scroll down and press SET
• The firmware update will start after a few minutes.

Application servers can communicate with the DECT system via the MQTT protocol. Dependent on the chosen Alarm server, one of the connection methods listed below is used.

The MQTT access can be configured via the:

• Web-interface
• Auto-provisioning

You can connect using:

• Pre-shared key (PSK) using port 8884 FAQ - Application server connection examples PSK
• Certificates using port 8885 FAQ - Application server connection examples Certificates
• Secure with username and password using port 8886 (Needs to be enabled) FAQ - Application server TLS connection using username/password

In the web-interface go to: SETTINGS - Online services - Application servers

Create an Account for an Application server

You now can create an application server access.

• Id: id for external clients are: "as1", "as2" ...
• Application server name (username) (At least one character is needed)
• Password (has to be at least 32 characters using hexadecimal digits only: 0 1 2 3 4 5 6 7 8 9 a b c d e f A B C D E F)

The following example shows you how to create an Application server account via auto-provisioning.

<?xml version="1.0" encoding="UTF-8"?>
<provisioning version="1.1" productID="e2">

<nvm>

<oper name="set_external_client">

<param name="Username" value="as1" />
<param name="Password" value="123456789012345678901234567890aB" />

</oper>

</nvm>
</provisioning>