Release Notes
4.13 Release Notes
Contact Center - Patch Release Notes - Version 4.13.44
11 min
release details release date 7th jan 2026 this document outlines the feature enhancements, bug fixes, and other updates included in the ecc 4 13 44 patch release summary this patch release focuses on improving system stability through enhanced version management and security updates key improvements include automated version synchronization during upgrades to prevent configuration mismatches and stricter validation during agent login the release also addresses critical bugs in voice operations, supervisor monitoring, and user interface performance to ensure a smoother customer experience build versions key versions included in this release are component build url ameyo server ameyo server 4 13 608 20260102 r 255329 x86 64 rpm ameyo art ameyo art 4 13 98 20260102 r 255296 x86 64 rpm note release marked in bold has the change only, other releases has no change and are same delivered in last patch cycle, thus listed in the previous release articles features enhancement automatic version updates during appserver rpm install/upgrade (ga 128) in this release, the app automatically writes and updates the correct version number (build tag) across key areas—like backend config files, ui toolbar, and database—whenever you install or upgrade the appserver rpm key improvements no more manual version updates needed prevents outdated ("stale") version info after upgrades ensures consistent version display everywhere for better tracking and reliability the script that loads ini settings into the database now checks for an existing release version key and updates it with the new build tag during install/upgrade this makes post upgrade access smoother and more dependable documentation https //exotel atlassian net/wiki/spaces/ecc/pages/1426620431/auto+cache+invalidation+for+4x+build+upgrades+ +toolbar (internal) server side version check in login api (ga 130) this release adds backend validation in the login api to catch client server version mismatches how it works server reads its version from config files (version props and dacxameyoproserverdefault ini) compares it to the client's version (sent in the login request) versions match? login continues normally versions mismatch? returns a specific error code so the client can detect the issue and respond (e g , prompt reload or upgrade) this prevents login problems from version gaps and ensures smooth compatibility handling client version sent in login api request (ga 129) this release updates the login api to include the client's version info in every request key changes client sends its version during login server detects mismatches and returns a specific error code to the frontend frontend can then clearly notify users (e g , "please upgrade to continue") this makes version incompatibilities obvious and guides users to upgrade smoothly before logging in security fixes fixed private ip exposure in api response (ga 17) issue the getalluserccpresence api was accidentally exposing private ip addresses in responses (flagged during existing customer setup assessment) fix resolved in the latest build private ips are no longer disclosed, improving security and compliance this change protects sensitive network details without impacting api functionality bug fixes system common bugs fixed source phone in call history for failed customer legs (ga 98) issue for calls with attempt failed disposition (customer not dialed), the call history always showed nodid in src phone, ignoring the configured did call context overwrite fix now correctly uses the did pool from campaign call context settings if a call id pool is set in the ui, it dumps the first did from the comma separated list in src phone for attempt failed calls this ensures accurate call history logging even when customer legs fail live monitoring now updates after tab switch (dca20251112704012) (sl 17749) issue agent duration in supervisor live monitoring froze when switching from workbench back to monitor tab fix the data refresh timer now restarts properly, keeping live monitoring data (like agent durations) updating at regular intervals no more stalled views—real time data flows seamlessly fixed postgresql connection leak causing zabbix alerts (dca20251209716962) (sl 17833) issue zabbix "transaction limit breached" alerts from postgresql max connections (1500) exceeded due to jdbc leak in voicelogarchiveruiservice fix leak resolved in latest art release build stable db performance—no more overload alerts fixed call context routing for non root contact centers (clone dca20230613265456) (ga 97) issue admins from contact centers (cc) other than ccid 1 creating call contexts for inbound campaigns saw calls wrongly routed to cc 1, causing failures fix call context routing now correctly sends calls to the cc where the admin created the context verified working in the latest build—proper routing restored voice fixed number masking after conference call leg ends (sl 17874) issue in conference calls, masked numbers showed correctly during the active call but after the first leg disconnected (call went to queued state), the agent toolbar revealed the actual phone number instead of staying masked fix masking now persists correctly through state changes fixed in latest release build agents see consistent masking—no more unmasking surprises enhanced callhungupstatus event for re acd scenarios (dca20251119707255) (sl 17773) update the callhungupstatus global event now includes laststatus—the call's state right before hangup (e g , ringing or connected) benefit helps distinguish hangups during ringing vs post connection, improving re acd handling on your end behavior is by design; sdk enhancement validated in latest build fixed preview dialer auto connecting before timeout (dca20251107702396) (sl 17734) issue in preview dialing, calls sometimes auto connected early—before their countdown timer finished—if a prior call was canceled mid countdown fix added proper active call validation now, each call waits for its full timeout before dialing reliable preview dialing, no more random early connections toolbar fixed number masking bypass in browser dev tools (dca20251205715552) (sl 17823) issue with number masking enabled, phone numbers were sometimes still visible in browser developer console logs or page elements fix client side masking strengthened—numbers now stay fully hidden in logs and elements when enabled better protection against accidental exposure via dev tools fusion(ic, chat, social media) chat campaign stats fixed on supervisor dashboard (sl 17853) issue supervisor dashboard showed blank chat campaign stats resolution fixed after app server restart not reproducible since debug logs added for monitoring under observation in latest app server build stats now display reliably vla fixed vla ui slowdown with large lead volumes (dca20250915681830) (sl 17568) issue voice log archiver (vla) ui lagged or stuck when loading with very large lead datasets, due to heavy client side processing of massive responses fix optimized for high volume scenarios sanity tested in latest art build vla ui loads smoothly tab switching works search modal opens fast better performance under heavy load ui/ux bugs blocked disposition bypass via keyboard/mouse (dca20251124710457) (sl 17791) issue agents could select dispositions (using enter key or clicking dropdown) even when campaign settings restricted it post call fix pointer events fully blocked on disabled disposition class dropdown—stops both mouse and keyboard workarounds campaign disposition rules now enforced consistently browser and platform compatibility chrome version version 143 0 7499 110 (official build) (arm64) contact support for issues or queries, please contact exotel contact center support via the support portal or through 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.