Skip to end of banner
Go to start of banner

Company Data Storage Procedure

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

This Procedure provides an overview of the storage changes in WMS 6.05, where user files are moved from local storage to Company Data Storage.

Created: November 2023

Permalink: https://wildix.atlassian.net/wiki/x/hQAMEw

Introduction

The Procedure explains the changes to the storage of user files in WMS 6.05. Starting from this version, files are stored in a dedicated storage system, Company Data Storage (CDS), within the same AWS region as a PBX is running.

This change is driven by several factors:

  • Change in Long-Term Storage Policy: We're updating the policy to offer our customers a centralized and scalable solution for system performance optimization

  • Improved Reliability: By moving to a dedicated storage, we aim to enhance system reliability

  • Improved Failover Capabilities: Storing files in a dedicated cloud environment improves the system's ability to switch to backup resources during disruptions

  • Preparations for Analytics and AI features: The change prepares the system for upcoming analytics and AI features

Implementation Overview

Cloud PBXs

The dedicated storage feature is enabled by default on Cloud PBXs running on WMS 6.05. After the update to WMS 6.05, an automatic migration process is launched to move existing data from the local storage to the Company Data Storage. During the migration, the following data is moved:

  • Call Recordings
    For users who have integrations that directly access recordings from PBX, we offer two options:

    • API for retrieving recordings: Access recordings through the API endpoint: GET /api/v1/pbx/recordings

    • 7 day local copy: A local copy of recordings is kept for seven days, ensuring continued access

  • Backups: The change includes the transfer of backups, ensuring the preservation and accessibility during disruptions

  • Voicemails and Faxes: Implementation for the shift of voicemails and faxes will be introduced in upcoming releases

Virtual and Hardware PBXs

Admins can activate this feature for Virtual Machine and Hardware PBXs. To enable it and transfer data to the CDS, you need to run the following script via Terminal:

/usr/sbin/sync_data_to_data_storage.php

Running this script initiates the migration process, ensuring that data is securely transferred to the CDS.

Implementation Timeline

The implementation of the dedicated storage feature is planned according to the following schedule:

  • WMS Beta 6.05: The beta version 6.05.20231129.1 is currently ongoing, released on November 30, 2023

  • WMS Stable 6.05: The stable release is planned for February 1, 2024 (ETA)

FAQ

Q1. Why are we migrating data to cloud storage?

The migration to cloud storage offers several benefits, including improved scalability, reliability, disaster recovery capabilities, and enhanced accessibility.

Q2. What types of data are being migrated to cloud storage?

The migration process includes call recordings, backups, and, in future updates, voicemails and faxes. These data types are moved from the local storage of PBX to the CDS in the cloud.

Q3. How will the migration process affect access to call recordings?

The migration process ensures uninterrupted access to call recordings. Users with integrations accessing recordings directly from PBX can use the API endpoint /api/v1/pbx/recordings to retrieve recordings. Additionally, local copies of call recordings will be kept on PBX for 7 days to ensure continued accessibility during the transition.

Q4. What will happen with local recordings after 7 days?

Local recordings will be automatically deleted from the PBX after this timeframe. The purpose of keeping local copies is to ensure continued access during the migration process.

Q5. Can the CDS be activated on VM/HW PBXs?

Yes, the feature can be activated on both standalone VM/ HW PBXs and as a part of WMS Network.

  • No labels