VIPEDIA-12 V4.2.0.8L Package A RNote 2023-03-09

Application Solutions (Safety and Security) Ltd
Unit 17 Cliffe Industrial Estate

East Sussex
BN8 6JL - UK
Tel: +44 (0) 1273 405411
Fax: +44 (0) 1273 405415
www.asl-control.co.uk
SOFTWARE RELEASE NOTE

Software title: VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount
Controllers/VIPA Devices/Tools
Version: V4.2.0.8L – Package A
Date released: 9th March 2023
Purpose of release: To release bug fixes and improvement updates.
Please refer to Sections “2 New Features” (page 13), “3 Changes and
Improvements” (page 48) and “4 Bug Fixes” (page 79).
Release type: General release for systems that require V4.2 features and bug fixes.
This software does not require any additional concession forms to be raised
before use in an end user application.
However, distribution to customers is subject to approval by Project Manager
and Technical Director.
Due regard should be taken of the information of the release information
contained in the Release Note.
Notes 1) MPS-A refers to microphone main board with old processor (MAC address
C0:BA:E6:00:xx:yy).
MPS-B refers to microphone main board with new processor (MAC
address C0:BA:E6:04:xx:yy).
MPS refers to both.
2) VIPEDIA-12/Vipedia and V2000 are used as standard.
Unless required, no specific references to INTEGRA.
3) Network Card Manager V1.2.0.8P (or later) should be used to update
Network Cards.
4) Update Manager V1.4.0.9P (or later) is required to load the signed version
of the Vipedia and V2000 firmware/software (filename of main codes is
now “Sxxxx” rather than “Fxxxx”, where “S” means “signed code”. For
example: “S0641_12_HCP_V4.2.0.0P” instead of
“F0641_12_HCP_V4.2.0.0P”). Can be used to load previous releases.
5) V2000/INTEGRA 110V mains supply requires PSU V7.30.0.0P and Frame
Controller V4.2.0.7L (or newer).
6) Secure Bootloader for VIPEDIA-12 and V2000:
Secure Bootloader (V5.0.0 or later) is required for VIPEDIA-12/V2000
V5.0 (or later) or VIPEDIA-12/V2000 that may be updated to V5.0.
Secure Bootloader is fully compatible with all current latest LTS
releases for 2.1, 3.3 as well as 4.2 and future releases.
Units with Secure Bootloader only execute Signed versions of the
application (filenames starting with “S” rather than “F”).
VIPEDIA-12_V4.2.0.8L_Package_A_RNote.docx (09/03/2023) Page 1 of 113

Company Confidential
VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount Controllers/VIPA Devices/Tools V4.2.0.8L – Package A
1 Software Release Package
1.1 Software Version
1.1.1 VIPEDIA-12/INTEGRA Router

Components Version New
Router Host CP [1] V4.2.0.8L Yes [A]
UIP [19] V2.1.0027 No
DSP [17] V5.0.2.4P [11] Yes [A]
V1.4.1 (plain text) No
Host Bootloader [19] V4.0.0P (plain text) [20] Yes [A]
V5.0.0P (secure) [21] Yes [A]
V4.0.0.0P (plain text) [33] Yes [A]
Vipedia Host Bootloader Updater
V5.0.0.0P (secure) [34] Yes [A]
FPGA V0x16 No
CPLD [19] V0x0B No
Network Card [31] NET-VIPA V4.2.0.82P Yes [A]
Bundle_05 [27] [28] [29]:
• U-Boot: V3.0.0.1
• U-Boot-Env: V3.0.0.0
Image (Issue 2 only) [19] No
• Kernel: V3.0.0.3P
• RootFs: V3.0.0.3P
• EtcFs: V3.0.0.3P
TTS-D-NET-VIPA [23] V4.2.0.81P No
Dante USR Image V0.0.0.1 No
Dante Brooklyn II [26] V4.1.1.4 No
1.1.2 V2000/INTEGRA Amplifier Mainframe

Frame Controller [1] V4.2.0.7L Yes [A]
V2.0.0 (plain text) No
Frame Bootloader [19] V4.0.0P (plain text) [20] Yes [A]
V5.0.0P (secure) [21] Yes [A]
V4.0.0.0P (plain text) [33] Yes [A]
Frame Bootloader Updater
V5.0.0.0P (secure) [34] Yes [A]
Amplifier Frame 24 V (up to issue 4) V2.22.1.1P No
24 V (issue 5.0 to 5.4) V5.23.1.1P [3] No
V7.30.0.0P-24V; see [32]
24 V (issue 5.0 or later) [2] Yes [A]
PSU [19] [4] [6] [7] [8]
V7.30.0.0P-48V; see [32]
48 V [2] [4] [5] [6] [7] [8] [9] Yes [A]
Does not support 110 V
DSP [10] V5.2.0.5P [12] [13] Yes [A]
LSZDC Interface
LSZDC Bootloader [10] V5.2.0.4P [12] [13] Yes [A]
Card
CPLD [19] V0x03 No

1.1.3 VIPA Devices (VIPA Server, VIPA Host, iPAM400, etc.)

V4.2.0g No
VIPA Stack
V4.2.0d (iPAM400) No
Image VIPA Host (Lanner LEC-7230M) - Vipa-host-base-image- No
SLES 11 20181203
VIPA Host (Linutop) - openSUSE 10.3 Linutop-base-image-20101206 No
iPAM400 - openSUSE 10.3 ipam-base-image-20130625 No
Jabber RPM VIPA Host (Lanner) V1.6.0.asl-9 No
VIPA Host (Linutop) NA NA
iPAM400 NA NA
1.1.4 Microphones (MPS/EMS/VRMS4/SAP03/SAP04/ATEX) and Wall-Mount Controllers (WMC01)

English (GB)
Portuguese (PT)
Spanish (ES)
Turkish (TR)
V4.3.0.6L
App Czech (CZ) Yes [A]
Main Board Slovak (SK)
(MPS-A) [24] French (FR)
Swedish (SE)
Danish (DK) Not available
V1.1.4 No
Boot [19]
V1.1.0.5P [22] No
English (GB)
Portuguese (PT)
Spanish (ES)
Turkish (TR)
App Czech (CZ) V4.3.0.6L Yes [A]
Main Board Slovak (SK)
(MPS-B) [24] French (FR)
Swedish (SE)
Danish (DK)
V1.0.0.0P No
Boot [19]
V1.0.1.0P [35] Yes [A]
V1.2.2
Navigation Board (MPS/EMS/WMC only) [14] [19] No
V3.1.0.0 [22]
V2.2.1999 (up to MPS20 only)
Button Board [19] No
V2.3.0002 (up to MPS100)
1.1.5 NETWORK-SWITCH-LP01
Network Switch Firmware V1.0.2.S0 No

1.1.6 Tools
PAVA System Configuration Tool (PAVA SCT) V4.2.0.6P No
Firmware Transfer Tool (FTT) V4.2.0.6P No
Router Dynamic Configuration Tool (RDT) [15] [25] V4.2.0.6P No
Audio Settings Manager [16] V4.2.0.6P No
Vipedia Finder NA NA
Vipedia Bootloader (Firmware updater) [1] V1.1.1 No
Amplifier Dynamic Configuration Tool (ADT) [18] [25] V4.2.0.6P No
VIPA Config Tool V4.2.0.0087 No
Event Viewer V3.1.0.6P No
MPS-A MB Ethernet Bootloader (Firmware Updater) V2.0.3 (requires cygwin1.dll) No
Boot V1.1.0002 No
MPS-A MB USB Bootloader (Firmware Updater)
Driver V1.3.7611 No
MPS-B MB Ethernet Firmware Updater Use FTT V3.3.2.0 (or later) -
MPS-B MB USB Firmware Updater Use drag and drop -
XML Loader (Configuration Tool) V2.1.5 No
Microphone Finder V1.1.2.7611 No
Update Manager V2.0.0.0P Yes [A]
Network Card Manager V1.2.0.12P Yes [A]
Network Card Image Manager V1.0.0.1P [30] No
Dante Controller [26] V4.2.3.1 No
1.1.7 Notes and Warnings

[1] Vipedia bootloader is used to load the Host CP and Frame Controller.
[2] Frame Controller will report the PSU version of the 48V firmware as 8.x.
Frame Controller will report the PSU version of the 24V firmware as 7.x.
[3] Should only be used with issue 5 hardware fitted with SCHOTTKY diode.
[4] Should only be used with issue 5 hardware fitted with D24 SILICON diode.
[5] Should only be used with PSUs fitted with 48V fans.
[6] DC input versions of PSU (both 24V and 48V) should have D24 removed to avoid sourcing of current into low
voltage input, otherwise D24 should always be silicon diode type.
[7] For 24V and 48V = ensure MOD C for issue 5.4 or earlier.
[8] D24 change was implemented in issue 5.5 onwards for 24V and 48V.
[9] Issue 5.6: 48V Hardware modified according to: A0623601_Iss_050_MOD_A, A0623601_Iss_050_MOD_B,
A0623601_Iss_050_MOD_C, A0623601_Iss_050_MOD_D, A0623601_Iss_050_MOD_E,
A0623601_Iss_050_MOD_F, A0623601_Iss_050_MOD_J. and A0623601_Iss_050_MOD_H.
[10] The LSZDC DSP software is available in two versions:
• Combined: includes the bootloader as before (any LSZDC BS that has combined LSDC+bootloader and
Frame that has not been updated with split LSZDC DSP/bootloader V3.2.0.0 or later)
• Application: DSP and bootloader are split (LSZDC BS 4 onwards and Frame that has been updated with split
LSZDC DSP/bootloader V3.2.0.0 or later)
• Frame V3.2.0.0 will update the LSZDC accordingly if all combined and split DSP and bootloader files are
present.
[11] Vipedia DSP V5.0: The DSP is same for V4.2 and V5.0.
[12] V2000 LSZDC V5.0:
The LSZDC DSP and Bootloader are same for V4.2 and V5.0.

[13] LSZDC:
• This version (bootloader and DSP) is compatible with flash part MT25QL128 and W25Q128JVSIM on
LSZDC hardware build standard 8 (or newer) and is back compatible with flash parts on older LSZDC
hardware.
• LSZDC hardware build standard 08 (or newer) must not be downgraded to a firmware version that does not
support flash part MT25QL128 and W25Q128JVSIM.
LSZDC firmware versions that support the above flash part at the time of this release package:
- DSP V5.0.2.5P / DSP Bootloader V5.0.2.4P
If older version is required, please contact ASL.
• V2000 Frame V4.2.0.7L (or later) and V5.0.2.5P (or later) do not allow downgrading DSP Bootloader
V5.0.2.4P.
[14] WMC01 may have Navigation Board V2.0.0 under concession T-0664-0762.
[15] The Router Dynamic Configuration Tool (RDT) is launched from the PAVA SCT. Note that the access to the RDT
is only enabled if a valid configuration is loaded into the PAVA System Configuration Tool.
[16] The Audio Settings Manager is launched from the RDT.
[17] DVA levels: refer to ASL0641-Tech-Note-DVA_Levels Technical Note for instructions if updated from earlier
versions. Note that for level adjustment DSP V3.1.0.0P is same as V2.0.0002.
[18] The Amplifier Dynamic Configuration Tool (ACT) is launched from the PAVA SCT. Note that the access to the
ACT is only enabled if a V2000 is present in the system configuration.
[19] Vipedia Host / V2000 Frame Bootloader: Programmed in manufacturing.
[20] Vipedia Host /V2000 Frame Secure Bootloader V4.0.0 (plain text):
Plain text Bootloader V4.0.0 can replace the original V1.4.1. It can be used with any pre-existing application. It is
more robust and recommended where security is not required. It allows easy recovery when the application
update fails (typically with TFTP ERROR).
See details in “3.1.8 Vipedia Host / V2000 Frame Bootloader V4.0.0/V5.0.0”.
[21] Vipedia Host /V2000 Frame Secure Bootloader V5.0.0 (secure):
Secure Bootloader V4.2 and V4.3 is now deprecated.
Secure Bootloader V5.0.0 replaces the pre-existing secure Bootloader V4.2/V4.3.
Secure Bootloader is required for VIPEDIA-12/V2000 V5.0 (or later) or VIPEDIA-12/V2000 that may be updated
to V5.0 with security enabled, and Secure Bootloader V5.0.0 is the recommended version.
Secure Bootloader is fully compatible with all current latest LTS releases for 2.1, 3.3 as well as 4.2 and future
releases.
Units with Secure Bootloader only execute Signed versions of the application (filenames starting with “S” rather
than “F”).
[22] On new units only (MAC address C0:BA:E6:00:>=50:yy and C0:BA:E6:04:xx:yy).
[23] TTS is not part of the standard product. Acapela license is required for each TTS installation.
[24] MPS-A = old processor (MAC address C0:BA:E6:00:xx:yy)
MPS-B = new processor (MAC address C0:BA:E6:04:xx:yy)
[25] Router Dynamic Configuration Tool (RDT) used to be called VIPEDIA-12 Dynamic Configuration Tool (VIPEDIA-
12 DCT)
Amplifier Dynamic Configuration Tool (ACT) used to be called V2000 Dynamic Configuration Tool (V2000 DCT)
[26] Version of Dante products for reference only.
Dante products are not included in the release package. These are available from Audinate website
(www.audinate.com). Refer to ASL for further information.
Audinate® is a registered trademark of Audinate Pty Ltd.

Dante™ is a trademark of Audinate Pty Ltd.
[27] Bundle 5 additional firmware:
• DOM: F0641_NET_DOM_V3.0.0.1_VIPA_2_17_5_29
• U16: F0641_21_U16_Rev8_UBT_V3.0.0.1_ENV_V3.0.0.0_KRN_V3.0.0.3P_EFS_V3.0.0.3P.srec
• U17: F0641_21_U17_Rev5_RFS_V3.0.0.3P.srec
[28] Bundle 5 is only required if Network Card ETH ports are used in loop configuration with RSTP enabled.
[29] Bundle 5 issues:
• Downgrade to V2.1 requires RSTP to be disabled using V3.3 or later. Otherwise, the Network Card keeps
rebooting.
• ETH3 and ETH4 in loop configuration only works if an SFP module is fitted to ETH5/6.
[30] Network Card Image Manager loads Network Card Image Bundle 5 (Network Card Issue 2 only): KERNEL
V3.0.0.3P / ROOTFS V3.0.0.3P / ETCEFS V3.0.0.3P.
Not part of standard release package. Available on request. Please contact ASL for details.

[31] Network Card MAC Address:

• Issue 1: C0:BA:E6:02:YY:XX, where YY is ≤ 05 (if YY = 05, XX is ≤ 3C)
• Issue 2: C0:BA:E6:02:YY:XX, where YY is ≥ 05 (if YY = 05, XX is ≥ 3D)
[32] PSU V7.30.0.0P-24V only required for 110 V supply.
PSU V7.30.0.0P-48V: 110 V supply not supported.
PSU V7.25.0.0P / V7.29.0.0P for 230 V supply does not require update to V7.30.0.0P.
[33] Vipedia Host / V2000 Frame Bootloader Updater V4.0.0.0P: for Bootloader V4.0.0 (plain text) installation.
Not part of the standard release package. Available on request. Please contact ASL for details.
[34] Vipedia Host / V2000 Frame Bootloader Updater V5.0.0.0P: for Bootloader V5.0.0 (secure) installation.
Not part of the standard release package. Available on request. Please contact ASL for details.
[35] MPS-B Bootloader V1.0.1.0P is required for ATEX microphones. Compatible with standard microphones.
1.2 Software Details (Filename and Checksum)
1.2.1 VIPEDIA-12/INTEGRA Router

Components Filename Checksum (MD5)
S0641_12_HCP_V4.2.0.8L_enGB.v12_cp 9ce09b6aa142ff3cff127
English
S0641_12_HCP_V4.2.0.8L_enGB.integra_cp 36f41f9fd5e
S0641_12_HCP_V4.2.0.8L_svSE.v12_cp 0b2b786bae5ef454d6f7
Host CP Swedish
S0641_12_HCP_V4.2.0.8L_svSE.integra_cp 9b4aec7e8fa2
S0641_12_HCP_V4.2.0.8L_daDK.v12_cp f06f0439b3f59380743f9
Danish
S0641_12_HCP_V4.2.0.8L_daDK.integra_cp b187d88cc24
921e6eb53f16a199c93f
UIP F0641_12_UIP_V2_1_0027.hex
ffcd59e2515a
S0641_12_DSP_V5.0.2.4P.v12_dsp 63f19bbfd8c3a9c6ac21
DSP
S0641_12_DSP_V5.0.2.4P.integra_dsp 293037d46fa2
e5ea653a85519cd57bc
HOST_Bootloader_1_4_1.srec
49832b676fa42
Router f7c1dab0f443bdb81b03
Host Bootloader F0641_HCP_Bootloader_V4.0.0P.srec
73d15f6eba4e
87724305a7a6b31a4e4
S0641_HCP_SecBootloader_V5.0.0P.srec
aa4e5ee6ec9c3
F0641_HCP_BL_Updater_V4.0.0.0P.v12_cp 41537ca93ca120dee0f
F0641_HCP_BL_Updater_V4.0.0.0P.integra_cp 1b56b422faa43
Vipedia Host
Bootloader Updater S0641_HCP_BL_SecUpdater_V5.0.0.0P.v12_cp
28456f970b20f158c6f6f
S0641_HCP_BL_SecUpdater_V5.0.0.0P.integra e165edbb4f4
_cp
652538b8cc7d55979d2
FPGA asl0641_u32_top_0x16.v12_fpga
b69f8ac381012
96ae173e2b43884733e
CPLD ASL0641_u4_top_V0x0b.jed
e69eded214d39
69cb75f500bcde12866
NET-VIPA NET-VIPA-4_2_0_82L.tar.bz2
d033bbf1b8ad9
eae27684b915ddb9f95
TTS-D-NET-VIPA TTS-D-NET-VIPA-4_2_0_81P.tar
Network 41b63b82badd1
Card Dante USR (user) 9c7e3d6c9f5d23be10ef
F0641_DNT_V0.0.0.1.dnt
Image 1517504ef708
36cf77054757150301a
Dante Brooklyn II bklyn2-4.1.1.4_fpga-4.0.2.10_vcxo-4.0.2.8.dnt
c011afcedcae1

1.2.2 V2000/INTEGRA Amplifier Mainframe

S0623_2000_HCP_V4.2.0.7L.v2k_frame 5c6cf27be9d6db9b3d
Frame Controller
S0623_2000_HCP_V4.2.0.7L.v2k_frame e33d1d71b15cb9
91db1323738bb16d6
V2000_Bootloader_V2_0_0.srec
eef1c613a626ea2
da89e60a4842ca275
Frame Bootloader F0623_HCP_Bootloader_V4.0.0P.srec
026b7aab7974ebd
beef3767ba8a08ee9b
S0623_HCP_SecBootloader_V5.0.0P.srec
22e2db0473342c
F0623_HCP_BL_Updater_V4.0.0.0P.v2k_frame 24e374aea00d156f97
V2000 Frame F0623_HCP_BL_Updater_V4.0.0.0P.integra_frame c63177f03ad90f
Bootloader S0623_HCP_BL_SecUpdater_V5.0.0.0P.v2k_frame
Updater daec358eaca0f148fce
Amplifier S0623_HCP_BL_SecUpdater_V5.0.0.0P.integra_fra 9136e10779a26
Frame me
PSU – 24 V 53e0788f78a9bbf84b
F0623_2000_PSU_V2.22.1.1P.hex
(up to issue 4) 15e5d3c4c7cc2a
PSU – 24 V
cd165f204c938d43a3
(issue 5.0 or 5.4, F0623_2000_PSU_V5.23.1.1P.hex
ceec779e2d0fa4
SCHOTTKY diode)
PSU – 24 V
(issue 5.0 or later, 6e3139bba951c49ae
F0623_2000_PSU_V7.30.0.0-24V.hex
D24 SILICON 127aae207279b74
diode)
PSU – 48 V (issue
30f82072217334ea4b
5.0 or later, D24 F0623_2000_PSU_V7.30.0.0P-48V.hex
1653b8a21644d4
SILICON diode)
S0623_V2000_DSP_V5.0.2.5P.v2k_lszdc 3bf2bddf85e8dee160
Combined
S0623_V2000_DSP_V5.0.2.5P.integra_lszdc 52419a3bd5dd9d
S0623_V2000_DSP_V5.0.2.5P.v2k_lszdc_app 7eda763fde9dcf0a68
LSZDC Application
Interface S0623_V2000_DSP_V5.0.2.5P.integra_lszdc_app c847546eb6e0e7
Card S0623_V2000_DSP_BL_V5.0.2.4P.v2k_lszdc_bl 71cff338fecc0235a0a
Bootloader
S0623_V2000_DSP_BL_V5.0.2.4P.integra_lszdc_bl b3d6fa369bd40
f733777e019252475a
CPLD ASL0623_4sU19_v0x03.jed
e03a0429ab0214
1.2.3 VIPA Devices (VIPA Server, VIPA Host, iPAM400, etc.)

74acedc8736dff5a607fd
vipa_v4_2_0g.tar.bz2
e70649042e7
VIPA Stack
c146748cefcf539f45860
vipa_v4_2_0d.tar.bz2
15275ec298f
VIPA Host (Lanner LEC-7230M) - vipa-host-master-image- 30b5aaf0f0a6a7c7fbd33
SLES 11 20181203.bin 3dfd8a56592
Image VIPA Host (Linutop) Linutop-20110412.img NA
iPAM400 iPAM-platform- 73a064511f066aa2e919
20130625_v2_14_0.img e302a85b4b4b
VIPA Host (Lanner) f81c9ea2e3b6042b9a1f6
jabberd14-1.6.0.asl-9.i386.rpm
886dddb29bd
Jabber RPM
VIPA Host (Linutop) NA NA
iPAM400 NA NA

1.2.4 Microphones (MPS/EMS/VRMS4/SAP03/SAP04/ATEX) and Wall-Mount Controllers (WMC01)

Components Language Filename Checksum (MD5)
bd7a8df373272cef42
English F0664_MPS_HST_V4_3_0_6L_HW3_enGB.bin
426ab847cde2dc
96e73c8ad0d8da05b
Portuguese F0664_MPS_HST_V4_3_0_6L_HW3_ptPT.bin
047f29d4e7c9871
e598ab524d8a14a21
Spanish F0664_MPS_HST_V4_3_0_6L_HW3_esES.bin
2475cf2bc2f68dd
83afb1031e63edf85f
Turkish F0664_MPS_HST_V4_3_0_6L_HW3_trTR.bin
a52d3e51061cb6
MPS-A App 2ec86218675bd43df
Czech F0664_MPS_HST_V4_3_0_6L_HW3_czCZ.bin
Main af9619ebda9ca84
Board 6f98281ecbc760f1aa
Slovak F0664_MPS_HST_V4_3_0_6L_HW3_skSK.bin
9f670786c7a6d0
d868ab335756f0ef9f
French F0664_MPS_HST_V4_3_0_6L_HW3_frFR.bin
72a28c187131f1
69ad1b250ab5e48ae
Swedish F0664_MPS_HST_V4_3_0_6L_HW3_svSE.bin
1b6f5f7c074e641
Danish Not available
f8d76dfd407eea61c3
Boot NA F0664_MB_BL_V1.1.0.5P.bin
99f0c0417c8d2e
67666cb2bc604021b
F0664_MPSB_HST_V4_3_0_6L_enGB.hex
e1ff9cdc5b893d8
58113be3a8aa2e759
English F0664_MPSB_HST_V4_3_0_6L_enGB.mpsb
eee8218be49cb89
832e4a0de211948e9
F0664_MPSB_HST_V4_3_0_6L_enGB.mpsb_host
b80ab2c9fe60dea
cba02e0a01f0e6009
F0664_MPSB_HST_V4_3_0_6L_ptPT.hex
dd3854f61fb699c
a1190389d9e1cb5fa
Portuguese F0664_MPSB_HST_V4_3_0_6L_ptPT.mpsb
df126d28469fc63
f4a4fa0b53ce2b9954
F0664_MPSB_HST_V4_3_0_6L_ptPT.mpsb_host
52a6b22ab6e7b0
f894ef561fcba2ca5c8
F0664_MPSB_HST_V4_3_0_6L_esES.hex
8ece699ef0031
844ecafeeef2f80ed1
Spanish F0664_MPSB_HST_V4_3_0_6L_esES.mpsb
cd0e75d15c0c00
5816e0a53bff9b9b64
F0664_MPSB_HST_V4_3_0_6L_esES.mpsb_host
3cc364d0dd842f
MPS-B
f9d1c293eab4e55d7
Main App F0664_MPSB_HST_V4_3_0_6L_trTR.hex
638b3ebd37b7aa1
Board
a6c89858289fc9bae
Turkish F0664_MPSB_HST_V4_3_0_6L_trTR.mpsb
32f8ab4ec346a14
148173c00584f9a28
F0664_MPSB_HST_V4_3_0_6L_trTR.mpsb_host
6181edf2242b855
968e8976705e6d431
F0664_MPSB_HST_V4_3_0_6L_czCZ.hex
460cc23c3284e32
378de02efb0fb07e8a
Czech F0664_MPSB_HST_V4_3_0_6L_czCZ.mpsb
1ef9341d1abfeb
9962fd1c36e32697c
F0664_MPSB_HST_V4_3_0_6L_czCZ.mpsb_host
0b9474646c4f2a0
132bb3a11ac427dbf
F0664_MPSB_HST_V4_3_0_6L_skSK.hex
0ff41ba0f912b98
ec5384bf1cf49cd33af
Slovak F0664_MPSB_HST_V4_3_0_6L_skSK.mpsb
6e77a5a8b3ddd
ed1c7f381916b2eb0
F0664_MPSB_HST_V4_3_0_6L_skSK.mpsb_host
c92921ae4ce010b
328df09650cc11b4c5
French F0664_MPSB_HST_V4_3_0_6L_frFR.hex
3fac08c8e210f3

Components Language Filename Checksum (MD5)

