Skip to main content
Version: Latest
Technical Manual

Telephony - Azure Blob Storage for Recordings

Feature NameTelephony - Azure Blob Storage
Feature IDCrestApps.OrchardCore.Telephony.Azure

Provides an optional storage backend for the Telephony media store, which holds Contact Center call recordings and the master copy of every voice media clip (hold music, IVR prompts and agent voicemail greetings). When enabled and configured, the feature replaces the default local encrypted store with an Azure Blob Storage backend — while keeping the exact same encryption at rest.

Overview​

By default, call recordings and voice media master copies are stored on the local file system under a tenant-scoped application-data folder:

App_Data\Sites\<tenant-name>\RecordingMedia

Recordings are ingested there by any voice provider that records calls (for example Telnyx and Asterisk): the provider records the call on its side, and the provider-specific ingest downloads the finished recording into the store. A voice media clip is written there when it is uploaded on the Voice Media screen or recorded as an agent's greeting, and read back whenever a telephony provider has to be given a copy; see Voice Routing. The bytes are always encrypted at rest with the tenant data-protection key and are never stored inside the Contact Center orchestration data.

If you want those recordings to live in Azure Blob Storage instead, enable CrestApps.OrchardCore.Telephony.Azure.

What the feature changes​

When the feature is enabled and valid Azure settings are present:

  • call recordings and voice media master copies are written to Azure Blob Storage instead of the tenant application-data folder
  • the default IRecordingMediaStore file backend is replaced with an Orchard Core BlobFileStore
  • encryption at rest is unchanged: recordings are still encrypted with the tenant data-protection key before they are written to Azure, so Azure only ever holds ciphertext
  • Orchard Core can create the blob container automatically when the tenant starts
  • tenant-wide media cleanup on tenant removal continues to work (the encrypted store supports tenant purge)

If the Azure configuration is missing or incomplete, the default local encrypted storage remains active.

This feature changes only where the encrypted bytes are stored. Recording orchestration — start/stop/pause governance, recording-state events, right-to-erasure deletion, and audit — is owned by the Contact Center Call Recording feature (CrestApps.OrchardCore.ContactCenter.Recording) and is unaffected, as is the voice media provisioning that gives each telephony provider its copy of a clip. Live bidirectional media streaming (the Contact Center Voice Media feature) is a separate, ephemeral capability and stores nothing.

Getting started​

  1. Enable the Telephony - Azure Blob Storage feature in Orchard Core.
  2. Add the CrestApps:Telephony:AzureRecordings settings under the tenant's OrchardCore configuration section.
  3. Restart the tenant or application if needed so the updated configuration is applied.
  4. Record calls normally through the Contact Center Call Recording feature, and upload voice media normally; both land in the container.

Configuration​

Configure the feature under the Orchard Core shell configuration section:

{
"OrchardCore": {
"CrestApps": {
"Telephony": {
"AzureRecordings": {
"ConnectionString": "",
"ContainerName": "telephony-recordings",
"BasePath": "{{ ShellSettings.Name }}",
"CreateContainer": true
}
}
}
}
}

Settings reference​

SettingDescription
ConnectionStringAzure Storage account connection string.
ContainerNameAzure Blob container name. Supports Liquid, so recordings-{{ ShellSettings.Name }} gives each tenant its own container. See Separating tenants.
BasePathOptional subdirectory inside the container where recordings are stored. Supports Liquid, so a per-tenant path (for example {{ ShellSettings.Name }}) keeps tenants isolated within a shared container.
CreateContainerWhen true, the feature creates the blob container automatically if it does not already exist.

Separating tenants​

ContainerName and BasePath both accept Liquid, with the tenant's ShellSettings available, so one configuration in the root appsettings.json serves every tenant. There are two ways to keep tenants apart:

  • A container per tenant. Set ContainerName to a template such as recordings-{{ ShellSettings.Name }} and leave BasePath empty. Each tenant's recordings are in a container of their own, created automatically when CreateContainer is true, and access policies or lifecycle rules can be applied to one tenant at a time. Deleting the tenant purges its recordings, as described below, but leaves the empty container; remove it in Azure if you no longer need it.
  • One shared container. Keep a fixed ContainerName and set BasePath to {{ ShellSettings.Name }}. Every tenant's recordings are in the same container, separated by a folder prefix. Deleting a tenant purges only that tenant's recordings.
{
"ContainerName": "recordings-{{ ShellSettings.Name }}",
"CreateContainer": true
}

For a tenant named Contoso, this resolves to the container recordings-contoso.

The resolved container name is lowercased and must be a valid Azure container name: 3 to 63 characters, lowercase letters, digits and single hyphens, starting and ending with a letter or digit. A tenant name that breaks these rules, for example one with an underscore, resolves to an invalid name, and an error is logged when the tenant starts. Use the shared container for such tenants.

Encryption note​

Enabling this feature does not weaken recording protection. The same encrypted store that backs local storage is reused over the Azure blob backend, so every recording is encrypted with the tenant data-protection key before it leaves the application. Azure server-side encryption then applies on top of that ciphertext. Reads decrypt transparently for authorized right-to-access and playback paths.

Tenant removal and cleanup​

Removing a tenant purges that tenant's recording blobs through the base Telephony recording-media cleanup, which blocks tenant removal until the purge completes. The container itself is not removed, whether it is shared through a per-tenant BasePath or belongs to one tenant through a per-tenant ContainerName. An emptied per-tenant container can be deleted in Azure.

Notes​

  • ContainerName and BasePath support Orchard Core Liquid shell-token formatting through Orchard's blob-storage options pipeline. See Separating tenants.
  • Container names are normalized to lowercase during configuration.
  • This feature changes only where encrypted recording bytes are stored. Provider recording, ingest, orchestration, and erasure behavior stay the same.
  • Use local file-system storage unless you specifically need shared cloud storage or Azure-hosted deployments.