Theodore Phipps
Posts: 9
Stars: 0
Date: 5/17/13
« Back

Beep Beep... on Record

7/15/09 1:38 PM
Recently noticed that there have been repeated questions from our developer community complaining that they can't seem to get the beep to work with <record>. They have set the beep attribute to "true" alright, and the reference guide even says this is supported but why doesn't it work?

It fails to work coz IOS still has a vxml version defaulted to pre2.0, you can check this using the "show run" on the gateway. And hence it still behaves as a pre2.0 compliant browser wrt some . Run this command at the CLI to make it 2.0 compliant
# vxml version 2.0
and voila!! the beep works emoticon

Another tedious way would be to add a beep.wav audio before the record element. Any takers?
By Ranjana Narayan
9743 Views, 2 Comments
vxml record beep
Average (3 Votes)
The average rating is 4.0 stars out of 5.
Comments
Wes Schochet
Thanks for the info. Two questions:

1. Are you saying that even if there is a <vxml version="2.0" lns="http://www.w3.org/2001/vxml"> tag in the document it's still interpreted as a 1.x document?

2. Any other features that change (or what will I break) by entering the version command?
Posted on 7/23/09 12:35 AM.
Ranjana Narayan
@Wes,

1. For the beep attribute to work, you will have to set the vxml version both in the vxml script and the gateway. Enabling 2.0 on the GW makes it compatible with the VXML2.0 Spec.

2. Other features enabled are :
- error.badfetch will not be thrown when it fails to fetch/play a media file. [ You can turn this on, by executing "vxml audioerror"]
- Blind transfer would be as defined in the vxml2.0 (which in default environment would be similar to COnsultation transfer)
- VXMl2.0 spec compatilbility.
Posted on 7/23/09 9:11 AM in reply to Wes Schochet.