2eee79aad67456c4d
F0664_MPSB_HST_V4_3_0_6L_frFR.mpsb
302a184804534df
63da4d08578d347c8
F0664_MPSB_HST_V4_3_0_6L_frFR.mpsb_host
96bc4ddbb5e3b39
52673ea3022597efa
F0664_MPSB_HST_V4_3_0_6L_svSE.hex
79341bb79ef3b1d
bb888b7215f3f06c8d
Swedish F0664_MPSB_HST_V4_3_0_6L_svSE.mpsb
9dd6bd44fff5f2
369f53dc99225998a
F0664_MPSB_HST_V4_3_0_6L_svSE.mpsb_host
ea6c44dcb657dce
9bd6a46f0a521cfa6b
F0664_MPSB_HST_V4_3_0_6L_daDK.hex
07ede4241df09b
f78eb68dcdcde08c55
Danish F0664_MPSB_HST_V4_3_0_6L_daDK.mpsb
f980142e0b5fd0
9ba202dd12b465a3a
F0664_MPSB_HST_V4_3_0_6L_daDK.mpsb_host
1b1ab662e686a57
Note:
*.hex: for use with USB script
*.mpsb: for use with USB drag and drop
*. mpsb_host: for use with Firmware Transfer Tool (FTT)
bcbfbf5c3410f794a1
NA F0664_MPSB_BL_V1_0_0_0P.srec
5bc8fd9e86261d
Boot
5e252b641c005450a
NA F0664_MPSB_BL_V1_0_1_0P.bin
87673499968f99b
a39fc86be72c6e9fac
Navigation Board NA DM_NB_V1_2_2.hex
8b21ea3c84d963
(MPS/EMS/
WMC01 only) 030fb76016ff2f227e9
NA F0664_MPS_TCH_V3_1_0000P.hex
95713a5f6044f
c0d5b30d21c01083b
Ten Button Board NA TEN-BB_V2_3_0002.hex
a36a8febc7d9b8b
NETWORK-SWITCH-LP01-105- 5cd834aa2e67b5bf2455
Network Swich Firmware
1.0.2.S0.fw 8daecb1fd68d
1.2.6 Tools
1626ea4032a3a2c276
Install_ASL_PAVA_SCT_V4_2_0_6-P.exe Branded
PAVA System 9747ad829eb3c0
Configuration Tool ea49d1e33a37136197
Install_PAVA_SCT_V4_2_0_6-P.exe Unbranded
269297bd493d47
Filer Transfer Tool for
As part of the PAVA System Configuration Tool NA
configuration only
Firmware Transfer Tool ae9ee3489328c25bbb
Install_ASL_FTT_V4_2_0_6-P.exe Branded
(stand-alone) for 1f37132e24dcbe
configuration and firmware e69d5a1b02ffeaf13d5
update Install_FTT_V4_2_0_6-P.exe Unbranded
ddaf1e004ba4b
Router Dynamic Installed as part of the PAVA System Configuration Tool
NA
Configuration Tool above
Installed as part of the Router Dynamic Configuration Tool
Audio Settings Manager NA
above
Vipedia Finder NA NA
Vipedia Bootloader a90e7e94302b6749c1
Vipedia_bootloader.exe
(Firmware updater) d20778c6b6f66a
Amplifier Dynamic Installed as part of the PAVA System Configuration Tool
NA
Configuration Tool above


2243ab40ce3e0faf088
vipa-config-4-2-0-0087.exe Branded
d9070a0639acc
VIPA Config Tool
b34053011852f4ce44
vipa-config-unbranded-4-2-0-0087.exe Unbranded
8cc613d599c669
b5844dbc537e5c7436
ASL Event Viewer Setup 3-1-0-6P.exe Branded
1292cce39e01a1
Event Viewer
c0f9907bbdbd2c923c
PAVA Event Viewer Setup 3-1-0-6P.exe Unbranded
4be49dfc3a77eb
MB Ethernet
Bootloader MB_ethernet_bootloader.exe 723f7b91e672fe80544
V2.0.3
(requires cygwin1.dll) 1518a4bcf5903
(Firmware
MPS-A updater)
MB USB b4aec21b4ee5dbe01c
Boot dfuprog.exe
Bootloader b283d55d3f9292
(Firmware 809f7f042dfb0088ad2f
updater) Driver MB_usb_device_bootloader_V1.3.7611.zip
bb7facbd7741
MB Ethernet
Firmware Use FTT V3.3.2.0 or later NA
Updater
MPS-B
MB USB
Firmware Use drag and drop NA
Updater
Microphone XML Loader 27d9e0e7ef5a189bb9
ASL-CONFIG.exe
(Configuration Tool) 429dffd79e2ab1
6e12efbce3032f8d903
Microphone Finder finder.exe
8e57307c0ce74
79fc5bc1434340ae34
Branded
Update Manager UpdateManager.exe 1f2ba3a2008e39
Unbranded Not available
6737352c734ae60080
Branded
2401030dd4c292
Network Card Manager NetworkCardManager.exe
fe5b974848171a8154
Unbranded
9fb4b10fa60d1d
106a6cd28e19eb2e28
Branded
Network Card Image 65eb7a837cdc39
NetworkCardImageManager.exe
Manager e95e96edd25cd1b5ee
Unbranded
cff91370561ab0
1.3 Compatibility
a) The components of this release package may not be inter-compatible with older releases. ALL units
within a given system MUST use the versions listed on this release note.
b) VIPEDIA-12 PCB Issue 4 with Dante or standard Network Card.
c) VIPEDIA-12 and V2000 in this release are compatible with flash part FL128S and existing flash parts.
d) V2000 PSU V7.30.0.0P:
a. Frame Controller SW for INTEGRA & 48V V2000:
Will work in backward compatibility mode with frame controller 3.0.1.x but ideally to be used with
Frame controller 3.3.2.xL (or newer)
b. Frame Controller SW for V2000:
Frame Controller version V3.3.2.xL (or newer).
It is also compatible with Frame Controller V2.1.x.xL.
e) V2000/INTEGRA 110V mains supply:
Requires PSU V7.30.0.0P and Frame Controller V4.2.0.0P (or newer).

f) NET-VIPA V4.2.0.81 (or later) no longer supports Network Card Issue 1 due to updates to the boot
script.
g) Dante Brooklyn II firmware V4.1.1.4 and Dante Controller V4.2.3.1
h) VIPA Config Tool (VCT) V4.2.0.0087 or later:
• Suitable for generating configuration files for VIPA s/w V4.2.0.
• Suitable for reading configuration files from VIPA s/w V0.11.1 and above.
• Matching release VIPA V4.2.0.
• ASL Qt version 4.7.4.3.
i) UIP V1.2.0027 is compatible with Vipedia V2.1 or later.
j) Vipedia DSP V3.3.1.0 onwards also supports Macronix Flash part (U80) MX29GL512 (to replace
Spansion S29GL-S part in production).
k) Network Card Manager V1.2.0.8P (or later) and Update Manager V1.4.0.9P (or later). Can be used
with previous releases of the PAVA SCT and VCT.
• Network Card Manager V1.2.0.8P (or later) must be used when updating Network Cards Issue 2.
• Update Manager V1.4.0.9P (or later) is required to load the signed version of the Vipedia and
V2000 firmware/software (filename of main codes is now “Sxxxx” rather than “Fxxxx”), where “S”
means “signed code”. For example: “S0641_12_HCP_V4.2.0.0P” instead of
“F0641_12_HCP_V4.2.0.0P”.
Can be used to load previous releases.
l) Network Card Image Manager V1.0.0.1P can only update the image on Network Card Issue 2 to
image bundle 5 (KERNEL V3.0.0.3P / ROOTFS V3.0.0.3P / ETCEFS V3.0.0.3P).
m) MPS-A USB firmware loader is not compatible with Windows 10. If required, contact ASL.
n) MPS V4.3.0.6L is compatible with:
• VIPEDIA-12 V4.x, V3.3.x.xL and V2.1.34.xL
• VIPA Stack V4.x, V3.x and V2.x
• VAR Routers: VAR MODE should be enabled
- Any version of VAR Routers for legacy Paging Protocol
VAR4/12/20 V6.1.0031 is required for fault and Voice Alarm status reporting using legacy
Protocol. MPS ‘fault’ and Voice Alarm LED is synchronised with Router’s ‘fault’ and VA LEDs
are synchronised with Router’s ‘fault’ and ‘voice alarm’ LEDs respectively. Only available on
microphones connected to inputs 1 to 4. Not available from VAR8 and VAR8-ACU.
- VAR4/12/20 V6.1, VAR8 V3.1 and VAR8-ACU V3.1 for new Serial Protocol
Busy indication on green=zone select is not currently provided on VAR4/12/20 and VAR8,
only on VAR8-ACU V3.1.0017 or later (the microphone should be set with LED behaviour =
Busy Standard).
o) VIPA Listen-in: All Network Cards of VIPEDIA-12/INTEGRA routers must be updated to V4.2.0.79P or
later and all VIPA devices must be updated to VIPA Stack V4.2.0d or later. Failure to do so may result
in issues with Listen-in functionality.
p) Vipedia Host /V2000 Frame Bootloader V4.0.0 (plain text):
Plain text Bootloader V4.0.0 can replace the original V1.4.1. It can be used with any pre-existing
application. It is more robust and recommended where security is not required. It allows easy recovery
when the application update fails (typically with TFTP ERROR).

q) Vipedia Host /V2000 Frame Secure Bootloader V5.0.0 (secure):

Secure Bootloader V4.2 and V4.3 is now deprecated.
Secure Bootloader V5.0.0 replaces the pre-existing secure Bootloader V4.2/V4.3.
Secure Bootloader is required for VIPEDIA-12/V2000 V5.0 (or later) or VIPEDIA-12/V2000 that may
be updated to V5.0 with security enabled, and Secure Bootloader V5.0.0 is the recommended version.
Secure Bootloader is fully compatible with all current latest LTS releases for 2.1, 3.3 as well as 4.2
and future releases.
Units with Secure Bootloader only execute Signed versions of the application (filenames starting with
“S” rather than “F”).
r) Update Manager V2.0.0.0P supports:
• VIPEDIA-12: 2.1 onwards
• V2000: 2.1 onwards
• PAVA SCT Schema: 3.00.00 to 8.05.00
s) V2000 LSZDC:
• This version (bootloader and DSP) is compatible with flash part MT25QL128 and W25Q128JVSIM
on LSZDC hardware build standard 8 (or newer) and is back compatible with flash parts on older
LSZDC hardware.
• LSZDC hardware build standard 08 (or newer) must not be downgraded to a firmware version that
does not support flash part MT25QL128 and W25Q128JVSIM.
• LSZDC firmware versions that support the above flash part at the time of this release package:
- DSP V5.0.2.5P / DSP Bootloader V5.0.2.4P
V2000 Frame V4.2.0.7L (or later) and V5.0.2.5P (or later) do not allow downgrading DSP Bootloader
V5.0.2.4P

2 New Features
2.1 V4.2.0.8L-A
2.1.1 V2000 LSZDC Flash Part W25Q128JVSIM (LSZDC Bootloader V5.2.0.4P / LSZDC DSP
V5.0.2.5P)
The LSZDC Bootloader V5.2.0.4P / LSZDC DSP V5.0.2.5P support flash part MT25QL128 and
W25Q128JVSIM on LSZDC hardware build standard 8 or newer.
Warning:
LSZDC hardware build standard 08 (or newer) must not be downgraded to a firmware version that does
not support flash part MT25QL128 and W25Q128JVSIM.
LSZDC firmware versions that support the above flash part at the time of this release package:
• DSP V5.0.2.5P / DSP Bootloader V5.0.2.4P
Notes:
a) LSZDC hardware build standard 8 not yet released at the time of release of V4.2.0.8L Package A.
b) LSZDC Bootloader V5.2.0.4P / LSZDC DSP V5.0.2.5P are back compatible with older LSZDC
hardware versions.
c) V2000 Frame V4.2.0.7L (or later) and V5.0.2.5P (or later) do not allow downgrading DSP Bootloader
V5.0.2.4P.
2.1.2 Danish Language Support (VIPEDIA-12 V4.2.0.7P / MPS-B V4.3.0.5P or newer)
Danish language is now supported on Vipedia and MPS-B front panels.

Danish language is not available for MPS Type A. Contact to ASL if required.
2.1.3 Vipedia Host / V2000 Frame Bootloader V4.0.0/V5.0.0
See “3.1.8 Vipedia Host / V2000 Frame Bootloader V4.0.0/V5.0.0”.
2.2 V4.2.0.6P-C
2.2.1 V2000 Rack Fan / INTEGRA Box Fan Settings / Temperature Alarm (PAVA SCT V4.2.06P)
The temperatures that turn the V2000 rack fans and INTEGRA box fans on/off when they are controlled by
a digital output are now configurable on the Advanced settings of the amplifier frame.
The original default settings are preserved for pre-existing amplifier frames, and new default settings are
applied to new amplifier frames.
Also, the Temperature Alarm setting has been removed as it is not used (any amplifier frame version).

NEW
OLD
Fan Settings:
• Fan Control Output: the digital output(s)
configured as Fan (read-only).
If no fan output configured, shows “No fan
configured on [Unit Id and Name of master
VIPEDIA]” in red.
• PSU Fan Trip (°C): PSU temperature that
trips the fans (40 to 70)
• PSU Fan Range (°C): determines the PSU
temperature below which the fans stop (5
to 20)
• Amplifier Fan Trip (°C): PSU temperature
that trips the fans (40 to 70)
• Amplifier Fan Range (°C): determines the
PSU temperature below which the fans
stop (5 to 20)
Where:
1) fan stop temperature = trip temperature -

range
2) The fan control output must be an on-

board or BMB digital output on the master
VIPEDIA-12 unit (which is labelled [DBB1]
in the PAVA SCT tree).
New default:
• PSU Fan Trip (°C): 60

• PSU Fan Range (°C): 10
• Amplifier Fan Trip (°C): 60
• Amplifier Fan Range (°C): 10
Old default:
• PSU Fan Trip (°C): 70

• PSU Fan Range (°C): 5
• Amplifier Fan Trip (°C): 70
• Amplifier Fan Range (°C): 5
2.2.2 Placeholder for the next item
2.3 V4.2.0.6P-B
None.
2.4 V4.2.0.6P-A
2.4.1 AS Redundant System - SIP (NET-VIPA V4.2.0.81P) (SysAid #21486)
The SIP client is now supported by AS-redundant network cards but note that only the active network card
registers with the SIP server. During a redundancy changeover, the old active network card de-registers
from the SIP server and the new active network card registers.
Notes:
a) The maximum number of accounts that can be registered is 100.

b) Total number of accounts = Number of SIP Servers * Number of Accounts in PAVA SCT config
2.4.2 AS Redundant System - MPS hosted by Network Card (NET-VIPA V4.2.0.81P) (SysAid
#22112)
MPS can now be hosted by AS-redundant Network Cards. However, note that since from VIPA's point of
view there is only one network card, the standby Network Card cannot perform audio routing. Because of
this, only the active Network Card communicates with the microphone which means that the MPS only
ever shows one host controlling it, not two.
Notes:
a) “system” fault LED and class faults (on LCD) are suppressed on MPS hosted by AS-redundant
Network Cards. This is to avoid an issue where the “system” fault LED and class faults alternate
between on & off when the system contains AS-redundant units.
Please note that the same issue will exist in other VIPA devices running va-global-status-d (e.g.
other network cards that are not part of an AS-redundant unit, VIPA hosts, VIPA managers, etc.
b) The Network Card hosting a microphone completely ignores the host IP value of the "Control Port"
of VCT (JOUL:<microphone IP>:<host IP>:<port>). Instead, it always uses its own IP address.
2.5 V4.2.0.5P-D (pre-release to Production)
2.5.1 LSZDC Flash Part MT25QL128 (LSZDC Bootloader V4.2.2.0 / DSP V4.2.0.7P)
The LSZDC Bootloader V4.2.2.0 supports flash part MT25QL128 on LSZDC hardware build standard 8 or
newer.
The ‘combined’ version of DSP V4.2.0.7P contains Bootloader V4.2.2.0.
Notes:
d) LSZDC hardware build standard 8 not yet released at the time of release of V4.2.0.5 Package D.
e) Bootloader V4.2.2.0 and DSP V4.2.0.7P are back compatible with older LSZDC hardware versions.
Warning:
LSZDC hardware build standard 08 (or newer) must not be downgraded to firmware version that does not
support flash part MT25QL128.
For each firmware branch, do not downgrade to firmware version older than:
• DSP V4.2.0.6P / DSP Bootloader V4.2.2.0
• DSP V3.3.3.2L / DSP Bootloader V4.2.2.0P
• DSP V2.1.19.0P / DSP Bootloader V2.1.0.7P
If older version is required, contact ASL.
First external release of ASL NETWORK-SWITCH-LP01.
2.6 V4.2.0.5P-C
2.6.1 Vipedia Host / V2000 Frame Bootloader V4.3.0
VIPEDIA-12 and V2000 now support Secure Bootloader to support secure encryption/authentication
mode.
The Secure Bootloader is required for VIPEDIA-12/V2000 V5.0 (or later) or VIPEDIA-12/V2000 that may
be updated to V5.0.
It is fully compatible with all current latest LTS releases for 2.1, 3.3 as well as 4.2 and future releases.

Warning:
• Units with Secure Bootloader only execute Signed versions of the application (filenames starting
with “S” rather than “F”).
• Non-signed versions may still be downloaded but will not run. There is a risk that you may not be
able to return a unit to operational mode unless you have a signed version of the application. Do
not proceed with the download unless you are sure of this.
• Contact ASL if a Signed version of the application is not available for download.
The Bootloader version is displayed on:
- On Vipedia front panel: Configuration > Router > Identity > S/Ware > [Bootloader: V4.3.0P]
- On FTT (File Transfer Tool) > Write
- On FTT (File Transfer Tool) > Network Settings
- On Vipedia front panel in Bootloader Mode
- On serial monitor: “get ver” monitor command
- On ADT (Amplifier Configuration Tool)
Summary of features/changes in Bootloader:
1) Allows easy recovery method for update tools when stuck in bootloader mode.
2) Bootloader automatically reboots after inactivity timeout.
The inactivity timeout is programmable: 60 s to 3600 S (default is 90 s).
Warning:
The Serial Number will be erased if an application older than V4.2 is loaded into a unit with
subsequent static config clear or application update.
3) New status and messages display for VIPEDIA-12; see summary below
4) Serial Number programming:
If programmed, the Serial Number is displayed on VIPEDIA-12 V4.2 (or later) via front panel menu
option Configuration > Router > Identity > S/Ware > [S/N: xxxxxxxxxxxxx].
V2000 serial number is not currently displayed on any tool.
Warning:
5) Fault sounder can be suppressed using Fault Accept key.
6) Status messages to applications (e.g. FTT and Update Manager).
7) Telnet is no longer supported.
VIPEDIA-12 LCD display in bootloader mode:

• First char animation "-+|+"
• First char animation "-+*+" buzzer suppressed.
• First char animation "x!" bootloader self-signature check failed.
• Second char ':' serial port active.
• '9!' to '0!' inactivity timeout pending.
Messages:
• " Good Application Present "
• " Downloading 100% from 192.168.1.123 "
• " *** TFTP error to 192.168.1.123 *** "
• " *** No Application Present *** "
• " *** Application Bad Checksum *** "

• " *** Application Bad Signature *** "
• " *** Corrupt Bootloader *** "
• "Rebooting (console reset command)"
• "Rebooting (due to inactivity)"
• "Rebooting (keyboard request)"
• "Rebooting (set network info)"
• "Rebooting (update host image)"
2.6.2 Vipedia Host / V2000 Frame Bootloader Updater V4.3.0.0
A special Bootloader Updater application is available that upgrades an older bootloader.

A subsequent downgrade is not permitted. Downgrade can only be performed in manufacturing.
The Bootloader Updater application is not part of the standard release package.
It is available on request. Please contact ASL for details.

2.7 V4.2.0.5P-B
2.7.1 VIPA Devices V4.2.0e – VIPA Host Redundancy
Two VIPA Host (Lanner) units can now operate as a redundant pair. The primary unit is configured as
Master, and the secondary as Slave (VCT > Advanced Settings of the device).
Note:
In order to support VIPA Host redundancy, XMPP heartbeats are now enabled by default. This may
impact any non-standard modules used on VIPA devices using this firmware version (or a later version).
If your non-standard module experiences unexpected DISCONNECTED errors, especially after
approximately 20 seconds of operation, please check that you are invoking setNoopTimer() correction on
your JCOPConnection object after sign-on.
All standard VIPA modules have already been (or have been in this release) updated with heartbeat
support.
2.7.2 None
2.8 V4.2.0.5P-A
2.8.1 VIPA Devices V4.2.0c and MPS V4.3.0.3 – Client-directed Listen
In addition to Server-directed listen-in, VIPA Devices (VIPA Servers, VIPA Host, etc.) now support Client-
directed listen-in which allows a VIPA MPS microphone at the Control Centre and a MPS microphone at
the local Station to independently listen to that station. It also allows multiple microphones at the Control
Centre to listen to a distinct station without impediment.

• The VIPA Device at the Control Centre is set to use the “Client-directed” listen-in, which uses the B
mixer on the Vipedia.
• The VIPA Device at the stations are set use the “Server-directed” listen-in, thus continuing to use the
A mixer on the Vipedia.
• The station VIPEDIA Network Cards are configured with the A mixer associated with a local station
listen in multicast address and port - unique for each Station.
• The Station’s VIPA-hosted MPS is configured with this local station listen-in multicast address.
• The VIPA-hosted MPS microphones at the Control Centre are each configured with their own listen in
unicast address (this means they can operate with maximum independence).
Notes:
a) The Network Card currently does not support Client-directed listen-in.
b) Server-directed listen-in support has not changed on VIPA devices and Network Cards.
c) Each MPS microphone can listen to a mix of zones on a single VIPEDIA, chosen by the microphone
listen-in buttons.
d) As standard, only one Vipedia can be listened to at a time.
e) Only one microphone at the Control Centre can listen to any one given station at a time. If one Control
Centre microphone is listening to station A, and then a second Control Centre microphone attempts to
listen to station A, audio will be directed to the second microphone.
f) The VIPA-hosted microphone at each station can listen to any configured mix of zones at that station
(and only that station).
g) A brief artefact at the start of the listen-in may be noticed when a listen-in button is selected when
another listen-in button is active on the same microphone.
2.8.1.1 Requirements:
• VIPA Stack V4.2.0c (or later)

• VCT V4.2.0.87 (or later)
• MPS V4.3.0.3P (or later)
• Network Card V4.2.0.75P (or later)
2.8.1.2 Configuration:
The first step in configuration is to allocate a unique multicast address for each station to be used for local
listen in. You then need to choose a single UDP port number to be used across the system for listen-in –
this port number should not be in use for any other purpose at any Station. (This is referred to from here as
“the chosen listen-in port”.)
2.8.1.2.1 Station Configuration
• The Station VIPEDIA Network Card must be configured with a single “Mixer”; see Figure 2.
• This Mixer must be set to ID 1 (one) 1 and associated with the “listenin” group; see Figure 2.
• The “listenin” group must also be associated with the first PMC output of a dedicated PMCDevice on
the netcard; see Figure 4.
• This PMCDevice must use the unique multicast address allocated for listen-in for that station, and the
chosen listen-in port; see Figure 3.
• The local MPS microphone must have its “Listen In Source Address” and “Listen In Source Port” set to
match these parameters; see Figure 1.
1 ID 1 corresponds to “MIXER A” in the PAVA System Configuration Tool.

The above settings are already the standard for a local Station microphone that listens to zones at the
station only.
2.8.1.2.2 Control Centre Configuration
• No Mixer or associated PMCDevice should be added to the Control Centre VIPA Device configuration.
• The Control Centre VIPA Device must have the “Use Client Listen In for Microphones” advanced setting
enabled (ticked). The default for this setting is disabled; see Figure 5.
• For each MPS IP microphone, the “Listen In Source Address” must be set to that microphone’s unicast
IP address; see Figure 6.
• For each MPS IP microphone, the “Listen In Source Port” must be set to the chosen listen-in port; see
Figure 6.
2.8.1.2.3 Example Configuration Extract
There follows an edited VCT configuration pointing out the salient settings:
<?xml version='1.0' encoding='ISO-8859-1'?>

<ASLCONFIG version="4.2.0" config-tool-build-number="0087">
<System>
<VIPEDIA-NET secondary-mps-instance="n" mcast-control-address="239.2.0.1" run-va-global-
status-d="y" ip-address="162.168.1.227" netmask="255.255.255.0" name="vnet-42" run-announced="y"
gateway-address="162.168.1.253" display-message-timeout-seconds="20">
<Vipedia var-id="42" ip-address="162.168.1.72" jpc-name="vnet-42">
<RouterOutput number="1" zones="Zone.42.all,Zones.All,zone-02-42-01"/>
</Vipedia>
<Microphone multicast-listen-in-channel="1" protocol="2"
multicast-listen-in-port="15001" multicast-listen-in-address="239.80.1.1"
audio-group="239.12.1.10:20121:1" unit-id="64">
<Button number="10" type="listen-in" text="listen.42.1-3" zones="zone-02-42-
01,zone-02-42-02,zone-02-42-03"/>
</Microphone>
<PMCDevice port="15001" dva-end-channel="1" dva-start-channel="1"
mcast-address="239.80.1.1">
<PMCOutput groups="listenin" type="static"/>
</PMCDevice>
<Mixer mixer-id="1" priority="63" output-group="listenin" output-type="pmc"/>
</VIPEDIA-NET>
<Linutop stream-all-dvas="y" run-va-global-status-d="y" writeable-dva-
dirs="/dva/msgs/dist"
client-mic-listen-in="y" ip-address="162.168.1.167"
netmask="255.255.255.0" name="linutop-mar-01" run-announced="y"
display-message-timeout-seconds="20">
<Microphone serial="JOUL:162.168.1.183:162.168.1.167:15600"
multicast-listen-in-channel="1" protocol="2"
multicast-listen-in-port="15001" multicast-listen-in-
address="162.168.1.183"
audio-group="239.12.1.20:20121:1" unit-id="64">
<Button number="10" type="listen-in" text="Listen.Vip.42" zones="Zone.42.all"/>
</Microphone>
</Linutop>
</System>
</ASLCONFIG>

The settings can be found at these locations within the VIPA Config Tool:
Figure 1 VCT Setting for Station Microphone
Figure 2 VCT Setting for Station Mixer

Figure 3 VCT Setting for Station Listen-In Source
Figure 4 VCT Setting for Station Listen-In Source (cntd)

Figure 5 VCT Setting for Control Centre VIPA Device
Figure 6 VCT Setting for Control Centre Microphone
2.8.2 Disabling VIPA Devices (VCT V4.2.0.87)
A VIPA device can now be marked as “disabled” in the configuration (“Unit Disabled” option in the device’s
Advanced Settings).
This is presently only used by VAVE, but will have uses generally in VIPA in the future.
VAVE will exclude “disabled” devices as hosting devices.

2.9 V4.2.0.4P-A
2.9.1 VAVE Support
Vipedia/Network Card, VIPA Devices (VIPA Host, VIPA Server, etc.) can now support VAVE.
Vipedia IP microphones can be configured to operate in VAVE mode falling back to Vipedia mode when
VAVE is offline.
External VAVE Host: can only be configured for automatic VIPA configuration
Hostname: hostname a VIPA Host (Linutop/Lanner)

IP Address: IP address of the VIPA Host
Netmask: Netmask of the VIPA Host
Gateway: Gateway of the VIPA Host
Warnings:
a) A Linutop with above settings will be added to the automatic VIPA config.
b) There is no validation of the IP settings.
c) Is mandatory if more than 2 x VAVE instances are configured.
• ID: automatically assigned (not configurable)

• Description: as required (will be displayed on VAVE)
• Monitored: for future use
• Microphone: a Vipedia IP microphone (as required)

VAVE Host:
• Auto-generated VIPA configuration: Network Card with lowest ID
• External VIPA configuration:
If VIPA Servers are present, VAVE Host will be the first VIPA Server in the configuration.
If no VIPA Servers, the VAVE Host will be the first Linutop, VAIA or iPAM400 in the configuration.
If no VIPA Servers, Linutop, VAIA or iPAM400s, the VAVE Host will be Network Card (VIPEDIA-
NET) with lowest ID in the configuration.
The device that runs announce-d global has precedence in all cases.
VAVE Host should be set with:
• Standard Settings > Run announce-d (Global)
• Standard Settings > Run Global VA Status Module: Yes
• Advanced Settings > Force DVA Streaming (enabled)
2.9.2 Swedish Language Support

