Skip to main content

Cloud Storage Integrations

Cloud Storage Integrations allow you to store call recordings and voicemail messages in your preferred cloud storage solution.

This feature is particularly useful for accessing recordings and voicemails directly through Call Analytics all while maintaining a centralized storage location for all your communication records.

Cloud Storage Integrations interface showing available storage options

Overview​

The system supports several cloud storage providers:

  • Internal cloud storage
  • Amazon Web Services (AWS)
  • Microsoft Azure
  • MinIO
note

Only one cloud storage integration can be active at a time. You'll need to disconnect any active integration before connecting a different one.

Internal Cloud Storage​

The internal cloud storage option provides a straightforward solution that requires no additional configuration. When enabled, your recordings are automatically stored and accessible through the system.

Key Benefits​

  • No external credentials needed
  • Immediate setup and availability
  • Integrated with call history
  • Automatic management
warning

Call recordings stored in the internal cloud storage are retained for a maximum of three months.

AWS Integration​

Amazon Web Services (AWS) integration allows you to store recordings in your own S3 bucket.

Configuration Steps​

  1. Sign in to your AWS Management Console

  2. Locate your S3 bucket information:

    • Navigate to the S3 service
    • Note your bucket's region and name
    • Ensure proper bucket permissions
  3. Get your IAM credentials:

    • Access IAM in AWS Console
    • Create or select an IAM user
    • Generate access keys
    • Note the Access Key ID and Secret Access Key
  4. Connect in the phone system:

    AWS connection configuration form

    Enter your AWS details:

    • Bucket Region (e.g., us-east-1)
    • Bucket Name
    • Access Key ID
    • Secret Access Key

Azure Integration​

Microsoft Azure integration enables storage of recordings in your Azure Blob Storage account.

Configuration Steps​

  1. Access your Azure Portal

  2. Get your storage account details:

    • Navigate to Storage Accounts
    • Select or create an account
    • Create a container if needed
  3. Locate your credentials:

    • Go to Access Keys under Security + networking
    • Copy your storage account name
    • Note your access key
    • Record your container name
  4. Connect in the phone system:

    Azure connection configuration form

    Enter your Azure details:

    • Storage Account Name
    • Storage Access Key
    • Container Name

MinIO Integration​

MinIO provides an alternative self-hosted object storage solution compatible with the S3 API.

Configuration Steps​

  1. Set up your MinIO server

  2. Gather your credentials:

    • MinIO server endpoint
    • Bucket name
    • Access key ID
    • Secret access key
  3. Connect in the phone system:

    MinIO connection configuration form

    Enter your MinIO details:

Managing Active Integrations​

Once configured, your active integration will be displayed at the top of the page:

Active cloud storage integration status

Integration Status​

  • Green dot: Integration is active and working
  • Status text: Shows current connection state
  • Disconnect button: Remove the active integration
tip

Before switching to a different storage provider:

  1. Download any important recordings
  2. Disconnect the current integration
  3. Configure the new provider

Best Practices​

  1. Storage Management

    • Monitor storage usage
    • Implement retention policies
    • Back up important recordings
    • Review access permissions regularly
  2. Security Considerations

    • Use dedicated storage accounts
    • Implement least-privilege access
    • Enable encryption when available
    • Regularly rotate access keys
  3. Performance Optimization

    • Choose geographically close regions
    • Monitor access patterns
    • Configure appropriate storage tiers
    • Test integration thoroughly
warning

Ensure your chosen storage solution has sufficient capacity and appropriate security measures in place. Lost recordings cannot be recovered if storage limits are exceeded or access is revoked.