Difference between revisions of "Release Note Exigo 1.2"

From exigoWiki
Jump to navigation Jump to search
(Created page with "= Exigo 1.2.3.13 = Release: Official, available on request Date: 2016-12-19 Software Collection File: EXIGO-1.2.3.13.ZIP ==Software Included in the EXIGO-1.2.3.13.ZIP fil...")
 
(→‎Line Monitoring)
 
(56 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
= Exigo 1.2.3.14 =
 +
 +
Release: Official, available on request
 +
Date: 2017-5-16
 +
Software Collection File: EXIGO-1.2.3.14.zip
 +
 +
==Software Included in the EXIGO-1.2.3.14.zip file==
 +
For upgrade procedures see PDF
 +
document included in each product folder inside the EXIGO-1.2.3.14.zip file;
 +
except VS-DEVICE-MIB, as this may vary between monitoring tools.
 +
{| border="1"
 +
|+
 +
|'''Product'''
 +
|'''Version'''
 +
|'''Description'''
 +
|-
 +
|EXI-Firmware
 +
|4.2.3.14
 +
|Firmware for the following devices:  ESC1(Secondary System Controller), ENA2200, ENA2400, ECPIR-3P, ECPIR-P, EAPIR-8, EAPFX-1, EAPFX-6, EAPII-1, EAPII-6, TKIS-2, TKIE-2
 +
|-
 +
|AlphaSys Firmware
 +
|12.2.3.13
 +
|Firmware for the ESC1 (Primary System Controller/AMC-IP board)
 +
|-
 +
|Exigo Management Tools
 +
|1.2.3.7
 +
|Configuration tool, installed on a Windows PC
 +
|-
 +
|INCA Firmware
 +
|2.20.3.6
 +
|Special Exigo software for the CRM-V based panel
 +
|-
 +
|VS-DEVICE-MIB
 +
|201610190000Z
 +
|SNMP MIB for Exigo EXI-Devices, for upload in 3rd-party SNMP based monitoring tools
 +
|-
 +
|}
 +
<br>
 +
 +
== Improvements ==
 +
Support for new amplifier (ENA2x00) hardware, where Line input and Mic input have switched position.
 +
 +
== Known Issues ==
 +
 +
=== CRM-V Access Panels ===
 +
The CRM Access Panel is based on a different hardware and software than the other Exigo devices.<br>
 +
Hence the functionality is limited compared to the native Exigo ECPIR panels.
 +
 +
'''Exigo Features Not Supported on the CRM-V Access Panel:'''
 +
* Call Escalation function.
 +
* Panel lamp test.
 +
* Zone select option "Deselect Zone(s) after activity".
 +
 +
'''Deviant LED Behavior for the CRM-V Access Panel:'''
 +
* When triggering local mute control from a DAK on CRM-V, the green LED blinks. Should be steady.
 +
* Recall record green LEDs active when mic test is performed.
 +
* If microphone test is stopped by timeout, green LED never goes off (this also goes for recall record LEDs).
 +
* Red LED never active when performing mic test.
 +
* DAK key with "Alarm stop with no zones", green led lit when alarm is active but DAK not possible to use for stopping the alarm.
 +
* Zone select DAK keys can trigger activity indicators green led on other DAK keys with same zone.
 +
* DAKs with message/program/live speech/alarm programmed with zones only triggers green LED when activated.
 +
* Zone selection to all zones on DAK. No LED activity when audio activity in only some zones.
 +
* LED for live speech lit when recall control active (and vice versa).
 +
'''Workaround:''' Avoid use of CRM-V panels for functionality that is not supported.
 +
 +
=== System Configuration (Commissioning) ===
 +
Adding a new non-existing panel to the system will only report "missing device" in the ESC1 A. (After first time registration of panel the "missing device" reports will always be displayed in both A and B controller.)<br>
 +
'''Workaround:''' On commissioning, ensure that the panel has been registered.
 +
 +
Newly added ENAx does not receive audio. <br>
 +
'''Workaround:''' On commissioning, ensure that ENAx is rebooted after first time configuration.
 +
 +
System Status DAK indicators - Incorrect status after reconfiguration from system status from A to system status from B <br>
 +
'''Workaround:''' If changing the configuration of original A/B system from where "System Status DAK LED" should be showing, reboot the panel involved to assure changes take effect.
 +
 +
Device IP settings in WEB lost after upgrading from EXI-Firmware version 4.1 to 4.2. Device still has the same static IP address. <br>
 +
'''Workaround:''' Exigo mode in device WEB has to be manually selected when going from 4.1 to 4.2.
 +
 +
ECPIR-3P behaves as registered, after being removed from system, for up to 5 minutes <br>
 +
'''Workaround:''' Unplug the panel or wait for 5 minutes.
 +
 +
ESC1 Call list: Long program names will not be displayed correctly <br>
 +
'''Workaround:''' Limit program names to 10 standard characters.
 +
 +
EMT - SNMP Community string allows space character but SNMP does not support space. <br>
 +
'''Workaround:''' Avoid using space in the community string.
 +
 +
It is not possible to remove the options "Overwrite Destination" or "Timeout" from an already configured Call Escalation DAK without rebooting. <br>
 +
'''Workaround:''' Panel must be rebooted after updated configuration sent from EMT.
 +
 +
Call option "Release delay" does not work in combination with call option "Wait for PTT". <br>
 +
'''Workaround:''' Avoid using this combination.
 +
 +
"Live Speech" from DAK with "Wait for PTT" and "Timeout", starts timer from when DAK is pressed, not when PTT is pressed. <br>
 +
'''Workaround:''' Add additional 5 second Live Speech timeout when using this configuration (Wait for PTT timeout is 5 sec).
 +
 +
=== Line Monitoring ===
 +
During continuous LET monitoring and GA at high volume, LETs sometimes fail. <br>
 +
'''Workaround:''' Always have "Suspend Monitoring" enabled.
 +
 
= Exigo 1.2.3.13 =
 
= Exigo 1.2.3.13 =
  
 
  Release: Official, available on request
 
  Release: Official, available on request
 
  Date: 2016-12-19
 
  Date: 2016-12-19
−
  Software Collection File: EXIGO-1.2.3.13.ZIP
+
  Software Collection File: EXIGO-1.2.3.13.zip
  
−
==Software Included in the EXIGO-1.2.3.13.ZIP file==
+
==Software Included in the EXIGO-1.2.3.13.zip file==
−
'''For upgrade procedures see EXIGOZIP-readme.txt inside EXIGO-1.2.3.13.ZIP'''
+
For upgrade procedures see PDF
 +
document included in each product folder inside the EXIGO-1.2.3.13.zip file;
 +
except VS-DEVICE-MIB, as this may vary between monitoring tools.
 
{| border="1"
 
{| border="1"
 
|+
 
|+
Line 15: Line 117:
 
|EXI-Firmware
 
|EXI-Firmware
 
|4.2.3.13
 
|4.2.3.13
−
|Firmware for the following devices: Secondary System Controller, ENA2200, ENA2400, ECPIR-3P, ECPIR-P, EAPIR-8, EAPFX-1, EAPFX-6, EAPII-1, EAPII-6, TA-10, TKIE-2, TKIS-2, IP-Speaker
+
|Firmware for the following devices: ESC1(Secondary System Controller), ENA2200, ENA2400, ECPIR-3P, ECPIR-P, EAPIR-8, EAPFX-1, EAPFX-6, EAPII-1, EAPII-6, TKIS-2
 
|-
 
|-
 
|AlphaSys Firmware
 
|AlphaSys Firmware
 
|12.2.3.13
 
|12.2.3.13
−
|Firmware for the System Controller AMC-IP board.
+
|Firmware for the ESC1 (Primary System Controller/AMC-IP board)
 
|-
 
|-
 
|Exigo Management Tools
 
|Exigo Management Tools
Line 27: Line 129:
 
|INCA Firmware
 
|INCA Firmware
 
|2.20.3.6
 
|2.20.3.6
−
|Spesial Exigo software for the CRM-V based panel.
+
|Special Exigo software for the CRM-V based panel
 
|-
 
|-
 
|VS-DEVICE-MIB
 
|VS-DEVICE-MIB
 
|201610190000Z
 
|201610190000Z
−
|SNMP MIB for Exigo EXI-Devices, for upload in 3rd-party SNMP based monitoring tools.
+
|SNMP MIB for Exigo EXI-Devices, for upload in 3rd-party SNMP based monitoring tools
 
|-
 
|-
 
|}
 
|}
−
<br>
 
 
<br>
 
<br>
 
<br>
 
<br>
  
−
== Error Corrected ==
+
== Corrections ==
−
=== Flowire Connected Panels Can Lock Up During Network Storm (MTN-960) ===
+
=== Flowire, RSTP Setup ===
−
Panel RSTP was not working correctly in combination with Flowire. If connection issues with the primary Flowire during high system traffic could result in a network storm.<br>
+
Network storm could be generated and destabilize the system during a combination of high system traffic and connection instability on the primary Flowire link to an Access Panel.
  
−
=== Flowire Issues When Used in a RSTP Setup (MTN-995, MTN-967) ===
+
=== Database on ENA Sometimes Lost when Device is Rebooted During High Traffic ===
−
Related to fix of (MTN-960)<br>
+
Buffered configuration data was not written to configuration file if the device rebooted during high traffic situations.
−
In some reset situations the Flowire links could generate a network storm and destabilize the system. <br>
 
−
'''Side effects when RSTP is enabled in the panel:'''
 
−
*It is not possible to connect PC directly to the panel/Turbine. Workaround: connect both port of panel to an un-managed switch.
 
−
*If rack-side Flowire goes down, the network will also loose contact with the panel/Turbine-side Flowire.
 
−
*panel/Turbine will no longer forward traffic from one interface to another. (Redundant link)
 
  
−
=== Database on ENA Sometimes Lost when Device is Rebooted During High Traffic (MTN-1000) ===
+
=== ESC1 Long Term Stability ===
−
Buffered configuration data was not written to configuration file, but the file was still interpreted to be legal after reset. <br>
+
Reboot of ESC1 has been observed after 3+ months of continuously monitoring the internal DSPs status.
−
Since the file was interpreted as legal the configuration backup file was not used and the device entered "not configured" mode.<br>
 
−
The issue could also result in endless reboot of the device after reboot. <br>
 
  
−
=== AlphaSys Long Term Stability (MTN-965) ===
+
=== ESC1 Fault List and Attached Device List Not Being Synchronized ===
−
After 3 months the system could reboot. The continuous monitoring of the internal DSPs status resulted in an approx. memory leak of 180kbytes every 24 hours.<br>
+
After reset of an A/B system, B devices not connected would generate a system fault message in the A Controller (should only report to B). <br>
  
−
=== Fault List and Attached Device List not Being Synchronized (MTN-973) ===
+
=== White Noise on Devices Running EXI-Firmware ===
−
After reset of an A/B system, B devices not connected would generate a system fault message in the A Controller. (Should only report to B.) <br>
+
The internal audio driver could enter a faulty state, resulting in noise from audio sources. The white noise could occur when the device was sourcing audio to "Live Speech" or "Program" for all devices running EXI-Firmware.
−
When the B device finally connected the fault status was not removed from A, but the attached device list was correct.<br>
 
  
−
=== White Noise on Devices (MTN-1001) ===
+
=== ENAx Line Monitoring Reports Wrong Fault State in Complex Speaker Line Configurations ===
−
The internal audio driver could entered a faulty state resulting in noise from audio sources. The white noise could occur when the device was sourcing audio to "Live Speech" or "Program". The following devices could potentially have the issue : Secondary System Controller, ENA2200, ENA2400, ECPIR-3P, ECPIR-P, EAPIR-8, EAPFX-1, EAPFX-6, EAPII-1, EAPII-6, TA-10, TKIE-2, TKIS-2. <br>
+
Due to tolerances of the line monitoring, sometimes the wrong fault state has been reported. Now state "Open" and "Shorted" are both reported as "Line fault".<br>
  
−
=== Line Monitoring Reports Wrong Fault State in Some Cases (MTN-966) ===
+
=== Access Panel Fault LED Stops Indicating Local Faults if Local ESC1 is Down ===
−
Due to tolerances of the line monitoring sometimes the wrong fault state was reported. <br>
+
Exigo Panels configured with fault-LED for indication of local fault does not show local fault if the ESC1 is down. <br>
  
−
=== Fault LED Stops Indicating Local Faults if Local PSC is Down (MTN-1026) ===
+
=== Audio Activity stops After Release Delay Timeout ===
−
Exigo Panels configured with fault-LED for indication of local fault does not show local fault if the PSC is down. <br>
+
Exigo Calls using the release delay feature would terminate if the call was re-started within the release delay timeout period.  
  
−
=== Alarm stops After Release Delay Timeout ===
+
=== CRM-V Access Panel, LED behavior ===
−
Exigo Calls using the release delay feature would terminate if the call was re-started within the release delay timeout period. <br>
+
* The activity range configuration for the Zone selection action was not working on the CRM-V station.
 +
* Microphone LED blinking when connected and with no faults in the system. <br>
  
−
=== Panel Lock Up During Software Upgrade ===
+
===ENAx Remains in Suspended Monitoring if ESC1 Reboots During Suspension===
−
There has been observation of panels not rebooting correctly after software upgrade. A manual power reset had to be preformed to start the panel correctly.
+
If monitoring was suspended on an ENAx and the controller rebooted, the monitoring would not be reactivated. <br>
  
−
=== CRM-V Issues with LED behaviour ===
+
=== ECPIR Access Panel, Activity LED Behaviour ===
−
The activity range configuration for the Zone selection action was not working on the CRM-V station.<br>
 
−
Microphone LED blinking when connected and with no faults in the system . <br>
 
−
 
 
−
===ENA Still in Suspended Monitoring after ESC(s) Reboot===
 
−
If monitoring is suspended on an ENA and the controller reboots, the monitoring will not be reactivated. <br>
 
−
 
 
−
=== Activity LED Issues ===
 
 
*Configuring and activating several call setup DAK keys with partly overlapping zones could indicate queued state on wrong DAK key.<br>
 
*Configuring and activating several call setup DAK keys with partly overlapping zones could indicate queued state on wrong DAK key.<br>
−
*Using call escalation, with the option:"always include" enabled, resulted in disabling the green LED indicating Live Speech when the call was escalated.<br>
+
*Using call escalation, with the option "always include" enabled, resulted in disabling the green LED indicating Live Speech when the call was escalated.<br>
 
*Microphone Test: Call LED was lit when toggled off during playback.
 
*Microphone Test: Call LED was lit when toggled off during playback.
  
−
=== Click Noise Heard when Canceling Live Speech with PTT ===
+
=== Tick Tone Test in Zone not Working for TKIS Kits and IP Speakers ===
−
When releasing the ptt button on EMMAR-1H, the noise from the mechanical button could be heard on the PA system . <br>
+
The tick tone test was not supported for TKIS kits and IP speakers. <br>
  
−
=== Tick Tone Test in Zone not Working for TKIS Kits ===
+
=== ENAx, Drift in Audio Between A and B System ===
−
The tick tone test was not supported for the IP speakers. <br>
 
−
 
 
−
=== Drift in Audio Between A and B System ===
 
 
The audio from A and B amplifiers could drift, if a call was active for a long time, due to increasing jitter buffer variations between the amplifiers.
 
The audio from A and B amplifiers could drift, if a call was active for a long time, due to increasing jitter buffer variations between the amplifiers.
  
−
=== Live Speech with Wait for PTT - not Possible to Toggle off Before 5 Seconds Timeout ===
+
=== Live Speech with Wait for PTT - Not Possible to Toggle off Before 5 Second Timeout ===
−
When starting a Live Speech with the option "wait for ptt" enabled, without pressing the ptt-button, the waiting live speech could not be canceled before a 5 seconds timeout. <br>
+
When starting a Live Speech with the option "Wait for PTT" enabled, without pressing the PTT-button, the waiting live speech could not be canceled before a 5 second timeout. <br>
  
 
== Known Issues ==
 
== Known Issues ==
−
(Numbers in brackets are used for internal references).
+
(AL-numbers in brackets are used for internal references).
−
===INCA CRM-V Panels===
+
=== CRM-V Access Panels ===
−
The INCA-CRM-V panel is based on a different hardware and software than the other Exigo devices. <br>
+
The CRM Access Panel is based on a different hardware and software than the other Exigo devices. <br>
 
Hence the functionality is limited compared to the native Exigo ECPIR panels.<br>
 
Hence the functionality is limited compared to the native Exigo ECPIR panels.<br>
−
'''Unsupported Features on the CRM-V panel'''
+
'''Exigo Features Not Supported on the CRM-V Access Panel:'''
−
*Call Escalation function. (AL-2354)
+
* Call Escalation function.  
−
*Panel lamp test. (AL-2352)
+
* Panel lamp test.  
−
*Zone select option "Deselect Zone(s) after activity". (AL-2025)
+
* Zone select option "Deselect Zone(s) after activity".  
−
'''Issues with CRM LEDs Activity Indications'''
+
'''Deviant LED Bahaviour''' '''for the CRM-V Access Panel:'''
−
*When triggering local mute control from a DAK on CRM-V, the green LED blinks. Should be steady. (AL-2353)
+
* When triggering local mute control from a DAK on CRM-V, the green LED blinks. Should be steady.  
−
*Recall record green LEDs active when mic test is performed. (AL-2351)
+
* Recall record green LEDs active when mic test is performed.  
−
*If mic test is stopped by timeout, green LED never goes off (this also goes for recall record LEDs). (AL-2351)
+
* If microphone test is stopped by timeout, green LED never goes off (this also goes for recall record LEDs).  
−
*Red LED never active when performing mic test. (AL-2351)
+
* Red LED never active when performing mic test.  
−
*DAK key with "Alarm stop with no zones", green led lit when alarm is active but DAK not possible to use for stopping the alarm. (AL-2349)
+
* DAK key with "Alarm stop with no zones", green led lit when alarm is active but DAK not possible to use for stopping the alarm.  
−
*Zone select DAK keys can trigger activity indicators green led on other DAK keys with same zone. (AL-2591,AL-2590)
+
* Zone select DAK keys can trigger activity indicators green led on other DAK keys with same zone.  
−
*DAKs with message/program/live speech/alarm programmed with zones only triggers green LED when activated. (AL-2266)
+
* DAKs with message/program/live speech/alarm programmed with zones only triggers green LED when activated.  
−
*Zone selection to all zones on DAK. No LED activity when audio activity in only some zones. (AL-2266)
+
* Zone selection to all zones on DAK. No LED activity when audio activity in only some zones.  
−
*Led for live speech lit when recall control active (and vica versa). (AL-2265)
+
* LED for live speech lit when recall control active (and vice versa).  
−
'''Workaround:'''Avoid use of CRM-V panels for functionality that is not supported.
+
'''Workaround:''' Avoid use of CRM-V panels for functionality that is not supported.
  
−
=== Issues Related to Calls with Option "Wait For PTT" ===
+
=== System Configuration (Commissioning) ===
−
'''Description:''' Call option "Release delay" does not work in combination with call option "wait for ptt". (AL-2610)<br>
+
Adding a new non-existing panel to the system will only report "missing device" in the ESC1 A. <br>
−
'''Workaround:''' Avoid using this configuration.<br>
 
−
<br>
 
−
'''Description:''' "Live Speech" from DAK w/"wait for PTT" and Timeout, starts timer from when DAK is pressed, not when PTT is pressed. (AL-2197) <br>
 
−
'''Workaround:''' Add additional 5 second Live Speech timeout when using this configuration. (Wait for PTT timeout is 5 sec.)
 
−
 
 
−
=== System Configuration Issues and Workaround ===
 
−
'''Description:''' Adding a new non-existing panel to the system will only report "missing device" in the ESC A. (AL-2585) <br>
 
 
(After first time registration of panel the "missing device" reports will always be displayed in both A and B controller.) <br>
 
(After first time registration of panel the "missing device" reports will always be displayed in both A and B controller.) <br>
−
'''Workaround:''' On commissioning, ensure that the panel has been registered once.<br>
+
'''Workaround:''' On commissioning, ensure that the panel has been registered.<br>
−
<br>
 
−
'''Description:''' Newly configured ENA does not receive audio. (AL-2345)<br>
 
−
'''Workaround:''' On commissioning, ensure that ENA is rebooted after first time configuration. <br>
 
 
<br>
 
<br>
−
'''Description:''' CO activity inherits idle state of COs after performing GET of database. (AL-2315)<br>
+
Newly added ENAx does not receive audio. <br>
−
'''Workaround:''' On commissioning, verify correct "idle state" after EMT get operations. (?).<br>
+
'''Workaround:''' On commissioning, ensure that ENAx is rebooted after first time configuration. <br>
 
<br>
 
<br>
−
'''Description:''' System Status DAK indicators - Incorrect status after reconfiguration from system status from A to status status from B (AL-2207)<br>
+
System Status DAK indicators - Incorrect status after reconfiguration from ''system status from A'' to ''system status from B'' <br>
−
'''Workaround:''' If changing the configuration of origin A/B system from where "System Status DAK LED" should be showing, reboot the panel involve to assure changes to take effect. <br>
+
'''Workaround:''' If changing the configuration of original A/B system from where "System Status DAK LED" should be showing, reboot the panel involved to assure changes take effect. <br>
 
<br>
 
<br>
−
'''Description:''' Device IP settings in WEB lost after upgrading from 4.1 to 4.2. Device stil has the same static IP address. (AL-1668)<br>
+
Device IP settings in WEB lost after upgrading from EXI-Firmware version 4.1 to 4.2. Device still has the same static IP address. <br>
−
'''Workaround:''' Exigo mode ind device WEB has to be manually selected when going from 4.1 to 4.2.<br>
+
'''Workaround:''' Exigo mode in device WEB has to be manually selected when going from 4.1 to 4.2.<br>
 
<br>
 
<br>
−
'''Description:''' ECPIR-3P A1 behaves as registered after removed from system for up to 5 minutes, (AL-2177)<br>
+
ECPIR-3P behaves as registered, after being removed from system, for up to 5 minutes, <br>
 
'''Workaround:''' Unplug the panel or wait for 5 minutes.<br>
 
'''Workaround:''' Unplug the panel or wait for 5 minutes.<br>
 
<br>
 
<br>
−
'''Description:''' ESC Call list gui - program 1 shows as "95001" in call list if name is to long. (AL-2531)<br>
+
ESC1 Call list: Long program names will not be displayed correctly <br>
−
'''Workaround:''' Use shorter program names.<br>
+
'''Workaround:''' Limit program names to 10 standard characters<br>
 
<br>
 
<br>
−
'''Description:''' EMT - SNMP Community string allows space characters. (AL-2550)<br>
+
EMT - SNMP Community string allows space character but SNMP does not support space. <br>
−
'''Workaround:''' Avoid using space in the community string.<br>
+
'''Workaround:''' Avoid using space in the community string.<br><br>
−
<br>
+
It is not possible to remove the options "Overwrite Destination" or "Timeout" from an already configured Call Escalation DAK without rebooting. <br>
−
'''Description:'''Removing option "Overwrite Destination" or "timeout" from an already configured Call Escalation DAK does not take effect. (AL-2209,AL-2458) <br>
+
'''Workaround:''' Panel must be rebooted after updated configuration sent from EMT.
−
'''Workaround:''' Panel must be rebooted after updated configuration sent from EMT.<br>
+
 
−
<br>
+
Call option "Release delay" does not work in combination with call option "Wait for PTT". <br>
−
'''Description:'''Some of the functionality that's available on Call Escalation is not supported on the activity that can be escalated (AL-2221)<br>
+
'''Workaround:''' Avoid using this combination.
−
'''Workaround:''' Assure matching parameter use for Escalation function and calls to be escalated.<br>
 
  
−
=== Call Escalation ===
+
"Live Speech" from DAK with "Wait for PTT" and "Timeout", starts timer from when DAK is pressed, not when PTT is pressed. <br>
−
'''Description:''' In some situations the activity LEDs will not be correct when Call Escalation is activated and panel used for Live Speech with PTT or ReCall.(AL-2596,2285,2283)
+
'''Workaround:''' Add additional 5 second Live Speech timeout when using this configuration (Wait for PTT timeout is 5 sec).
  
 
===Line Monitoring ===
 
===Line Monitoring ===
−
'''Description:''' During continuous LET monitoring and GA at high volume sometimes LET fail is reported. (AL-2153)<br>
+
During continuous LET monitoring and GA at high volume, LETs sometimes fail. <br>
−
'''Workaround:''' Always have suspend monitoring enabled.<br>
+
'''Workaround:''' Always have "Suspend Monitoring" enabled.<br>
  
−
=== Audio Codec Filter Implementation (MTN-990) ===
+
[[Category:Release notes]]
−
'''Description:''' The internal codec filter system has some issues, the result is that part of equalizer not working correctly.
 

Latest revision as of 08:00, 10 May 2022

Exigo 1.2.3.14

Release: Official, available on request
Date: 2017-5-16
Software Collection File: EXIGO-1.2.3.14.zip

Software Included in the EXIGO-1.2.3.14.zip file

For upgrade procedures see PDF document included in each product folder inside the EXIGO-1.2.3.14.zip file; except VS-DEVICE-MIB, as this may vary between monitoring tools.

Product Version Description
EXI-Firmware 4.2.3.14 Firmware for the following devices: ESC1(Secondary System Controller), ENA2200, ENA2400, ECPIR-3P, ECPIR-P, EAPIR-8, EAPFX-1, EAPFX-6, EAPII-1, EAPII-6, TKIS-2, TKIE-2
AlphaSys Firmware 12.2.3.13 Firmware for the ESC1 (Primary System Controller/AMC-IP board)
Exigo Management Tools 1.2.3.7 Configuration tool, installed on a Windows PC
INCA Firmware 2.20.3.6 Special Exigo software for the CRM-V based panel
VS-DEVICE-MIB 201610190000Z SNMP MIB for Exigo EXI-Devices, for upload in 3rd-party SNMP based monitoring tools


Improvements

Support for new amplifier (ENA2x00) hardware, where Line input and Mic input have switched position.

Known Issues

CRM-V Access Panels

The CRM Access Panel is based on a different hardware and software than the other Exigo devices.
Hence the functionality is limited compared to the native Exigo ECPIR panels.

Exigo Features Not Supported on the CRM-V Access Panel:

  • Call Escalation function.
  • Panel lamp test.
  • Zone select option "Deselect Zone(s) after activity".

Deviant LED Behavior for the CRM-V Access Panel:

  • When triggering local mute control from a DAK on CRM-V, the green LED blinks. Should be steady.
  • Recall record green LEDs active when mic test is performed.
  • If microphone test is stopped by timeout, green LED never goes off (this also goes for recall record LEDs).
  • Red LED never active when performing mic test.
  • DAK key with "Alarm stop with no zones", green led lit when alarm is active but DAK not possible to use for stopping the alarm.
  • Zone select DAK keys can trigger activity indicators green led on other DAK keys with same zone.
  • DAKs with message/program/live speech/alarm programmed with zones only triggers green LED when activated.
  • Zone selection to all zones on DAK. No LED activity when audio activity in only some zones.
  • LED for live speech lit when recall control active (and vice versa).

Workaround: Avoid use of CRM-V panels for functionality that is not supported.

System Configuration (Commissioning)

Adding a new non-existing panel to the system will only report "missing device" in the ESC1 A. (After first time registration of panel the "missing device" reports will always be displayed in both A and B controller.)
Workaround: On commissioning, ensure that the panel has been registered.

Newly added ENAx does not receive audio.
Workaround: On commissioning, ensure that ENAx is rebooted after first time configuration.

System Status DAK indicators - Incorrect status after reconfiguration from system status from A to system status from B
Workaround: If changing the configuration of original A/B system from where "System Status DAK LED" should be showing, reboot the panel involved to assure changes take effect.

Device IP settings in WEB lost after upgrading from EXI-Firmware version 4.1 to 4.2. Device still has the same static IP address.
Workaround: Exigo mode in device WEB has to be manually selected when going from 4.1 to 4.2.

ECPIR-3P behaves as registered, after being removed from system, for up to 5 minutes
Workaround: Unplug the panel or wait for 5 minutes.

ESC1 Call list: Long program names will not be displayed correctly
Workaround: Limit program names to 10 standard characters.

EMT - SNMP Community string allows space character but SNMP does not support space.
Workaround: Avoid using space in the community string.

It is not possible to remove the options "Overwrite Destination" or "Timeout" from an already configured Call Escalation DAK without rebooting.
Workaround: Panel must be rebooted after updated configuration sent from EMT.

Call option "Release delay" does not work in combination with call option "Wait for PTT".
Workaround: Avoid using this combination.

"Live Speech" from DAK with "Wait for PTT" and "Timeout", starts timer from when DAK is pressed, not when PTT is pressed.
Workaround: Add additional 5 second Live Speech timeout when using this configuration (Wait for PTT timeout is 5 sec).

Line Monitoring

During continuous LET monitoring and GA at high volume, LETs sometimes fail.
Workaround: Always have "Suspend Monitoring" enabled.

Exigo 1.2.3.13

Release: Official, available on request
Date: 2016-12-19
Software Collection File: EXIGO-1.2.3.13.zip

Software Included in the EXIGO-1.2.3.13.zip file

For upgrade procedures see PDF document included in each product folder inside the EXIGO-1.2.3.13.zip file; except VS-DEVICE-MIB, as this may vary between monitoring tools.

Product Version Description
EXI-Firmware 4.2.3.13 Firmware for the following devices: ESC1(Secondary System Controller), ENA2200, ENA2400, ECPIR-3P, ECPIR-P, EAPIR-8, EAPFX-1, EAPFX-6, EAPII-1, EAPII-6, TKIS-2
AlphaSys Firmware 12.2.3.13 Firmware for the ESC1 (Primary System Controller/AMC-IP board)
Exigo Management Tools 1.2.3.7 Configuration tool, installed on a Windows PC
INCA Firmware 2.20.3.6 Special Exigo software for the CRM-V based panel
VS-DEVICE-MIB 201610190000Z SNMP MIB for Exigo EXI-Devices, for upload in 3rd-party SNMP based monitoring tools



Corrections

Flowire, RSTP Setup

Network storm could be generated and destabilize the system during a combination of high system traffic and connection instability on the primary Flowire link to an Access Panel.

Database on ENA Sometimes Lost when Device is Rebooted During High Traffic

Buffered configuration data was not written to configuration file if the device rebooted during high traffic situations.

ESC1 Long Term Stability

Reboot of ESC1 has been observed after 3+ months of continuously monitoring the internal DSPs status.

ESC1 Fault List and Attached Device List Not Being Synchronized

After reset of an A/B system, B devices not connected would generate a system fault message in the A Controller (should only report to B).

White Noise on Devices Running EXI-Firmware

The internal audio driver could enter a faulty state, resulting in noise from audio sources. The white noise could occur when the device was sourcing audio to "Live Speech" or "Program" for all devices running EXI-Firmware.

ENAx Line Monitoring Reports Wrong Fault State in Complex Speaker Line Configurations

Due to tolerances of the line monitoring, sometimes the wrong fault state has been reported. Now state "Open" and "Shorted" are both reported as "Line fault".

Access Panel Fault LED Stops Indicating Local Faults if Local ESC1 is Down

Exigo Panels configured with fault-LED for indication of local fault does not show local fault if the ESC1 is down.

Audio Activity stops After Release Delay Timeout

Exigo Calls using the release delay feature would terminate if the call was re-started within the release delay timeout period.

CRM-V Access Panel, LED behavior

  • The activity range configuration for the Zone selection action was not working on the CRM-V station.
  • Microphone LED blinking when connected and with no faults in the system.

ENAx Remains in Suspended Monitoring if ESC1 Reboots During Suspension

If monitoring was suspended on an ENAx and the controller rebooted, the monitoring would not be reactivated.

ECPIR Access Panel, Activity LED Behaviour

  • Configuring and activating several call setup DAK keys with partly overlapping zones could indicate queued state on wrong DAK key.
  • Using call escalation, with the option "always include" enabled, resulted in disabling the green LED indicating Live Speech when the call was escalated.
  • Microphone Test: Call LED was lit when toggled off during playback.

Tick Tone Test in Zone not Working for TKIS Kits and IP Speakers

The tick tone test was not supported for TKIS kits and IP speakers.

ENAx, Drift in Audio Between A and B System

The audio from A and B amplifiers could drift, if a call was active for a long time, due to increasing jitter buffer variations between the amplifiers.

Live Speech with Wait for PTT - Not Possible to Toggle off Before 5 Second Timeout

When starting a Live Speech with the option "Wait for PTT" enabled, without pressing the PTT-button, the waiting live speech could not be canceled before a 5 second timeout.

Known Issues

(AL-numbers in brackets are used for internal references).

CRM-V Access Panels

The CRM Access Panel is based on a different hardware and software than the other Exigo devices.
Hence the functionality is limited compared to the native Exigo ECPIR panels.
Exigo Features Not Supported on the CRM-V Access Panel:

  • Call Escalation function.
  • Panel lamp test.
  • Zone select option "Deselect Zone(s) after activity".

Deviant LED Bahaviour for the CRM-V Access Panel:

  • When triggering local mute control from a DAK on CRM-V, the green LED blinks. Should be steady.
  • Recall record green LEDs active when mic test is performed.
  • If microphone test is stopped by timeout, green LED never goes off (this also goes for recall record LEDs).
  • Red LED never active when performing mic test.
  • DAK key with "Alarm stop with no zones", green led lit when alarm is active but DAK not possible to use for stopping the alarm.
  • Zone select DAK keys can trigger activity indicators green led on other DAK keys with same zone.
  • DAKs with message/program/live speech/alarm programmed with zones only triggers green LED when activated.
  • Zone selection to all zones on DAK. No LED activity when audio activity in only some zones.
  • LED for live speech lit when recall control active (and vice versa).

Workaround: Avoid use of CRM-V panels for functionality that is not supported.

System Configuration (Commissioning)

Adding a new non-existing panel to the system will only report "missing device" in the ESC1 A.
(After first time registration of panel the "missing device" reports will always be displayed in both A and B controller.)
Workaround: On commissioning, ensure that the panel has been registered.

Newly added ENAx does not receive audio.
Workaround: On commissioning, ensure that ENAx is rebooted after first time configuration.

System Status DAK indicators - Incorrect status after reconfiguration from system status from A to system status from B
Workaround: If changing the configuration of original A/B system from where "System Status DAK LED" should be showing, reboot the panel involved to assure changes take effect.

Device IP settings in WEB lost after upgrading from EXI-Firmware version 4.1 to 4.2. Device still has the same static IP address.
Workaround: Exigo mode in device WEB has to be manually selected when going from 4.1 to 4.2.

ECPIR-3P behaves as registered, after being removed from system, for up to 5 minutes,
Workaround: Unplug the panel or wait for 5 minutes.

ESC1 Call list: Long program names will not be displayed correctly
Workaround: Limit program names to 10 standard characters

EMT - SNMP Community string allows space character but SNMP does not support space.
Workaround: Avoid using space in the community string.

It is not possible to remove the options "Overwrite Destination" or "Timeout" from an already configured Call Escalation DAK without rebooting.
Workaround: Panel must be rebooted after updated configuration sent from EMT.

Call option "Release delay" does not work in combination with call option "Wait for PTT".
Workaround: Avoid using this combination.

"Live Speech" from DAK with "Wait for PTT" and "Timeout", starts timer from when DAK is pressed, not when PTT is pressed.
Workaround: Add additional 5 second Live Speech timeout when using this configuration (Wait for PTT timeout is 5 sec).

Line Monitoring

During continuous LET monitoring and GA at high volume, LETs sometimes fail.
Workaround: Always have "Suspend Monitoring" enabled.

Retrieved from "https://exigo.zenitel.com/w/index.php?title=Release_Note_Exigo_1.2&oldid=17778"