Swedish language is now supported on Vipedia and MPS front panels.
2.9.3 MPS - PMC TTL Configuration
It is now possible to configure the PMC TTL on MPS microphones and MPS-base products such as the
WMC01.
Configuration is from the MPS configuration menu (not currently available on PAVA SCT or VCT):
IP SETTINGS >> PMC TTL
• Default: 9
• Range: 1 to 30
2.10 V4.2.0.2P-B
See “4 Bug Fixes” (page 79) and “3 Changes and Improvements” (page 48).
2.11 V4.2.0.2P-A
See “4 Bug Fixes” (page 79).

2.12 V4.2.0.0P-A
1) Vipedia NTP Server configuration and self-hosting NTP
The configuration of the NTP on the Vipedia system has been simplified and no longer requires the
use of the VCT or manual configuration to setup an NTP server within a Vipedia cluster.
By default, the Vipedias with the lowest Unit-id will used as the default NTP server if no external
servers are configured. The unit with the 2nd lowest unit-id will be used as a backup NTP server.
It is possible to configure external NTP servers for time synchronisation across the Vipedia network.
The Vipedia front panel display will now show the current time, the local time zone, the date and, if
present, synchronisation fault (!LCL TS or !SYS TS).
The synchronisation state of the network NTP can be viewed from the Vipedia front panel bottom row
column 1:
• ! Indicates major faults on this unit.
• : Local unit time synchronisation fault
The VCT status tree and the front panel Fault log provide details of the faults. These are
transient faults and are not latched.
• . System time synchronisation fault.
This unit has no time synchronisation faults but other units in the system have.
• Individual time synchronisation status may be checked in the front panel Fault summary.

The Time Master clock can be set from the File Transfer Tool. This could be used to set time during
commissioning of systems with no external NPT servers or when the NTP servers are unavailable.
Notes:
a) HCP and GPS time synchronisation is no longer supported. Please contact ASL if required.
b) NTP Servers on external VIPA configuration using the VIPA Config Tool (VCT) must be configured as
global NTP Servers.
Local NTP Servers can be used if all VIPA devices in the config have the same local NTP
Servers.
VIPA configuration files that contain NTP Servers that do not conform to these rules will not be
accepted by the PAVA SCT.
Note that the VCT shows a warning for multiple global NTP Servers. You can safely ignore this
warning.
c) VIPEDIA-12 in an external VIPA configuration must have the “Set Time” option set to “None”.

2) Vipedia Fading up/down (e.g. background music)
All Vipedia routes have intrinsic 200 ms fading up and down times.
It is possible to set custom fading up and/or down times for certain low priority routes.
The setting is common to all Vipedia in the same cluster.
Custom fade times are applied to routes that meet the following
conditions (see example on the right):
• The route priority is 20 to 63
• Route is Non-emergency
• Restore Audio after override is enabled
• Volume adjustment is enabled
Custom fade down on override only applies if the original route
meets the above criteria and the overriding route is non-
emergency and has priority 11 to 63.
The above settings determine the Fade Behaviour of a route:

Background, Standard or Urgent (see details in PAVA Cluster
Options>Route Configuration tab – example above). The Fade
Behaviour information is displayed in the routing attributes; see
example on the right and below.
Notes:
a) Custom fade up and down times are not applied to any VIPA
route irrespective of the route attributes.
b) Custom fade down on override is not applied if the overriding
route is a VIPA route.

Check the Fade-up and Fade-down times in the PAVA

Cluster Options>Route Configuration tab for fading
up/down times applied to Background routes.
3) Cluster/Node Voltage selection
There is an additional selection field for setting the expected AC voltage input range of the cluster.
This is used to ensure that the 1000W power rating of the V2000 amplifier frames is not exceeded
when running from low voltage AC supplies. It has no direct control of any product functionality.
Cluster voltage settings may be overridden at the node level.
If the wrong setting is applied the Vipedia will report a Configuration error against that frame and will make
any necessary adjustments to the V2000 amplifier powers to ensure the units do not overload.

4) Vipedia now reports faults of MPS microphones attached to a Network Card. The front panel fault is in
the following format:
VNET MIC FAULT y:XXX, where y = fault code and XXX = Mic Id
• VNET MIC FAULT 1:XXX = ASLPAVA.abc.MPSXXX.MicFault

• VNET MIC FAULT 2:XXX = ASLPAVA.abc.MPSXXX.MicCapsuleFault
• VNET MIC FAULT 3:XXX = ASLPAVA.abc.MPSXXX.ConfigError
• VNET MIC FAULT 4:XXX = ASLPAVA.abc.MPSXXX.MPXFault
• VNET MIC FAULT 5:XXX = ASLPAVA.abc.MPSXXX.PowerWarning
• VNET MIC FAULT 7:XXX = ASLPAVA.abc.MPSXXX.CommsFailure
5) The PAVA SCT and MPS now supports ATEX microphones with electret fist microphones:
a. MPS-EX-FE (electret): new type

b. MPS-EX-FD (dynamic): replaces MPS-EX-F0 in previous releases
6) Vipedia now reports CHIME DVA MISSING for missing chimes.
The missing DVA numbers are now logged in the Event Logger (up to 10).
7) Main code filenames are now "Sxxxx" (rather than "Fxxxx"), where “S” means “signed code”. For
example: “S0641_12_HCP_V4.2.0.0P” instead of “F0641_12_HCP_V4.2.0.0P”
Update Manager V1.4.0.9P (or later) is required to support signed codes.
8) Vipedia bootloader version is now displayed in the front panel menu option
Configuration>Router>Identity>S/Ware.

9) The PAVA SCT and associated tools now uses Windows 10 look and feel; see example below:
BEFORE (tab background = grey and drop-down=white)
NOW (tab background = white and drop-down=grey),

2.13 V4.1.0.0-A
1) Network Card:
a) VIPA applications can now dynamically configure permanent routes. Any pre-configured BGM
source can be used as the source which can be permanently routed to any local analogue audio
output.
NOTES:
i. You must not use the same BGM source for a permanent route as well as a BGM route.
ii. You must also never use the same output in a permanent route and a BGM route.
iii. You must not override a permanent route with another permanent route.
iv. The following permissions are user configurable:
• ASL_ROUTE_NON_BUSY = 0x04
• ASL_ROUTE_ANS_ENABLED = 0x08
• ASL_ROUTE_ANS_TOLERANT = 0x10
• ASL_ROUTE_NVC_IGNORE = 0x80
• ASL_ROUTE_EMERGENCY = 0x100
b) It is now possible to configure permanent PMC streams from VIPEDIA-12 inputs (including
processed Dante inputs) on the PAVA SCT. The PCM streams are configured in the PAVA SCT
and fulfilled by the appropriate network card, for example, an input of Vipedia unit 3 can only be
streamed by the Network Card of Vipedia unit 3.
NOTES:
i. These permanent routes can still be configured using the VCT. Both configurations will be
honoured by the Network Card.
ii. Note that you must reload the configuration unit after upgrading to V4.1 because the
internal configuration files have slightly changed.
c) VIPA BGM sources can now be configured on the PAVA SCT.
01 to 06: External PMC Streams

07 7o 09: External Dante Sources
10 to 13: Processed Dante Inputs
14 to 15: Internal PMC Streams
NOTES:
i. The VCT can only configure PMC sources as BGM sources but the PAVA SCT can
configure other sources as well, like DANTE streams.
ii. BGM sources can still be configured on the VCT but only one will be used. If PAVA SCT
has configured any BGM sources, then that configuration will be used, otherwise, the
configuration from the VCT will be used instead.
iii. The VIPA BGM routing mechanisms (microphone buttons, SIL or other VIPA application)
have not changed.

d) Dante traffic on PRO units can now be isolated from the PAVA traffic via “Isolate Dante Network
(ETH5/6) from the Secure Loop Network” option on the PAVA SCT configuration.
If isolated, the SFP ports ETH5 and ETH6 are disconnected from the internal switch and
exclusively used by the Dante module. And copper ports ETH1, ETH2, ETH3 and ETH4 are used
by the PAVA network (i.e., Vipedia and Network Card) as standard.
NOTES:
i. This option should not be used where Dante is used for VA applications.
ii. This option takes effect immediately, no reboot is required.
e) The Network Card is now capable of adjusting the volume of the analogue audio outputs of its
VIPEDIA-12. This allows clients like the ASL PA HMI to adjust the volume of VIPEDIA-12 outputs.
f) Network Card Issue 2: Image bundle 5 included as units are shipped with new image.
NOTES:
i. Only required if Network Card ETH ports are used in loop configuration with RSTP
enabled.
ii. ETH3 and ETH4 in loop configuration only works if an SFP module is fitted to ETH5/6.
iii. Downgrade to V2.1 requires RSTP to be disabled using V3.3 or later. Otherwise, the
Network Card keeps rebooting.

2) VIPEDIA-12:
a) Vipedia can now route external PMC Streams.
The external PCM Streams are configured on the new PMC Streams page of the PAVA SCT and
are available as source in the available routing mechanisms: contact, button, permanent routes,
etc.
b) Vipedia can now route VIPA BGM where the source is an external Dante source configured in the
PAVA SCT; see Network Card item c) above.
3) PAVA SCT:
a) V2000/INTEGRA Amplifier Frame battery operation filter:
• For clarity, a help text has been added next to the V2000/INTEGRA Amplifier Frame battery
operation filter.
• The default value for the Class setting is now “Emergency Only (Low & High)” instead of "All
Classes".
b) The Cluster Overview now displays the PMC start IP address and port (as part of support for the
internal PCM/BGM streams).

c) The “Silence Enabled” default setting is now automatically set according the route Emergency
Class:
• Non-emergency routes: “Silence Enabled” enabled
• Emergency routes: “Silence Enabled” disabled
This automatic behaviour is represented by a lock in the UI.
It is possible, at any time, to override the automatic behaviour by opening the lock icon, and to
restore the automatic behaviour by closing the lock icon.
NOTES:
i. The automatic setting based on Emergency Class is done for microphone live
announcements since V3.0, where the “Silence Enabled” option is not visible on the GUI
ii. Non-default “Silence Enabled” settings will be preserved when an old config is loaded.
2.14 V4.0.0.1-A
1) Network Card:
a) Support for ATOP LM38-C3S-TI-N multimode SFP (NET-VIPA V3.3.2.63 or later).
b) NA.
2) MPS:
a) Translation to Slovak and Czech.
b) Version updated to support the new languages. No functional change since previous release
(V3.3.4.1).

2.15 V4.0.0.0-A
1) VIPEDIA-12/PAVA SCT: Dante Support
a) The PAVA SCT now supports the configuration of INTEGRA-PRO units.
b) External Dante sources are now available for all Vipedia routing mechanisms: contacts,
microphone buttons, permanent routes and VOX gates.

c) External Dante source can be processed by Vipedia (by using one analogue input) and then
routed over PMC to non-PRO units by any of the routing mechanisms.
Processed Dante inputs can trigger VOX routes similar to miscellaneous inputs.
The processed external Dante source can also be routed over Dante to PRO units (loopback
Dante channel).
d) Unprocessed external Dante sources can only be routed to PRO units (VIPEDIA-12-PRO or
INTEGRA-PRO).
e) Vipedia outputs are now permanently available over Dante.

f) The Dante configuration pane showing the Dante channel allocation is now read-only.
The Dante channel is now allocated on the Analogue Input configuration pane.
Tick the box to allocate a Dante channel
Read-only
g) The PAVA SCT can now generate the Dante configuration (*.xml) which can then be loaded into
the Dante Brooklyn II modules using the Dante Controller.
h) The file extension for the system configuration has been changed from *.xml to *.pava_sct to help
users to differentiate PAVA SCT XML configuration from the Dante Controller XML configuration.
Notes:
a) The firmware on Dante Brooklyn II module should be updated to V4.1.1.4.
b) Raw external Dante sources are allowed in routes to non-PRO units. If routed to non-PRO units,
no busy indication is provided but the outputs will be internally routed and low/equal priority routes
will not be routed to these outputs.
Only PRO units should be selected for raw external Dante sources.
c) The maximum number of Dante receive channels in a PAVA system is 32.
d) Import Dante Controller configuration is not supported.
e) Local loopback Dante channels are not time-aligned with network outputs (although difference in
delay is < 1ms, so hardly noticeable).
2) NA

2.16 V3.3.3.0-A
1) PAVA SCT:
It is now possible to enable (default)/disable the HCP communications monitoring (HCP COMMS
FAULT) via the Fault Report check box on the HCP configuration pane.
2) NA
2.17 V3.3.2.7-B
None.
2.18 V3.3.2.7-A
None.
2.19 V3.3.2.4-B
None.
2.20 V3.3.2.4-A
None.
2.21 V3.3.2.3-B
None.
2.22 V3.3.2.3-A
1) VIPA Stack (VIPA Host, iPAM400, etc.):
VIPA devices now set the IP settings and Unit ID of microphone using ASL Serial Protocol.
The IP Settings include the microphone IP address, netmask, gateway and control port.
This requires the correct MAC address in the microphone configuration.
2) NA
2.23 V3.3.2.0-C
None.
2.24 V3.3.2.0-B
None.

2.25 V3.3.2.0-A
1) MPS:
a) The MPS now supports the Disable LED button which, when it is active, turns the microphone
LEDs (except from the “power” LED) and the LCD backlight off.
Notes:
• The Disable LED is configurable on MPS type microphones.
• The LAMP TEST may turn the LEDs on when the Disable LED button is active.
• The LEDs are turned on power up, and may be turned on briefly when reconnecting the
comms.
b) The MPS-B firmware can be updated using the FTT Firmware Transfer Tool. The firmware update
is similar to VIPEDIA-12/V2000 firmware update.
2) Network Card:
a) The Network Card now sets the IP settings and Unit ID of microphone using ASL Serial Protocol
(if configured with correct MAC address). The IP Settings include netmask, gateway and control
port.
b) The Network Card now reports a fault when PMC streams are not being transmitted/received as
expected:
• VNET AUDIO FAULT 3:0 (PMCTransmitFault) is reported if the network card should be
transmitting audio but it’s not
• VNET AUDIO FAULT 4:0 (PMCReceiveFault) is reported if the network card should be
receiving audio but it’s not
FAULT CLEAR should clear the faults when the error condition is no longer active; i.e. if the
streams are now running normally or if they are no longer required.
c) The integrity validation of configuration and application files has been improved with new faults
being reported:
• VNET GENERAL FAULT 1:0 (Integrity.VerificationInactive): The verification process is not
running or stuck. This means that the integrity of configuration and application files is no
longer validated, so corruption faults will not be noticed.
• VNET GENERAL FAULT 2:0 (Integrity.VerificationOverrun): The periodic validation took
longer than the period between validations. The periodic validation runs every 30 minutes so if
it takes more than 30 minutes to complete there is a problem. This could result in corruption
faults not being reported within the 60-minute limit specified by EN 54-16.
• VNET GENERAL FAULT 3:0 (Integrity.FileSystemMonitorInactive): The file-system monitor is
not working and changes to files will not be detected. This does not affect the periodic
validation, but it could cause other errors like configuration mismatch.
• VNET GENERAL FAULT 4:0 (Integrity.ConfigDirMonitorInactive): The file-system monitor is
not monitoring changes to configuration files. Although this has a different cause from the
previous fault, it results in the same behaviour.
• VNET GENERAL FAULT 5:0 (Integrity.AppDirMonitorInactive): The file-system monitor is not
monitoring changes to application files. This is not presently used because applications are
never changed without a restart so it should never be raised.
3) VIPEDIA-12 (PAVA/SCT):
It is now possible to configure AS Redundant systems without RCB01.

2.26 V3.3.1.0-A
1) VIPEDIA-12:
a) DVA MISSING fault is now spontaneously reported if DVA is configured and not loaded.
Spontaneous DVA MISSING fault is not currently supported for Chimes and remote DVAs
configured on Selectable Route. If missing, DVA MISSING is still reported when chime or
Selectable Route remote DVA is activated.
b) Vipedia now automatically resets after DVA load is complete.
c) The Vipedia DSP has been updated to also support Macronix Flash part (U80) MX29GL512 (to
replace Spansion S29GL-S part in production).
2) VIPEDIA-12/V2000:
A new fault (FRMxxx AMPyy ROUTE FAIL) is now reported if a V2000 amplifier reports asleep or not
routed for a configured and active Vipedia route.
#11743: The ROUTE FAIL fault is intended to help diagnostic in cases where audio is routed but no
audio is routed to the speakers.
Note that when speaker lines are isolated due to line fault, ROUTE FAIL is only reported when both
lines are isolated.
3) Network Card:
a) The network card now verifies the integrity of all config files. These include:
• PAVA system config (SCT):
VNET STORAGE FAULT 3:18
NetCard<X>.Integrity.DeviceConfigCorrupt
• Device-specific config derived from the PAVA system config:
NetCard<X>.Integrity.SystemConfigCorrupt
• VIPA system config (VCT):
NetCard<X>.Integrity.CurrentConfigCorrupt
b) The oemtest now accepts .dva files in the --frags option. The format of a .dva file is:
• First line - A comma separated list of fragments.
• Second line - PID text. This line is ignored by oemtest.
• Third line - permissions.
• Fourth line - priority.
• Fifth line - Description. This line is ignored by oemtest.
Blank lines are ignored so if you want to specify the priority but not the permissions you may leave
the third line empty.
Multiple .dva files along with fragment files can be specified in a single command line. The list of
fragments queued for playback will be formed from all the fragments specified both in the --frag
option and in .dva files in the order they were specified. Note that duplicate fragments will not be
removed.
If the priority or permissions are specified in multiple .dva files, then the last specified value will be
used. The command-line parameters --permissions and --priority take precedence over values
from .dva files. If any .dva file specifies invalid values for those two options, the utility will abort.
4) PAVA SCT/FTT:
a) It is now possible to change the network interface without re-launching the FTT. The Local IP
Address on the FTT is now a drop-down menu with all available network interfaces. Users select
the appropriate network interface or the Auto option. With Auto option the FTT automatically
selects (if available) the correct network interface required for connection to the target device.
Note that all required the network interfaces should be configured before launching the FTT.
b) The new Cluster Overview on the PAVA SCT provides an overview of the IP addresses used by
the PAVA system (excluding those configured on the VCT). The report can be exported to an
HTML file.

Note that the overview currently does not show the multicast address/port used for listen-in on IP
microphones attached to a Vipedia unit or used by internal processes/other applications (normally
hard-coded multicast addresses/ports).
5) IP settings (address, netmask and gateway) and Vipedia Unit Id using the PAVA SCT/FTT:
It is now possible to set the IP settings of a VIPEDIA-12, Network Card or V2000 from the FTT via the
new Network Settings tab. The current IP settings can be verified and modified (manually or by
applying the setting in XML configuration).
It is also possible to set Vipedia unit ID from the FTT.
Notes:
• It is highly recommended that the Local IP Address on the FTT is set to Auto.
• The changes to the Network Card via the Network Settings tab are temporary and should be
finalized by loading the corresponding configuration file. It is best to use the Write configuration
with Network Card IP address override.
• The changes to Vipedia and V2000 units are permanent.
• Vipedia and V2000 units automatically reboot and clears the static configuration when changes
are applied.
• Users should be careful to select the correct unit when applying changes.
6) Network Card configuration exclusively via PAVA SCT/FTT: from version 3.3.1.56, you can no longer
load VIPA configuration using the VCT or vipet_setup:
a) By default, the PAVA SCT generates the minimum VIPA configuration required by the Network
Card (PAVA SCT > System Options > VIPA Configuration = Automatic).
b) If an external VIPA configuration is required (e.g. other VIPA devices, IP microphones attached to
a VIPA device, interface to iVENCS, interface to third-party applications, etc.) the VIPA Config
must be imported into the PAVA SCT configuration via the PAVA SCT > File > Import VIPA
Configuration (PAVA SCT > System Options > VIPA Configuration = Advanced - Imported from
<*.cfg> on <date when it was imported>).
• A copy of the external *.cfg config is included in the XML config.
• You must re-import the external VIPA Configuration if this is updated.
• If you try to update a Network Card and some common elements do not have matching
values, the update will be rejected, and you will be notified about the first element that did not
match and must be fixed.
The elements common to both system configurations are:
- The multicast router control IP address in SCT (multicast control address in VCT).
- The multicast router control port in SCT (multicast control port in VCT).
- The unit ID of the VIPEDIA-12.
- The IP address of the VIPEDIA-12.
- The hostname of the VIPEDIA-NET.
- The IP address of the VIPEDIA-NET.
- The netmask of the subnet.
- The gateway used.
c) The VIPA configuration (automatic or imported) can be exported via the PAVA SCT > File >
Export VIPA Configuration. The exported CFG configuration can be modified as required using
the VIPA Config Tool (VCT).
Recommended procedure when creating a new VIPA configuration:
• Create the system configuration using the PAVA SCT.
• Export the VIPA configuration (PAVA SCT > File > Export VIPA Configuration).
• Load the above VIPA configuration into the VIPA Config Tool (VCT).
• Configure all required VIPA services (e.g. Linutop, VIPA Server, IP microphones, etc.) using
the VCT.
• Save the VIPA configuration (*.cfg).
• On the PAVA SCT, import the updated VIPA configuration (PAVA SCT > File > Import VIPA
Configuration).
• Save the file and load the configuration into the devices.

d) You can still load the VIPA configuration into the Network Card using the Network Card Manager.
However, this is not recommended as the configuration may have conflicts with the config
imported into PAVA SCT.
e) It is highly recommended that the Local IP Address on the FTT is set to Auto.
f) The configuration load page (Write tab) now has an option to override the Network Card IP
address (if required).
g) Recommended procedure to set up Vipedia and Network Card (including AS Redundant Vipedia):
Note that it assumes the current IP address is known.
• Update the Vipedia firmware to V3.3.1.x release using the Update Manager with clear config
option enabled.
• Update the Network Card firmware to V3.3.1.x release using the Network Card Manager.
• Load the configuration into the PAVA SCT and import the VIPA configuration (if required).
• Configure the PC with required network interfaces.
• Launch the FTT.
• Select Local IP Address = Auto.
• Select the Network Settings tab.
• Enter the current Vipedia IP address and click Show Current Settings.
• Click Choose New Settings.
• Select Source = <target Vipedia>.
• Click OK. Vipedia will reboot.
• If Active Standby Redundant Vipedia, repeat the above steps for the second Vipedia unit.
• Select the Write tab.
• Wait for Vipedia(s) to start up.
• Click the padlock icon to unlock the device selection.
• Select the Vipedia (the first if Active Standby Redundant Vipedia).
• Override the network card’s IP address with its current IP address.
• Click Write Config.
• If Active Standby Redundant Vipedia, repeat the above steps for the second Vipedia unit.
h) The above procedure can be used to unconfigure redundant units.
7) V2000 Dynamic Tool:
The tool now displays two small LEDs that show the amplifier wake state, as well as whether the
amplifier is currently routing audio.
Note that the amplifier will always be awake (LED ON) by default as the tool automatically sets the
continuous surveillance tone. Therefore, it is not ideal to check the wake state during a fault condition.
8) Event Logger/Vipedia Fault Log:
The following events are now logged in the Event Logger and Vipedia Fault Log:
• User log in/out
• Contact input/output state change
• Static/dynamic config update
• DVA load start/erase/end
• DSP/FPGA firmware update
• Active/standby Vipedia changeover.
9) Network Card Manager Tool:
It is now possible to upload custom (and default) SIP audio files (WAV) into the Network Card via the
Functions>Upload SIP Audio Files menu option.
Note that the SIP audio files (WAV) ideally should have the following properties:
• Codec: PCM S16 LA
• Sample rate: 8 kHz
• Bits per sample: 8
• Bit rate: 64 kb/s

2.27 V3.3.0.2-A
1) Network Card:
a) The Location of the Network Card is now published in the JPC tree. Any device under the network
card in the JPC tree will also publish its Location if a) it is set and b) it is different from the Network
Card’s Location.
Currently, the location of the Network Card is provided by the PAVA SCT as:
• either (if set) the name of the rack (or Integra) node which contains the hosting router (Vipedia
or Integra)
• or (if above not set) the router's (amplifier frame’s) unique ID (e.g. VIP01, ITG01, etc) followed
by the router's (amplifier frame’s) name
For example, for a rack node with no name and:
• a Vipedia with ID 5 and name "System A", the resulting Location will be "VIP05 System A".
• an amplifier frame with ID 10 and name “System A - Frame”, the resulting Location will be
“FRM10 System A - Frame”
b) The Network Card now supports the installation and configuration of a separately licensed Text to
Speech (TTS) module.
Avoid installation of TTS on heavily-loaded network cards as the TTS module requires significant
CPU resources when converting text to speech.
The TTS module must be installed manually, refer ASL0582-ID4375 NET-VIPA: Text to Speech -
Tech Note for further information.
c) The Network Card now supports HTTP-hosted DVA.
Unlike other VIPA devices, HTTP-hosted DVAs are not available by default. A “Text to Speech”
module must be added to the network card in VCT for the service to be available. Note that this
will not enable the text-to-speech functionality unless you have acquired the appropriate license
and installed the TTS-D-NET-VIPA software package.
d) The quick-config utility (/dva/bin/quick-config) now enables the JPC tree which means that
vipedia-fault-d will now be started (it wasn’t before). This is because it is possible for customers to
configure the network card without using VCT but expect to see fault events in the Event Viewer.
This is not possible without the JPC tree.
2) NA
2.28 V3.3.0.1-D
1) MPS-A (MAC address C0:BA:E6:00:>=50:yy):
a) Firmware update via Ethernet requires new Ethernet Bootloader V2.0.3 due to new main board
bootloader V1.1.1.5.
• Ethernet Bootloader V2.0.3 is back compatible with old microphones (i.e. previous main board
bootloader versions).
• Ethernet Bootloader V2.0.3 requires a DLL file (cygwin1.dll).
• Old versions of Ethernet Bootloader will hang at 0%. The new microphones will reboot after ~
5 minutes. It will run the original firmware if the old Ethernet Bootloader is closed.
• You can check the version of the Ethernet Bootloader by running:
MB_ethernet_bootloader --version
• You can access the help text for the Ethernet Bootloader by running:
MB_ethernet_bootloader --help
b) Default IP settings on out-of-the box units:
• Unit IP Address/Port: 192.168.1.200 / 15554
• CTL IP Address/Port: 239.0.0.254 / 15556
• PMC Live Address/Port/Channel: 239.0.0.35 / 15001/1
• PMC BGM Address/Port: 239.0.1.35 / 15135
• Gateway Address/Prefix size: 0.0.0.0 / 1
• Unit Id: 70

2) MPS-A fitted with navigation board (MPS, EMS and WMC) (MAC address C0:BA:E6:00:>=50:yy):
a) The new navigation board firmware V3.1.0.0 transfers touch button information to the MPS.
• MPS V3.2.0.3 (or later) uses this information to diagnose and fix problems with sensitivity of
touch buttons.
• Navigation board V3.1.0.0 is compatible with previous versions of the MPS.
• MPS V3.2 (or later) is compatible with previous version of the navigation board (V1.2.2.).
b) The new main board bootloader V1.1.1.5 uses the bargraph blue LEDs to provide feedback when the
microphone is in bootloader mode (MPS and EMS only).
Bargraph LED Indication in Bootloader Mode on MPS/EMS

