Hi Nagarajan,

Can you tell me what version of Audium you are using?

Also, if you are specifiying a path for the say it smart audio, are you using a full or relative url?

In older versions of Audium (v3.2.0 and below), the path content is always appended to the default audio path application setting, so you cannot specify a full url. Therefore, if you are using an older version, I would suggest upgrading to the latest release.

Regards,

Joe

Hi Nagarajan,

Are your audio files located in <tomcat_home>/webapps/ROOT/sound/numbers? If so, I would try doing this:

time.getVAudio("/sound/numbers/") ;

In other words, I think you need a / before the path.

Hope this helps,
Val

Hi,
Thanks a lot for your suggestions. The problem persists though.

I am using Voxeo with VWS 1.3 for testing this application. It has been written using VFC's only.(the Builder was not used at all)

I found from the Voxeo logs that when ever I use the time.getVAudio() method (where time is a VTimeNumber object) the filenames meant for the numbers are accessed with out their extensions.

For e.g if I want to play the time "12.30 PM" to the user, the files are accessed as follows

http://IP-Address:8080/soundFiles/12
http://IP-Address:8080/soundFiles/30
http://IP-Address:8080/soundFiles/PM

Even though the application is able to locate the soundfiles, it does not apply the extension "WAV" to their filenames.

So, instead of finding 12.WAV, the application loads the file name as 12 only. Since there is no file named 12 (there is a 12.WAV instead), Audium plays the TTS versions of 12, 30 and PM.

How ever Audium is able to load other prompts from the same location with the WAV extension. So, i dont have a problem playing files that are prompt menus/questions etc.

When I use the getVAudio() function for playing the time, all I get is TTS.

Hope this explains the problem better.

Thanks,
Nagarajan

Nagarajan,

The Audium Builder and Audium server is built to automatically take care of the procedures you are trying to perform yourself. While most of the questions about the VFCs are answered in the VFC Javadocs, the VFCs themselves are only a small part of the Audium software. If you build an application on Audium software using the processes described in the Audium documentation, you would not encounter any of the problems you described in this post.

As I mentioned before, if you were to look at the approach for building voice applications provided with Audium 3, you will see that it will cut down significantly the work you will have to do compared to the approach you are using. Audium Elements already provide most of the dialog functionality you will need, without the need to do any coding at all. The VFCs are needed only to build voice elements not currently provided by Audium, and even in these cases, Audio Groups and SayItSmart automatically takes care of using the VFCs inherited from VNumber. The Audium Builder allows you to build your call flow graphically, you don't have to handle it yourself.

In very early versions of Audium software, Audium provided support for the process of building voice applications you are using. In Audium 3, however, Audium can only provide support for those processes involving both the Audium Builder and the Audium Server.