Contact Center - Patch Release Notes - Version 4.13.53

release details release date 2nd june 2026 build versions key versions included in this release are component build url ameyo server ameyo server 4 13 629 20260601 r 312746 linux gtk x86 64 rpm ameyo art ameyo art 4 13 110 20260602 r 313421 linux gtk x86 64 rpm management server ameyo management server 3 15 128 20220819 r 53820 x86 64 management ui ameyo management server ui 3 15 79 20220825 r 54354 x86 64 ameyo asterisk ameyo asterisk13 100 0 123 20230202 r 54429 el7 linux gtk x86 64 rpm ameyo asterisk13 100 0 122 20230201 r 77845 el8 x86 64 rpm ameyo asap ameyo asap 100 0 19 20210708 r 53436 linux gtk x86 64 rpm ameyo asap 100 0 31 20231212 r 122778 el8 linux gtk x86 64 rpm ameyo djinn ameyo djinn 100 0 411 20250115 r 176400 x86 64 rpm ameyo codec ameyo codecs13 100 0 10 20180312 r 37320 i386 rpm ameyo codecs16 3 10 1 20150917 linux gtk x86 64 rpm ameyo crm ameyocrm 100 0 379 20240516 r 54694 x86 64 rpm jdk java 1 8 0 amazon corretto devel 1 8 0 312 b07 1 x86 64 rpm caf google play store caf googleplay 100 0 37 20231011 r 112974 x86 64 rpm caf youtube caf youtube 100 8 0 20230904 r 54528 x86 64 rpm ui less integration zoho connector zoho connector 100 0 36 20230817 r 104650 x86 64 rpm ui less integration zoho user management zoho crm connector 100 0 10 r 54327 aaex wfm nice response transformation app nice connector app 100 0 13 r 54375 aaex amf (whatsapp, cogno, instagram) amf 100 0 272 20250916 r 54869 x86 64 rpm voicelog privilege app voice log privilege app 100 0 61 r 54105 aaex dial user app dial user app 100 0 31 r 51344 aaex system smart view app smart user app 100 0 135 r 54858 aaex pick call app pick call app 100 0 36 r 51381 aaex bulk operation app bulk operation 100 0 48 r 51285 aaex desktop notification app notificationapp 100 0 29 r 52192 aaex agent signature app agent signature app 100 0 27 r 51283 aaex agent self monitoring app agent self monitoring 100 1 98 r 51265 aaex redirection app redirectionapp 100 0 3 r 51489 aaex quota app quota management app 100 0 74 r 54362 aaex skill monitoring app skill monitoring app 100 0 14 r 54167 aaex routing test app routingtest 100 0 1 r 54180 aaex debugger app debuggerapp 100 0 7 r 54338 aaex acp acp 100 1 92 20231130 r 120901 x86 64 rpm amd ameyo amd16 100 0 31 20210521 r 52916 linux gtk i386 rpm zabbix ameyo zabbix 100 0 127 20221115 r 63336 el7 x86 64 rpm ameyo zabbix agent 100 0 54 20210617 r 53204 x86 64 rpm failover ameyo failover 100 0 29 20230504 r 89111 x86 64 rpm video micro service video 4 13 110 20240304 r 133174 x86 64 rpm voice agent mobile app android voice agent app 5 7 5 r ios voice agent app 3 3 field agent mobile app android field agent app 5 4 r ios field agent app version 3 3 supervisor mobile app android com ameyo supervisor 2 1 20210812 release apk ios moved to live on apple store grafana grafana 7 1 4 1x86 64 rpm sfdc integration app crm integration 100 0 8 r 54454 aaex note release marked in bold has the change only, other releases have no change and are the same as delivered in last patch cycle features list routing & configuration en 1519 || enable priority reordering for call routing profiles in multicc ui multicc managers can now set the evaluation order of system routing profiles directly from the multicc ui, so the routing rules that matter most are applied first on inbound calls managers can reorder call routing profiles on the system routing screen (call routing → system routing) using up/down controls apply saves the new order with confirmation and password authorization list order = routing priority the profile at the top is evaluated first en 1110 || call context distribution at cc level in multicc manager multicc managers can view, assign, and unassign call contexts to contact centers from the multicc manager web ui call contexts are the sip channels used for voice traffic previously this could only be done through the legacy java client this release moves the workflow into the multicc manager ui for faster, auditable context assignment en 1942 || certify routing test allow testing of inbound routing routing test helps validate routing before or after configuration changes, providing clear pass/fail results for each test case, identifying where calls are routed (profile, node flow, campaign), and reducing support tickets caused by incomplete or incorrect routing setup platform & infrastructure en 1333 || hybrid log rotation and retention ameyo ecc now rotates and compresses application logs automatically and retains them for 10 days, reducing disk full risk and making troubleshooting easier the platform uses a hybrid log rotation policy with automatic 10 day retention so logs stay available for troubleshooting without uncontrolled disk growth en 1335 || tenant level channel restriction in ecc to prevent misuse 4x ameyo introduces tenant level channel restrictions so customers operate within their purchased or allocated channel capacity administrators can configure channel limits at the tenant level, and the platform enforces those limits in real time when calls are initiated this improves platform reliability in multi tenant deployments and reduces misuse/overutilization en 936 || publish micrometer based appserver business metrics ameyo now exposes business metrics from the app server using a micrometer based metrics framework, integrated with prometheus and grafana this provides operational visibility into live contact center activity faster incident detection through real time business kpis, better capacity and traffic monitoring (calls, campaigns, channels), and improved platform stability tracking reporting & analytics en 2080 || hiding columns with only null values in interaction details reports the interaction details report now automatically hides columns that contain only null or na values reports and csv exports include only columns with meaningful data, making analysis faster and exports more enterprise ready en 2081 || displaying deleted custom fields in interaction details reports the interaction details report now uses historical field accuracy when building report output reports reflect the fields that were active when the interaction data was captured, including deleted custom fields in historical date ranges en 1711 || user id masking in amplitude analytics events now use a masked (hashed) user identifier instead of raw user ids, with tenant and domain stored as persistent user properties for safer, more consistent reporting this strengthens privacy and security in product analytics (amplitude) across ameyo ccaas, voicebot, and platform agent & campaign management en 1753 || queue level custom field assignment queue level control over custom field assignment is now available, enabling contextual data capture and reducing manual effort admins can assign custom fields to specific queues so fields are only available where relevant a "copy custom fields to all queues" option is available in campaign settings (on by default), with system auto assign to all queues by default en 2324 || crm popup after connected during conference for conference participants, the crm panel now opens only after the call is answered and reaches the connected state crm is no longer triggered when the conference invitation is received this eliminates unnecessary crm/api activity for unanswered conference invitations and prevents crm from appearing before a participant joins the live conversation tech tasks na security fixes na benchmarking na debugging docs / sops monitoring tasks na limitations and known facts/issues in features customer reported and legacy bugs fix system common bugs sl 18173 || team members' lunch break auto removed issue agents in break status (lunch, tea break etc ) were incorrectly subject to the inactivity timeout mechanism in certain race condition scenarios, inactivity timers were not properly cleared, resulting in inactivity warnings and automatic logout during valid breaks enhanced the inactivity timeout handling to correctly exclude agents in break status from inactivity monitoring sl 18067 || error while transferring to feedback reopening the transfer popup during an active call could cause issues reinitializing the campaign selection component improved the select2 component initialization and cleanup logic with safer handling during component destruction, preventing errors when reinitializing across repeated popup open/close actions sl 18074 (sl 18047) || interaction details report issue users were unable to execute the default interaction details report because the run button remained disabled the report validation and button state handling have been corrected, allowing the run button to become active when the required report criteria are met sl 18267 || email body could not be displayed some emails failed to display their content because the mail server returned an invalid bodystructure response a fallback mechanism was introduced to fetch and parse raw email content directly, allowing the system to process affected emails even when standard body structure parsing fails sl 18178 || unable to download voicelogs from vla when encryption is enabled encrypted voicelog downloads were generating empty (0 kb) zip files due to a filename handling regression where encrypted audio files were always assigned an mp3 extension during processing, causing the decryption process to overwrite its own input enhanced the decryption workflow to use a temporary intermediary file during processing en 1119 || issue in format of number in rule engine fixed an issue where large numeric values (greater than 2,147,483,647) in rule conditions could be automatically converted to scientific notation (e g 2 147483647e9) when saved numeric values are now converted and stored according to the field's data type, so large numbers remain in the expected format sl 18120 || auto correct issue in whatsapp chat fixed an issue where auto corrected text could be sent incorrectly when agents used the enter key immediately after selecting a spelling correction the message editor now ensures that auto corrected text is synchronized before sending en 1126 || lead tagging with different id fixed a bug in auto dial with preview where using click to dial (ctd) from crm while a preview call was in progress could dial a different contact but attach it to the wrong customer while a preview call is active, ctd from crm is now blocked with clear ui feedback sl 18065 || ameyo call back to our system fixed to ensure the resolved did (caller id) can be passed to crm urls during manual dialing when using custom nodeflows, improving crm context and integration accuracy sl 18063 || unable to login in ameyo post patch upgrade activity fixed a login issue that could occur after upgrading to newer builds on deployments using custom startup configurations users can now log in successfully after upgrade activities, including deployments configured with custom ports and non default startup environments en 956 || vapt | sensitive info in url addressed a vapt finding where sensitive session information (session id and related identifiers) could appear in the browser url when agents opened embedded applications session identifiers can now be omitted from the application url when a contact center preference is enabled en 1006 || implement debouncing and button disable on email send reply action when an agent clicks send reply, the button is disabled immediately, and debouncing ensures only one send request is processed per action—even if the agent clicks multiple times quickly sl 17979 || i18n japanese language support in c019 dos several japanese language translations identified by the ips team have been corrected to improve localization accuracy across the platform the corrected language strings are included in both application (app server) ui components and reporting (art) components en 1523 || ecc 4 x – sast re scan findings security improvements based on a third party sast (static application security testing) re scan the re scan initially reported 41 open findings (27 medium, 14 low) all have been reviewed, remediated, or dispositioned, and the vendor re scan (seciq) confirms all issues are closed en 1714 || routing issue fixed an issue where custom configuration data saved through the custom configuration apis could be altered in the database when values contained single quotes or similar special characters sl 18042 (en 1735) || supervisor dashboard | total ticket count mismatch | petromin fixed a ticket count mismatch on the supervisor dashboard for email setups the issue occurred when agents sent outgoing emails including the campaign media profile email address in to, cc, or bcc, which could create invalid interactions counted as tickets sl 52 || customers mobile numbers visible in ameyo customer numbers remain masked on agent toolbar during click to dial and dispose when campaign client side masking is enabled fixed a privacy issue where customer mobile numbers could appear in clear text even when campaign client side masking was enabled en 1544 || dialers not dialing due to callmanagerconfiguration single threaded queue blocking | traya fixed a reliability issue where predictive dialers could slow down or stop placing calls when the platform was under heavy load (e g , during bursts of voice resource state changes or telephony resets) predictive dialers no longer stall when handling large volumes of voice resource and telephony events sl 18236 || data inconsistency in queue details (missing queuename for unanswered calls) | ather integration fixed to ensure that queuename and agentqueueid are correctly populated in post processing global variables for missed and transferred call scenarios, including transfer to campaign calls that went unanswered, auto dial missed calls, and click to call missed calls sl 18128 || get userdetails by username api failing receiving 2 crm urls | iiitb fixed when user a transfers a call to user b, only one crm push is sent with user b's correct credentials when user a confers with user b, one crm push is sent with both users' details when call ownership is subsequently transferred, a new crm push is sent with only user b's details en 1659 || extend lead to user dialing to support progressive mode 4 x progressive outbound campaigns can now use lead to agent mapping so each lead is dialed to the assigned agent when lead to user dialing is enabled on a progressive campaign, the system routes outbound calls to the agent mapped to each lead, instead of using standard progressive distribution ui/ux bugs en 1688 || caller leg disconnects if agent disposes the call during re acd phase fixed an issue where the customer's call could disconnect if disposecallforuser was used for an agent who had not yet answered the call (during ringing or re acd) the platform now validates that the agent was connected before allowing disposition the customer call continues when dispose is requested for a non connected agent, and re acd/post acd ivr behave as designed en 2315 || crm push behavior during conference fixed crm integration when an agent conferences a call to another user when user a conferences an active call to user b, the platform now sends one crm push with the correct details for user b (session id, user id, user crt object id), and also retains additional crm url parameters that were present when the call was first connected with user a browser version chrome version version 148 0 7778 179 (official build) (arm64) hot fixes