Release Notes
4.13 Release Notes
4.13.30
6 min
ameyo contact center patch release notes version 4 13 30 release date 2025 02 23 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 component versions component version/build tag change summary ameyo server 4 13 586 (r 182589) tomcat upgrade, app sdk, bug fixes note only components with significant changes are listed full build details are available in internal documentation feature enhancements 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 document link https //exotel atlassian net/wiki/spaces/ecc/pages/280002973/app+sdk+api 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 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 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 autoselectextension api calls (sl 16368) fixed an issue where autoselectextension api was called multiple times unnecessarily when the allowmultiplevoiceextensions license was disabled 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 security and performance updates tomcat version upgrade (ga 14461) upgraded the embedded apache tomcat library from version 9 0 0 to 9 0 98 to address potential vulnerabilities limitations / known issues dual extension app sdk refer to the limitations listed under feature enhancements dual extension ui/functionality known issues persist regarding inconsistent ui states (e g , extension fallback scenarios, multiple extensions appearing), call handling (stuck calls in specific inbound scenarios), and data reflection in crm tabs after linking customers 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
🤔
Have a question?
Our knowledgeable support team and an awesome community will get you an answer in a flash.
To ask a question or participate in discussions, you'll need to authenticate first.