Version 6.4 457 March 2012
SIP User's Manual 20. Configuring the IP Media Parameters
Language Code Language
vi
Vietnamese
yu
Cantonese
zh
Mandarin
20.1.3.5 Combining <audio> Elements
The VXML specification supports multiple <audio> elements nested within other elements
such as prompts. An example demonstrating this functionality which includes the
AudioCodes extensions is useful to show how multiple components can be combined to
create a single announcement.
The following example shows how an announcement can be constructed that says
“Welcome to Acme Corporation. Today’s date is June 20th, 2010. Today’s special is large
widgets, two for ten dollars.” For the sake of the example, assume the following:
“Welcome to Acme Corporation” and “Today’s special is large widgets, two for ten
dollars” are stored on an external file system and is played using HTTP streaming.
“Today’s date is” is a recording provisioned on the APS as segment 99.
“June 20th, 2008” is a multi-language variable announcement made up of multiple
recordings provisioned on the APS.
<prompt bargein=”false”>
<audio src = “http://192.168.1.2/announcements/welcome.wav”/>
<audio src = “http://localhost/99”/>
<audio src=”?sel=lang=en”> <say-as interpret-as=”date”>
20080620 </say-as> </audio>
<audio src =
“http://192.168.1.2/announcements/todaysspecial.wav”/>
20.1.3.6 Notes Regarding Non-compliant Functionality
The AudioCodes resident VXML Interpreter doesn't asynchronously throw events as
described in the VXML Specification. For example, if the clear element tries to clear an
element within a script and that element does not exist, the VXML Specification specifies
that the Interpreter should throw an “error.badfetch” event. In contrast, the AudioCodes
Interpreter logs an appropriate error to the syslog for the device and the script exits. The
VXML Interpreter behaves similarly for software errors in general such as running out of
memory resources, trying to access non-existent audio files, etc. The impact of not
throwing events asynchronously can be minimized by carefully testing all code paths for a
VXML script before its deployment.
20.1.3.7 Supported Elements and Attributes
The following status legend should be referenced for all tables in the following subsections:
NS: Not Supported
PS: Partially Supported
S: Supported