/mcpCisco Emergency Responder Version 15 Release Notes First Published: 2023-12-18 Last Modified: 2025-05-05 Introduction Cisco Emergency Responder Release 15 supports the following new features: Migration of All Applications to 64-Bit System Release 15 brings an enhanced experience for users and administrators with major platform upgrades to align with the industry standards. Enhancements include Application-layer changes and core Linux transition for long-term support. This enhancements also includes transition to 64-bit application architecture for removal of memory bottlenecks and mitigating end-of-life for 32-bit dependencies. This release provides enhanced protection, security, innovation, and flexibility. Some of the important considerations when installing or migrating to Release 15 are: • Emergency Responder 15 requires a minimum ESXi version of 7.0 U3 or 8.0 U1 (see https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/ virtualization-cisco-emergency-responder.html) with a minimum VM Hardware version 17. The other required VM specifications like guest OS type may be found in the Readme of the base OVA on software.cisco.com. • Updated vRAM considerations for Release 15 of Emergency Responder. See Cisco Emergency Responder 15x Supported Upgrades, on page 28 for more information. • Direct Refresh Upgrades from Pre-12.5.x source to Release 15 is not supported. You must first upgrade your source to Release 12.5.x or 14 and SUs and then upgrade your source to Release 15. • Virtual Floppy Drive is replaced with virtual CDROM for touchless installation. • IPSec policy with 3DES Algorithm is not supported in FIPS mode for Release 15 in case you are planning to upgrade to Release 15. You must delete and recreate the IPSec policy with the Encryption and ESP Algorithms other than 3DES in both the nodes between which the IPSec tunnel is to be established, and then plan an upgrade. Enhanced Security Considerations From Cisco Emergency Responder Release 14 onwards, all the certificate-related operations are moved from IPsec to Tomcat certificates. To create a trust between a publisher node and subscriber node, the Tomcat certificate should be exchanged between the publisher and subscriber for any cluster-related operations to work. From Release 14SU2 onwards, if you need to perform manual or scheduled DRS backups or if you Cisco Emergency Responder Version 15 Release Notes 1