5 (top) 4Hz flashing when in bootloader USB mode.
Fast flashing when updating firmware via USB.
ON when in bootloader Ethernet mode.
4 ON: DIP switch 1 active and in bootloader mode.
1Hz flashing when updating firmware via Ethernet.
3 ON: No application detected (empty device) or the first 8 bytes of application space
are either empty or invalid.
2 ON: Corrupt application present. The application is either partially programmed or
corrupt.
1 (bottom) Always off when in bootloader mode
Notes:
a) Only the power (green) and system fault (yellow) LEDs are now turned on when the unit is in
bootloader mode.
In previous versions of the main board bootloader, all top LEDs were turned on in bootloader mode,
incorrectly indicating voice alarm active.
b) In normal operation:
i) The bargraph LEDs indicate the speech level as before.
ii) Bargraph LED 5 (top) is briefly turned on during boot, indicating bootloader is active prior to
transferring control to application. LED 5 is off in previous versions of the main board bootloader.
2.29 V3.3.0.1-B
1) V2000:
The V2000 has been updated to support 110VAC PSU operation (requires PSU update to 7.12.0.0 or
later).
This involves changes to display only. There is no direct operational impact from this change.
This change does not affect compatibility with 230 V AC PSU.
Note that V2000 110V (AVA10009-S1) is available for demo purposes only.
2) NA
2.30 V3.3.0.1-C
1) Network Card / PAVA SCT:
V2000 units are no longer required in the VCT configuration since V3.3.0.1 Package A.
The Network Card auto-generates the list of V2000 units from the PAVA SCT configuration. The
Network Card does not reject VCT configurations with V2000 units. However, the Network Card only
reports faults for V2000 units that are present in the PAVA SCT configuration.
2) NA

2.31 V3.3.0.1-A
1) V2000:
New Monitor command: “get-wake x” prints the AWAKE/ASLEEP state of each amplifier in the frame.
Example:
V2000-01>get-wake 3
Amp: 1 - AWAKE
Amp: 2 - AWAKE
Amp: 3 - AWAKE
Amp: 4 - SLEEPING
Amp: 5 - SLEEPING
Amp: 6 - SLEEPING
Amp: 7 - SLEEPING
Amp: 8 - SLEEPING
Amp: 9 - SLEEPING
Amp: 10 – SLEEPING
If an amplifier number is provided (x), the trace starts printing the current status of each wake/sleep
trigger for the amplifier:
[SRV] Amp 3: SLEEPING - Announcement: 0, GUI: 0, LF-Tone: 0, HF-Tone: 0, DC-Offset: 0
If no amplifier number is included with the monitor request, it will cancel any outstanding trace print.
2) NA
2.32 V3.3.0.0-A
1) Vipedia: front panel audio monitoring of TDM channels via Test>Monitor>Audio>Inputs>PMC
• I/P 01-07 => Master Vipedia VIPA outputs, i.e. VIPA sources into Vipedia via Network Card
• I/P 08 => loopback for VIPA TDM channel monitoring
• I/P 09 => loopback for Vipedia TDM channel monitoring
• I/P 10 => reserved
• I/P 11-16 => Master Vipedia Vipedia outputs, i.e. remote Vipedia sources (including IP mics) into
Vipedia via Network Card
• I/P 17-24 => DBB Slave Vipedia VIPA outputs (when DBB unit not fitted with Network Card)
• I/P 25 => loopback for Vipedia TDM channel monitoring
• I/P 26 => reserved
• I/P 27-32 => DBB Slave Vipedia Vipedia outputs (when DBB unit not fitted with Network Card)
2) Network Card:
a) The audio channels between the network card and the VIPEDIA-12 are now monitored for errors.
If an error is found the network card will attempt to correct it and if it fails, it will raise a fault.
There are two groups of channels, one ‘owned’ by the VIPEDIA-12 and one ‘owned’ by the
network card. If the former fails, the fault raised will identify as VA audio (VNET AUDIO FAULT
1:0) while the latter will identify as PA audio (VNET AUDIO FAULT 2:0).
b) PMC audio routing is now supported for Unit IDs 1 to 63.
Note the maximum number of Vipedia units in a system/cluster is still 32.
2.33 V3.2.0.4-A
1) V2000 – MAC address:
It is now possible to set the MAC address from the serial monitor.
Command syntax:
set mac-address <PIN> c0.ba.e6.xx.xx.xx
All characters are required.
2) NA

2.34 V3.2.0.3-A
The PSU version number of the connected V2000 is now displayed in the status bar, alongside the
other V2000 firmware information.
2) NA

3 Changes and Improvements
3.1 V4.2.0.8L-A
3.1.1 Vipedia Logging of NTP Synchronisation Status Changes (VIPEDIA-12 V4.2.0.8L)
The logging of NTP synchronisation status changes has been optimised and the relevant fault codes have
been decoded to text:
1) NTP synchronisation faults that are handled as events rather than faults are now logged by name
rather than code.
Local NTP synchronisation events will be logged directly as:
• VNET NTP NO SYNC (was VNET OS FAULT 3:5)
• VNET NTP NO SERVERS (was VNET OS FAULT 3:4)
• VNET NTP DAEMON OFFLINE (was VNET OS FAULT 3:3)
• VNET NTP BAD SYNC (was VNET OS FAULT 3:6)
• VNET TIME SET FAILED (was VNET OS FAULT 3:13)
• VNET NTP NO STATUS (was VNET OS FAULT 3:14)
Other NTP synchronisation faults will be reported and logged as VNET OS FAULT 3:x as before.
2) Local NTP synchronisation faults are logged by all VIPEDIAs as before.
3) Local NTP waiting status (nominally NTP WAITING LOCAL) is no longer written to the fault log.
4) Local NTP recovery status (nominally NTP LOCAL TS OK) will be logged by all VIPEDIAs. This event
will also be sent for the Event Logger.
5) System NTP waiting/recovery status (nominally NTP WAITING SYSTEM TS and NTP SYSTEM TS
OK) will be logged only by the Primary Time Master. These events will also be sent for the Event
Logger.
6) The front panel NTP status displays (“:”, “ ”, “!LCL TS” and “!SYS TS”) are as before; see details in
“7.9 NTP Status Indication on Vipedia Front Panel (V4.2 and newer)”.
3.1.2 Network Card VNET AUDIO FAULT 1:0 / 2:0 / 4:0 (NET-VIPA V4.2.0.82L)
The audio processing between the Network Card and Vipedia and the error detection have been improved
to prevent VNET AUDIO FAULT 1:0 / 2:0 / 4:0 caused by small spikes in the CPU load.
3.1.3 Network Card NTP Bad Synchronisation Fault Threshold (NET-VIPA V4.2.0.82L)
The threshold for ASLPAVA.abc.Applications.TimeSync.NTP.BadSync error has been increased.

It is now reported if the difference between the local clock and the NTP server’s clock (the ‘offset’) is more
than 100 ms instead of the previous value of 20 ms.
Note that that transient NTP synchronisation faults do not drive the fault LEDs on Vipedia and MPS units.
They are logged in the Vipedia fault log and drive the NTP status indication on the front panel; see
“7.9 NTP Status Indication on Vipedia Front Panel (V4.2 and newer)”.
3.1.4 Network Card oemtest Monitor Commands (NET-VIPA V4.2.0.82L)
1) The oemtest monitor command (--subcommand=mon) now exits as soon as it displays the response
from a monitor interface. In previous releases, it waits for about 10 seconds before exiting.
2) The monitor command ‘show-data’ now displays all TDM channels available to the VIPEDIA-12 (9 to
15). In previous releases, it displays TDM channels 9 to 14.

3.1.5 VIPA BGM Permanent Routes Removal (NET-VIPA V4.2.0.82L)
It is now possible to remove all VIPA permanent routes during a configuration update, by selecting the
appropriate option in the PAVA SCT.
Note that the PAVA SCT V4.2.0.6P (or older) does not support this option.
3.1.6 V2000 Select LED Indication for Sleeping Amplifier Identification (V2000 V4.2.0.7L / LSZDC
DSP V5.0.2.5P)
The new amplifier SELECT LED function is enabled at regular intervals (typically 4 s) (controlled by the
Frame Controller) to allow identification of amplifiers that may be left awake when no audio routed.
When enabled the SELECT LED behaviour will be as follows:
a) If amplifier is sleeping, it will flash once for 350 ms followed by off for at least 1350 ms.
b) If amplifier is awake and has audio routed, it will normally be on, but will flash off for 350 ms at the 4 s
poll of the Frame Controller.
c) If amplifier is awake but no audio routed, it will flash four times (350 ms on 350 ms off) following the
4 s poll by the Frame Controller. This is expected during the surveillance tone every 85 seconds.
Otherwise, it indicates that the amplifier is awake when it shouldn’t.
Notes:
• The SELECT LED flashing rate for standby amplifier switch over and audio monitoring is now slower
than in previous releases.
• The SELECT LED of the standby amplifier will normally be on if in use and audio routed.
3.1.7 V2000 PSU Fan Control Improvements
The PSU fan control has been improved for better thermal performance. The change ensures that if
temperature difference between main power heatsink and 5V heatsink exceeds threshold that the fan is
engaged. The fan will be engaged until the difference is below a lower threshold or for a fixed period of
time.
Also, the fan will be enabled if the mains input current exceeds fixed threshold.
3.1.8 Vipedia Host / V2000 Frame Bootloader V4.0.0/V5.0.0
Vipedia Host /V2000 Frame Bootloader V4.0.0 (plain text):

• Plain text Bootloader V4.0.0 can replace the original V1.4.1. It can be used with any pre-existing
application. It is more robust and recommended where security is not required. It allows easy recovery
when the application update fails (typically with TFTP ERROR).
Vipedia Host /V2000 Frame Secure Bootloader V5.0.0 (secure):
• Secure Bootloader V4.2 and V4.3 is now deprecated.
• Secure Bootloader V5.0.0 replaces the pre-existing secure Bootloader V4.2/V4.3.
• Secure Bootloader is required for VIPEDIA-12/V2000 V5.0 (or later) or VIPEDIA-12/V2000 that may
be updated to V5.0 with security enabled, and Secure Bootloader V5.0.0 is the recommended version.
• Secure Bootloader is fully compatible with all current latest LTS releases for 2.1, 3.3 as well as 4.2
and future releases.
• Units with Secure Bootloader only execute Signed versions of the application (filenames starting with
“S” rather than “F”). Non-signed versions may still be downloaded but will not run. There is a risk that
you may not be able to return a unit to operational mode unless you have a signed version of the
application. Do not proceed with the download unless you are sure of this.
• Contact ASL if a Signed version of the application is not available for download.
The Bootloader version is displayed on:

- On Vipedia front panel: Configuration > Router > Identity > S/Ware > [Bootloader: V4.0.0P]
- On FTT (File Transfer Tool) > Write
- On FTT (File Transfer Tool) > Network Settings
- On Vipedia front panel in Bootloader Mode
- On serial monitor: “get ver” monitor command
- On ADT (Amplifier Configuration Tool)
Summary of features in the Bootloader:
8) Allows easy recovery method for update tools when stuck in bootloader mode.
9) Bootloader automatically reboots after inactivity timeout.
The inactivity timeout is programmable: 60 s to 3600 S (default is 90 s).
Warning:
10) New status and messages display for VIPEDIA-12; see summary below.
11) Serial Number programming:
If programmed, the Serial Number is displayed on VIPEDIA-12 V4.2 (or later) via front panel menu
option Configuration > Router > Identity > S/Ware > [S/N: xxxxxxxxxxxxx].
V2000 serial number is not currently displayed on any tool.
Warning:
12) Fault sounder can be suppressed using Fault Accept key.
13) Status messages to applications (e.g. FTT and Update Manager).
14) Telnet is no longer supported.
VIPEDIA-12 LCD display in bootloader mode:

• First char animation "-+|+"
• First char animation "-+*+" buzzer suppressed.
• First char animation "x!" bootloader self-signature check failed.
• Second char ':' serial port active.
• '9!' to '0!' inactivity timeout pending.
Messages:
• " Good Application Present "
• " Downloading 100% from 192.168.1.123 "
• " *** TFTP error to 192.168.1.123 *** "
• " *** No Application Present *** "
• " *** Application Bad Checksum *** "
• " *** Application Bad Signature *** "
• " *** Corrupt Bootloader *** "
• "Rebooting (console reset command)"
• "Rebooting (due to inactivity)"
• "Rebooting (keyboard request)"

• "Rebooting (set network info)"

• "Rebooting (update host image)"
3.1.9 Update Manager V2.0.0.0P
The Update Manager supports VIPEDIA-12 systems V2.1 onwards with the following improvements.
3.1.9.1 Multi-cluster V5 / V4 / V3 / V2.1 Systems
The Update Manager now support multi-cluster PAVA configuration file (schema v8.00.00) created by
PAVA SCT V5.0 (or newer).
It also supports loading of multiple PAVA configuration files as long as they are in the same folder. This is
only meant for loading multiple PAVA clusters of the same system that have been created with PAVA SCT
prior to V5.
3.1.9.2 Updating V5 / V4 / V3 / V2.1 Devices via Gateway
The Update Manager can now update devices via gateway.

Note that the PC running the Update Manager must have been configured correctly for connections via
gateway.
3.1.9.3 Clearing Configuration on V5 / V4 / V3 / V2.1 Devices
Clearing the configuration is no longer an on/off checkbox but a drop-down menu with 3 possible options:
• Auto: This is the recommended value, and it allows the Update Manager to decide for each device if
the config should be cleared or not. Basically, the Update Manager will clear the configuration unless it
is certain that the new image is compatible with the existing configuration.
• Always: The Update Manager will clear the existing configuration on all devices.
• Never: The Update Manager will leave the existing configuration on all devices.

3.1.9.4 More Information on the Update of V5 / V4 / V3 / V2.1 Devices
A new “State” column now show additional details of the update process (see example above).
Note that some of details will only be displayed if Vipedia / V2000 bootloader is V4.0.0 / V5.0.0 (or newer).

3.1.9.5 Security Support on V5 Devices
The Update Manager now supports V5 devices with security enabled. The security status of each device
is shown in the UI as “Security” with the following values (see example above):
• *blank*: The Update Manager has not received enough message from the device to determine if it
supports security or not.
• not supported: The device does not support security.
• not enrolled: The device supports security but has not been enrolled in a security group yet.
• none: The device has been enrolled in a security group but security has not been enabled.
• 1 (auth): The device authenticates control messages and audio streams.
• 2 (enc/auth): The device authenticates and encrypts control messages but only authenticates audio
streams. This is the currently supported protection level when the device is protected (i.e. security is
set to ON).
• 3 (enc): The device authenticates and encrypts both control messages and audio streams.
• invalid: The device reported a security mode which is not currently recognised. This is most likely an
error with the device, but it could be a newer version with more security modes.
• time error: The device has a date/time too different from the PC so updated will be prevented.

If any device selected for update has security enabled, the Update Manager will request the site
“Password” and the “Two-factor code”; see example above. It will keep requesting them until either the
correct site password and two-factor code have been entered or the device is no longer selected for
update.
Notes:
a) An update/config session may have been activated by a FTT or another instance of the Update
Manager. In which case, the “Two-factor code” is not requested.
b) Normally you only have to enter the security details for one of the selected devices if they share the
security credentials.
Warnings:
b) The Update Manager cannot update devices with date/time that is too different from the update PC’s
date/time. You will have to fix the device’s date/time using FTT first.
c) The Update Manager starts a 15-minute update/config session, whereas the FTT starts a 60-minute
config session.
d) If the update/config session times out for a selected device, the Security Details dialog will
automatically pop up and it may be behind other application window. If the Security Details dialog is
behind other application window, the Update Manager will appear to be locked up. Use ALT + tab to
bring the Security Details dialog to the front to close the dialog and ‘unlock’ the Update Manager.

3.1.9.6 Error Indication on V5 Devices
The Update Manager now flags V5 device issues in the device list. An error mark will appear (red
exclamation mark) at the beginning of the row, next to the update checkbox. The error has a tooltip with
details of the issue; see example above. Some of the possible issues are:
• FPGA image missing (VIPEDIA-12 only).
• DSP image missing (VIPEDIA-12 only).
• Reported device type does not match the configuration. For example, the configuration has an IP
address as a VNET but the device reports as a VIPEDIA-12.
• Reported MAC address is not an ASL MAC address.
• Reported MAC address does not match the device type.
• Missing application. Reported by a bootloader without an application so the device cannot boot.
• Corrupted application. Reported by a bootloader with an application that failed the checksum so the
device cannot boot.
Some of the errors, like missing DSP, will prevent the correct operation of the device while others, like
corrupted application, will prevent it from even booting. Almost all issues should be fixable from the
Update Manager but there may be some that are due to configuration errors, some require the FTT or a
serial connection.

3.1.10 Network Card Manager V1.2.0.12P
1) The output of commands executed via SSH is now shown immediately and not after the command
has exited.
2) Updates are no longer started if it detects that there may be not enough available memory (RAMDISK)
on the target device.
3) Crashes of commands run on the target are now detected and the attempted action is aborted.
4) It supports V5 multi-cluster configuration.
5) The “Site Password” is only required for V5 Network Cards with security commissioned irrespective of
its on/off state.
3.2 V4.2.0.6P-C
3.2.1 LSZDC resumes operation after watchdog reset (V2000 V4.2.0.6P)
In previous releases of the LSZDC, if the LSZDC does not respond to 3 requests, it is assumed that it has
likely either died or been reset, and, if available, the standby amplifier will be switched. This may lock the
standby amplifier where the LSZDC can recover after a reset.
The LSZDC now enters diagnostic mode and attempts to re-enumerate and reconfigure the device. If
unsuccessful or if the device fails again within preset time (60 minutes), the standby amplifier will be
switched in or the device will be ignored until fault clear.
Known Issue:
Spurious line and amplifier faults may be reported after a fault clear where unrecoverable SRV CARD fault
is present. This may also happen on power up if faulty SRV CARD fault is present. Clear fault again if
unexpected faults.
3.2.2 Improvement to PSU fan operation (V2000 V4.2.0.6P)
If the PSU heatsink (HS) temperature is higher than the 5 V regulator temperature by pre-set amount
(~10°C), then the PSU fan is turned on.
In previous releases of the V2000 frame controller, there is no hysteresis on this setting and the fan can
be briefly triggered on and off in a short period.
The V2000 frame controller now applies a hysteresis to the setting: the PSU fan is turned on if HS to 5V
regulator difference exceeds the threshold (~10°C) and is turned off when the difference is reduced
(~2°C). The PSU fan will be turned on for minimum 1 minute.
The serial monitor output of V2000 V4.2.0.6P shows when the PSU fan is turned on / off due to the
differential temperature. Example:
[PSC] Fan ON delta 8

[PSC] Fan OFF delta 2
3.2.3 Improvements to V2000/INTEGRA PSU reliability (PSU V7.29.0.0P)
3.2.3.1 PSU fan turned on when battery charging current is high
The temperature sensing for the charger supply is done on the secondary side but the rectifier remains
cool in the process. The switcher IC however heats up. Since this IC is on the primary side, the PSU does
not directly sense its temperature, so the PSU fan is not turned on. If the supply is concurrently feeding
current from the DC output on the back, the switcher IC will become quite hot. To cool down the switcher
IC, now the PSU fan is turned on when the supply is charging at at 500 mA or more for 30 seconds.

3.2.3.2 Inrush relay de-activation
When activating the voltage doubler relay, it is good practice to first open the inrush current relay to avoid
high current through its contacts. In previous releases of the PSU, the inrush relay is not deactivated when
the voltage doubler is activated. This could cause the capacitor(s) in the primary circuit to blow up.
The inrush relay is now deactivated when the voltage doubler is activated.
3.2.4 Improvement to serial monitor temperature testing (V2000 V4.2.0.6P)
Changes have been made to the serial monitor “test-temp” command to improve the temperature testing
function and feedback. No functional changes.
The “test-temp” monitor command now also decrease the temperature alarm timeout by a factor of 10 to
allow for easier testing. The timeout is defined by the warning start/stop settings in the XML static config.
Command: temp-test <ID> <TEMP>
• where ID is 0 for PSU or non-zero for appropriate amplifier slot.
• the test can be cleared by running "temp-test" without parameters.
Warning: Care should be taken to ensure that the settings are not left on!
Example:
V2000-065>temp-test 0 80
temperature inject test: set-point =0 temperature=80
V2000-065>[TMP] PSU - FAN ON: Tpsu=80 (70)
[TMP] PSU - WARNING_1: Tpsu=80 (80) Texp=600 (3600)
[TMP] PSU - WARNING_2 Tpsu=80 Texp=600 (3600)
[TMP] PSU - FAULT Tpsu=80
temp-test
temperature inject test: All points cleared
V2000-065>[TMP] PSU - FAN ON (Was FAULT)
[TMP] PSU - OK (Was FAN-ON) Tpsu=40 (65) Texp=600 (30000)
3.2.5 Spurious faults due to clock changes (V2000 V4.2.0.6P and LSZDC V4.2.0.8P)
This is a workaround for a problem with D-series amplifier clock changes.

When the clock is changed, there can be a large common-mode voltage generated on the output of the
amplifier. This can cause a number of side effects, including LSZDC resets, amplifier failures and
surveillance faults.
The clock change can happen when audio changes level or when the force-250k state is changed.
The force-250k is needed when HF (20 kHz) surveillance tone is active to prevent audible artefacts.
Ideally, the clock change is only done when the amplifier is asleep as this avoids the common-mode
voltage glitches.
The fix for the non-surveillance faults is to leave the force-250k enabled, but this causes excess battery
drain so option is to do only on mains, but this may cause higher than normal power dissipation.
It is now possible the force-250k is always active on mains supply by a configuration option as additional
power dissipation is too high to have as a default setting. However, note that the option is not currently
supported on the PAVA SCT. The default operation is as follows:
1) The force-250k is enabled before the start of the surveillance cycle when no route is active (amplifier
is asleep) and HF surveillance tone is required (e.g. impedance and IEL01). This prevents
surveillance faults due to common-mode voltage glitches. In previous releases, the force-250k is
enabled after the amplifier is awake.

2) The force-250k is enabled before the start of the surveillance cycle when route is active irrespective of
the need for HF (20 kHz) surveillance tone as the activation of the force-250k line prevents additional
clock changes from occurring due to audio level changes. In previous releases, the force-250k is only
enabled when HF surveillance tone is required (e.g. impedance and IEL01).
Must use V2000 Frame Controller V4.2.0.6P (or newer) and LSZDC V4.2.0.8P (or newer).
3.2.6 INTEGRA - Fan Digital Output (PAVA SCT V4.2.06P)
The description field for digital outputs configured as Fan now refers to Fan 1 and Fan 2 to highlight there
are two distinct fans on the back box.
Note that this will only apply to newly created INTEGRA, existing INTEGRA will keep the old description.
OLD
NEW
3.3 V4.2.0.6P-B
3.3.1 Input Gate is now configurable on DANS Input (RDT V4.2.0.5P) (SysAid #22375)
The Input Properties page now enables the Gate controls irrespective of DANS configuration (previously
the Gate was hidden when DANS was enabled on the unit).
This is to allow VOX routing in systems with DANS.
3.3.2 Local and remote input names and external Dante device info (PAVA SCT V4.2.0.5P / NET-
VIPA V4.2.0.78P or later)
The source names given to VIPA for inputs of PAVA-created routes are now the names assigned by SCT.
For clarification, these are the names shown by oemtest when subscribing to zones with v3 messages
next to “SN:” and by the Event Viewer.
The source-name section in /dva/config/vipediad.xml is no longer necessary but if present it will override
the names from SCT.
Known Issues:
a) Event Viewer shows Unit ID = Device Name (in PAVA SCT tree) for External Dante source
b) Event Viewer does not show the source id in Origin for External Dante source
c) Event Viewer shows origin of External Dante source as the Vipedia that owns the trigger if the
trigger is on a non-PRO unit

d) Event Viewer shows mic host Vipedia as audio source for selectable routes of remote audio
source (proxy route)
e) Event Viewer shows UNKNOWNyy in route events for external PMC streams
f) Input Names (SN) for analogue inputs 1 to 6 not per PAVA SCT configuration (manual
configuration is required, refer to ASL)
g) Event Viewer shows Origin = Vipxx:SRCyy instead of Vipxx:IPyy <Name> for Miscellaneous
Input/Processed Input routed over Dante
h) Analogue Inputs (0x03xxyyyy) may be ‘converted’ into Processed Dante Input (0x0Exxyyyy) in
device-config.xml
i) Event Viewer and VIPA source name (SN) may be confusing for Vipedia IP microphones
j) Event Viewer - **Origin** doesn’t show WMC input name for IP WMC music source
3.4 V4.2.0.6P-A
3.4.1 Jabber memory monitoring (NET-VIPA V4.2.0.81P)
A workaround has been implemented for a known memory problem due to unreachable VIPA devices.
Basically, when too many VIPA devices are offline, or do not yet exist, the memory used by jabber keeps
increasing. This is not necessarily a bug, but a direct result of the way jabber operates and its assumption
that there'll always be enough memory available.
The workaround is to restart jabber when memory is very low and jabber is using too much of it. Note that
this may affect active announcements involving the machine whose jabber gets restarted but it's
impossible to predict in what way. The announcements may not be disturbed, they may play OK but errors
are reported, they may terminate early or they may not start at all.
The VCT Status Tree now shows details of

memory usage and number of jabber restarts due
to jabber memory leakage.
3.4.2 VIPA daemons and applications using jabber / OEM gateway (NET-VIPA V4.2.0.81P)
All VIPA daemons (and applications that use jabber) will now reconnect to jabber if the connection is lost
for any reason. Additionally, all daemons now support the heartbeat functionality so they should not lose
connection when enabled in jabber.
Please note that the OEM gateway has had significant changes to support reconnection of its clients so
now it will:

• refuse to authenticate with jabber on behalf of clients with a user/resource already in use by
another client. This is because it would cause all clients with the same user/resource to
continuously disconnect & reconnect.
• respond with the following new error messages when it cannot forward the client's message to
jabber:
!400 BADREQUEST user/resource already connected.

!401 DENIED Must authenticate first.
!503 UNAVAILABLE Not currently connected to jabber.
Due to the impact of these changes the OEM gateway now identifies as version 1.2.0.
3.4.3 Unsupported daemons removed (NET-VIPA V4.2.0.81P)

