IVR languages & audio

Language catalogue#

Open IVR Audio to manage the available languages and prompt tokens. Static routes use the exact configured language name. A TTS locale such as en-US and an IVR language name such as English are not interchangeable.

Upload and convert#

1. Select or create the intended language.
2. Choose the prompt token required by your flow.
3. Upload an appropriate source WAV file.
4. Convert the required PCMA, PCMU or G729 variants.
5. Check the variant badges and required-prompt coverage.
6. Assign the same language and static media settings to the Voice route.

File organization#

The source and runtime directories are intentionally separate.

audio/<language>/source/    original WAV masters
audio/<language>/runtime/   raw RTP-ready variants
  <prompt>.g711a
  <prompt>.g711u
  <prompt>.g729Copy

Runtime prompts have no media container. Renaming a WAV file to a codec extension does not convert it. The API and worker share VOICE_AUDIO_DIR and require appropriate filesystem permissions.

Codec behavior#

A static call offers only codecs for which all required prompts are available. The gateway answer selects the actual variant and RTP payload type. Gateway codec preference affects ordering; it does not fabricate missing audio.

G729 and migration#

G729 conversion requires a verified encoder in ffmpeg. The project includes an IVR migration tool for existing prompt files. Preserve original sources before changing runtime variants.

Deletion#

Deleting a prompt can remove every converted variant. Check active routes and required tokens first; a missing mandatory variant can prevent audio playback.