Contact Center - Patch Release Notes - Version 4.13.48

release details release date 23rd feb 2026 build versions key versions included in this release are component build url ameyo server ameyo server 4 13 623 20260219 r 274505 linux gtk x86 64 rpm ameyo art ameyo art 4 13 104 20260223 r 275748 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 laravel build zoho connector 100 0 36 20230817 r 104650 x86 64 rpm ui less integration zoho user management app zoho crm connector 100 0 10 r 54327 aaex wfm nice response transformation app nice connector app 100 0 13 r 54375 aaex amf for whatsapp, cogno and instagram integration 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 (voice agent 5 7 4 20211011 release apk) ios voice agent app 3 3 field agent mobile app android field agent app 5 4 r (ameyo fieldagent com 5 4 20230905 release apk) ios field agent app version 3 3 supervisor mobile app android supervisor app 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 has no change and are same delivered in last patch cycle features & enhancements en 706 ||ip and domain whitelisting for shared 4x stamps domain whitelisting behavior has been validated across multiple scenarios with and without gatewaypublicbaseurl configuration gatewaypublicbaseurl acts as a global override cc level whitelisting is validated only after global domain validation passes multi domain access on the same app server is not supported when a single gatewaypublicbaseurl is configured en 934/en 356||secure cloud mounting options for call recordings (key based sftp & iam based s3) evaluate secure and scalable alternatives to username/password based mounts for exporting call recordings to customer cloud storage current solution uses static credentials, which creates security risks, is not enterprise friendly and does not align well with compliance standards if the conclusion is that mount based solutions should be avoided entirely in favor of a more cloud native approach (e g , direct sdk based uploads), that is a valid and acceptable outcome documentation https //exotel atlassian net/wiki/spaces/arch/pages/1763606551/aws+s3+credential+process+integration+backend (internal) documentation https //exotel atlassian net/wiki/spaces/ecc/pages/1701544013/accessing+aws+resources+from+azure+vms+using+aws+sts (internal) en 365 ||per tenant configurable retention for voicelog & report archiver this release introduces tenant level retention configuration for voicelog archiver (vla) and report archiver key points tenant level configuration overrides system defaults minimum retention 3 months cleanup job runs daily at midnight if no tenant config exists, system behaves exactly as before no changes to cleanup logic, tagging logic, or audit/history behavior this enhancement improves multi tenant isolation and compliance flexibility without impacting existing behavior documentation https //exotel atlassian net/wiki/spaces/arch/pages/1642201092/per tenant+configurable+retention+for+voicelog+report+archiver+en 365 (internal) en 115||make exotel logos consistent across screens the exotel logo has been updated to ensure a consistent and unified brand experience across all platforms, personas, and user touchpoints this change replaces any previous versions of the logo wherever applicable notes this is a ui/branding consistency update only no functional changes are introduced as part of this update en 768 || implementation of help center icon on the ecc ccaas solution (4x & 6x) users can now access and interact with the help center documentation directly within the ccaas ui a help center icon is added across supported platforms, enabling contextual access to documentation via an embedded resource center powered by amplitude when amplitude is configured and enabled, clicking the help center icon opens the documentation portal within the application interface the resource center icon clicked event is triggered and tracked in amplitude this enhancement is expected to reduce user drop offs and minimize documentation related support tickets by providing quick, in product guidance security fixes en 675 ||4x source code scan medium and low severity fixes all encryption changes (voicelog, attachment, custom fields) maintain backward compatibility systems with mixed legacy and new encrypted data will continue to function without disruption customer reported and legacy bugs fix system common bugs en 881 || contact center inbound call routing automatic call routing profile & policy creation for administrator implemented enhancement to ensure that default routing profiles and routing policy entries are automatically created at the contact center (cc) level via multicc manager during new cc creation upon creating a new cc entries are auto created in cc routing profile and cc routing policy tables default routing configurations are visible under the call routing tab in admin ui (after campaign creation) sl 17976 ||sms notification after call disposition resolved an issue where multipart http requests (e g , exotel sms) were using the default client encoding (iso 8859 1), causing special utf 8 characters such as em dash (—) and curly quotes (’ “) to be replaced with ?, leading to incorrect sms content or failures encoding is now configurable, and http node resolves charset in the following order script variable httpmultipartcharset server preference http node multipart charset (system/campaign hierarchy supported) default behavior (unchanged if not configured) en 680||introduce flags for allowing special characters in userid/username introduced two new configurable server preference flags at contact center (cc) level to control allowed special characters in userid and username using regex validation allowed userid regex (default ^\[a za z0 9 @]+$) allowed username regex (default ^\[a za z0 9 '@ ]+$) these flags are configurable in server preference store with context type = 'contactcenter' context id = \<ccid> the system now validates user creation and modification based on the configured regex user creation via ui – working as expected user creation via bulk upload – working as expected userid remains non editable after creation username modification follows configured regex rules only allowed characters are accepted; additional special characters are rejected as per configuration en 692||sip entity ordering updated sip configuration handling to ensure correct ordering between statically configured and dynamically generated sip entities in sip conf static sip entities (e g , inbound calling, outbound calling) are now always placed above dynamically generated entities (e g , webrtc, kamailio, central registrar) since the topmost entity handles inbound calls, this ordering ensures static sip entities take precedence over dynamic ones dynamic sip entities (e g , webrtc \<userid>) are automatically added below static entries at server startup and user creation, and removed appropriately upon user deletion call context based sip entities are added above dynamic entries as expected en 1542||4x ||file descriptor fix an issue was identified in the 4x app server where file descriptors were not properly released while accessing configuration files (server props, jwtproperties, and jwtcertificates) as a result, enabling the 4x → 6x harmony mode configuration could lead to a gradual increase in open file descriptors (fds), potentially impacting application stability over time the issue has been resolved by ensuring all file streams are properly closed after use, preventing further file descriptor leaks voice na toolbar en 1381||callback scheduled for masked number from toolbar closed the issue after identifying that callback disposition was failing when toolbar masking was enabled and shouldallowalphabetsinphone was set to false since client side masking introduces alphabets in the phone field, validation during dispose call/callback scheduling fails if the flag is false to support masked numbers correctly, shouldallowalphabetsinphone must be set to true when masking is enabled after updating the configuration, callback disposition and scheduling are working as expected video cc en 456||spike video cc – twilio room type compatibility change identified a breaking change in twilio where newly created accounts no longer support the legacy group small room type, resulting in runtime failure during video room creation with error code 53126 this impacts new video cc onboarding and tenant migrations to fresh twilio accounts, as the current implementation relies on the deprecated room type ui/ux bugs sl 17910(sl 18009)||dca20260102727576\ unable to change extension getting error can't be modified fixed a ui issue where the autoprovisioningforallusers configuration was not handled correctly, causing an incorrect webrtc flow execution and triggering the change extension api with a null crt object id the ui logic has been corrected to ensure that the change extension api is invoked only when a valid crt object id is present (webrtc extension or configured call context based extension) the extension selection and post login extension change flows now work correctly across all configurations, including auto provisioning enabled/disabled and webrtc disabled scenarios sl 17903||dca20251229725766 || stars showing in phone1 field resolved an issue where agents could copy paste values containing special characters (e g , 12345) into the alternate number field during callback disposition, and the call would be disposed successfully with invalid data saved now, proper validation is enforced on the alternate number field (including copy paste cases), and the system prevents call disposal if special characters are present sl 17911||dca20260102727586 || unable to preview the customer information fixed an issue where the view customer flow was failing after campaign switch because the ui was sending campaignid = 1, resulting in a “voice campaign not selected” error the issue occurred as the agent dialer was not refreshing after a successful campaign switch, causing the old campaign data to be used in the flow now, the agent dialer refreshes immediately after campaign switch, ensuring the correct campaignid is passed to the api the fix applies to both agent and supervisor (workbench) flows, and the view customer functionality works correctly across scenarios en 906||restrict default ivr for transfer for agent in voice toolbar in the release build, the enhancement restricts the “default” ivr option in the toolbar transfer dropdown based on the campaign level flag adddefaultivrfeaturecontextsforcampaign (hidden when false), applicable only to inbound campaigns applicable only for inbound campaigns not applicable for outbound campaigns browser and platform compatibility chrome version \ version 145 0 7632 46 (official build) (arm64) contact support for issues or queries, please contact exotel contact center support via the support portal or through designated email channels