The install script now removes unsupported platform daemons and their related files to minimise the
debris left behind by newer versions when downgrading.
3.4.4 Network Card configuration installation (NET-VIPA V4.2.0.81P)
The configuration files written by FTT to Network Cards now always get installed, even if they already
exist with the correct data. Please note that this will take the network card out of action for about a minute,
more if it is heavily loaded.
3.4.5 Network Card boot script (NET-VIPA V4.2.0.81P)
The boot script has been updated with all the latest firmware changes.
If the Network Card is using the latest version of the etc file-system image the script will remain the same
and if the Network Card is using an older version the script will be updated to the newer one.
3.4.6 Source names in zone status messages (NET-VIPA V4.2.0.81P) (SysAid #21502)
The source names used in output status messages generated by vipedia-d, has been reverted to blank for
all VIPA routes. This solves an issue created by NET-VIPA 4.2.0.78P whereby announce-d sometimes
reports the source name assigned by vipedia-d before reporting the correct name causing issues with
third-party applications.

None.
3.6 V4.2.0.5P-C
None.
3.7 V4.2.0.5P-B
3.7.1 VIPA Listen-in Cancel (VIPA Stack V4.2.0d and NET-VIPA V4.2.0.79P)
The operation of Client-directed Listen-in (see “Use Client Listen-In for Microphones” in VCT) has been
changed. A client that requests Client-directed Listen-In (specifying the target address of the audio
stream) must use the new annDisableClientListenIn API.
This change is required to prevent Client-directed listen-in being cancelled when Server-directed listen-in
to same zones is cancelled (and vice-versa).
Warning:
All Network Cards of VIPEDIA-12/INTEGRA routers must be updated to V4.2.0.79P or later and all
VIPA devices must be updated to VIPA Stack V4.2.0d or later. Failure to do so may result in issues
with Listen-in functionality.

Note that the latest release of the VIPA Stack (V4.2.0e) is part of this release package to meet
requirements of various projects.
3.7.2 XMPP Heartbeats Enabled by Default (VIPA Stack V4.2.0e)
In order to support VIPA_HOST redundancy, XMPP heartbeats are now enabled by default. This may
impact any non-standard modules used on VIPA devices using this firmware version (or a later version).
If your non-standard module experiences unexpected DISCONNECTED errors, especially after
approximately 20 seconds of operation, please check that you are invoking setNoopTimer()
correction on your JCOPConnection object after sign-on.
All standard VIPA modules have already been (or have been in this release) updated with heartbeat
support.
3.7.3 Volume Adjustment Updates to Clients (NET-VIPA V4.2.0.79P)
Network traffic to clients is now reduced when the volume for Volume Adjustable Routes is being modified
on a live system.
3.8 V4.2.0.5P-A
3.8.1 PMC TTL (VIPEDIA-12 V4.2.0.5P, V2000 V4.2.0.3P and Network Card V4.2.0.78P)
The TTL for multicast packets is now 20 on VIPEDIA-12 (was 64), V2000 (was 64) and Network Card
(was 9).
Note that the PMC TTL is configurable (1 to 30) on MPS microphones and wall-mount controllers on MPS
V4.3.0.0 (or later).
Known issue:
TTL for SIP live announcement is 1.
3.8.2 Network Card V4.2.0.78P - Vipedia Source Names
The source names given to VIPA for inputs of PAVA-created routes are now the names assigned by SCT.
For clarification, these are the names shown by oemtest when subscribing to zones with v3 messages
next to “SN:”.
The source-name section in /dva/config/vipediad.xml is no longer necessary but if present it will override
the names from SCT.
3.9 V4.2.0.4P-A
3.9.1 MPS/Network Card/VIPA Stack - Multiple Listen-in Buttons on a VIPA microphone using
ASL Serial protocol
The MPS, Network Card and VIPA devices (VIPA Server, VIPA Host, etc.) now support multiple listen-in
buttons on a VIPA microphone using ASL Serial protocol.
Requires MPS V4.3.0.1 (or later) and NET-VIPA V4.2.0.75 (or later) or VIPA Stack V4.2.0b (or later)
Listen-in operation and limitations:
1) On an MPS, the listen-in zone buttons are now exclusive in operation: selecting one will deselect any
other listen-in button active on that microphone.
A brief artefact at the start of the listen-in may be noticed when a listen-in button is selected when
another listen-in button is active on the same microphone.
2) It is necessary for operators to co-ordinate such that they do not attempt to listen-in from more than
one MPS at a time.

Configuration (VCT):
1) A single multicast address and port to be allocated and used for the listen-in group on each VIPEDIA-
12 Network Card, and a Mixer to be configured for that listen-in group.
Single listen-in
multicast address
Audio Group s = “listenin”
Output Type = “PMC”

Output Group = “listenin”
Priority = as required
(VIPEDIA-12) Mixer ID = “1” or “2”

2) That multicast address and port to be specified as the listen-in target for the VIPA-hosted MPS
microphones using ASL Serial protocol.
Single listen-in multicast

address (Channel = 1)

3) Each listen-in zone button to select zones on a single VIPEDIA-12 Network Card. Zones associated
with more than one Network Card should not be selected.
Zones on a single
VIPEDIA-12 Network
Card only
3.9.2 MPS - Chime in iVENCS/VAVE/SMS Mode
The MPS in IP mode with local chime enabled will no longer generate its own chime when it is hosted by
iVENCS, VAVE or SMS. This is to avoid double chime where the MPS is hosted by iVENCS, VAVE or
SMS with fallback to a Vipedia or a VIPA device and chime is required in Vipedia or VIPA mode.
3.9.3 MPS - Audio Ungated (#20096)
AUDIO UNGATED (microphone audio permanently routed to microphone audio output) can now be set on
microphones using ASL Serial protocol.
AUDIO UNGATE is set from the MPS display and will not be reset by the host (Vipedia or a VIPA device).

3.9.4 Vipedia Volume Adjustable Routes - Default Attenuation

Vipedia now supports a configurable power on default attenuation for adjustable volume levels.
This is to prevent routes with adjustable volume (e.g., background music) to start up at full volume after
power up.
The power on default attenuation is configured in the PA/VA Cluster Options of the PAVA SCT:
• Default: 0 dB (for backwards compatibility)
• Range: 0 to 90 dB
3.9.5 Vipedia Zone Faults for Offline V2000 Frames
Vipedia now reports zone faults (yellow LED of zone select buttons) when a V2000 frame goes offline.
Notes:
1) Only works after frames being lost after having been online.
2) Only reports zone faults for two frames where a Vipedia output is connected to more than two
frames.
3.9.6 WM01 - Level Adjustment Updates
The level bar on WMC01 now displays updates to volume level when operating with multiple volume
control devices (e.g. WMC01, VAVE, microphone volume buttons, VC volume control, etc.).
3.9.7 VA Global Status
The VA Global Status service no longer exchanges cluster fault data with other instances. Instead, each
service directly monitors one or more PAVA clusters.
Network cards no longer need to run the service unless they’re hosting microphones whose LEDs must be
driven according to voice-alarm rules, e.g. same as if hosted by a VIPEDIA-12. When the service is
enabled, it will only monitor the network card’s PAVA cluster by default. If additional PAVA clusters must
be monitored, a network card from each of those clusters must be selected in VCT’s “Hosts Monitored for
Global VA Status” option. Note that those network cards do not need the service and that selecting other
VIPA devices has no effect.

If no hosts in “Hosts Monitored for Global VA Status” are selected but the field “Host Whitelist for
Announcements” in VCT contains network cards, their clusters will also be monitored for faults. Again,
other VIPA devices in this field have no effect.
When the service runs on other VIPA devices, it will directly monitor all PAVA clusters defined in the
config. Neither “Hosts Monitored for Global VA Status” nor “Host Whitelist for Announcements” options
affect this.
This change will reduce the CPU load on network cards that have the service enabled but do not host
microphones because the service can now be disabled. However, network cards hosting microphones in a
multi-cluster system will end up with higher CPU load than before if they are configured to monitor multiple
clusters.
To ensure network cards do not get overloaded by this service, it is strongly recommended that it is not
enabled on network cards that must monitor more than 10 devices in total, irrespective of the number of
clusters. It is better to host the microphones and enable the service on a more powerful VIPA device,
preferably a full-blown PC like an iVENCS workstation.
WARNING: If your system has VIPA devices configured with VA Global Status then you must upgrade
them to 4.2.0a or newer before upgrading the network cards. If you do not, microphones hosted on those
VIPA devices will not show any PAVA faults.
3.10 V4.2.0.2P-B
1) PAVA SCT:
a) It is now possible to configure a microphone as dual interface without specifying the other input it
is shared with, i.e. both inputs are not linked.
This is to allow two instances of a dual host microphone to be configured independently, for
example when using Selectable Route buttons.
In previous V3.x and V4.x releases, the MISC SETTINGS>DUAL I/F MODE on the MPS is only
enabled if the inputs are linked (by adding the second input via Audio Input>Add>Ins>Dual
Interface Mic option).
b) The PAVA SCT XML configuration file now contains a full copy of the equivalent VIPA CFG
configuration file, when VIPA mode is set to Auto.
The SCT XML schema has been updated to v7.06.00
This change allows better interoperability with other ASL tools and has no impact to end users.
2) NA
3.11 V4.2.0.2P-A
See “4 Bug Fixes” (page 79).
3.12 V4.2.0.0P-A
See “2 New Features” (page 13) and “4 Bug Fixes” (page 79).
3.13 V4.1.0.0-A
See “2 New Features” (page 13) and “4 Bug Fixes” (page 79).

3.14 V4.0.0.1-A
1) VIPEDIA-12:
Pre-filtering of messages has been increased to reduce processor and buffer usage, and
consequently, improve routing times.
2) NA
3.15 V4.0.0.0-A
1) Network Card:
The NET-VIPA package currently installed is now retained in /dev/builds so it can be used to re-install
when required. Everything else will be automatically deleted from /dva/builds. In V3.3.x.x., all
everything is deleted from /dva/builds.
2) NA
3.16 V3.3.3.0-A
1) Network Card:
a) It is now possible to enable logging mode on the OEM gateway using the normal methods; e.g.
rcasl-pcdva-oem-telnet startd/startl.
b) Slightly improved handling of RSTP during start-up.
2) V2000/LSZDC:
Version update to V3.3.3.0. No functional changes since Package Release V3.3.2.7-A.
3) V2000-48V:
The PSU-48V has been updated to same version as PSU-24V.
Notes:
a. DC input versions of PSU (both 24V and 48V) should have D24 removed to avoid sourcing of
current into low voltage input, otherwise D24 should always be silicon diode type.
b. For 24V and 48V = ensure MOD C for issue 5.4 or earlier.
c. D24 change was implemented in issue 5.5 onwards for 24V and 48V.
d. Issue 5.6: 48V Hardware modified according to: A0623601_Iss_050_MOD_A,
A0623601_Iss_050_MOD_B, A0623601_Iss_050_MOD_C, A0623601_Iss_050_MOD_D,
A0623601_Iss_050_MOD_E, A0623601_Iss_050_MOD_F, A0623601_Iss_050_MOD_J, and
A0623601_Iss_050_MOD_H
3.17 V3.3.2.7-B
1) Network Card:
The Network Card now supports latency for PMC audio streams down to 67 ms and it honours, as
much as it can, the “Audio Latency” value in PAVA SCT when "Override Default VIPEDIA-NET
Network Card Audio Latency" is enabled.
The Network Card supports latency between 66.33ms and 994.33ms in increments of 10.67ms (512 /
48 to be exact) but the PAVA SCT setting allows values between 30 ms and 300 ms. The actual
latency will be the nearest value lower than the requested value; e.g. 66.33, 77, 87.67, 98.33, 109,
119.67, 130.33, 141, etc.
Note that if the Network Card audio latency is overridden by the PAVA SCT, the VIPEDIA-12 will delay
its local audio outputs by the requested value which may not match the actual Network Card latency.
For values above 67 ms, the difference between local and remote outputs will be minimal (no more
than 15 ms) but this will increase for lower values. So, for example, if the audio latency setting in the
PAVA SCT is set to 30 ms, local outputs will start playing audio 37 ms before remote outputs. This is
by design. If you wish both local and remote outputs to be approximately synchronised, use values

above 67 ms. If you wish local and remote outputs to be synchronised as much as possible, then do
not override the setting or override the setting with values between 67 ms and 300 ms.
The default Network Card latency (i.e. when "Override Default VIPEDIA-NET Network Card Audio
Latency" on the PAVA SCT is disabled) is 109 ms (same as on V3.3.x.x).
Notes:
• Any PAVA SCT version and Vipedia matching the Network Card version can be used to override
the default Network Card latency as described above. For example, PAVA SCT V3.3.2.2, Vipedia
V3.3.2.4 and NET-VIPA V3.3.2.67.
• Artefacts may be present in the PMC audio for Network Card latency lower than the default value
of 109 ms depending on the Network Card load.
2) PAVA SCT:
a) The PAVA SCT now allows the configuration of multiple SIP-enabled Network Cards.
b) The PAVA SCT now allows the configuration of multiple networks in a PAVA system.
The PAVA system configuration now requires a Base IP Address in the PA/VA Cluster Options.
The Cluster Unicast IP Settings configured for the PAVA Cluster (see example below) is applied to
all devices in the configuration as in previous release of the PAVA SCT (V3.3.2.2).
If required, the Cluster Unicast IP Settings can now be overridden by the Node Unicast IP Settings
(see example below).

Notes:
• The PAVA system has always supported multiple networks in a single PAVA system. The
limitation was introduced in the PAVA SCT configuration.
• An error will be displayed when a configuration created with previous release of the PAVA
SCT is loaded.
• The Update Manager has been updated to support the new PAVA system configuration (XML
schema v6.00.00). However, it does not support firmware update of devices outside the
Cluster network if the configuration contains multiple networks. If the PAVA SCT configuration
contains multiple networks, use the firmware update via script, Firmware Transfer Tool or the
VCT to update the firmware as appropriate.
Note that the Update Manager does not support firmware update via gateway. The
configuration PC’s must be in the same network as the target device.
• The Network Card Manager has been updated to support the new PAVA system configuration
(XML schema v6.00.00). However, it does not support firmware update of devices outside the
Cluster network if the configuration contains multiple networks. If the PAVA SCT configuration
contains multiple networks AND contains AS redundant systems, use the VCT to update the
firmware.
• The Cluster Overview does not include the Node Gateways.

3) Network Card/Lanner, Linutop, iPAM400, etc. (VIPA Stack)/VCT:
a) It is now possible to configure which VIPA devices are available to announce-d for
announcements when it is set to “Global”. This helps reducing the messages generated and
consumed by announce-d.
The “Host Whitelist for Announcements” in Advanced Settings of the VIPA device (see example
above) contains the list of VIPA devices available to announce-d (global). If the list is not empty,
hosts that are not in the list will not be available to announce-d (i.e. will not be added to the list of
devices in /dva/config/announce-d.xml).
b) Route permissions “Force DVA Streaming” and “Allow Volume Adjustment on Routes” are now
configurable in the VCT.
Microphone settings “MPS Generated Chimes” and “Secondary Microphone Host” are also now
configurable in the VCT.
These new settings have been added to the Advanced Settings page of the VIPA device in the
VCT (see example above).
These settings may have been enabled using the /dva/vipa or /etc/sysconfig/vipa file in previous
V3.x.x.x releases.
Notes:
• These are global flags, i.e., they are applied to any route or microphone within the VIPA
device.
• If you have manually customised any of these settings using the /dva/vipa or /etc/sysconfig/vipa file,
it is strongly advised that you remove the customisations and add them through the VCT. This is
especially true for announce-d’s implicit flags. However, note that if you require announce-d’s implicit
flags other than “Force DVA Streaming” and “Allow Volume Adjustment on Routes” then you should
continue using your manual customisation and avoid using any of the above VCT options.
c) “Do not queue” route permission is now configurable for microphone button-triggered DVAs (see
example below).
This setting may have been enabled using the /dva/vipa or /etc/sysconfig/vipa file in previous
V3.x.x.x releases.

Notes:
• If you’ve manually customised the “Do not queue” route permission using the /dva/vipa or
/etc/sysconfig/vipa file, it is strongly advised that you remove the customisation and add it through the
VCT.
• NA
3.18 V3.3.2.7-A
None.

3.19 V3.3.2.4-B
1) V2000 (LSZDC) / PAVA SCT:
It is now possible to disable the Voltage Limiter on a V2000 (Frame>Advanced>Engineering
tab>Power Management). This is to allow clipping instead of limiting.
Notes:
• The limiter should be normally enabled.
• Audio may be cut out when the Voltage Limiter is disabled, and the amplifier is overdriven.
The Advanced Settings dialog has been modified; see example below:
• Configuration split into two tabs: General and Information.
• Frame IP Port removed as Port should always be 15356.
PAVA SCT V3.3.2.2
PAVA SCT V3.3.2.1 (or older)
2) NA

3.20 V3.3.2.4-A
1) VIPEDIA-12 (DSP):
The “Signal-Present” threshold used to detect short-circuits on microphone data and audio lines has
been raised from -30dB to -15dB. This is to prevent false-positive IPxx AUDIO INPUT S/C fault reports
during EMC testing. This fault is enabled for EN 54 microphones only.
2) PAVA SCT V3.3.2.0 onwards (late notification):
The default values for the Amplifier Current and Voltage limiters were not optimal for performance and
have been updated in V3.3. These values are present in the PAVA SCT configuration file, but they are
not configurable on the PAVA SCT:
New defaults:
• <voltage-limiter attack="1" release="10" hold="20"/>
(Previous V2.x. defaults were: <voltage-limiter attack="100" release="3000" hold="25"/>)
(Previous V3.2. defaults were: <voltage-limiter attack="1" release="10" hold="10"/>)
• <current-limiter attack="2000" release="2000" hold="20"/>
(Previous V2.x. defaults were: <current-limiter attack="100" release="3000" hold="250"/>)
When loading non-default configurations with a schema number prior to v5.05.00 the user will be
presented with the choice to retain their existing limiter settings or to up-date to the new defaults.
Loading files with schema number v5.05.00 or later that have non-default configurations will preserve
the existing configuration without user confirmation.
3.21 V3.3.2.3-B
1) VIPA devices/Network Card/MPS
Microphone handling in redundant configurations has been improved so that whenever both VIPA
instances are running, the primary instance is preferred for MPS connection.
2) Microphones
The splash window and About now display MPS-A/MPSxx-A for microphones/wall-mount controllers
with old processor (MAC address C0:BA:E6:00:xx:yy), and MPS-B / MPSxx-B for microphones/wall-
mount controllers with new processor (MAC address C0:BA:E6:04:xx:yy).
3.22 V3.3.2.3-A
1) VIPEDIA-12:
a) Improvements to DANS configuration to ensure reliable operation.
b) Improvements to the Audio Settings Manager interface for speed and avoidance of retries.
2) Network Card:
The --implicit-dva-flags command-line option for announce-d in /dva/config/vipa now applies to all
routes except BGM. This allows custom routing permissions to be applied consistently across the
VIPA system.
On the Network Card, these custom routing permissions were only applied to DVAs. These are now
applied to all routes except BGM (if applicable).
Notes:
a) The --implicit-dva-flags command-line option is used where the required routing permissions are
not configurable on the VIPA Config Tool (VCT), typically VIPA DVA streaming, Vipedia volume
control and Do not queue option for VIPA DVAs.
b) The --implicit-dva-flags command-line option should be configured on the VIPA device that
triggers the route. The permissions enabled in the --implicit-dva-flags command-line option are
applied to all routes except BGM, and they override the permissions configured in the VCT.
3) Event Logger/Network Card:
Basic support of events from AS redundant systems. However, note that the Event Viewer application
currently does not fully report the display of these events.

4) Event Viewer:
a) The ordering of fields in the detailed area is now more logical. The order for fault-raise events is:
date/time, unit, location, fault path, VIPEDIA-12 front panel text, fault impact, maintenance info
and engineering info.
The order for all other events is: date/time, unit, location, origin, destinations, priority and
information.
Additionally, for all events, fields with no value are not shown at all.
b) When adding new devices to be monitored, the Event Viewer now supports both PAVA system
configuration files (PAVA SCT) and VIPA system configuration files (VCT).
c) The Event Viewer installation now uninstalls any existing version prior to installation. The Event
Viewer configuration will be reset. Previous releases require manual uninstallation of any existing
version prior to installation.
5) PAVA System Configuration Tool (PAVA SCT)/Router Dynamic Configuration Tool (RDT)/Audio
Settings Manager (ASM)
a) The following pop-up warning is now displayed when the PAVA SCT or standalone FTT is
launched:
“This tool should only be used by appropriately trained personnel.
Incorrect use of this tool may adversely affect the performance of a Life Safety system.”
This is to inform users that untrained usage could affect the operations of live systems.
b) General improvements to the ASM operation, reliability and speed of dynamic configuration
loading and reading.
c) It is now possible to restore the Vipedia dynamic configuration to factory default from the ASM.
Note that if DANS has been configured and commissioned, but subsequently removed from the
static configuration, the factory default DANS parameters will not be restored to removed DANS
processors. Thus, if DANS is reconfigured in static configuration, the old dynamic settings will be
restored.
d) The RDT no longer requires a PIN code when committing or changing some of the parameters
(Input Surveillance, Input Phantom Power and Output Override).
Enabling Input Phantom Power triggers a brief confirmation dialog (with the option to cancel).
Other actions are triggered immediately with no warning.
e) On the RDT Advanced Output dialog, the “Reset” button has been hidden, because its
functionality was confusing. It should be re-instated later with correct operation.
f) “Master” and “Backup” has been re-instated in the AS redundant system configuration. They have
been incorrectly change to “Active” and “Standby”.
g) The V2000/INTEGRA Amplifier Frame RCD is now disabled by default.
The setting can be modified as in previous releases.
The new default only applies to new systems or new units within existing systems. Existing units
in existing systems are unaffected.
6) V2000/INTEGRA Amplifier Frame:
a) Audio routing delay on power up has been reduced from 60 seconds to about 10 seconds.
b) NA
7) VIPA Host (Lanner LEC-7230M)
Jabber has been update to protect against communications failure due to intermittent network
connections.
Note that the jabber update is not installed as part of the main application (VIPA Stack) update.
Please use the Jabber RPM Update procedure that is available from Technical Support.
8) MPS-B
The MPS-B has been modified to prevent reset due to EMC noise.
3.23 V3.3.2.0-C
None.

3.24 V3.3.2.0-B
1) PAVA SCT and associated tools:
a) Audio Settings Manager:
The IP Address of the PC and the target unit (including the Unit ID) is now automatically set when
the Audio Settings Manager is launched. It takes the settings from the VIPEDIA-12 Dynamic Tool.
The Read is now only allowed after committing the dynamic settings of the target unit.
b) Router Configuration Tool (RDT) has been renamed to Router Dynamic Tool (RDT)
Amplifier Configuration Tool (ACT) has been renamed to Amplifier Dynamic Tool (ADT)
c) The WMC01 Wall Mount Controller priority range has been extended from 20-63 to 01-63.
d) The FTT now checks if the unit ID currently given to the VIPEDIA-12 matches the unit ID expected
in the configuration file for a router at that IP address.
If the IDs do not match, an error is raised and the configuration does not get written into the
router.
Users must set the correct unit ID in the configuration file or on the unit (via front panel or the
Network Settings tab of the FTT).
2) NA
3.25 V3.3.2.0-A
1) V2000/INTEGRA PSU:
The PSU has been updated for IEC 61508 compliance.
2) Network Card:
a) The NET-VIPA package (NET-VIPA-<version>.tar.bz2) used during a software update is no
longer copied to the disk (/dva/builds). This would eventually cause the disk to become full which
would prevent further updates.
Note that that packages already stored on the disk are not removed.
b) The following JPC tree entries have been renamed:
• Integrity.SystemConfigCorrupt to Integrity.PAVASystemConfigCorrupt
• Integrity.DeviceConfigCorrupt to Integrity.PAVADeviceConfigCorrupt
• Integrity.CurrentConfigCorrupt to Integrity.VIPASystemConfigCorrupt
3) VIPEDIA-12:
DANS is now supported on any VIPEDIA-12 output.
3.26 V3.3.1.0-A
1) VIPEDIA-12:
a) Input Gate: The default Threshold has been updated to -50 dB (was 0 dB).
Note that new default is only applied when the dynamic configuration is erased.
b) Input Gate: The maximum Hold Time has been extended from 5 seconds to 60 seconds.
c) ANS fault timeout has been extended to 12 seconds (for default debounce-ms=200) to allow for
transient overload condition and prevent spurious fault conditions if ANS is positioned in noisy
areas.
Note that the ANS fault timeout depends on the debounce-ms attribute of the analogue input:
• debounce-ms > 200 ms: fault timeout decreases down to 5 seconds
• debounce-ms < 200 ms: fault timeout increases up to 60 seconds
• debounce-ms can only be changed by manually editing the XML configuration file.
d) BMB comms fault is now suppressed for 5 seconds after microphone ports are enabled.
#11538: This is to prevent BMB comms fault when INTEGRA with two or more BMBs is powered
up.

2) Network Card:
a) The VIPA stack on the Network Card now recognises the group names VipediaInput<X> &
AudioInput<X> as being equivalent to mic<X>. All 3 group names refer to the 12 audio inputs of
the hosting VIPEDIA-12 so X can be between 1 and 12.
So, for example, to route audio input 3 with oemtest you can use --mic=mic3 or --mic=AudioInput3
or --mic=VipediaInput3.
The names are case-insensitive so audioinput and vipediainput will work, as well as any form of
capitalisation; e.g. aUdiOiNPut.
b) The priority of vipedia-d & jabber-d has been lowered to improve network performance.
c) The Nagios agent now reports more information about fil-d and memory used by processes. Along
with the value for VSize, it now also reports the values for RSS, RSS peak, VSize peak and stack.
3) PAVA SCT/FTT/Dynamic Tools:
a) New application icons and labels. Main changes:
• Application icons now have text identifying the application: SCT (PAVA SCT), RCT or R
(VIPEDIA-12 Dynamic Tool), ACT or A (V2000 Dynamic Tool), FTT or F (File/Firmware
Transfer Tool), UM (Update Manager) and NM (Network Card Manager).
• VIPEDIA-12 DCT and V2000 DCT have been renamed Router Dynamic Configuration Tool
(RCT) and Amplifier Dynamic Configuration Tool (ACT).
• “Upload”/”Download” “Inject/Extract” have been changed to “Write”/”Read”.
• “Retrieve” has been changed to “Rollback”.
• BMB: all references to “Analogue” and “Digital” Inputs have been removed:
o “Analogue Input” has been changed to “Volt-Free Contact”
o “Digital Input” has been changed to “Volt-Driven Contact”
b) SNMP enable/disable check box has been reinstated on the PA/VA Cluster Options page and
default changed to false due to SNMP having a large performance overhead.
c) The gain fader and audio meter on the V2000 Dynamic Configuration Tool is now available on
the all tabs, not only on the Audio Settings tab.
d) The DVA page on the VIPEDIA-12 Dynamic Configuration Tool now displays 16 DVAs per page
(previously 12).
e) The DANS control pannel on the VIPEDIA-12 Dynamic Configuration Tool now only displays
Adjacent-Zone faders and meters for configured channels. This prevents confusing the setup of
the function with useless controls cluttering up the screen.
4) Event Logger:
Serial monitor command events are no longer logged in the Event Logger.
3.27 V3.3.0.2-A
1) VIPEDIA-12:
The Vipedia can now recover sufficiently to allow DSP and/or configuration to be cleared if the DSP is
hung up for whatever reason. On previous versions, the Vipedia reset few seconds after starting up.
2) Network Card:
a) The Network Card latency has been reduced from 180 ms to 109 ms.
b) The Telnet server is no longer started on Network Cards Issue 2.
c) Issue 2 Network Cards start a compact SSH server on port 2222 which can be used when the
main SSH server is inoperable (e.g. when the DOM of the Network Card becomes unusable or
corrupted).
3) V2000:
Low priority ELK and RCD data have been removed from Nagios messages as Nagios messages
could overflow the available maximum message size.

