Release Note Exigo 1.3
Contents
- 1 Exigo 1.3.2.10
- 1.1 Software included in EXIGO-1.2.3.13.zip
- 1.2 New features
- 1.3 New Functionality
- 1.3.1 Turbine Extended kit support (AL-83)
- 1.3.2 Flowire Monitoring (AL-1306)
- 1.3.3 Auto mute function (AL-1372, AL-1823)
- 1.3.4 Multiple escalation functions for each function added (AL-1960)
- 1.3.5 Adjustable timeout for Recall, Record (AL-1064)
- 1.3.6 Remote activation of microphones (AL-2734)
- 1.3.7 ENA Line monitoring: Optional detailed reporting (AL-2592)
- 1.3.8 ENA Line monitoring: Suspend monitoring during alarms (AL-1388)
- 1.4 System configuration
- 1.4.1 EMT: Remote device configuration (AL-1761)
- 1.4.2 EMT: Selectable “missing device” reporting (AL-326, AL-1251)
- 1.4.3 EMT Wizard: Advanced settings pane (AL-773, AL-1767)
- 1.4.4 EMT: Option to add multiple devices (AL-2003)
- 1.4.5 EMT: Possible to drop new devices in the entire system pane (AL-1968)
- 1.4.6 EMT: Drag and drop multiple devices to zones (AL-1903)
- 1.4.7 EMT: Backup of database (AL-2504, AL-229)
Exigo 1.3.2.10
Release status: Limited Availability, available on request. Release date: 28.04.2017 Software collection file: EXIGO-1.3.2.10.zip
Software included in EXIGO-1.2.3.13.zip
For upgrade procedures, see PDF document included in each product folder inside the EXIGO-1.3.2.10.zip file; except VS-DEVICE-MIB, as this may vary between monitoring tools.
Product | Version | Product description |
EXI-Firmware | 4.3.2.10 | 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.3.2.9 | Firmware for the ESC1 (Primary System Controller/AMC-IP board) |
Exigo Management Tools | 1.3.2.9001 | Configuration tool, installed on a Windows PC |
INCA Firmware | 2.20.3.8 | 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 |
New features
Backup Amplifier (AL-100)
- One amplifier can be configured as a replacement for up to 6 other amplifiers.
- The “replacement candidates” can be prioritized from 1 to 6, where 1 is highest priority; so if more than one replacement candidate is lost, the one with the highest priority will be replaced.
- For details, see our wiki article
Alphacom and SIP integration (AL-38)
- Exigo supports full Alphacom integration and integration with other SIP trunks.
- Alphacom/SIP Integration is supporting single and AB systems
- An Exigo system can be integrated with multiple Alphacom/SIP systems.
- Alphacom/SIP connection link can be monitored by Exigo
- Alphacom/SIP stations can start and control any pre-configured audio activity in Exigo
- Exigo can send audio to Alphacom stations or groups
- Exigo can send audio via the SIP trunk to SIP stations
- Outgoing calls will have a priority translation from Exigo to standard SIP priorities.
- Control outputs can be triggered by incoming calls from the Alphacom/SIP system.
- For details about Alphacom integration, see our wiki article.
- For details about the SIP integration, see our wiki article.
IP speaker support (AL-52, AL-53)
- Exigo supports 200 IP speakers
- IP speakers are now a separate device in EMT
New Functionality
Turbine Extended kit support (AL-83)
- The Turbine Extended kit (TKIE-1/2) is now fully supported and can be configured in EMT.
Flowire Monitoring (AL-1306)
- For details, see our wiki article.
Auto mute function (AL-1372, AL-1823)
IP speakers and all other audio channels can be configured to be digitally muted based on activity in the system
Multiple escalation functions for each function added (AL-1960)
Adjustable timeout for Recall, Record (AL-1064)
Remote activation of microphones (AL-2734)
ENA Line monitoring: Optional detailed reporting (AL-2592)
By default, the system reports both “Open” and “Shorted” as “Line Fault”. It is now possible to choose detailed reporting for “Open” and “Shorted”.
ENA Line monitoring: Suspend monitoring during alarms (AL-1388)
Amplifiers with high load can generate false load faults during GA. Suspend monitoring will pause monitoring during the alarm to prevent such faults.
System configuration
EMT: Remote device configuration (AL-1761)
Remote device configuration is implemented in EMT under Operation panel. This allows configuration of basic device settings such as IP settings and directory number from EMT.
EMT: Selectable “missing device” reporting (AL-326, AL-1251)
Devices can now be configured to be reported as missing in either A, B or both controllers.
EMT Wizard: Advanced settings pane (AL-773, AL-1767)
In the EMT Wizard, the user can now configure global settings in an advanced settings pane. Including:
- Monitoring of ETH1 or ETH2 on/off for all rack devices and access panels
- AC monitoring on/off for all rack devices
- DC monitoring on/off for all rack devices
- "Enable SSH" flag is moved from the Default Configuration page to the Firewall Setting group in the Advanced Settings
- The Firewall Settings group also have an option to enable the SNMP port
EMT: Option to add multiple devices (AL-2003)
It is possible to add multiple devices to a database with only one drag&drop operation. When selecting a device in the Components pane, there is an option to select how many devices will be added.
If the database is an AB system, and paired devices are selected, then the Add Multiple devices option will add the selected number of pairs to the database.
EMT: Possible to drop new devices in the entire system pane (AL-1968)
EMT: Drag and drop multiple devices to zones (AL-1903)
It is now possible to drag and drop multiple devices to a zone. Use Shift and/or Ctrl keys to select multiple devices before dragging the selected devices to a zone.
=== EMT: Allow installation of two EMT versions (AL-2502) It is now possible to have one EMT version 1.2, and one version 1.3, installed simultaneously.
EMT: Backup of database (AL-2504, AL-229)
When opening a project, EMT will check what EMT version the project was created with, and if different from the current version, a backup file (.zip) will be created.
The backup file will be named <ProjectName>_<CreatedInVersion>.zip. The backup file will be saved in a \backup directory inside the project directory.
The creation of the backup file goes silently without notification to the user, unless the backup file of some reason cannot be created.
It is also possible to create a backup file manually.