Actions

Zenitel Connect 1.11 - Release Notes

From Zenitel Wiki

This article provides the release notes for Zenitel Connect Pro (ZCP) running on the ICX-510 hardware or in a Virtual Environment. The release notes for ZCP 1.11 describe new features, improvements and fixed issues after version 1.10.x.

Release info

Version: 1.11.0
Date: 11.11.2026
Status: 1.11.0: General Availability
Compatibility: Compatible with device software version 10.1.3.X. Compatible with Zenitel PAVA Vipedia-12 running Vipedia SW bundle 5.1.4.0P

The Zenitel Connect Pro software is available in different packages:

  • Zenitel_Connect_ICX_1.11.x.swu - Upgrade package for Zenitel Connect Pro running on ICX-510
  • Zenitel_Connect_VM_1.11.x.swu – Upgrade package for a VMWare or VirtualBox VM
  • Zenitel_Connect_VMware_1.11.x.zip - Installation package for a fresh install of Zenitel Connect Pro running on VMWare
  • Zenitel_Connect_VBox_1.11.x.zip - Installation package for a fresh install of Zenitel Connect Pro running on Virtual Box
  • Zenitel_Connect_ICX_1.11.x-node-red.swu – installation package for Node-RED on ICX-510
  • Zenitel_Connect_VM_1.11.x-node-red.swu – installation package for Node-RED on VM
  • Zenitel_Connect_ICX_prod_icx510_1.11.x.zip - Software used for changing an ICX-510 from running ICX-AlphaCom to run Zenitel Connect Pro, or recovery after a system crash.
  • Excel template file for easy importing: Zenitel Connect Excel Template 1.20

Version 1.11.0

New features

  • Advanced GPIO for SPA Broadcast integration
  • Integrated Node-RED page into ZC with credential management
  • Support for Out of Band management
  • New fault management system


Fixed issues

ZEN-3135 When both eth0 and eth1 were set to DHCP, the system might become inaccessible after upgrade due to default routes

When both eth0 and eth1 were configured with DHCP and both DHCP servers provided a default gateway, the system installed two default routes with the same metric. As a result, the system could become inaccessible from remote networks. This has been fixed. The system now installs only one default route: via eth1 on ICX-510 and via eth0 on VMs.

Note: if remote access is needed through the other interface, connect a PC directly to the network port, open Connect Web, and add a static route to the remote network via that interface. Click Save. Remote access will then be restored.

ZEN-2803 The use of 802.1X to control access to device networks did not work in version 1.10.0

A new, more secure commissioning mechanism caused an issue with 802.1X: Zenitel Connect Pro overwrote preconfigured values with defaults.

ZEN-2754 If system time was set to a date prior to the JWT token send to devices during commissioning, devices could start continuously rebooting

This is now fixed. This occured right after an ICX-510 system stared up without NTP server connection. The system date was then set to 2024. To remedy the issue, either make certain that the system can connect to an NTP server, or manually set the correct date and time.

ZEN-2720 Issues with accessing ETH0 from the network as the server is routing traffic back out via ETH1

This is now fixed. When used eth0 and eth1 for different specific purposes the routing could not be configured and might have caused issues setting up the desired traffic flows.

ZEN-2686 Enforced authentication for inbound SIP requests on External Communication trunks with outbound registration (if inbound authentication was configured).

If the IP telephony provider did not support authenticating to an external system (i.e., ZCP inbound), outbound credentials needed to be entered in the ZCP trunk configuration, and the inbound password left blank. On upgrade from earlier versions, this had to be manually adjusted if needed.

ZEN-2158 NTS setting not applied until reboot on ZCP virtual machine

On Zenitel Connect running as a virtual machine, enabling NTS or changing the NTP server to an NTS server does not take effect until the system is rebooted. Until then, time is not synchronized. This has been fixed, and NTS settings now take effect immediately after saving.

ZEN-649 TLS SIP trunk to CUCM fails due to certificate exchange

A SIP trunk to Cisco CUCM using TLS failed because of certificate exchange errors. Previously the workaround was to use TCP or UDP. This is fixed; TLS SIP trunks to CUCM now work as expected.


Fixed Security issues

ZEN-3016 Fixes the CVE-2026-95615

  • CVE-2026-95615 Zenitel Connect OS command injection in hiatus container via unsanitized filename in audio messages API

ZEN-3015 Fixes the CVE-2026-95614

  • CVE-2026-95614 Zenitel Connect host applies rsyslog configuration written to a volume shared with the hiatus container

ZEN-3012 Fixes the CVE-2026-95613

  • CVE-2026-95613 Zenitel Connect pREST API adopts arbitrary PostgreSQL role from unvalidated JWT sub claim

ZEN-2918 This change fixes the CVE-2026-105625

  • CVE-2026-105625 - Zenitel Connect web interface loads integration iframe without sandboxing or origin restriction