3.28 V3.3.0.1-B
1) V2000:
The V2000 has been updated to support 110VAC PSU operation (requires PSU update to 7.12.0.0 or
later).
This involves changes to display only. There is no direct operational impact from this change.
This change does not affect compatibility with 230 V AC PSU.
Note that V2000 110V (AVA10009-S1) is available for demo purposes only.
2) MPS-A with navigation board:
Navigation board V3.1.0.0 (standard on microphones BS 15 or later) can transfer touch button
information to the MPS.
MPS V3.2.0.3 (or later) uses this information to diagnostic and fix problems with sensitivity of touch
buttons.
Navigation board V3.1.0.0 is compatible with previous versions of the MPS.
MPS V3.2 (or later) is compatible with previous version of the navigation board (V1.2.2.).
3.29 V3.3.0.1-A
1) Microphone:
The Store&Forward message recording changed from 60 s to 75 s.
2) NA
3.30 V3.3.0.0-A
1) Event Viewer:
• The Origin and Destination columns now show the name assigned to inputs and outputs in the
PAVA SCT configuration (if non-default names are used).
• The Information column now shows the fault description.
• The Information column now identifies the trigger for routing events.
• Details of the events are now displayed at the bottom of the GUI.
• The log can now be filtered by Type and/or Location.
• The route attribute descriptions now match the PAVA SCT options.
2) File Transfer Tool:
The configuration is now first loaded into V2000/INTEGRA Amplifier Frames when All Devices is
selected. This change fixes the issue where FRMxxx CFG MISMATCH could be reported after config
load (All Devices) into the V2000/INTEGRA Amplifier Frame has been fixed.
3.31 V3.2.0.4-A
1) VIPEDIA-12 Host CP – Mute input:
a) V3.2.x Mute with Class Silence do not indicate busy as in V2.1. The indications are now similar to
Silence.
b) The Vipedia does not restore volume level on WCM01 comms timeout to 0dB as in previous
release. This used to prevent changes in output levels on reconnection.
c) The fault relay (Relay 1) in V3.2.x changed as follows:
• Fault Master Vipedia: fault relay indicates any fault in the system
• Non-fault Master Vipedia: fault relay only indicates local faults
In V2.1.x and V3.1.x, the fault relay of any Vipedia unit indicates any fault in the system.
2) Microphone
• Microphone faults (reported as MICxx GENERAL and/or MICxx SYSTEM) are now retained on
the microphone fault menu until they are locally cleared (by pressing the centre of the navigation
wheel).
• The I/F tabs on dual interface microphones now indicate which interface is active (*) / inactive (#).

3) VIPA Config Tool (VCT):

The timeout for a “set configuration” operation has been increased to 5 minutes. This is to allow units
that host a large number of IP microphones to be supported.

4 Bug Fixes
4.1 V4.2.0.8L-A
4.1.1 Faults for ANS on VIPEDIA-12 Contact Input with High Noise (VIPEDIA-12 V4.2.0.8L)
The ANS readings for on-board and BMB01 contact inputs were different especially with high noise. With
high noise levels, this difference would cause ANS faults for on-board contact inputs.
The processing has been updated to align the on-board ANS readings to the BMB01 ANS readings, and
the ANS faults with high noise are no longer reported for on-board contact inputs.
To support the diagnostics via serial monitor:
• “bm-get 0 ana” now also displays equivalent BM01B level and diagnostic information on expected
voltage levels and Vipedia ADC reading.
• “bmb-get x ana” for inputs configured as Selector / Volume Control now displays the converted switch
position (1-12). Note this is 1-12 and not 0-11.
4.1.2 Vipedia Logging of Transient NTP Synchronisation Faults (VIPEDIA-12 V4.2.0.8L)

An issue where NTP synchronisation faults would only be logged once between fault clears has been
fixed. This was because the NTP synchronisation faults were logged as faults rather than events, meaning
that they were checked for uniqueness between fault clears. The transient NTP synchronisation faults are
now logged as events and they are fully decoded to text descriptions rather than codes. See the new text
descriptions in “3.1.1 Vipedia Logging of NTP Synchronisation Status Changes (VIPEDIA-12 V4.2.0.8L)”.
4.1.3 Network Card Time Synchronisation Daemon Memory Leak (NET-VIPA V4.2.0.82L)
An issue that caused memory leak in the time synchronisation daemon (time-sync-d) has been fixed. The
memory leak eventually, after several months, exhausted all memory triggering a hardware restart.
4.1.4 Vipedia Output Surveillance Occasionally Incorrect (#23453) (Vipedia DSP V5.0.2.4P)
An issue where the Vipedia output surveillance frequency could be incorrect on power up or reboot
causing unclearable FRMxxx/SLOTx INPUT faults on V2000 units has been fixed.
4.1.5 WMC Configuration (VIPEDIA-12 V4.2.0.8L)

An issue whereby a WMC with no source configured could cause Vipedia reset after configuration load or
power up has been fixed.
4.1.6 V2000 LSZDC Reset/Comms Issues Fixed (V2000 V4.2.0.7L / LSZDC DSP V5.0.2.5P)
a) An issue where spurious line and amplifier faults could be reported after a fault clear with
unrecoverable SRV CARD fault present has been fixed.
b) An issue where the frame could get stuck in LSZDC comms retry loop after subsequent LSZDC resets
has been fixed.
c) An issue where the standby amplifier could not switch in after two or more LSZDC resets has been
fixed.
d) An issue where a LSZDC reset during surveillance tone could cause spurious open circuit impedance
faults on other slots has been fixed.
4.1.7 V2000 PSU Shutdown on Over-Currents at 110 V Supply
An issue where the V2000 PSU did not shutdown on over-currents when at 110 V supply has been fixed.

4.1.8 V2000 High Battery Temperature

An issue where the float voltage could be excessive high if battery temperature exceeded has been fixed.
4.1.9 EMS / MPS - Occasional Fist PTT Deactivation (MPS V4.3.0.6L)
It was expected that in operation the fist PTT switch would be very low impedance. However, it has been
found that the contacts of the fist PTT switch age which may cause high impedance readings when the
PTT switch is active. This unexpected high impedance reading could cause the route to be dropped. To
mitigate these effects the high active threshold has been increased.
Also, an issue whereby the different thresholds for standard and ATEX microphones were incorrectly
applied has been fixed.
4.1.10 WMC Start-up (MPS V4.3.0.6L)
An issue where the serial WMC did not start up correctly not allowing access to the source selection tab
has been fixed.
4.1.11 MPS Fault List Display Limited to 127 Faults (MPS V4.3.0.6L)
The fault list display would stop working after reaching fault 128. The MPS now only allows display up to
fault 127. This ensures that all 127 faults can be scrolled up/down.
4.2 V4.2.0.6P-C
4.2.1 V2000/INTEGRA mains supply not restored (#23221) (PSU V7.29.0.0)
An issue introduced on PSU V7.27.0.0P whereby, after isolation and reconnection of the mains supply,
the V2000/INTEGRA could not power up on mains supply has been fixed. The mains supply had to be
isolated for 20 minutes or more before the unit powered up on mains.
4.2.2 Output surveillance monitoring when audio is routed (V2000 V4.2.0.6P)
The V2000 now checks if audio is/has been routed during the surveillance period and, if it has, the output
surveillance is only compared to the low threshold. This is to prevent output surveillance faults (SLOTxx
AMP FAIL) created by routed audio.
4.3 V4.2.0.6P-B
4.3.1 Audio drop out on outputs with DANS (DSP V4.2.0.1P)
Ref. “4.4.1 Audio drop out on outputs with DANS (Vipedia HCP V4.2.0.6P)” (page 80).
The root cause for the audio drop outs on outputs with DANS has been identified and fixed.
4.3.2 DANS compensation applied to ANS disabled (or tolerant) routes (DSP V4.2.0.1P)
An issue whereby DANS compensation would be applied to ANS disabled (or tolerant) routes in some
combinations of DANS configuration and routes has been fixed.
4.4 V4.2.0.6P-A
4.4.1 Audio drop out on outputs with DANS (Vipedia HCP V4.2.0.6P)
A one-minute drop out could occur on outputs with DANS for any route irrespective of its DANS/ANS
setting.
A workaround has been implemented in the DSP refresh cycle to prevent the audio drop out.

4.4.2 EN 54-16 microphones temporarily blocked when mic comms is broken during an EN 54-16
live announcement (Vipedia HCP V4.2.0.6P)
In previous releases, EN 54-16 microphones may be blocked for up to 10 minutes if microphone comms is
broken during an EN 54-16 announcement.
Now, EN 54-16 microphones will be operational soon after an EN 54-16 microphone comms is lost.
4.4.3 AS Redundant System - Vipedia IP microphone not routing on Active/Standby switchover

(MPS V4.3.0.4)
An issue whereby Vipedia IP microphone connected to a redundant pair could not route when the Backup
unit became active has been fixed.
4.4.4 PTT and MPX PTT interaction causing microphone audio drop out (MPS V4.3.0.4P) (SysAid
#21792)
An issue whereby triggering a PTT or fist mic button whilst MPX PTT route in progress cancelled the
microphone audio has been fixed.
The main PTT and MPX PTT can now be configured without any zone selection.
4.4.5 Button press on VIPA microphones (NET-VIPA V4.2.0.81P / VIPA Stack V4.2.0f)
As issue has been corrected that could in very rare circumstances prevent button presses being
processed from a hosted microphone.
4.4.6 DOM version (NET-VIPA V4.2.0.81P)
The Network Card now correctly reports the version of the installed DOM image for DOM images version
3.0.0.2 and newer. The reported version will also be consistent between the front panel and VCT (albeit
with more details). Unfortunately, all older versions of DOM will continue to identify as 0.0.0.1 on the front
panel and vipedianet-base-dva-image-1 on VCT.
4.5.1 V2000 Amplifier Failure / Route Failure Spurious Fault Reporting (Frame Controller
V4.2.0.5P / LSZDC DSP DSP V4.2.0.7P) (#20838)
An issue where amplifier type at high temperature could be detected as missing and spuriously reported
as Amplifier Failure (FRMxxx/SLOTxx AMP FAIL / AmpFramexxx.AMPxx.AmpFailure) and/or Route
Failure (FRMxxx/SLOTxx ROUTE FAIL) has been fixed.
4.5.2 V2000 Amplifier Mismatch Fault Reporting (Frame Controller V4.2.0.5P / LSZDC DSP DSP
V4.2.0.7P)
An issue where the V2000 could fail to resolve the amplifier type correctly at low temperature has been
fixed.
Note:
Amplifier Failure due to mismatch type (FRMxxx/SLOTxx AMP FAIL /
AmpFramexxx.AMPxx.AmpPowerMismatch) is no longer reported for D500 amplifiers configured as D150.
This type mismatch has no impact on operation as the D500 amplifier can correctly function as D150.
4.5.3 VIPA Host (VIPA Stack V4.2.0g) – Dual-hosted Microphones on Redundant Pairs
The display of EN 54 indications on dual-hosted microphones hosted are now correctly updated across a
redundant pair of VIPA Servers or VIPA Hosts.

In previous releases, the display of EN 54 indications on a dual-hosted microphone did not update for the
slave unit of a redundant pair.
4.5.4 VIPA Host (VIPA Stack V4.2.0g) – HTTP-hosted DVAs
An issue has been addressed that could cause a memory leak when using HTTP-hosted DVAs.
4.6 V4.2.0.5P-C
4.6.1 VIPA Host (VIPA Stack V4.2.0f)
An issue has been corrected with the hosted microphone connection to the secondary device in a
redundant pair of VIPA-HOSTs.
Re-apply the VIPA configuration to your secondary device after installing this update.
4.6.2 VIPA Host, VIPA Servers and others (VIPA Stack V4.2.0f)
As issue has been corrected that could in very rare circumstances prevent button presses being
processed from a hosted microphone (using ASL Serial Protocol).
4.6.3 iPAM400 (VIPA Stack V4.2.0d)
VIPA Stack V4.2.0e and V4.2.0f are not compatible with iPAM400. They cause iPAM400 to continuously
reboot.
VIPA Stack V4.2.0d should be installed on iPAM400 where latest V4.2.0 is required.
4.7 V4.2.0.5P-B
4.7.1 V2000 Firmware Update (V2000 V4.2.0.4P, LSZDC DSP V4.2.0.5P and LSZDC Bootloader
V4.2.1.0P)
Issues with LSZDC firmware update have been fixed. These issues could happen when:
• Combined LSZDCs were updated with frame configured, especially in frames populated with few
slots.
• Combined or split LSZDCs were updated with LSZDCs fitted but not configured.
4.7.2 V2000 LSZDC (LSZDC DSP V4.2.0.5P)
The Low Pass Filter (LPF) has been updated from 22.3kHz to 24kHz to improve frequency response at
20 kHz by +0.6 dB.
This is to ensure LSZDCs pass production test within specification.
4.7.3 SIP Live Announcement - PMC TLL (NET-VIPA V4.2.0.79P)
The SIP live announcement PMC TTL is now 20 (was 1).
4.8 V4.2.0.5P-A
4.8.1 MPS-B V4.3.0.3P - PMC TTL

An issue on MPS-B where the PMC TTL was always 255 irrespective of the configuration menu option
setting has been fixed.
4.8.2 V2000 LSZDC V4.2.0.4 - Spurious RCD Faults

The RCD holdoff after amp-wake is triggered has been to 750ms to prevent spurious RCD faults.

4.9 V4.2.0.4P-A
4.9.1 Vipedia:
An issue which prevented a Vipedia listen-in mixer to be shared between Vipedia microphone and VIPA
microphone has been fixed.
Notes:
a) VIPA microphone listen-in always overrides Vipedia microphone listen-in.
b) Overriding listen-in mix may play on overridden microphone.
4.9.2 MPS:
a) #19343: An issue where hardwired PTT could not operate correctly after short comms restoration
has been fixed.
b) An issue whereby the MPS did not always broadcast a chime when hosted in IP mode by a
Vipedia (or VIPA unit) has been fixed.
c) An issue whereby the iVENCS/SMS MPS did not display loss of IP comms has been fixed.
4.9.3 V2000:
a) A problem where the V2000 could not detect NVM device failures and report NVM FAULT has
been fixed.
b) An issue where amplifier was not slept correctly on amplifier hardware fault has been fixed.
c) An issue where spurious speaker line faults were reported especially for fully populated frames
has been fixed.
d) An issue which caused amplifier type to be incorrectly reported for low temperatures (below 16C)
has been fixed. The amplifier type is now correctly detected down to 5C.
e) Zipper noise on EQ parameter adjustment has been corrected.
The number of interpolation steps has increased from 100 to 250. The EQ morph now takes
0.25sec (was 0.1sec) so is no longer subject to zipper noise.
4.9.4 Network Card:
a) An issue in the loader of time zone info files which would have caused the time synchronisation
daemon to crash has been fixe.
It is unlikely the bug ever manifested because it is only triggered by time zone info files that
contain erroneous data.
b) An issue in the installation of NET-VIPA which always caused sfpd to crash has been fixed.
4.10 V4.2.0.2P-B
1) PAVA SCT:
#15772: An issue where the busy contact output configuration (XML) would only include one of the
inputs of a dual interface microphone has been fixed. Now both inputs of a dual interface microphone
(as displayed on the busy configuration dialogue; see example below) are included in the busy output
configuration.

• PAVA SCT V4.2.0.2P (or older): busy output

configuration (XML) includes VIP01/IP01 input
only.
• PAVA SCT V4.2.0.3P (or newer): busy output
configuration (XML) includes VIP01/IP01 and
VIP02/IP01 inputs.
2) NA
4.11 V4.2.0.2P-A
1) VIPEDIA-12
a) An issue on V4.2.0.0 whereby input surveillance fault was not reported for non-microphone inputs
(for example, DANS input) has been fixed.
b) An issue where a DVA routed by multiple triggers could not resume after short stop/start has been
fixed.
c) An issue where Vipedia host could use incorrect IP port to address its Network Card after
configuration load or reboot has been fixed. This could result in unnecessary reboot of Network
Cards running VA Global Status module (va-global-status-d) and/or Time Synchronisation module
(time-sync-d).
d) A problem where Vipedia failed to detect NVM device failures and report NVM FAULT has been
fixed.
e) An issue on V4.2.0.0 where the normal top-level menu was misleadingly displayed following a
reboot command (for example, when updating the Unit ID) has been fixed.
Now the top line shows “HOST REBOOTING” when rebooting, and then the normal “Initialising –
please wait ...” message.
2) Network Card
a) An issue on NET-VIPA V4.2.0.72 where the NTP/Time zone/Date&Time information on Vipedia
front panel and FTT>Time Settings tab could not update after configuration changes has been
fixed.
The issue would manifest when configuration changes to time synchronisation and/or multicast
control address were loaded after reboot or power cycle. Changes to configuration would only be
fully effective after manually restarting the Time Synchronisation module.
b) NA
3) V2000
a) The default DC-EOL Delay has been changed from 4000 ms to 4500 ms in the system
configuration to prevent spurious short-circuit faults on speaker lines with DC surveillance
especially when the frame is fully populated.
The PAVA SCT will preserve the settings in pre-existing configuration files.
b) NA

4) PAVA SCT
a) The PAVA SCT now always sets the preferred_master attribute to “false” in the exported Dante
controller XML configuration file. This is so that the clock configuration is line with Audinate
guidelines.
In previous releases, the preferred_master is set to true if the VIPEDIA-12-PRO unit is a time
master.
b) The PAVA SCT now validates INTEGRA configuration when a system configuration is loaded that
contains an INTEGRA. It checks that the amplifier is configured to point at the correct output
(correct Router unit ID and output number same number as the amplifier slot).
If incorrect settings are detected (typically in configuration files that have been manually updated),
a warning is raised, and the settings are automatically corrected.
c) The PAVA SCT now automatically sets default fault texts for fault input contacts whenever any of
the fields is empty. This is to prevent faults with no fault text.
The default matches the BMB address:
• BMB01:
“Ext Fault - BMBx:AnaCIyy” (front panel) / “ExternalFaulttBMBxAnalogueContactInputyy”
(JPC)
“Ext Fault - BMBx:DigCIyy” (front panel) / “ExternalFaultBMBxDigitalContactInputyy” (JPC)

• On-board:
“Ext Fault – BMB0:CIyy” (front panel) / “ExternalFaultBMB0ContactInputyy” (JPC)
It is still possible to manually override these default values with custom values. Pre-existing
custom values are preserved.
5) MPS/WMC/etc.:
a) An issue where WMC units could not update routing correctly on the host Vipedia has been fixed.
Typically, it would show “route cancelled” when route was still active on Vipedia.
b) An issue on MPS-B where IP listen-in would be silenced when the microphone was connected to
the network via an IGMP-enabled network switch has been fixed. The issue was caused by IGMP
not working on MPS-B.
4.12 V4.2.0.0P-A
1) Network Card
An issue where the SIP module would fail following a store and forward operation has been fixed.
2) V2000&VIPEDIA-12 and INTEGRA
An issue where amplifier input and network faults would be reported if both Amplifier Frame and
Router were powered on simultaneously has been fixed.
3) VIPEDIA-12/INTEGRA
a) Vipedia/INTEGRA front panel fault report text has been changed from FRM:xx/AMPxx to
FRMx/SLOTxx.
This is to avoid confusion between slots and amplifiers in cases where not all slots of
V2000/V400/X400 Amplifier Frames are populated with amplifiers.
b) An issue where WMC routes could not be restored if reactivated immediately after being cancelled
has been fixed for local inputs. Remote sources may still not be restored if reactivated
immediately after being cancelled.
c) DVA loading progress no longer disappears from the Vipedia front panel when loading long DVAs.
d) The pre-fader volume level of DVA files played to the front-panel are now correct.
Previously pre-fader played +13 dB too loudly compared to the post-fader level.

e) The RDT now updates inputs that are changed from miscellaneous to processed Dante Input (or
vice-versa) on Vipedia connection. In previous releases, it could take 8 to 30 minutes.
f) A problem whereby chime generation at startup with a full DVA flash caused an incorrect "DSP
PM Fault" which in turn led to an unexpected reboot (and fault-reboot cycle continually repeated)
had been fixed.
g) A test has been added to detect corrupt DVA flash file-index data (leading to a reset of the DVA
flash, instead of attempting to read from invalid memory addresses resulting in a core-hang and
reboot).
4) ADT (Amplifier Dynamic Configuration Tool)
a) Surveillance tab:
The ADT now enforces the maximum 10 x EOL resistors per amplifier configured for DC line
surveillance.
b) Audio Settings tab:
The range of the frequency knob is now set to different values according to the filter type:
• Low-Shelf: 20Hz->1kHz
• High-Shelf: 1kHz->20kHz
• All Other Filter Types: 20Hz->20kHz
This is to prevent audio lock-up when low-shelving EQ frequency is set to 20kHz.
5) RDT (Router Dynamic Configuration Tool) – Inputs and Outputs tabs
a) Shelving filter frequency controls are now logarithmic instead of linear.
b) The range of the frequency knob is now set to different values:
• LOW-Shelf control: 20Hz -> 1kHz
• HIGH-Shelf control: 1kHz -> 20kHz
This is to prevent audio lock-up when low-shelving EQ frequency is set to 20kHz.
6) PAVA SCT
An issue whereby the WMC would display blank source when default names were used for
Dante/Processed Dante sources has been fixed.
7) FTT
a) #18214: The FTT now displays the characters following the software version number, for
example, “Host Firmware v4.2.0.0-P”
b) The Firmware Transfer Tool (and Update Manager) no longer displays “Qt: Untested Windows
version 6.2 detected!”
8) Event Viewer/Network Card
#17984: Multiple instances of Event Viewer logging events from the PAVA system are now supported.
4.13 V4.1.0.0-A
1) VIPEDIA-12:
a) The DSP refresh was broken into further smaller refresh items so that the DSP is not blocked and
routing times increased.
In Vipedia V4.0.0.1, a delay/pause could be noticed when playing short DVAs (about 1.5
seconds).
Note that the RDT will take about 30 minutes to update inputs that are changed from
miscellaneous to processed Dante Input (or vice-versa). Rebooting the Vipedia will update the
RDT when Vipedia starts up.

b) NA
2) Network Card
a) VIPA BGM routes now have the “Allow Volume Adjustment” permission enabled so that the
volume of VIPA BGM routes can be controlled by volume control mechanisms available to Vipedia
and clients like the ASL PA HMI.
b) The “Silence Enabled” for VIPA routes is now set according to emergency class:
• VIPA non-emergency routes: “Silence Enabled” flag enabled
• VIPA emergency routes: “Silence Enabled” flag disabled
c) Fixed a bug which caused audio to be put on an internal channel used for monitoring purposes.
This in turn caused all VIPA audio channels to be continually reset thereby disrupting all VIPA
routes (PAVA routes were unaffected).
The bug would only manifest when all internal channels were in use.
3) PAVA SCT:
a) An issue where loading a config containing an INTEGRA-PRO with no amplifiers would change
the type to INTEGRA has been fixed.
b) NA
4) ADT (Amplifier Dynamic Configuration Tool): changes to fix error and improve clarity
a) “HF Modulus” has been changed to “Impedance” to match terms used on the PAVA SCT.
BEFORE
NOW

b) The Help next in the Tone Generation box has been modified and an error wrt to HF for
impedance monitoring has been fixed.
BEFORE
NOW
5) RDT (Router Dynamic Configuration Tool):

An issue were the input and output shelving-EQ filters displayed different values for Slope on the main
EQ page, and on the advanced value-entry window has been fixed.
BEFORE (different)
NOW (same)

4.14 V4.0.0.1-A
1) VIPEDIA-12:
a) Dante routes:
An issue where raw Dante routes could be silenced when overriding multiple PMC routes has
been fixed.
b) Service Record #16601 - Legacy microphones and EAP01:
An issue where an EAP01 stopped other legacy microphones (e.g. SMC) from working properly
on comms reconnection (for example, on power up) has been fixed.
c) Front panel fault sounder and display:
A timeout issue which caused the fault sounder to beep and “Limited Hw bypass mode
functionality”, “INTERNAL ERROR” or “No Host Processor Comms” to be displayed during start-
up has been fixed.
d) Front panel DVA monitoring:
An issue that prevented inactive DVAs to be monitored on the front panel has been fixed. All
DVAs can now be monitored as long as a DVA player is available.
e) An issue where delay/pause could be noticed when the DSP was refreshed (every 10 minutes)
especially when playing short DVAs (less than 15 seconds) has been fixed. The DSP refresh is
now split into smaller components to avoid long delay/pauses.
2) NA
4.15 V4.0.0.0-A
1) VIPEDIA-12:
a) #15445 and #16060:
An issue where delay in V2000 wake-up could clip initial audio has been fixed.
b) An issue where multiple active PMC routes could not be restored correctly after config load has
been fixed.
c) An issue where PMC TX channel assignment could get stuck when multiple PMC routes where
activated has been fixed. In previous releases, if the assignment got stuck, fewer number of PMC
routes could be active at the same time.
Note that there is a settling time when multiple sources try to allocate a PMC channel, and wrong
source may be routed during the settling time.
d) An issue where a Vipedia IP microphone could drop out after 10 seconds has been fixed.
e) An issue with clearing and setting PMC channels has been fixed. In previous releases, wrong
audio could be routed to outputs when concurrently activating multiple PMC routes at same
priority.
f) An issue where proxy routes could be dropped due to timeout has been fixed. Proxy routes are
triggered by triggered by selectable route button where the source is not local.
g) Issues handling DVA players have been fixed. In previous releases, fewer concurrent DVAs could
be active due to incorrect handling of the DVA players when multiple DVAs where activated and
cleared at the same time.
h) An issue where Vipedia could reset when a DVA triggered by a selectable route button overrode a
DVA player has been fixed.
i) An issue where a Vipedia IP microphone could behave unexpectedly due to a late IP microphone
response being treated as an early response from the next microphone has been fixed. In
previous releases where a Vipedia has multiple IP microphones, a DVA could be unexpectedly
triggered from an IP microphone button when the same button was used on another IP
microphone.
j) Fix problem with context prioritisation.

k) An issue where routes (normally proxy routes) could be dropped due to routing outputs being be
continuously reset, resulting in no output of message for some contexts, has been fixed.
2) Network Card:
An issue whereby SFP ports where incorrectly reinitialised near the end of the NET-VIPA installation
has been fixed. This potentially could cause the RSTP loop on Issue 2 Network Card to misbehave
during NET-VIPA firmware update, causing all Vipedia units to reset (due to data storm).
4.16 V3.3.3.0-A
1) VIPEDIA-12:
a) DANS:
An issue where DANS would not disconnect correctly from previous output channel when DANS
mapping was reconfigured has been fixed. Power-cycle is no longer required to restore the correct
operation of the unconfigured output.
b) VOX Routes:
An issue where multiple VOX Input Gates could not correctly trigger associated VOX routes has
been fixed. This issue was present since V3.3.1.0P.
2) Network Card:
a) VCT: Advanced: Disk Write Mode option
An issue which prevented the advanced VCT option “Disk Write Mode” from working correctly
when set to Writable on issue 2 Network Cards has been fixed.
This also fixes the issue where SSH files were not created or updated; e.g.
/root/.ssh/authorized_keys, /root/.ssh/known_hosts, etc.
b) #13315:
An issue in the OEM gateway which occasionally caused requests to be lost has been fixed. The
issue was triggered by packets containing multiple requests and caused all of them except the
first to be discarded. The fix ensures that both packets with multiple requests and requests split
over multiple packets are now processed correctly.
c) NTP:
A rare issue which prevented NTP changes from taking effect after a configuration update without
a reboot has been fixed.
d) VIPA microphones: Zone faults
An issue which prevented VIPA-hosted microphones from lighting up the zone-fault LED for
VIPEDIA-12 outputs with faults when the default control multicast address was used has been
fixed.
Zone-fault LEDs on should now correctly light up for faults irrespective if they are generated by
VIPA or VIPEDIA-12.
4.17 V3.3.2.7-B
None.

4.18 V3.3.2.7-A
1) VIPEDIA-12:
a) EN 54-16 microphones: The short-circuit detection between audio and data lines on inputs has
been made less sensitive. This is to prevent false-positive IPxx AUDIO INPUT S/C fault reports
due to EMC events.
b) An issue with HCP (Host Protocol) routes where NVC, Silence and other volume control attributes
were not correctly applied has been fixed.
HCP routes have now the following volume control attributes:
Volume Control Attribute HCP Routes

