Notes on OPENSCAPE devices (April 2018)

IMPORTANT: to avoid device damage during firmware update it is advisable to use a local FTP server (in company LAN) to update the system phones and not the FTP server that Swyx provides.

I.e. the firmware files should only be downloaded from Swyx-FTP and made available to the devices on a local drive and a local FTP server.

The system phones Openscape 62, 64 and 68 are always delivered by UNIFY with a SIP firmware.

To use these SIP system phones with a SwyxWare (NOT SwyxON), they have to be flashed to the HFA firmware.

In the first deliveries of UNIFY firmware versions smaller than version 1.7 were installed.

This first had to be updated to a version greater than or equal to 1.7 to be able to flash over to the HFA version.

Swyx has therefore released version SIP 2.5 in support.

 In a few cases, the devices were shipped with a SIP Developer version, recognizable on the device's WebUI. This firmware name ended with the abbreviation DEV.

With these devices the firmware update had to be done with DERT Tool, but this was not possible with http via WebUI or FTP via SwyxWare MMC. The DERT tool is also provided by Swyx.

 The above points should be a thing of the past, i.e. the devices are already delivered with a SIP version greater than 1.7, the DEV version is also no longer in circulation (old stocks of the partners excluded).

If the above points are fulfilled, i.e. the SIP firmware version is greater than or equal to version 1.7 and there is no DEV version, these devices can be reflashed to the HFA firmware in the familiar way (FTP via SwyxWare Administration or http via the device's WebUI).

It is also possible to update several devices simultaneously from an old SIP firmware to a new one using SwyxWare MMC. For example, 20 devices delivered with SIP version 1.3 can be automatically updated to SIP version 1.7 using SwyxWare MMC and then reloaded to HFA. Only the corresponding firmware files have to be exchanged on the FTP.

Emergency operation (NT)" display

This message occurs if the NTP server is not compatible with the phones.
Workaround: use alternative NTP server (e.g. pool.ntp.org) on the phones.
Note: if the time server is distributed via DHCP, this must be taken into account