ZEN-2917 This change fixes the CVE-2026-105623

  • CVE-2026-105623 - Zenitel Connect web interface serves production JavaScript source maps without authentication

ZEN-2883 This change fixes the following reported CVE’s:

  • CVE-2026-105671 - Zenitel Connect login allows username enumeration via verbose error responses*.*
  • CVE-2026-105624 - Zenitel Connect login allows account-lockout denial of service
  • CVE-2026-105622 - Zenitel Connect missing lockout and rate limiting on the WAMP-CRA authentication channel


Known issues

ZEN-3194 When a second broadcast is created using the same linked audio message as an already existing broadcast it will not work

To workaround this, upload a copy of the first Audio message and use this for the second broadcast.

ZEN-3159 Unable to forward call to ITSV-5 with Autoanswer ON

When making a call to a forwarded station with ITSV-5 as final target, it is expected that the call is forwarded to ITSV-5 and auto-answered there, but this is not working. Workaround is to use the Autoanswer OFF until this has been fixed.

ZEN-3149 TLS between different ICX cannot be configured in a local network without DNS or internet access

When two ICXs try to use SIP trunks with TLS through a firewall, they do not trust each other. This makes the SIP trunks unreachable. This is due to the certificate specifies hostnames.

Workaround:

  • Set the IP address for the hostname.
  • Reboot to regenerate the CA.
  • Use the new CA.

ZEN-3121 When replacing a device and you get the message “Mismatched device types found” the device needs to be reset

The system will try and set the new device type read from the device but this results in system instability. These devices needs to be reset and the excel updated or added manually.

ZEN-3118 When importing from Excel if you get the message “Mismatched device types found” on devices these devices needs to be reset

Most likely the device type in the excel does not match the real device type reported by the device. The system will try and set the new device type read from the device but this results in system instability. These devices needs to be reset and the excel updated or added manually.

ZEN-2973 When calls come into a call queue in bursts sometimes they can be answered out of order

This can happen when the queue is under load. There is currently no work around for this issue.

ZEN-2774 It may take a long time for an ITSV to pair with Zenitel Connect after the ITSV was manually factory defaulted

If an ITSV was factory reset from its Device gui it takes a long time to pair again with Zenitel Connect. To speed this up, the ITSV needs to be deleted from the Zenitel Connect device list and then be set up again.

Workaround: Take a backup, then delete it from the Zenitel Connect configuration, and restore backup

ZEN-2758 Devices not operational after backup and restore

After an upgrade followed by a backup and restore, devices may remain in the Not Operational state.

Workaround: run a new device scan in Zenitel Connect Web, devices will return to the Operational state.

ZEN-2669 Bug where Cloud connection is not possible to activate after factory defaulted Zenitel Connect system

If the system and devices were connected in RMM when factory defaulting Zenitel Connect, the cloud can think it is already claimed by the previous version.

Before performing a factory reset, make sure to remove claimed Zenitel Connect and its devices from the RMM.

ZEN-2248 Issue with removing devices from the Zenitel Cloud RMM without removing them from the Zenitel Connect device list

If a device is removed from the Zenitel Cloud RMM but it is still existing in the Zenitel Connect setup it needs to be deleted from the Zenitel Connect setup as well to get the RMM to start working properly with this device again.

ZEN-1667 Adding a second network adapter to a VMWare VM

When a second network adapter is added to an already configured system running on VMware, the original network adapter is no longer available under its configured IP-address. Its configuration becomes ‘Disabled’. The new network becomes Eth0 and has DHCP as configuration.

ZEN-1605 If no device type is set when importing excel the import will fail

The system cannot switch the device type from empty to the detected device. To fix this add the correct device types to the excel before importing.

ZEN-796 Cannot replace a device by importing devices via the Excel spreadsheet

When in the Devices and Connections - Configuration menu and selecting Import from Excel. If the imported list has the same directory number as one of the currently configured devices but with a different MAC address the old device is kept

Work around: Update the device manually in Zenitel Connect Web

ZEN-752 Vipedia Store and Forward can only be initiated from ITSV as it requires # and * which is not present on other Zenitel devices.

There is no workaround for this, other then to use an ITSV.

DS-1778 Important Notice: Firmware 10.x Compatibility on Legacy i.MX28 Devices (Manufactured ≤ 2018)

  • Affected: Turbine i.MX28 devices manufactured up to the end of 2018.
  • Recommendation: Do not upgrade directly to 10.x. Remain on VS-IS 9.4.3.x until automated support is available in an upcoming release.
  • If already upgraded to 10.x: The device remains fully operational, but subsequent upgrades/downgrades will fail (Failure - Recovery OS cannot start).
  • Action: Install Recovery OS 1.2.0.1 via DeviceWeb (Station Administration > Upgrade > Recovery OS Upgrade) to restore normal upgrade functionality.

Full procedure documented on Wiki: Legacy_iMX28_Recovery_OS_Upgrade_Procedure