Non-emergency Emergency
NVC Enabled Disabled
Silence Enabled Enabled
Volume Adjustment Enabled Enabled
ANS Enabled Enabled
Relative Gain None None
c) #15553: An issue that was introduced in V3.3.2.4 which prevented the operation of the VA Relay
(relay 2) in non-redundant systems has been fixed.
2) NA
4.19 V3.3.2.4-B
None.
4.20 V3.3.2.4-A
1) Lanner, Linutop, iPAM400, etc. (VIPA Stack):
a) An issue has been fixed that caused communications with an IP-hosted MPS microphone to be
lost 3.5 minutes after a power cycle on certain types of VIPA hosting device. This issue does not
affect microphones hosted by a Network Card.
The microphone reported HOST COMMS LOST, but no comms fault was reported by the VIPA
hosting device. Re-loading the VCT config or restarting the VIPA device fixed the issue.
b) An issue that occasionally prevented a VIPA-hosted microphone from working after a
configuration update or reboot has been fixed. The microphone was irresponsive to button
presses although the microphone comms and global status were ok.
The issue was caused by a synchronisation issue between the daemon responsible for
microphone buttons and the daemon responsible for microphone comms. They now synchronise
correctly.
2) Network Card:
a) Issues that caused Network Card configuration updates to silently fail when the filename of the
PAVA SCT configuration contained spaces have been fixed.
The Network Card configuration is now correctly updated when a configuration file with space in
the filename is loaded.
b) An issue that could cause Network Card configuration validation fault
(Integrity.PAVADeviceConfigCorrupt) when the filename of the PAVA SCT configuration
contained spaces has been fixed.
c) #15176: An issue that occasionally would cause spurious PMC receive faults (VNET AUDIO
FAULT 4:0 / PMCReceiveFault) when the route was terminated has been fixed.
d) An issue that occasionally prevented a VIPA-hosted microphone from working after a
configuration update or reboot has been fixed. The microphone was irresponsive to button
presses although the microphone comms and global status were ok.
The issue was caused by a synchronisation issue between the daemon responsible for
microphone buttons and the daemon responsible for microphone comms. They now synchronise
correctly.

3) VIPEDIA-12:
a) #15176: Issues that occasionally would case spurious FRMxxx AMPyy ROUTE FAIL faults have
been fixed.
Spurious FRMxxx AMPyy ROUTE FAIL faults have been reported in sites with more than 3
amplifiers per frame and sites using VIPEDIA-48 with V2000.
This update should resolve these issues.
Note that spurious FRMxxx AMPyy ROUTE FAIL faults may be reported very occasionally if
routes are made whilst commissioning the V2000/INTEGRA Amplifier Frame.
b) NA
4.21 V3.3.2.3-B
1) Network Card:
An issue where local DVA playback initiated from VIPA clients to multiple VIPEDIA-12 units was often
out of sync has been addressed.
The beginning of the DVA may be cut off in one or more VIPEDIA-12 units, especially with long DVAs
and where the Network Cards are heavily loaded and/or with low memory. Increasing announce-d
Sync Delay (VIPEDIA-NET>Advanced Settings) from 1000ms to 2000ms will likely solve the issue.
2) NA
4.22 V3.3.2.3-A
1) VIPEDIA-12:
a) An issue where loading DANS configuration could freeze output meters and disable output has
been fixed.
b) An issue where the ANS gain values for DANS were incorrectly updated after loading the
configuration has been fixed. Vipedia reboot was required for correct ANS gain to be applied.
c) An issue with the HCP Interface where the host route status could not show the last
acknowledged route has been fixed.
d) An issue where the incorrect type (on, off or pulsed) of High Frequency (HF) output surveillance
could be stored in NVM when the dynamic configuration was loaded by the Audio Settings
Manager has been fixed.
Present in previous releases.
e) An issue where contact outputs (on-board and BMB) configured as VA (High, Low or Any) were
not activated has been fixed.
Present in V3.3.2.0.
f) An issue where the Input State Change event in the Event Viewer showed reversed state change
for low active contact outputs (on-board and BMB) has been fixed.
The Event Viewer showed inactive change when the contact actually had become active.
Present in V3.3.2.0.
g) An issue where the fan outputs could not be re-enabled after configuration update especially while
the fan outputs were active. The fan outputs would be re-enabled after a LAMP TEST.
The fan output is used to control the V2000 fan tray and INTEGRA back box fans.
Probably present in V3.3.2.0.
h) An issue that could cause DVA Load to erroneously report “file not present” has been fixed.
2) Network Card:
a) An issue that prevented fault reporting from microphones attached to the Network Card when the
microphone control port was different from the Network Card control port has been fixed. A
comms fault was reported as result of the missing fault reporting.
The microphone control port can now be set to any value provided that it is not one of the
reserved ports.
b) A bug which caused incorrect input number for VOX inputs in routing events to be logged has
been fixed. The number displayed was one less than what it should have been.
c) A rare bug has been addressed which would make storage faults for the PAVA system
configuration, the PAVA device configuration and the VIPA system configuration unclearable.
Now when the above faults are unclearable, re-loading the configuration using the File Transfer
Tool will allow these faults to be cleared.

d) A bug where one or more storage faults would often be raised right after a configuration update
has been fixed.
e) A bug that caused VNET STORAGE 3:17 (PAVASystemConfigCorrupt) after a configuration
update has been fixed. The fault would be raised early in the update and logged in the Vipedia
Fault Log and Event Logger. Depending on the load of the network card, the fault could remain
raised after the configuration update was completed.
f) An issue where overridden announcements resumed after the override was removed even when
the resume-after-override flag was not specified has been fixed.
3) PAVA SCT/RDT/ASM:
An issue where the Audio Settings Manager could not correctly read/write the configuration to Vipedia
units in systems with DANS has been fixed.
4) V2000:
a) An issue where total short-circuit fault could be reported on the wrong speaker line on dual
outputs using impedance monitoring has been fixed.
b) An issue where the speaker line on a dual output using impedance monitoring could not be
isolated has been fixed.
c) Issues where amplifiers could not return to sleep mode after Ethernet or mains restore (typically
after configuration load) have been fixed.
d) An issue where AMP FAIL fault was spuriously reported on LSZDC comms fail fault has been
fixed.
4.23 V3.3.2.0-C
1) Network Card:
An issue where the netmask of network cards were set to seemingly random values has been fixed.
2) NA
4.24 V3.3.2.0-B
3) PAVA SCT and associated tools:
a) An issue whereby cancelling the VIPA Configuration Import operation on the PAVA SCT would
erase any pre-existing imported VIPA Configuration has been fixed. The issue would also erase
all SIP accounts with VIPA zones in its configuration.
Cancelling a VIPA Configuration Import now leaves the configuration unchanged (any pre-existing
Imported VIPA Configuration is preserved).
b) The VIPEDIA-12 Dynamic Tool now correctly points to a valid Vipedia-ID upon being launched
(previously it defaulted to ID=1, even when it did not exist in the system).
4) NA
4.25 V3.3.2.0-A
1) VIPEDIA-12:
a) Issues with AS Redundant systems whereby both units in the redundant pair could be Active or
Standby at the same time have been addressed.
b) An issue where Dynamic Config Mismatch fault could be reported in AS Redundant systems after
using the NVC override feature has been fixed.
c) #11743: DSP Channel slip caused by DVA load
d) #13438: An issue where FRM ???? could be reported when the Amplifier Frame configured with
DC power supply (battery or external DC supply) was powered up on mains only has been fixed. It
now reports FRMxxx DC SUPPLY or FRMxx BATTERY for the same condition.
2) Network Card:
#10935: An issue was fixed in the jabber daemon which occasionally prevented stale connections
from being closed. In those occasions applications on the device could not communicate with remote
applications and vice-versa.
3) PAVA SCT:
An issue where the PAVA SCT didn’t update the loop monitoring configuration when it was
enabled/disabled has been fixed.
4) V2000:

a) #13355: An issue with impedance monitoring where a short circuit fault could sometimes
incorrectly be reported for an open circuit has been fixed.
b) An issue where a working amplifier could incorrectly swap to a faulty standby amplifier has been
fixed.
4.26 V3.3.1.0-A
1) VIPEDIA-12:
a) “clear-op-surv” monitor command reinstated for production test.
b) A few issues whereby Vipedia could reset during DVA have been fixed.
c) An issue whereby incorrect audio source could be routed to the listen-in mix on a VIPEDIA-12-
PRO or Vipedias in a 36x36 or 48x48 DBB group has been fixed.
d) The Vipedia now monitors for output channel slip. If channel slip is detected, Vipedia resets
attempting to fix the issue (VIPEDIA-DSP CODE FAULT).
e) Active Standby Redundancy:
Changes to prevent both units in standby when no Ethernet comms to either side.
2) V2000:
a) Battery power save mode: An issue whereby blocked routes were allowed (after an overriding
route was cancelled or if activated within approx. 7 seconds of an allowed route) has been fixed.
b) Audio settings:
• The minimum Q value allowed for an EQ filter has been updated from 1.0 to 0.1.
• The EQ controls on the V2000 Dynamic Tool have been updated to display only supported
filter types and sensible ranges of parameter.
c) PSU fault reporting: The PSU fault is now reported if backplane voltage drops after current trip
where the debounce time on normal fault is too long.
Note that this fix is intended for #11658 which was later found to be due to a hardware and
firmware compatibility issue.
d) An issue whereby a speaker line could be incorrectly isolated on open circuit has been fixed.
Note speaker lines are not isolated in the event of open circuit or partial short circuit.
e) #12099: An issue whereby AMP FAIL fault would not be reported if standby amplifier in slot 10
(and possibly other slots) was pulled from frame has been fixed.
3) VIPEDIA-12/Network Card:
Issues whereby PMC routes could be silent or incorrect audio be routed where overrides take place
have been fixed.
4) Network Card:
a) An issue which prevented VCT from changing the IP address of a Network Card has been fixed.
b) A memory-leak issue in the jabber server has been fixed.
The jabber server would leak a very small amount of memory every time it tried to connect to a
remote jabber server irrespective of the outcome of the attempt. Although the memory loss per
device per attempt was insignificant, it was cumulative and, since failed attempts (e.g. when there
are offline devices) resulted in further attempts, ever increasing when devices were missing. In
large systems with many missing devices, this resulted in significant memory losses.
c) An issue whereby Network card (VIPA) zones could be not be reached from some network cards
(zone in Error) whilst reachable from others has been fixed.
This issue normally happened power cycling the Vipedia unit (or rebooting the Network Card).
d) An issue which prevented the Network Card from receiving multicast UDP packets from multiple
multicast address with same value in the last octet (for example, multicast addresses 239.x.x.1 )
has been fixed.
e) The Network Card now rejects multicast router control port set to an invalid value. Port numbers
15356 to 15359 & 19001 to 19004 cannot be used because it will result in two different services
using the same port numbers which would cause issues. Previously, port numbers 15257 and
19004 were allowed.
f) An issue where clearing faults would incorrectly clear the faults
Integrity.ApplicationsHashFileMissing & Integrity.ConfigHashFileMissing has been fixed.
5) Event Logger:

An issue whereby remote audio sources triggered by microphone buttons displayed Mic 0 instead of
Mic <input number> has been fixed.
6) PAVA SCT/FTT/Dynamic Tools:
a) Fixed routes (contact, microphone buttons, VOX) can now be either self-cancelled, or externally
cancelled, but not both.
Note that selectable route can still be both self-cancelled and externally cancelled.
b) An issue whereby retrieving/rolling back the dynamic settings would not update the Fader/Mute
settings for DVAs without changing tabs has been fixed.
c) DVA pages on VIPEDIA-12 Dynamic Configuration Tool are now hidden if not configured and
Only Configured Inputs/Outputs is selected (via PAVA SCT > Preferences > Router Dynamic
Configuration Tool Display Mode).
4.27 V3.3.0.2-B
1) VIPA Host (VIPA Stack) - Host Control Protocol
An issue has been resolved that could result in stuck zone busy state in rare circumstances when
using a VIPA HOST with Host Control Protocol.
2) NA
4.28 V3.3.0.2-A
1) VIPEDIA-12
a) An issue where remote Dante sources were not routed to the listen-in mixer has been fixed.
b) An issue where Vipedia IP microphones could not be routed to the listen-in mixer has been
sorted.
This issue affected IP microphones with:
(IP unit-id - 64) = unit-id of the Vipedia hosting the listen-in microphone.
c) An issue where the listen-in audio mix was not always updated with IP microphones/IP WMC
music input on override/restore has been fixed.
d) An issue with DVA load where DVA messages too large to fit into the first available space (after
erasing a DVA file) could corrupt or delete other DVA messages has been fixed.
e) An issue where corrupt DVA flash (due to a fixed DVA load issue present in previous releases)
could cause the DSP to get stuck causing Vipedia reset has been fixed.
f) An issue whereby Dante microphone could fail to override non-Dante sources routed to Dante
outputs has been fixed.
g) An issue whereby the VA status for Dante zones could be incorrect for Dante sources overriding
non-Dante sources has been fixed.
2) Network Card:
a) An issue whereby V2000 units removed from the PAVA SCT configuration could reappear in the
status tree after VCT config load has been fixed.
The same issue affected the SIP configuration.
b) The default Network Card config, /dva/config/default.cfg, has been updated and can now be used
to restore the Network Card to factory defaults.
You can install it either by copying it from the Network Card to a PC and using VCT or by login via
serial or ssh and running "vipet_setup --config=/dva/config/default.cfg --host=vnet-default".
Note that neither way reverts the SCT settings back to default values. To accomplish this, you will
have to delete the file /dva/config/device-config.xml before restoring the VIPA config.
3) Microphone (non-NAV PTT builds only):
An issue whereby selectable route and listen-in could not be activated from the LCD display menu has
been fixed. This issue affected switched microphones with zones assigned to the PTT. A PTT event
was triggered instead of activating the selectable route or listen-in.
4.29 V3.3.0.1-D
1) Microphones (MAC address C0:BA:E6:00:>=50:yy):

a) The main board bootloader has been updated to fix an issue where the microphone could lock up
in bootloader mode after failed firmware update.
b) The main board bootloader has been updated to fix an issue where incorrect MAC address
(OUI:FFFFFF) was used briefly during boot.
This issue caused long reconnection time on Vipedia IP microphones after firmware update via
Ethernet, requiring a Vipedia fault clear to quickly reconnect the microphone.
It now uses the correct MAC address, and Vipedia fault clear is no longer required to restore
comms after firmware update.
2) NA
4.30 V3.3.0.1-C
1) PAVA SCT:
a) An issue whereby deleting a Vipedia from the system configuration also deleted all zoneless SIP
accounts has been fixed.
b) An issue whereby the SCT crashed when importing a VCT config with missing Network Cards has
been fixed.
c) An issue whereby the SCT added V2000 units to all Network Cards in a DBB group has been
fixed. This caused multiple instances of V2000 faults on iVENCS.
d) An issue whereby the input type selector on On-Board GPIO would be partially obstructed by
invisible widgets when the window width was too small has been fixed. All windows can no longer
be made smaller than the width after which widgets start to overlap.
2) NA
4.31 V3.3.0.1-B
1) Network Card:
The Network Gateway is now correctly displayed on Vipedia front panel (NET-VIPA V3.1.0.42 or
later).
2) VIPEDIA-12:
Issues whereby, under certain circumstances, DVAs larger than the available memory could be
incorrectly installed have been fixed on DSP V3.3.0.1 (or later). This issue could cause existing DVA
messages to become corrupted.
4.32 V3.3.0.1-A
1) Network Card:
An issue where local and remote outputs could get stuck out of sync with default Network Card
Latency (compensation delay) has been addressed.
2) VIPEDIA-12:
a) Contact/microphone button routes:
An issue where Vipedia could reset if it was reset or config was loaded with multiple active
contexts (i.e. contact/button routes) has been addressed.
b) Event Viewer:
An issue where mic id was used in routing events in the Information column has been fixed.
Microphone routing events now shows the input number.
Note that remote sources triggered by microphone buttons will display ‘Mic 0’ not the input
number due to current limitations.
c) Multiple clusters:
An issue where VIPEDIA CFG MISMATCH, critical fault indication (!) and hardware bypass state
could leak across clusters during config load has been fixed.
The hardware bypass issue caused emergency microphones to enter ALL CALL ONLY mode with
no faults present in the cluster. Once in this mode, normal operation could only be restored by
rebooting the Vipedia.
If same VA Group is assigned to multiple clusters, VIPEDIA CFG MISMATCH, critical fault
indication (!) and hardware bypass state can still leak across clusters during config load. However,
a fault clear should clear the faults and restore normal operation.

If unique VA Group is assigned to each cluster, VIPEDIA CFG MISMATCH, critical fault indication
(!) and hardware bypass state should not leak across clusters during config load.
d) V2000 Lamp Test:
An issue where the Vipedia LAMP TEST did not test the V2000 LEDs has been fixed.
V2000 front panel LEDs and amplifiers’ select and fault LEDs are now tested by Vipedia LAMP
TEST.
Note that the amplifier level LEDs and V2000 fan are not tested by the LAMP TEST. V2000 fan is
tested by pressing the FAULT CLEAR key on Vipedia front panel.
3) Microphone:
a) An issue where ALL CALL ONLY was not displayed on request of Vipedia in hardware bypass
due to DBB audio or comms fault has been fixed.
b) An issue where serial dual interface microphones did not work correctly when same number of
critical faults (!) were present on the attached Vipedia(s) has been fixed.
4) V2000:
An issue where the amplifiers would not wake if the V2000 was powered up without Ethernet comms
to attached Vipedia units has been fixed.
4.33 V3.3.0.0-A
1) VIPEDIA-12/Microphone:
a) The MPS unit Id on IP microphones is now updated by Vipedia if the MAC address is configured.
Both Vipedia and microphone should be V3.3.x.x or later. Both are compatible with previous
releases.
b) Timing issues on microphone PTT timeouts have been fixed.
2) VIPEDIA-12-PRO:
A problem where local and remote Dante outputs were out of sync has been fixed. Network delay
compensation will not be applied to Dante enabled inputs.
3) Network Card – SIP:
a) Store&Forward now works correctly.
b) An issue whereby SIP service would stop if live announcement was overridden whilst playing
chime has been fixed.
c) An issue whereby SIP in Menu mode did not work correctly with zoneless accounts has been
fixed.
4.34 V3.2.0.4-A
1) VIPEDIA-12
a) An issue where zone faults of V400/X400 connected to DBB outputs were intermittently displayed
on microphones has been fixed.
b) An issue whereby Mute did not mute (override) remote outputs has been fixed.
c) The following issues with multiple WMC01 units attached to a single Vipedia unit have been fixed:
• Source names incorrectly loaded
• DVAs and Local Input (3.5mm jack) could not be cancelled
• Volume control not applied to DVAs and Local Input (3.5mm jack)
d) An issue whereby comms fault to one IP microphone blocked access to all other IP microphones
attached to the same Vipedia unit has been fixed.
a) Issues whereby IP microphones in dual mode not reporting comms faults could not work after
config load/host disconnection&re-connection/reboot have been fixed.
These issues affected IP microphones attached to VIPA redundant-instances and Active Standby
Redundant systems.
2) MPS
b) An issue where Key Protected or Button Name was not displayed for busy zones has been fixed.
c) The full range of Vipedia Netmask and Gateway can now be loaded into the IP microphone (if
MAC address is in the PAVA SCT configuration).

The microphone validates the Netmask and Gateway against its IP address. The MPS Gateway
will be set to 0.0.0.0 if not validated.
3) V2000
Issues that could prevent amplifier power up at low temperature have been fixed.
Requires PSU V7.11.0.0.
4) INTEGRA Frame
An issue whereby battery detection could take long has been fixed.
4.35 V3.2.0.3-A
1) VIPEDIA-12:
a) An issue where concurrent access to microphone local data could cause slowness and
unexpected reset on certain configurations has been fixed.
b) An issue introduced on DSP V3.2.0.2 where input 12 chime playback silenced DVA playback
(including chime on other inputs) has been fixed.
2) PAVA SCT:
GPO support has been disabled pending GUI design review.
3) VIPEDIA-12 Dynamic Tool
An issue whereby a spurious iVENCS database connection message and an additional tab (Broadcast
Event Log) could be displayed on some machines has been fixed.
a) A problem whereby the gate settings in the Audio Settings page would retain the values of
previously visited amplifiers has been fixed. The gate settings now retain their own values
correctly.
b) The gate attack in the Audio Settings used to incorrectly show “Attack (0.1ms)”. It now shows
"Attack (ms)".

5 Known Issues
5.1 Microphones
a) TRL (Transactionless Routing) not working on MPS.

b) VIPA MPS controlled by third-party (typically via SIL) or OEM gateway:
If no microphone buttons are configured in the VCT config:
• The bargraph will be stuck (bottom two LEDs lit)
• HOST COMMS LOST may be intermittently reported by the MPS
Ensure a button that is only accessible from the display is configured as zone select to a dummy zone.
If required, the “Select Zones” on the MPS display can be removed by enabling the “PTT All Call”
option for the MPS in the VCT config.
c) MPS Ethernet connection may be intermittent if microphone/wall-mount controller is connected to
Vipedia/V2000 ETH1/ETH2 causing MIC COMMS fault.
This issue may affect units with Serial Number 1500 xxxxxx yyy onwards and MAC address
C0:BA:E6:00:xx:yy.
Firmware update via Ethernet will fail and units will not start up. It may be possible to recover the unit
by loading the firmware via USB port.
d) MPS-A USB firmware loader is not compatible with Windows 10. If required, contact ASL.
e) MPS-A: Firmware update via Ethernet on Windows 10
If the host PC has multiple network interfaces, ensure the other network interfaces are temporarily
disabled as they may prevent the firmware update on MPS-A.
f) MPS-B: Firmware update may time out in the presence of multicast traffic on certain addresses
(depending on amount of traffic). Resetting the microphone may fix the issue. Isolating the target
microphone from the PAVA system normally fixes the issue.
5.2 Network Card
a) Local and remote outputs may be out of sync for a few seconds. The outputs should go back in sync.
If they get stuck out of sync, reboot the Network Card (or power cycle the Vipedia unit).
b) NETCARD CFG MISMATCH fault may be reported after a configuration update. This is a
synchronisation issue that is corrected after a while but because faults are latched, a fault clear is
required. There is no danger in clearing them because if they are real faults, they will be re-raised
almost immediately.
c) Refer to ASL if ETH3 to ETH5 are required to be used in a loop configuration.
d) The Network Card may not receive multicast UDP packets from multiple multicast addresses with
same value in the last octet (for example, multicast addresses 239.x.x.1 ).
e) If configuration load fails when no networking/configuration issues are present, power cycle the unit
and load the configuration again. Configuration load may fail due to a rare condition where the disk
cannot be set back to read-only mode.
f) SIPS (SIP Secure) scheme is configurable but is not currently supported.
g) VNET AUDIO FAULT 4:0 may be spuriously reported when routing is slow. FAULT CLEAR should
clear the fault when the audio is eventually routed.
h) The Network Card may rarely fail to access the disk. The symptoms include unclearable VNET
OFFLINE fault on boot up, configuration load failure, local DVA broadcast failure, etc.
The Network Card may recover after powered down for a couple of minutes.
i) If a Dante Network Card is rebooted, the Dante Rx Channels on other units may not carry audio with
working IP connection to the unit.

Power cycling the Network Card that was rebooted restores the Dante Rx channels on the other units.
j) Network Card issue 2 – Image V3.0.0.3P or later:
• ETH3 and ETH4 in loop configuration only works if an SFP module is fitted to ETH5/6.
• Downgrade to V2.1 requires RSTP to be disabled using V3.3 or later. Otherwise, the Network
Card will reboot continuously.
k) Network Cards may reboot after hostname changes especially whilst connected to the Event
Viewer/Logger. The reboot will be caused by a memory leakage and may take hours. If this happens:
i. Disconnect all PCs running Event Viewer from the PAVA network (if any).
ii. Power cycle the Network Cards.
iii. Restart the PCs running Event Viewer (if any).
iv. Reconnect the PCs to the PAVA network.
l) SIL/third-party interface: Analogue input routing (micx) will fail if VA Global Status is enabled.
5.3 VIPEDIA-12/INTEGRA
a) Fixed route microphone button routing a non-local source with external cancel turns off local select
LED if that button is pressed. No other effect should be evident.
b) Spontaneous DVA MISSING fault is not currently supported for remote DVAs configured on
Selectable Route. If missing, DVA MISSING is still reported when Selectable Route remote DVA is
activated.
c) # 13844: Working serial microphone may have slow response to button press and Speak Now delay if
comms is lost to other serial microphones.
Working IP microphone may have slow response to button press and Speak Now delay if comms is
lost to other IP microphones.
d) AS Redundant systems without RCB are configurable, but these are not fully supported by the
VIPEDIA-12.
e) DANS attenuation may be incorrect after configuration load that changes previous existing DANS
configuration. The issue may appear when DANS input faults are present. Power cycling the Vipedia
restores the correct DANS operation.
f) DANS attenuation is applied to ANS/DANS disabled routes if routes are to non-DANS outputs only.
g) After fixing zone faults, multiple fault clears may be required to clear zone fault indications on
microphones.
h) Volume of routes controlled by a Volume Control (VC) or a WMC01 is reset to max volume after
retrieving/rolling back the Vipedia dynamic configuration (or rebooting the Vipedia).
Changing the settings on the volume control device applies the correct volume level.
i) The front panel may freeze if comms to a V400/X400 frame is lost whilst a READ menu of the
disconnected frame is selected.
Workaround: Cause new faults or accept/clear faults from the Network Card (i.e. VCT) or another
Vipedia. Power cycling the Vipedia will also fix the issue.
j) Spurious FRMxxx AMPyy ROUTE FAIL faults may be reported very occasionally if routes are made
whilst commissioning the V2000/INTEGRA Amplifier Frame.
k) Audio may be cut off when the Voltage Limiter is disabled and the amplifier is overdriven.
l) The DSP may lock when changing the EQ settings on the RDT. If that happens, power cycle the unit.

5.4 AS Redundant VIPEDIA-12
a) The following features are not supported by Network Cards in an Active Standby (AS) Redundant
Vipedia system:
i. File synchronisation (rsync) and transfer
ii. BGM
iii. SNMP
b) Artefacts may be present in listen-in audio on IP microphones attached to Vipedia.
c) Systems with AS redundant and non-redundant units:
i. Global indications (e.g. “system” fault, class faults) on Backup unit are not propagated to non-
redundant units, and vice-versa.
ii. Microphones in AS redundant system should not have the “EN 54 Microphone Operation”
setting enabled. If enabled, EN 54 microphones may be overridden by lower/equal priority EN
54 microphones.
iii. Zone fault LEDs on VIPA microphones will flash on/off for non-redundant zones.
d) The “system” fault LED and class faults on MPS hosted by non-redundant devices (Network Card,
VIPA Host, etc.) alternate between on & off when the system contains AS-redundant units and non-
redundant units.
5.5 Event Logger
a) ID column is treated as text, not as number.

