Configuration Reference
Audio Resource to Text Mapping Properties
JSON type object
Location Configuration root
These properties define the mapping between an audio resource and its text.
Behavior and notes
- Audio Resource Text Mapping complements Prompt Module fallback behavior. A Prompt Module can request an audioResource while the mapping supplies text that can be synthesized if that recording is unavailable.
- This separation lets applications keep recorded-audio filenames stable while independently maintaining the text used for synthesis fallback.
- Mappings are especially useful for deployments where some languages, environments, or releases contain recorded prompts while others rely on synthesized speech.
Properties
audioResource
stringRequired
Audio-resource filename used as the lookup key. It may be specified literally or supplied as a complete runtime-field value.
Runtime fields: Supported — To supply the value dynamically, specify a runtime field as the complete property value using the $[FieldName] syntax.
Literal value
"audioResource": "Hello.wav"Runtime field
"audioResource": "$[AudioResource]"text
stringRequired
Fallback text associated with audioResource. When the requested recorded resource cannot be resolved, Andamento can synthesize this text instead.
Runtime fields: Supported — The complete value may be supplied with $[FieldName]. Embedded runtime fields are also supported within otherwise literal text.
Literal value
"text": "Hello there"Runtime field
"text": "$[FallbackText]"Embedded runtime field
"text": "Hello $[CollectedName], welcome back."language
stringOptional
Compatibility field. It is currently not used when resolving an Audio Resource Text Mapping. Language/resource behavior for synthesized prompt playback is configured by the Prompt Module.
Runtime fields: Not supported — No runtime behavior is documented for this property because it is currently not consumed when processing the mapping.
Examples
Example mapping
[
{
"audioResource": "Hello.wav",
"text": "Hello there",
"language": "en-US"
}
]