Voice Logger and Archival (VLA)

the voice log archiver (vla) is an automated system that fetches, converts, encrypts, and stores call recordings it ensures that voice logs are retained for extended periods (up to 8 years) without impacting the performance of the active contact center archival process workflow the vla operates through a four stage process to ensure data integrity and security fetching the system monitors the ameyo call server in real time new voice logs are identified and downloaded to the archiver server with a typical lag of only 20–25 minutes conversion raw audio files (separate in/out streams) are first converted to wav format the streams are mixed into a single wav file the file is compressed into mp3 format to optimize storage encryption the compressed files are secured using aes encryption a unique key is generated for each voice log and stored in the archiver database storage the final encrypted files are transferred to a mounted network drive (nas/san) via ftp user interface & search the vla console provides a centralized interface for supervisors and administrators search & retrieval supervisors and administrators can locate specific recordings using a combination of standard and advanced filters on their interface standard filters date range, campaign, queue, user/agent, customer phone number, and talk time call content filters call notes search for keywords within the notes added by agents qa scoring filter by "scored" or "unscored" calls dispositions filter by system or user dispositions advanced search allows attribute based queries using operators (e g , credit card number equals 1234) downloads single/bulk download users can download individual files or select multiple records to download as a zip file format downloads are typically provided in mp3 format for easy playback configuration & administration administrators have access to system level settings via the configuration tab audio controls ingain / outgain adjust the volume levels for the input (customer) and output (agent) audio streams values range from 1 to 9 presets select audio processing presets such as high phone, low phone, high voice, or low voice to optimize audio quality based on the source storage path define or update the destination directory on the nas/san storage reload applies changes made to the call server configuration without restarting the system monitoring & safeguards the system includes built in health monitoring to prevent data loss or server crashes disk usage protection the system continuously monitors disk space if free space falls below 5 gb , the fetching process stops automatically administrators must manually resume the service after clearing space execution details the monitoring tab displays the real time status of the "conversion" and "fetching" jobs operational guidelines prerequisites licensing separate licenses are required for voice log archiver infrastructure dedicated archiver server (windows/linux) network storage (nas/san) accessible via ftp/mapped drive ameyo call manager (for vla) and ameyo database access sizing considerations proper sizing is essential for performance factors influencing server requirements include total agents and calls per day average call duration retention period (e g , 1 year vs 5 years) recording format (mp3 compression ratio) retention & cleanup data lifecycle data is retained based on the configured policy (e g , 3 years) auto cleanup the system can be configured to automatically purge data older than the retention period to free up storage, though archival to external media is recommended before purging per tenant retention overrides (4 13 48+) administrators can configure per tenant voice log retention periods via the server preference store , overriding the global default the minimum retention is 3 months a nightly cleanup job automatically purges recordings that exceed the configured retention window number masking in voice logs when number masking is enabled at the process level, voice log filenames on the call server are masked by default the following controls are available reveal real numbers (4 13 9+) authorized users with the appropriate privilege can click an eye icon in the vla console to temporarily reveal the actual phone number associated with a masked recording unmasked filenames on call server (4 13 26+) the unmaskrawvoicelogs system configuration flag, when set to true , writes voice log files on the call server with the real (unmasked) filename while the ui continues to display masked values this is useful for integrations that rely on filenames matching actual phone numbers unmasked filenames in vla storage (4 13 38+) the unmasked filename behaviour was extended to recordings archived by vla, ensuring downstream systems consuming archived files also receive unmasked filenames token based voice log download api starting from version 4 13 25, a token based download api is available for secure programmatic access to voice log files external systems (crm, analytics, compliance tools) can request a short lived download token and use it to retrieve recordings without requiring a full ui session this is the recommended approach for automated integrations version history version enhancement release notes 4 13 9 authorized users can reveal real numbers via eye icon when masking is on 4 13 9 release notes docid 9nxxiuvss1xlp1svj ghj 4 13 25 token based voicelog download api for secure integrations 4 13 25 release notes docid 9qp nrj2vi08aiiqkvhp 4 13 26 unmaskrawvoicelogs flag for unmasked filenames on call server 4 13 26 release notes docid\ aftf0pmqlovldq f8wkot 4 13 38 extended unmasked filename behaviour to vla stored recordings contact center patch release notes version 4 13 38 docid\ pkcoa9s 8fugrj3c5jiv4 4 13 48 per tenant retention overrides (min 3 months, nightly cleanup) contact center patch release notes version 4 13 48 docid\ ohmti dqxjpuejrdrcdz0