b) Configuration and firmware filenames with more than 40 characters are truncated.
c) The Unit ID always shows vip-01 for contact input/output state change events irrespective of the
physical or configuration location of the contact.
d) The Event Viewer does not fully support the display of events from AS redundant systems.
e) Event Viewer database may be filled in (maximum 10000 events) quickly in large systems with
multiple contact inputs and outputs that are frequently operated.
Workaround: Ensure the maximum number of events is configured (default = 3000). If the database is
likely to be filled in quickly, make backup copies at required intervals.
f) HCP firmware update event does not show firmware version if firmware is loaded using the Update
Manager Tool.
g) The Event Logger does not support VIPA events (e.g. VIPA routes, Network Card firmware update,
etc.).
It does log faults from MPS microphones attached to a Network Card (new ASL serial microphone
protocol is required).
h) Vipedia can only show up to 65 outputs in Destinations.
i) The Event Viewer hasn’t been updated to show the updated front panel display for the following faults:
Front Panel V4.2.0.8L (or newer) Event Viewer V3.1.0.6P

Faults > Log > Router menu option VIPEDIA12 Front Panel field
VNET NTP NO SYNC VNET OS FAULT 3:5
VNET NTP NO SERVERS VNET OS FAULT 3:4
VNET NTP DAEMON OFFLINE VNET OS FAULT 3:3
VNET NTP BAD SYNC VNET OS FAULT 3:6
VNET TIME SET FAILED VNET OS FAULT 3:13
VNET TIME SET FAILED VNET OS FAULT 3:14

5.6 PAVA SCT/FTT
a) The Cluster Overview currently does not show the multicast address/port used for listen-in on IP
microphones attached to a Vipedia unit or used by internal processes/other applications (normally
hard-coded multicast addresses/ports).
b) The Auto option for the Local IP Address on the FTT is not saved in Preferences.
c) PAVA SCT may crash whilst navigating across BMB units. Therefore, periodically make a copy of the
configuration.
d) Dual interface microphones: It is configurable to route over Dante. However, dual microphones will not
work correctly if set to route over Dante.
5.7 V2000
a) A 250Hz sinewave with +1dB (or more) in the amplifier fader may cause the RCD to trip and fault be
reported.
b) Audio distortion when D150/D500 amplifiers are driven to their maximum voltage.
c) Main only V2000: the AUX OUT level is about 20 V when the V2000 is powered up with front panel
BATTERY switch OFF. Units powered from the AUX OUT may not power up depending on the load.
Workaround: Power the mains only V2000 with BATTERY switch ON. You can now turn the
BATTERY switch off - The AUX OUT level will remain at 24 V.
5.8 RDT (Router Dynamic Configuration Tool):

Reset button (or double click on control knob) does not always restore factory default value (ASL0701-
2324/2423).
Parameter Factory Default Reset Double

(V3.3.x.x) Button Click
Inputs Gate Attack 0.1 ms NA 10 ms
Hold 25 ms NA 100 ms
Release 50 ms NA 250 ms
Compressor Ratio 2.0:1 NA 1.0:1
Attack 0.1 ms NA 10 ms
Limiter Attack 0.1 ms NA 10 ms
EQ Band 2 500 Hz 2000 Hz 2000 Hz
Global Settings Surveillance Generator 1 Level -30 dB NA 0 dB
Outputs Limiter Attack 0.1 ms NA 10 ms
Surveillance Generator 1 Level -30 dB NA 0 dB
Clipper Level -2 dB NA 0 dB
Override Gain -16 dB NA -15.5 dB

5.9 Lanner, Linutop, iPAM400, etc. (VIPA Stack):
a) Vipedia zone faults are not displayed on VIPA microphones if default control multicast address
(239.1.0.1) is used (since VIPA Stack V3.1.1a).
b) Redundant pairs:
vipet_setup must be used to load the configuration into a VIPA Host (or Server) that is configured as
slave unit of a redundant pair. The VCT can be used the first time the configuration is loaded into the
VIPA Host (or Server).
c) Outputs on on-board and external sound cards:
The heartbeat support hasn’t been implemented for dtmf-routerd as expected.
This causes zones allocated to outputs on on-board and external sound cards to report Error after a
couple of minutes of the application startup. The Error is not self-recoverable, and announcements to
these zones will fail.

6 Warnings
6.1 Software and Firmware Update
1) The components of this release package may not be inter-compatible with older releases. ALL units
within a given system MUST use the versions listed on this release note
2) After installing this version, you MUST re-upload the configuration via SCT and/or SCT. Failure to do
so could lead to incorrect behaviour.
3) Downgrading V2000/INTEGRA FROM this version to other release branches (V3.0.1.x or V2.0.x.x)
MUST go via the following version (if not a fatal error will occur and the Frame will not boot
correctly):
MUST install V2.0.30.4L before target version.
4) Updating V2000/INTEGRA Amplifier Frame from V2.0.x.x or V3.0.1.x will cause dynamic settings to
be erased. Please ensure they have been extracted and backed up to XML file (via the Dynamic
Config Tool) before updating. Settings can then be re-injected.
5) V2000/INTEGRA Frame code V3.0.2.0P or later is incompatible with LSZDCs earlier than V3.0.2.0P.
6) After an FPGA and/or DSP firmware, IP address, ID or Multicast Low IP Address change, a power-
cycle is required for changes to take effect.
7) Downgrading VIPEDIA-12/INTEGRA Router to versions older than V3.1.0.x will erase the DSP and
FPGA.
8) You should not downgrade the NET-VIPA to a 2.17.x.x version older than 2.17.5.30. If you wish to do
that, then you must first downgrade to 2.17.5.30 and downgrade to an older 2.17.x.x version.
9) You cannot downgrade NET-VIPA to a 2.18.x.x version. If you wish to do that then you must first
downgrade to 2.17.5.30 and then upgrade to 2.18.x.x version.
10) Network Card Manager V1.2.0.8P (or later) must be used when updating Network Card Issue 2.
11) Downgrading a Network Card issue 2 with Image V3.0.0.3P or later to NET-VIPA V2.1 requires RSTP
to be disabled using V3.3 or later. Otherwise, the Network Card will reboot continuously.
6.2 EN 54-16 Systems
The following features MUST NOT be used for emergency broadcasts (messages and microphone
announcements) in EN 54-16 systems:
• IP microphones
• HCP Host Protocol
• Pulsed contact inputs (BMB or local)
• V2000-48V
• Functions hosted by the Network Card or other VIPA devices, such as:
- Microphones
- Contact routing
- SIP
- VIPA clients
- iVENCS
- TTS (Text to Speech)
- External Dante sources
• Disable LED button on emergency microphones
• VAVE

6.3 VIPEDIA-12
1) IP MIC comms with MPS-A will not restart for 30 minutes if firmware IP update is performed and on
same network as the host Vipedia. This is due to MPS boot loader mac address change from
bootloader to operation. If you clear the faults after the firmware update, the IP comms will restart after
a few seconds.
This issue is not present on new microphones/WMC wall mount controller units with MAC address
C0:BA:E6:00:>=50:yy and C0:BA:E6:04:xx:yy.
2) Vipedia Ethernet comms may not operate correctly if comms is lost to 7 or more IP microphones.
3) If using fixed route microphone button trigger with multiple DVA sources, then all sources of DVAs
sources should be hosted on the same Vipedia and ideally on the same Vipedia as the microphone.
4) A fault clear after MIC COMMS fault may be required to set the Vipedia gateway/netmask on IP
microphone attached to a VIPEDIA-12 (requires MAC address in the PAVA SCT microphone
configuration).
5) Listen-in:
a) Only fully supported for local outputs
b) IP Listen-in is streamed by the Vipedia unit, not the Network Card
c) Occasional audio clicks in the IP Listen-in
d) PMC audio sources may not be routed to the mixer
e) PMC audio sources may not be restored in the listen-in mix if completely overridden
f) Slave DBB unit operation of PMC Listen-in not fully supported.
6) A static configuration must be loaded before DVA messages can be routed to the front-panel speaker.
6.4 V2000
1) It is advised to go back through and re-check each V2000 Dynamic Tool tab is correct before finishing
the commissioning steps and disconnecting the tool.
2) It is advised to manually type DC-EOL values when commissioning using the V2000 Dynamic Tool,
even if the current value looks correct.
3) The V2000 Dynamic Tool may lose connection to the V2000 if configuration or firmware is updated.
Refresh by changing slot tab or re-connecting.
4) A few fault clears may be required to clear RCD and AMP FAIL faults.
5) Disallowed routes in battery only mode:
There will be a period of breakthrough for a “disallowed” route because amplifiers are held awake for
7 seconds when a route closes (to ensure any delay in the Vipedia Output is compensated for).
Thus, if there is no delay in the Vipedia output, there will be up to 7 seconds breakthrough after a
“valid” announcement. Whereas, if the Vipedia output is set to 5 seconds delay, there will be
5 seconds of breakthrough before the “valid” announcement (plus potentially a burst of up to
2 seconds after the “valid” announcement) before the amplifier is again slept.
6.5 WMC01
Zones should not be shared between multiple WMC01 units as this may result in stuck routes.

6.6 Update Manager Tool
1) The tool can only update MPS firmware if unit’s MAC address is C0:BA:E6:00:<50:yy.
2) Configuration load (Install Config) using the Update Manager should not be used as the configuration
will not be loaded into the Network Card. If the Network Card is not correctly configured, the Vipedia
may continually reset its Network Card.
3) The Update Manager V2.0.0.0P(or newer) can update devices via gateway. The PC running the
Update Manager must have been configured correctly for connections via gateway.
6.7 Network Card Manager Tool
It is not advisable to use the Network Card Manager to configure network cards with NET-VIPA 3.3.1.56 or
newer. It will not work correctly if the VIPA configuration has conflicts with the existing PAVA configuration.
Use the FTT for all configuration updates.
6.8 Multiple Cluster Systems
Each cluster should be assigned a unique VA Group in order to prevent fault status leakage across
clusters.
Note that VA Group is individually assigned to a VIPEDIA-12 in the PAVA SCT configuration. All units
within a cluster should be assigned the same VA Group which should be unique in the entire PAVA
system.
6.9 Microphones
Ports 15256 and 15356 should not be assigned to UNIT IP PORT or CTL IP PORT.
6.10 V2000 LSZDC
LSZDC hardware build standard 08 or newer must not be downgraded to firmware older than DSP
V5.0.2.5P / DSP Bootloader V5.0.2.4P. If older version is required, contact ASL.

7 Notes
7.1 General
1) PMC audio routing requires Network Card for operation. This includes PMC audio routing to/from DBB
slave units and from IP microphones hosted by a VIPEDIA-12.
2) Avoid multicast addresses in the ranges: x.0.0.y, x.0.1.y, x.128.0.y, and x.128.1.y
It is particularly important to avoid using any address in the ranges x.0.0.y, x.128.0.y, x.0.1.y, or
x.128.1.y (where x is 224-239 and y is 1-254). This is because x.0.0.y and x.128.0.y will map to the
same multicast MAC address as 224.0.0.y. Similarly, x.0.1.y and x.128.1.y will map to the same
multicast MAC address as 224.0.1.y. Most addresses in the ranges 224.0.0.y and 224.0.1.y are
reserved for contacting all routers, or for routing protocol messages, so they are always flooded out all
ports in the relevant VLAN. Therefore, all addresses in the ranges x.0.0.y, x.128.0.y, x.0.1.y, or
x.128.1.y are flooded out every port in the relevant VLAN. Using these addresses can significantly
increase multicast traffic in your network.
3) Assign System PMC Base Multicast to a higher port and address (by at least 256) than the Multicast
Low address and port as audio channels are assigned from the System PMC Base Multicast e
address and ports upwards.
For example, choose System PMC Base Multicast assignments from 239.2.2.0:18000 and Multicast
Low: 239.2.1.254:16000.
4) Do not use the following Multicast Port, as they are for internal user of the PAVA system and tools:
15356, 15357, 15358, 15359, 19001, 19003 and 19004.
5) The Transfer Tool when launched from the PAVA SCT V3.0.x.x can only be used for configuration. A
stand-alone Transfer Tool is required for firmware update.
For EN 54-16 compliance firmware changes can only be done at access level 4 which must be
restricted to persons trained and authorised by ASL to alter the firmware.
6) VIPA Config Tool (VCT):
Where existing CFG files are being updated with the VIPA Config Tool for the first time, it is
recommended to load the existing config(s) into the config tool and save them unaltered to get the
current configuration in the same order as is produced by the config tool, this enables easier
comparison when using a diff tool (e.g. winmerge, beyond compare).
7.2 VIPEDIA-PRO/INTEGRA-PRO
DANTE only supported for analogue inputs (miscellaneous input, microphone input or serial WMC01 local
music input).
7.3 WMC01 Wall Mount Controller
WMC01 Wall Mount Controller:

Serial WMC01 uses ROUTER 2 port for serial and music output connection.
Note that until the unit is set as Wall Controller, it will use ROUTER 1 port for serial connection just like a
microphone.
Refer to the WMC01 User’s Manual (U-0664-0833) for commissioning instructions.

7.4 Microphone
1) Continuous audio mode (MISC SETTINGS > PMC MIC STREAM and AUDIO UNGATED) is
incompatible with Chime and Store and Forward – these should not be configured simultaneously.
If set simultaneously with continuous audio mode:
• Chime: Chime is not played
• Store and Forward: Message is not recorded and the playback cannot be cancelled.
2) Microphone Config Utility:
i) Do not configure more than ONE microphone.
ii) Do not set the Auto Configure option on the Config Utility.
iii) <default-mic><port> must be 15256.
3) It is not possible to change MISC SETTIGS settings from the MPS/EMS Configuration menu (cogs
button) if the microphone is in host control mode, i.e. configured by the host (Vipedia or VIPA). Power
cycling the microphone with no comms to the host Vipedia will set the microphone back to normal
mode.
4) VAR MODE must be enabled for operation with VAR Routers.
7.5 Network Card
1) The software uses several UDP ports relative to the router control port for various functions. The port
offsets used are:
• -1 : unicast messages for communication with its host Vipedia (vipedia-d process).
• -2 : unicast or multicast fault reports.
• -3 : unicast messages for Vipedia GPIO controlling VIPA audio sources (vipedia-gpio-d process).
2) Hybrid route mode:
• The Listen-In PMC is streamed by the VIPEDIA-12 and not by the network card. The inputid
attribute of the listen-in element in the config file is ignored.
• Only 7 of the 16 network outputs are available for VIPA routing so you can’t have more than 7
simultaneous announcements. That means you can’t have more than 7 distinct sources whether
they are DVA files or PMC streams routed to the VIPEDIA-12.
• Permanent routes: Vipedia analogue input or output to PMC
• This is configured by creating a PMC device with a static PMC output and assigning the audio
group VipediaInput<X> or VipediaOutput<X> to it where <X> is the number of the input or output,
1 to 12.
• Dynamic routes: Vipedia analogue input to PMC only
• This is configured by creating a PMC device with a number of dynamic PMC outputs. How many
outputs depends on which input you want to use and they should match. So, for example, to route
analogue input 12 you must setup a PMC device with 12 outputs. The PMC device MUST be the
very first PMC device because that is what announce-d uses. Each PMC output must have a
pm<X> audio group where <X> is 1 to 12.
• Note that analogue inputs/outputs 9-12 can only be routed with NET-VIPA V2.18.0.24 (or later).
• Permanent routes from PMC sources to analogue outputs are not supported.
3) Static route mode is no longer supported
4) Listen-In supports both VIPEDIA-12 mixers but with the following limitations:
• You can only configure 1 listen-in ‘channel’ in VCT. The second listen-in ‘channel’ will use the
same PMC port, PMC channel & priority. It will use the other mixer and the IP address specified
by the VIPA client requesting the listen-in. This means that the other mixer can only be used if
both mixers have an output type of PMC.
• The selection of listen-in ‘channel’ is based on which interface VIPA clients use. If they use the
interface without an IP address, then the first listen-in will be used (the mixer configured via VCT)
and if they use the interface with an IP address then the second listen-in will be used.

• When a VIPA client adds zones to the second listen-in ‘channel’, the specified IP address will
override the IP address used. This means that if two VIPA clients request the second listen-in
‘channel’, the second request will override the first but the first client will not be notified.
• You must ensure that all network cards must use NET-VIPA 4.2.0.79P or later and all VIPA
devices use VIPA Stack 4.2.0d or later. Failure to do so may cause issues with listen-in
5) Hostname:
• A valid hostname consists of a series of dot-separated labels whose total length does not exceed
255 characters.
• Each label must be between 1 and 63 characters long and contain only alphanumerical characters
(a-z, A-Z and 0-9) and the minus sign ('-'). For compatibility, labels must not start with a digit or a
minus sign and must not end with a minus sign.
• Capital letters should not be used in the hostname.
6) TTS (Test To Speech) requires:
• An appropriate license and installation of TTS-D-NET-VIPA software package.
• A “Text to Speech” module in Network Card configuration (VCT)
7) HTTP-hosted DVA:
Unlike other VIPA devices, HTTP-hosted DVAs are not available by default. A “Text to Speech”
module must be added to the network card in VCT for the service to be available. Note that this will
not enable the text-to-speech functionality unless you have acquired the appropriate license and
installed the TTS-D-NET-VIPA software package.
7.6 UIP V1.2.0027
1) Displays message when DIP SW 1 and/or 2 are enabled:

• DIP1 set, erasing NVM
• DIP2 set, erasing config
• DIP1&2 set, erasing NVM & config
2) Allows faking DIP SW 1 and 2 using front panel keys during startup (if DIP SW 3 is enabled)
• Fake DIP1 = Left + DEFAULT + AUDIO MON
• Fake DIP2 = Down + DEFAULT + AUDIO MON
• Fake DIP1&2 = Right + DEFAULT + AUDIO MON
Notes:
• Fault Clear = Clear any pending erase
• Always power cycle the unit after erasing config.
3) Matches default display contrast mode with application
4) Changes “INTERNAL ERROR - No Host Processor Comms” to “INTERNAL ERROR - Limited HW
bypass mode functionality”
5) Allows display of UIP version during startup (if SELECT key is pressed)
6) Allows displaying VIPEDIA-12 or INTEGRA during startup according to DIP SW 4 setting (up =
VIPEDIA-12 / down = INTEGRA).
7.7 V2000:
1) Power-Saving Mode has been disabled due to causing occasional faults (since V2.1).
2) Amplifier fault LED may flash briefly when route is made due to a hardware artefact.
7.8 Network Card Manager V1.2.0.12P (or newer)
Site Password is only required for V5 Network Cards with protection/security.

7.9 NTP Status Indication on Vipedia Front Panel (V4.2 and newer)
THIS UNIT’S NAME 11:33:28

: FAULTS 0/0/0
Rotates time, time zone and date.

If NTP synchronisation error is present, the time zone
display alternates with a textual NTP error matching
the indication at the bottom left corner (“:” / “.”):
• !LCL TS: Local NTP synchronisation error
• !SYS TS: System NTP synchronisation error
Time and date format and NTP status indication:
• “12:34:56” and “01/03/23”:
The system time is synchronised.
First character: blank if no error or fault in the system. For NTP errors, check the indication at the
bottom left corner (“:” / “.”).
Error or fault indication:
• “12?34?56” and “01/03?23”:
: Local unit NTP synchronisation error: also
displayed in the front panel Faults>Summary This Vipedia has not yet received time, date, and
option time zone information from its Network Card.
Normally displayed on startup and is local only.
The VCT status tree and the front panel
Faults>Log>Router option provide details of the Will remain until the unit synchronises with a
errors. These are transient errors and are not primary or secondary time master.
latched. • “12:34?56” and “01/03?23”:
. System NTP synchronisation error The primary time master (or secondary if the
This unit has no time synchronisation errors but primary time master is down) has not
one or more units in the system have. synchronised to an external NTP server. System
wide and only displayed in systems with an
The units with NTP errors can be identified in the external NTP server.
front panel Faults>Summary option.
Note that a VIPA Host (V-SUITE) and/or VIPA
! It indicates a critical fault is present within this unit Server can configured as external NTP servers.
or in its DBB connection. This indication overrides
any NTP error indication.

8 User Documentation
This is the reference user documentation for this release package:
1) INTEGRA User’s Manual (U-0732-0051)
2) VIPEDIA-12 User’s Manual (U-0641-3283)
3) PAVA SCT User’s Manual V3.x (U-0701-1583)
4) V2000 User’s Manual V3.x (U-0623-1005)
5) Firmware and Configuration Load Procedures V3.x (U-0641-3036) (if required).
6) SIP Configuration Guide (U-0701-1497)
7) Event Viewer User’s Guide (U-0641-3133)
8) Dante Configuration Guide (U-0641-3466)
9) Active Standby Redundant System Configuration Guide (U-0641-3090)
10) Microphone and Wall-Mount Controller (Type A and Type B) Firmware Update Procedure
(U-0664-1005)
11) MPS User’s Manual V3.x (U-0664-1007)
12) VIPA Microphone (Serial Protocol) Configuration Guide (U-0582-4379)
13) VIPEDIA-NET Network Card - VIPEDIA-12 / INTEGRA Contact Inputs Configuration Guide
(U-0582-4644)
14) EMS01 User’s Manual V3.x (U-0664-1009): to be published
Use EMS01 User’s Manual V1.7 (U-0664-0465) until above document is published.
15) EMS10/20/50 User’s Manual V3.x (U-0664-1008): to be published
Use EMS01 User’s Manual V1.7 (U-0664-0464) until above document is published.
Please refer to the “New Features” and “Changes and Improvements” above for an overview of the new
features and changes.
Refer to ASL downloads page for latest revisions of all user documentation.
www.asl-control.co.uk/downloads

9 EN 54-16
The released software package is suitable for incorporation in EN 54-16 systems.
The following features MUST NOT be used for emergency broadcasts (messages and microphone
announcements) in EN 54-16 systems:
1) IP microphones
2) HCP Host Protocol
3) Pulsed contact inputs (BMB or local)
4) V2000-48V
5) Functions hosted by the Network Card or other VIPA devices, such as:
• Microphones
• Contact routing
• SIP
• VIPA clients
• iVENCS
• TTS (Text to Speech)
6) External Dante sources
7) Disable LED button on emergency microphones.
8) VAVE

VIPEDIA-12 V4.2.0.8L Package A RNote 2023-03-09

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VIPEDIA-12 V4.2.0.8L Package A RNote 2023-03-09

Uploaded by

Copyright:

Available Formats

Application Solutions (Safety and Security) Ltd

Unit 17 Cliffe Industrial Estate

SOFTWARE RELEASE NOTE

VIPEDIA-12_V4.2.0.8L_Package_A_RNote.docx (09/03/2023) Page 1 of 113

VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount Controllers/VIPA Devices/Tools V4.2.0.8L – Package A

1 Software Release Package

1.1 Software Version

1.1.1 VIPEDIA-12/INTEGRA Router

1.1.2 V2000/INTEGRA Amplifier Mainframe

VIPEDIA-12_V4.2.0.8L_Package_A_RNote.docx (09/03/2023) Page 2 of 113

VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount Controllers/VIPA Devices/Tools V4.2.0.8L – Package A

1.1.3 VIPA Devices (VIPA Server, VIPA Host, iPAM400, etc.)

1.1.4 Microphones (MPS/EMS/VRMS4/SAP03/SAP04/ATEX) and Wall-Mount Controllers (WMC01)

VIPEDIA-12_V4.2.0.8L_Package_A_RNote.docx (09/03/2023) Page 3 of 113

VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount Controllers/VIPA Devices/Tools V4.2.0.8L – Package A

1.1.7 Notes and Warnings

VIPEDIA-12_V4.2.0.8L_Package_A_RNote.docx (09/03/2023) Page 4 of 113

VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount Controllers/VIPA Devices/Tools V4.2.0.8L – Package A

Audinate® is a registered trademark of Audinate Pty Ltd.

VIPEDIA-12_V4.2.0.8L_Package_A_RNote.docx (09/03/2023) Page 5 of 113

VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount Controllers/VIPA Devices/Tools V4.2.0.8L – Package A

[31] Network Card MAC Address:

1.2 Software Details (Filename and Checksum)

1.2.1 VIPEDIA-12/INTEGRA Router

VIPEDIA-12_V4.2.0.8L_Package_A_RNote.docx (09/03/2023) Page 6 of 113

VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount Controllers/VIPA Devices/Tools V4.2.0.8L – Package A

1.2.2 V2000/INTEGRA Amplifier Mainframe

1.2.3 VIPA Devices (VIPA Server, VIPA Host, iPAM400, etc.)

VIPEDIA-12_V4.2.0.8L_Package_A_RNote.docx (09/03/2023) Page 7 of 113

VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount Controllers/VIPA Devices/Tools V4.2.0.8L – Package A

1.2.4 Microphones (MPS/EMS/VRMS4/SAP03/SAP04/ATEX) and Wall-Mount Controllers (WMC01)

VIPEDIA-12_V4.2.0.8L_Package_A_RNote.docx (09/03/2023) Page 8 of 113

VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount Controllers/VIPA Devices/Tools V4.2.0.8L – Package A

Components Language Filename Checksum (MD5)

VIPEDIA-12_V4.2.0.8L_Package_A_RNote.docx (09/03/2023) Page 9 of 113

VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount Controllers/VIPA Devices/Tools V4.2.0.8L – Package A

Components Filename Checksum (MD5)

VIPEDIA-12_V4.2.0.8L_Package_A_RNote.docx (09/03/2023) Page 10 of 113

VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount Controllers/VIPA Devices/Tools V4.2.0.8L – Package A

VIPEDIA-12_V4.2.0.8L_Package_A_RNote.docx (09/03/2023) Page 11 of 113

VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount Controllers/VIPA Devices/Tools V4.2.0.8L – Package A

q) Vipedia Host /V2000 Frame Secure Bootloader V5.0.0 (secure):

VIPEDIA-12_V4.2.0.8L_Package_A_RNote.docx (09/03/2023) Page 12 of 113

VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount Controllers/VIPA Devices/Tools V4.2.0.8L – Package A

2.1.2 Danish Language Support (VIPEDIA-12 V4.2.0.7P / MPS-B V4.3.0.5P or newer)

Danish language is now supported on Vipedia and MPS-B front panels.

2.1.3 Vipedia Host / V2000 Frame Bootloader V4.0.0/V5.0.0

See “3.1.8 Vipedia Host / V2000 Frame Bootloader V4.0.0/V5.0.0”.

VIPEDIA-12_V4.2.0.8L_Package_A_RNote.docx (09/03/2023) Page 13 of 113

VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount Controllers/VIPA Devices/Tools V4.2.0.8L – Package A

1) fan stop temperature = trip temperature -

2) The fan control output must be an on-

• PSU Fan Trip (°C): 60

• PSU Fan Trip (°C): 70

2.2.2 Placeholder for the next item

2.4.1 AS Redundant System - SIP (NET-VIPA V4.2.0.81P) (SysAid #21486)

VIPEDIA-12_V4.2.0.8L_Package_A_RNote.docx (09/03/2023) Page 14 of 113

VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount Controllers/VIPA Devices/Tools V4.2.0.8L – Package A

2.5 V4.2.0.5P-D (pre-release to Production)

2.6.1 Vipedia Host / V2000 Frame Bootloader V4.3.0

VIPEDIA-12_V4.2.0.8L_Package_A_RNote.docx (09/03/2023) Page 15 of 113

VIPEDIA-12/INTEGRA/VNET/V2000/Microphones&Wall-Mount Controllers/VIPA Devices/Tools V4.2.0.8L – Package A

VIPEDIA-12 LCD display in bootloader mode:

• " * Application Bad Checksum * "