Home / Companies / AssemblyAI / Blog / Post Details
Content Deep Dive

μ-law vs A-law: getting text-to-speech right on phone calls

Blog post from AssemblyAI

Post Details
Company
Date Published
Author
-
Word Count
2,934
Company Posts That Month
10
Language
English
Hacker News Points
-
Post removed?
No
Summary

G.711 remains the standard format for many telephone calls, transmitting 8 kHz, 8-bit companded audio as μ-law/PCMU, common in North America and Japan, or A-law/PCMA, common in many other regions. Its limited frequency range removes much of the high-frequency detail that gives modern 24 kHz text-to-speech voices clarity, while unnecessary transcoding, resampling, or improper buffer padding can further introduce noise, clicks, latency, and degraded interruption handling. For phone voice agents, the recommended approach is to request the carrier’s native 8 kHz μ-law or A-law format directly from the TTS provider, send it at the real-time rate of 8,000 bytes per second, and match the negotiated codec used by services such as Twilio, Telnyx, or SIP trunks. The discussion also highlights practical implementation concerns, including 20 ms frame sizing, clearing queued audio during caller barge-in, correct G.711 WAV headers for playback, and the fact that A-law call paths may require direct A-law output for TTS but decoding inbound audio to 8 kHz 16-bit PCM for speech-to-text systems that do not accept A-law.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Real-time 15 386 100 56 -91%
Voice AI 8 247 27 10 -91%
Universal-3.6 Pro Realtime 4 28 6 1 -88%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.