Freeze one caller path and expected prompt
Record timestamp and timezone, call direction, caller and dialed identity, matched route, selected Announcement, IVR or other consumer, expected recording and language, observed words or silence, answer state and any digit behavior. Preserve the saved configuration, generated dialplan, application messages and authorized file metadata before uploading, rerecording or applying configuration.
Classify whether the wrong content appears in every consumer of the object, only one call flow, only one language, only after a recent handset rerecording, or only on one media format. Those comparisons identify different owners.
Prove the consumer and recording reference
Open the call-flow object that handled the call and record the exact System Recording it references. Compare its saved selection with generated and loaded behavior for the same call. If the wrong consumer or destination ran, stay with routing or that module; replacing the referenced audio would change shared content without correcting route selection.
Enumerate other consumers of the same recording before any repair. A correct friendly name is not proof of a correct object identifier or playback list, and a consumer saved before a replacement can still be using the same now-changed shared object.
Inspect object parts, language and replacement history
Record the object name, description, language, ordered playback items, codecs or available formats and optional rerecording feature code. Compare the current preview and file metadata with the approved source, prior backup and known change time. Sangoma documents that saving a new upload or recording can replace the existing file, so a timestamp-aligned content change is evidence to investigate rather than a reason to overwrite again.
Keep secrets out of the evidence bundle. If a feature-code path exists, confirm its authorization, audit trail and target object separately; reaching the code does not prove which content was committed.
Trace language, filename and decoder selection
On the failed channel, preserve the effective language and the exact ordered filenames passed to playback. Expand relative names under the Asterisk sounds directory without assuming a displayed extension is the representation selected at runtime. Confirm that the intended language variant and a supported decodable format exist with readable permissions.
If only one language fails, continue through channel-language and fallback ownership. If every consumer fails on the same playback part, stay with the shared object, file or decoder boundary. Do not install broad prompt packs or copy files across language directories until the exact lookup is known.
Read Playback or BackGround outcome in call context
Identify whether the consumer uses Playback, BackGround or another application and preserve its status, channel answer state and adjacent dialplan result. Asterisk documents filename-without-extension lookup and SUCCESS or FAILED application status; BackGround also couples playback with digit collection. Audible silence, a missing-file failure, early-media behavior and ignored DTMF are not interchangeable symptoms.
Confirm selected file, application status and what the caller heard separately. A successful status does not certify the spoken message, language, volume or downstream route, and a browser preview does not reproduce the caller channel.
Correct the smallest owner and replay every consumer
Correct only the first demonstrated divergence: route or consumer reference, ordered item, approved media replacement, language, supported format, permission, feature-code access, generated state or application behavior. Use the supported FreePBX owner, Apply Config when required and a reversible backup; do not edit generated dialplan or overwrite managed sound files as the durable repair.
Retest the original call, each representative consumer, applicable languages, answer or early-media state and DTMF branch, then confirm the prior wrong content no longer appears. This workflow is documentation-derived and was not reproduced on a customer or laboratory PBX.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Sangoma FreePBX System Recordings module ↗
- Sangoma System Recordings Module User Guide ↗
- Sangoma System Recordings GraphQL APIs ↗
- FreePBX System Recordings source ↗
- FreePBX IVR release/17.0 metadata ↗
- FreePBX Sound Languages release/17.0 metadata ↗
- Asterisk Playback application ↗
- Asterisk BackGround application ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.