Difference between revisions of "Turbine 4.11 - Release notes"
From Zenitel Wiki
(→Bugfixes and Improvements - VSF-Turbine 4.9.3.1) |
(→Bugfixes and Improvements - VSF-Turbine 4.9.3.0) |
||
Line 18: | Line 18: | ||
== Bugfixes and Improvements == | == Bugfixes and Improvements == | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==Known Issues - VSF-Turbine 4.9.3.1 == | ==Known Issues - VSF-Turbine 4.9.3.1 == |
Revision as of 15:15, 9 January 2019
Contents
- 1 Release info
- 2 VSF-TURBINE 4.11.2.5
- 2.1 New Features - Turbine Intercom
- 2.2 New Features - Exigo Network Amplifiers
- 2.3 Technical Preview
- 2.4 Bugfixes and Improvements
- 2.5 Known Issues - VSF-Turbine 4.9.3.1
- 2.6 Known Issues - VSF-Turbine 4.9.3.0
- 2.6.1 MTN-598 IP station fails to register if Hebrew name is too long
- 2.6.2 MTN-1077 Lamp test not functioning on ECPIR-3P and belonging EBMDR-8
- 2.6.3 MTN-1073 Group call fails if system previously configured with ZAP
- 2.6.4 MTN-268 Relay follow M-key cannot handle quick M
- 2.6.5 MTN-1503 Changing the Detailed Logging setting disables syslog logging
- 2.6.6 VSIS-878 Factory reset does not delete uploaded Script
- 2.6.7 SNOW-579 TFIE-6 does not display AlphaCom status-messages in Idle
Release info
Name: VSF-Turbine
Description: VSF-Turbine is a firmware archive for all Turbine Family Intercom stations including devices:
TCIS-x, TKIS-2, TCIV-x, TMIS-x, TFIE-x, TKIE-x, TFIX-x, ECPIR-3P, ENA-2060AC (only in SIP mode), Exigo IP speakers and Exigo Network Amplifiers (AlphaCom mode only).
Version: The firmware is delivered in two different ZIP archives:
- vsft-4.11.2.x - Used for standard in-field upgrades
- vsft-prod-4.11.2.x - Used in production- and recovery upgrades.
Version: 4.11.2.5
Date: 15.01.2019
Status: Limited Availability
VSF-TURBINE 4.11.2.5
New Features - Turbine Intercom
New Features - Exigo Network Amplifiers
Technical Preview
Bugfixes and Improvements
Known Issues - VSF-Turbine 4.9.3.1
VSIS-878 Factory reset does not delete uploaded Script
All uploaded scripts should also be removed on Factory reset
MTN-1964 Tone volume not working for tone test
There was an error in the tone test that caused the Tone volume to be ignored. The Tone volume was always equal to the speaker volume.
MTN-2073 Turbine Sound detection (VAD) does not trigger correctly
Minimum Amplitude setting under the Turbine Sound Detection setting doesn't take effect. Reboot Main Application or System reboot doesn't have any effect.
Known Issues - VSF-Turbine 4.9.3.0
MTN-598 IP station fails to register if Hebrew name is too long
More than 12 characters entered causes registration problems
MTN-1077 Lamp test not functioning on ECPIR-3P and belonging EBMDR-8
Alphacom DAK Lamp test (feature 7874) not implemented on DAK Panel ECPIR-3P and belonging EBMDR-8
MTN-1073 Group call fails if system previously configured with ZAP
If system was configured with ZAP (VS-IMT Pulse SDK project) and then switched to XML configuration by deleting data.lua file, it is possible that Group Calls shall not work. A workaround is that (1) data.lua file is deleted from all stations including Pulse server - this will reboot stations, and (2) after reboot go to Server configuration -> Save + Apply - this will again reboot all stations.
MTN-268 Relay follow M-key cannot handle quick M
Relay configured to follow M-key does not handle quick press on M-key
MTN-1503 Changing the Detailed Logging setting disables syslog logging
If Detailed Logging is enabled or disabled, the syslog functionality doesn't work - Turbine log messages do not arrive on the syslog server. Workaround: Changing Log level setting for syslog will enable the syslog logging again
VSIS-878 Factory reset does not delete uploaded Script
All uploaded scripts should also be removed on Factory reset
SNOW-579 TFIE-6 does not display AlphaCom status-messages in Idle
There is no way of knowing if a TFIE-6 is for example forwarded(71,72) or marked absent(77x). Workaround: During commissioning it is possible by Class Of Service programming in AlphaCom to deny access to these services for the TFIE-6