Overview. Live Call Transcription turns live CX Voice call audio into text on the Media Server and posts those transcripts into the Expertflow CX conversation. Agents see customer and agent speech as text on Agent Desk during the call. Call audio is handled on the Media Server with Azure Speech — it does not go through Jambonz or LiveKit for this path.
Define the Feature
When a customer and an agent are connected on a CX Voice call, the Media Server sends speech to Azure Speech for recognition. Final transcript lines are posted into the same CX conversation that already belongs to the call. Agents see caller and agent text on Agent Desk in near real time.
This is the Media Server–native path for live call text on Agent Desk. It does not use Jambonz on the audio path.
Objectives
-
Deliver live transcription for CX Voice calls without putting Jambonz on the audio path
-
Keep speech recognition on the Media Server with Azure Speech, and deliver text into the existing CX conversation
-
Support inbound, manual outbound, and campaign calls, with control per tenant and call type
-
Work with Expertflow CX deployments that use gateway authentication, using the same pattern as other CX voice components
Business benefits
Contact centers get live transcript visibility on Agent Desk with fewer moving parts and less dependency on Jambonz for transcription. Operations can turn the feature on per tenant and call type — without changing how agents work day to day.
Intended Audience and Use Cases
-
Primary users: Contact center agents (read transcripts), supervisors (visibility), and voice / CX administrators (enable and operate the feature)
-
Key scenarios:
-
Live agent assist and compliance visibility on CX Voice inbound and outbound calls
-
Deployments that want Azure Speech on the Media Server instead of Jambonz transcription
-
How it works (high level)
Inputs → processing → outputs
-
Input: Customer and agent are connected on a bridged CX Voice call.
-
Processing: The Media Server streams call audio to Azure Speech (customer and agent legs separately). Final recognized text is posted into the CX conversation for that call.
-
Output: Transcript lines appear in the same conversation on Agent Desk, labeled for customer and agent.
Capabilities
Live dual-leg transcription
Final speech from the customer and the agent is transcribed separately and shown correctly on Agent Desk.
Call-type and tenant controls
Administrators can allow transcription by tenant and by call kind (inbound, manual outbound, or campaign), with optional filters for which inbound numbers are included.
Multi-tenant conversation delivery
Transcripts are delivered to the correct CX tenant conversation for the call, following the same tenant routing pattern used by other CX Voice components.
Secure delivery when gateway auth is enabled
On deployments where the CX gateway requires authentication, transcript delivery uses the same secure login pattern as Voice Connector. Deployments without gateway auth continue to work without that step.
Safe operate modes
Administrators can run in observe mode or active mode, and can stop transcription quickly without removing the feature from the Media Server.
Getting started
Live Call Transcription is enabled by voice / Media Server configuration for your environment. Agents do not turn it on from Agent Desk.
For install and configuration steps, see Set up Azure live call transcription on an EFSwitch server.
For day-to-day use on Agent Desk, see Live Call Transcription — User Guide.
Compatibility and integrations
-
Environments: On-prem / private cloud Media Server with Expertflow CX (single-tenant or multi-tenant)
-
Products: Expertflow CX Voice (Media Server + Voice Connector) with Azure Speech
-
Alternate speech engine: A Deepgram-based path also exists — do not run Azure and Deepgram transcription on the same live traffic at once
User interface overview
-
Navigation: Agent Desk → open the active voice conversation during a bridged call
-
Key screen: The conversation view shows live transcript messages for the customer and the agent. There is no separate transcription screen.
Security, compliance, and privacy
Data processed
-
Call audio (Media Server → Azure Speech)
-
Final transcript text posted into the CX conversation
-
Call metadata needed to place text on the correct conversation (for example conversation identity, service, customer number, and tenant)
Data storage and retention
-
Audio is streamed to Azure Speech for recognition; retention follows Azure and CX conversation policies for the deployment
-
The transcription service does not keep a separate transcript archive for customer reporting beyond what CX already stores in the conversation
Access control
-
Who can see transcripts on Agent Desk follows normal CX / Keycloak roles for that conversation
-
When gateway authentication is enabled, transcript delivery uses a dedicated service account configured by your administrators
Compliance
Treat transcripts as personal / sensitive conversation data. Apply your organization’s data-residency and retention rules for the Azure region and CX storage you use.
Supported cases and limitations
|
Case |
Status |
|---|---|
|
Inbound (bridged) |
Supported |
|
Manual outbound (bridged) |
Supported |
|
Campaign outbound (bridged, when enabled for the tenant) |
Supported |
|
Consult / transfer / conference / barge |
Not supported |
|
Voicemail |
Not supported |
|
Unanswered / never-bridged |
Not supported |
-
Transcription starts after the call is bridged, not while it is only ringing
-
Speech recognition may mis-hear noise as words; accuracy drops in noisy environments
-
If the customer keeps talking while the agent is on hold, that speech may still appear as text
-
Each bridged call uses two Azure speech streams (customer + agent) — plan capacity accordingly
FAQ
What is this feature?
Live Call Transcription — live speech-to-text on CX Voice calls using Azure Speech on the Media Server, shown on Agent Desk without Jambonz in the audio path.
How does text get to the agent?
The Media Server recognizes speech with Azure Speech and posts final lines into the CX conversation. Agents see those lines in the same conversation on Agent Desk.
Who uses it?
Agents and supervisors read the text during calls. Voice / CX administrators enable and operate the feature on the Media Server.
What do I need before go-live?
Working CX Voice with Voice Connector, an Azure Speech resource, and Live Call Transcription configured and enabled for your tenants and call types. See the Setup Guide for details.
Is it secure when gateway authentication is on?
Yes, when configured by your administrators: transcript delivery uses the same secure pattern as Voice Connector.
I do not see text on Agent Desk — what should I check?
Confirm the call is bridged, that you are viewing the conversation for that call, and that Live Call Transcription is enabled for your tenant and call type. If it should be on and still missing, contact your voice / CX administrator (ops checks are covered in the Setup Guide).