Difference between revisions of "Turbine 6.2 - Release notes"
From Zenitel Wiki
(→VSF-TURBINE 6.2.3.0) |
(→Release info) |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | Previous Release - [[Turbine 6.1 - Release notes]] | |
| + | |||
| + | Next Release - [[Turbine 6.4 - Release notes]] | ||
| + | |||
This document provides the release notes for VSF-Turbine 6.2 with incremental bug fix releases. The release notes for VSF-Turbine 6.2 describe new features, improvements and issues fixed after VSF-Turbine 6.1. | This document provides the release notes for VSF-Turbine 6.2 with incremental bug fix releases. The release notes for VSF-Turbine 6.2 describe new features, improvements and issues fixed after VSF-Turbine 6.1. | ||
| + | ==Release info== | ||
'''Name:''' VSF-Turbine <br> | '''Name:''' VSF-Turbine <br> | ||
| − | '''Description:''' VSF-Turbine is a firmware archive for | + | '''Description:''' VSF-Turbine is a firmware archive for [[Zenitel Devices based on iMX28|Zenitel devices based on the IMX28 processor]]. |
| − | + | ||
The firmware is delivered in a ZIP archive:. <br> | The firmware is delivered in a ZIP archive:. <br> | ||
'''Version:''' | '''Version:''' | ||
| − | * '''vsft-6.2.x.x''' - Used for standard in-field upgrades | + | |
| + | *'''vsft-6.2.x.x''' - Used for standard in-field upgrades | ||
| + | |||
'''Date:''' 09.08.2021 <br> | '''Date:''' 09.08.2021 <br> | ||
'''Status:''' General Availability | '''Status:''' General Availability | ||
| Line 21: | Line 27: | ||
{{Note|Both Multisite Trunking and VS-Client are free of charge in IC-EDGE}} | {{Note|Both Multisite Trunking and VS-Client are free of charge in IC-EDGE}} | ||
| − | = VSF-TURBINE 6.2.3.1 = | + | =VSF-TURBINE 6.2.3.1= |
| − | ==Fixed Issues - Turbine Intercom | + | ==Fixed Issues - Turbine Intercom== |
===MTN-3255 Calls going through 3CX SBC hangs up after 30 seconds=== | ===MTN-3255 Calls going through 3CX SBC hangs up after 30 seconds=== | ||
The record-route handling for strict routing did not work properly. This is now fixed. | The record-route handling for strict routing did not work properly. This is now fixed. | ||
| Line 28: | Line 34: | ||
<br> | <br> | ||
| − | = VSF-TURBINE 6.2.3.0 = | + | =VSF-TURBINE 6.2.3.0= |
| − | ==Fixed Issues - Turbine Intercom | + | ==Fixed Issues - Turbine Intercom== |
| − | === MTN-3359 Audio routing from Line-in to Speaker out not working === | + | ===MTN-3359 Audio routing from Line-in to Speaker out not working=== |
Fixed audio routing on devices supporting line in (TKIE and TFIE). This have been an issue on on all previous 6.x releases. | Fixed audio routing on devices supporting line in (TKIE and TFIE). This have been an issue on on all previous 6.x releases. | ||
| − | === MTN-3339 Relays now return states without need to be triggered first=== | + | ===MTN-3339 Relays now return states without need to be triggered first=== |
| − | === MTN-3334 TLS 1.1. support over https is removed from devices === | + | ===MTN-3334 TLS 1.1. support over https is removed from devices=== |
| − | === MTN-3319 Offhook does no longer trigger factory reset count.=== | + | ===MTN-3319 Offhook does no longer trigger factory reset count.=== |
<br> | <br> | ||
| − | + | =Known Issues= | |
| − | === MTN-3299 TLS Private Keys not restored on Turbine stations=== | + | ===MTN-3299 TLS Private Keys not restored on Turbine stations=== |
In case that TLS Private Keys are deleted from Turbine station, the only way to restore them is to manually upload them to the station. Factory reset or station upgrade will not restore TLS Private Keys. | In case that TLS Private Keys are deleted from Turbine station, the only way to restore them is to manually upload them to the station. Factory reset or station upgrade will not restore TLS Private Keys. | ||
| − | === MTN-2692 Turbine stations won't register to ICX500 or Alphacom if the dash symbol is not removed from the Directory Number field.=== | + | ===MTN-2692 Turbine stations won't register to ICX500 or Alphacom if the dash symbol is not removed from the Directory Number field.=== |
In an unconfigured Turbine station there is a dash character in the Directory Number field in the "Main Settings menu. This dash symbol must be removed when the directory number is entered, else the station will fail to register. | In an unconfigured Turbine station there is a dash character in the Directory Number field in the "Main Settings menu. This dash symbol must be removed when the directory number is entered, else the station will fail to register. | ||
| − | === MTN-2686 Outputs not working for Exigo amplifiers in SIP mode=== | + | ===MTN-2686 Outputs not working for Exigo amplifiers in SIP mode=== |
GPO's does not work when exigo amplifiers are in SIP mode. | GPO's does not work when exigo amplifiers are in SIP mode. | ||
| − | === MTN-2363 Factory reset does not delete uploaded Script=== | + | ===MTN-2363 Factory reset does not delete uploaded Script=== |
All uploaded scripts should also be removed on Factory reset | All uploaded scripts should also be removed on Factory reset | ||
| − | === MTN-2362 H.264 RTSP stream in UDP mode can display small artifacts at the bottom of the stream=== | + | ===MTN-2362 H.264 RTSP stream in UDP mode can display small artifacts at the bottom of the stream=== |
H.264 RTSP stream in UDP mode can display small artifacts at the bottom of the stream. | H.264 RTSP stream in UDP mode can display small artifacts at the bottom of the stream. | ||
| − | === MTN-2361 TCIV H264 stream does not work in Honeywell Maxpro NVR=== | + | ===MTN-2361 TCIV H264 stream does not work in Honeywell Maxpro NVR=== |
RTSP H.264 does not work in Honeywell Maxpro NVR, workaround is to use MJPEG RTSP stream | RTSP H.264 does not work in Honeywell Maxpro NVR, workaround is to use MJPEG RTSP stream | ||
| − | === MTN-2360 Client side forwarding does not work in SIP mode=== | + | ===MTN-2360 Client side forwarding does not work in SIP mode=== |
Client side forwarding, which can be configured as a DAK action or activated from INCA display menu, does not work in SIP mode. Workaround is to use SIP server side forwarding. | Client side forwarding, which can be configured as a DAK action or activated from INCA display menu, does not work in SIP mode. Workaround is to use SIP server side forwarding. | ||
| − | === MTN-2359 Stream is not always established in Pelco VideoExpert VMS version 3.0 or newer=== | + | ===MTN-2359 Stream is not always established in Pelco VideoExpert VMS version 3.0 or newer=== |
Stream is not always established in Pelco VideoExpert VMS version 3.0 or newer, workaround is to follow all the steps described here https://wiki.zenitel.com/wiki/Adding_TCIV_ONVIF_camera_to_Pelco_VideoXpert_Professional when adding TCIV station to Pelco VideoExpert | Stream is not always established in Pelco VideoExpert VMS version 3.0 or newer, workaround is to follow all the steps described here https://wiki.zenitel.com/wiki/Adding_TCIV_ONVIF_camera_to_Pelco_VideoXpert_Professional when adding TCIV station to Pelco VideoExpert | ||
| − | === MTN-2358 Making a point-to-point call during High priority Group call will drop group call audio.=== | + | ===MTN-2358 Making a point-to-point call during High priority Group call will drop group call audio.=== |
When 2 stations establish a point-to-point call during High priority Group call, they will no longer receive audio from current High priority group call. | When 2 stations establish a point-to-point call during High priority Group call, they will no longer receive audio from current High priority group call. | ||
| − | === MTN-2356 SNMP not working properly on TCIV under high CPU load=== | + | ===MTN-2356 SNMP not working properly on TCIV under high CPU load=== |
SNMP is not working properly on TCIV under high CPU load, which means that SNMP traps and inform messages can be sent with delay, or not be sent at all. This only happens if TCIV is placed under very high load, under normal operating conditions SNMP function without any issues. | SNMP is not working properly on TCIV under high CPU load, which means that SNMP traps and inform messages can be sent with delay, or not be sent at all. This only happens if TCIV is placed under very high load, under normal operating conditions SNMP function without any issues. | ||
| − | === MTN-2339 Group call chime is not played on 3rd party SIP stations=== | + | ===MTN-2339 Group call chime is not played on 3rd party SIP stations=== |
Group call chime (WAV file) is not played on third party SIP devices when Group Call is set over multicast IP address. | Group call chime (WAV file) is not played on third party SIP devices when Group Call is set over multicast IP address. | ||
| − | === MTN-2220 Default SNMP settings issue with firmware downgrade to 4.9=== | + | ===MTN-2220 Default SNMP settings issue with firmware downgrade to 4.9=== |
When downgrading from VSFT 4.11+ to 4.9 a factory reset is necessary if user wants to use default SNMP configuration. For custom snmp.conf file, re-upload with a custom snmp.conf file will fix the problem. | When downgrading from VSFT 4.11+ to 4.9 a factory reset is necessary if user wants to use default SNMP configuration. For custom snmp.conf file, re-upload with a custom snmp.conf file will fix the problem. | ||
| − | === MTN-1073 Group call fails if system previously configured with ZAP=== | + | ===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. | 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. | ||
<br> | <br> | ||
| − | |||
[[Category: Release notes]] | [[Category: Release notes]] | ||
Latest revision as of 09:28, 21 June 2024
Previous Release - Turbine 6.1 - Release notes
Next Release - Turbine 6.4 - Release notes
This document provides the release notes for VSF-Turbine 6.2 with incremental bug fix releases. The release notes for VSF-Turbine 6.2 describe new features, improvements and issues fixed after VSF-Turbine 6.1.
Contents
- 1 Release info
- 2 VSF-TURBINE 6.2.3.1
- 3 VSF-TURBINE 6.2.3.0
- 4 Known Issues
- 4.1 MTN-3299 TLS Private Keys not restored on Turbine stations
- 4.2 MTN-2692 Turbine stations won't register to ICX500 or Alphacom if the dash symbol is not removed from the Directory Number field.
- 4.3 MTN-2686 Outputs not working for Exigo amplifiers in SIP mode
- 4.4 MTN-2363 Factory reset does not delete uploaded Script
- 4.5 MTN-2362 H.264 RTSP stream in UDP mode can display small artifacts at the bottom of the stream
- 4.6 MTN-2361 TCIV H264 stream does not work in Honeywell Maxpro NVR
- 4.7 MTN-2360 Client side forwarding does not work in SIP mode
- 4.8 MTN-2359 Stream is not always established in Pelco VideoExpert VMS version 3.0 or newer
- 4.9 MTN-2358 Making a point-to-point call during High priority Group call will drop group call audio.
- 4.10 MTN-2356 SNMP not working properly on TCIV under high CPU load
- 4.11 MTN-2339 Group call chime is not played on 3rd party SIP stations
- 4.12 MTN-2220 Default SNMP settings issue with firmware downgrade to 4.9
- 4.13 MTN-1073 Group call fails if system previously configured with ZAP
Release info
Name: VSF-Turbine
Description: VSF-Turbine is a firmware archive for Zenitel devices based on the IMX28 processor.
The firmware is delivered in a ZIP archive:.
Version:
- vsft-6.2.x.x - Used for standard in-field upgrades
Date: 09.08.2021
Status: General Availability
Compatibility: Pulse to IC-EDGE System
You can upgrade from Pulse (VS-IS 4.x) to IC-EDGE, but the whole system needs to run with the same Turbine software (VS-IS 5/6).
In an IC-EDGE System, INCA intercoms cannot be used as the Edge Controller.
TCIV video intercoms should not be used as the Edge Controller for systems exceeding 4 devices.
IMT 1.5 or newer can be used for station discovery and upgrade but must not be used to configure IC-EDGE.
Pulse to IC-EDGE Licenses
Pulse licenses will be honored in an IC-EGDE System. This means that when you upgrade firmware from VS-IS 4.x to 5.x/6.x your Pulse licenses will work for IC-EDGE.
|
The number of free VS station licenses has been increased from 16 to 32 in IC-EDGE. This means that you get an additional 16 VS stations to connect to in IC-EDGE |
|
|
Both Multisite Trunking and VS-Client are free of charge in IC-EDGE |
VSF-TURBINE 6.2.3.1
Fixed Issues - Turbine Intercom
MTN-3255 Calls going through 3CX SBC hangs up after 30 seconds
The record-route handling for strict routing did not work properly. This is now fixed.
VSF-TURBINE 6.2.3.0
Fixed Issues - Turbine Intercom
MTN-3359 Audio routing from Line-in to Speaker out not working
Fixed audio routing on devices supporting line in (TKIE and TFIE). This have been an issue on on all previous 6.x releases.
MTN-3339 Relays now return states without need to be triggered first
MTN-3334 TLS 1.1. support over https is removed from devices
MTN-3319 Offhook does no longer trigger factory reset count.
Known Issues
MTN-3299 TLS Private Keys not restored on Turbine stations
In case that TLS Private Keys are deleted from Turbine station, the only way to restore them is to manually upload them to the station. Factory reset or station upgrade will not restore TLS Private Keys.
MTN-2692 Turbine stations won't register to ICX500 or Alphacom if the dash symbol is not removed from the Directory Number field.
In an unconfigured Turbine station there is a dash character in the Directory Number field in the "Main Settings menu. This dash symbol must be removed when the directory number is entered, else the station will fail to register.
MTN-2686 Outputs not working for Exigo amplifiers in SIP mode
GPO's does not work when exigo amplifiers are in SIP mode.
MTN-2363 Factory reset does not delete uploaded Script
All uploaded scripts should also be removed on Factory reset
MTN-2362 H.264 RTSP stream in UDP mode can display small artifacts at the bottom of the stream
H.264 RTSP stream in UDP mode can display small artifacts at the bottom of the stream.
MTN-2361 TCIV H264 stream does not work in Honeywell Maxpro NVR
RTSP H.264 does not work in Honeywell Maxpro NVR, workaround is to use MJPEG RTSP stream
MTN-2360 Client side forwarding does not work in SIP mode
Client side forwarding, which can be configured as a DAK action or activated from INCA display menu, does not work in SIP mode. Workaround is to use SIP server side forwarding.
MTN-2359 Stream is not always established in Pelco VideoExpert VMS version 3.0 or newer
Stream is not always established in Pelco VideoExpert VMS version 3.0 or newer, workaround is to follow all the steps described here https://wiki.zenitel.com/wiki/Adding_TCIV_ONVIF_camera_to_Pelco_VideoXpert_Professional when adding TCIV station to Pelco VideoExpert
MTN-2358 Making a point-to-point call during High priority Group call will drop group call audio.
When 2 stations establish a point-to-point call during High priority Group call, they will no longer receive audio from current High priority group call.
MTN-2356 SNMP not working properly on TCIV under high CPU load
SNMP is not working properly on TCIV under high CPU load, which means that SNMP traps and inform messages can be sent with delay, or not be sent at all. This only happens if TCIV is placed under very high load, under normal operating conditions SNMP function without any issues.
MTN-2339 Group call chime is not played on 3rd party SIP stations
Group call chime (WAV file) is not played on third party SIP devices when Group Call is set over multicast IP address.
MTN-2220 Default SNMP settings issue with firmware downgrade to 4.9
When downgrading from VSFT 4.11+ to 4.9 a factory reset is necessary if user wants to use default SNMP configuration. For custom snmp.conf file, re-upload with a custom snmp.conf file will fix the problem.
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.