---
title: Contact Center - Patch Release Notes - Version 4.13.30
slug: contact-center/contact-center-patch-release-notes-version-41330
docTags: 
createdAt: 2025-10-24T10:16:02.754Z
---

# Release Details

**Release Date:** 23-Feb-2025

**Short description:** This release includes security hardening by upgrading the embedded Tomcat version, enhancements to App SDK for dual extension support, and various bug fixes related to login, SSO, Nodeflow, call handling, and UI behavior.

# Highlights / Summary

- **Tomcat Version Upgrade:** Upgraded the embedded Apache Tomcat library to version 9.0.98 for security improvements.
- **App SDK for Dual Extensions:** Enhanced App SDK functionalities to better support dual extension scenarios.
- **Login & Session Fixes:** Resolved issues related to agent login failures after upgrades, SSO configuration with Nginx, and session handling in high-load scenarios.
- **Call Handling Improvements:** Fixed issues with local IVR conferencing and WebSocket connections in multi-session WebRTC.
- **UI Fixes:** Addressed issues with WebRTC troubleshooter visibility and ACP access for Analyst roles.

# Build Versions

The following table lists the updated component versions for this release.

| Component    | Build URL                                                          |
| ------------ | ------------------------------------------------------------------ |
| ameyo-server | **ameyo-server-4.13.586.20250222-R\_182589-linux-gtk.x86\_64.rpm** |

:::hint{type="info"}
**Note - **Release mentioned in the above table has a change, other releases has no change and are same delivered in last patch cycle
:::

# Feature Enhancements

- ***Tomcat Version Upgrade (GA-14461):*** Upgraded the embedded Apache Tomcat library from version 9.0.0 to 9.0.98 to address potential vulnerabilities.
- ***App SDK Enhancements for Dual Extensions (EN-141606):*** Implemented changes in the App SDK to provide better support and functionality for agents using the dual extension feature. Documentation [Link](https://exotel.atlassian.net/wiki/spaces/ECC/pages/280002973/App+SDK+API) (Internal)
  - **Limitations:** Includes known issues related to parameter consistency (`userCrtObjectId` vs `userCRTObjectId`), method testing coverage, and UI data reflection post-link customer actions.

# Bug Fixes

## System Common Bugs

- `autoSelectExtension`*** API Calls (SL-16368):*** 

Fixed an issue where `autoSelectExtension` API was called multiple times unnecessarily when the `allowMultipleVoiceExtensions` license was disabled. This issue has been fixed in this app server build.

- ***Agent Login Failure (SL-16619):***

Resolved a deadlock scenario where a failed message handling during server restart could block subsequent login attempts for the affected user ID. In the Ameyo framework, if a message is added to the queue but fails to be handled, its thread remains in a WAITING state indefinitely. Here, the session service thread locked the user ID, but due to a **component not found exception **(as the app server had just restarted), the message became a zombie, staying in a **WAITING **state since midnight on Dec 31. This blocked other operations for that user ID, as all other threads entered a **BLOCKED**state while waiting for the lock to be released. This issue has been fixed in this app server build.

- ***SSO with Nginx (SL-16559):*** 

Fixed an issue where SAML SSO URLs were incorrectly formed with HTTP instead of HTTPS when Nginx was used as a reverse proxy. Introduced a system flag `should.override.protocol.for.saml.if.nginx.present` to enforce HTTPS.

- ***Central Registrar Configuration (SL-16651):***

 Removed the 30-character limit for the `proxy_server_host` column in `vr_pr_settings` table, resolving API failures during configuration.

- ***Local IVR Nodeflow (SL-16678):*** 

Corrected the logic in call context creation UI to select the correct Routing Profile ID, fixing failures when conferring calls to local IVR.

- ***Campaign Call Connection (SL-16775):*** 

Addressed an issue preventing calls from connecting in a specific campaign configuration.

## Toolbar

- ***Multi-Session WebRTC Stability (SL-16679):*** 

Resolved a race condition in WebSocket connection handling during campaign changes that could lead to call failures (480 error) in Multi-Session WebRTC setups.

## UI/UX

- ***WebRTC Troubleshooter Visibility (SL-16620):*** 

Fixed an issue where the WebRTC Troubleshooter option disappeared after changing campaigns.

- ***ACP Access for Analyst Role (SL-16649):*** 

Corrected an issue where the Control Panel (ACP) tab was not visible for users with the Analyst role after SSO configuration.

# Limitations / Known Issues

- *GA-14704 || After selecting the extension fallback, both WebRTC and the extension start appearing on the Executive screen* 

  *GA-14703 || On the Executive & Supervisor screen sometimes 3 extensions appear *

  *GA-14702 || Call Getting stuck in case of Dual Extension Inbound Calling*****
  ****
  *GA-14706 || After the link customer, if I switch ameyoCrm tab, data is not reflecting on ameyoCrm tab.*

# Browser and Platform Compatibility

- **Supported Browsers:** Chrome Version 132.0.6834.110 (Official Build) (64-bit) or later is recommended.
- **Mobile Apps:** No updates in this patch.

# Contact / Support Information

For issues or queries, please contact Ameyo Support via the support portal or designated email channels.