Problems Playing Sound Files

[Guest sanjayetsi]

Hello,

We have a PC AMD sempron 2200+ with 512 mb RAM with windows xp home edition, Intel dialogic D/4PCI card. The software we have installed is VoiceGuide 5.2.3063 Enterprise Version with tapi drivers (convenient to us because we can use the better sound files).

 

In our calling scripts we have play the introduction.wav sound file and then we play the prompts.wav sound file when a human picks up the phone.

 

(sounds\introduction.wav,sounds\prompts.wav)

 

Now the introduction.wav file is 60 seconds long and the prompts.wav is 15 seconds long. The introduction.wav file is to describe us and the prompts.wav is to tell them that they can press certain keys to show their responses.

We capture the keys pressed and put them in one of our table to take action on these phone calls.

 

What We have confirmed after studying the results is that often (35% of the total calls) a human presses a key even after hearing our message for only 15, 17 or even 12 seconds. This clearly indicates that the introduction.wav file was not played in these situations at all! Because they would not know what key is to be pressed until they have heard the introduction.wav followed by the prompts.wav file which has the indication on what keys are to be pressed.

 

We have experimented to call ourselves many many times and that the introduction.wav file is always played and never skipped.

 

 

What could be the problem?

 

I have run all the tests using the UDD - Universal Dialogic Diagnosis utility program and after running all the test the results are fine - as it shows PASSED for all test and finally shows NO errors found message.

 

One important thing though, I would like to make aware that the Device manager in the system properties in windows does show a yellow question mark saying 'Other Device' and when clicked on the + sign on the left displays the name of type of card 'Dialogic D/4PCI type card'

 

Please help

Thanks

[SupportTeam]

We have confirmed after studying the results is that often (35% of the total calls) a human presses a key even after hearing our message for only 15, 17 or even 12 seconds.

Looks like some callers press keys (at random) to just get out of hearing the remainder of the message...

[Guest sanjayetsi]

Replying to your Answer:

Looks like some callers press keys (at random) to just get out of hearing the remainder of the message...

 

I don't think that 35% of the callers would want to press keys in this manner at random!

So now I would like to know from any logs how much time is exactly the CALL LENGTH for each calls which is maintained by voice guide software.

 

We know when was the exact time of call from the outdialedHuman file as below:

10:13 PM 13/04/07, "13234647368", 0, 240, NONE, C:\Program Files\VoiceGuide\Scripts\3_hm_800.vgs, C:\Program Files\VoiceGuide\Scripts\3_am_800.vgs, none[PathSysVoice]{C:\Program Files\VoiceGuide\system\voice\}[PathApp]{C:\Program Files\VoiceGuide\}[PathDataVm]{C:\Program Files\VoiceGuide\data\}[PathVgSys]{C:\Program Files\VoiceGuide\system\}[OutDial_RetriesLeft]{0}

 

But can we know without using the $RV_CALLLENGTH variable from your logs how much exact duration of call?

[SupportTeam]

The log file for the script would include information about the start of the call and the end of the call, so call length can be calculated based on that. (see the .xml/.vgl/.csv files in script's directory).

 

The $RV_CALLLENGTH would not be saved by default - but you may save it's value and any other relevant information in a log file or database is you use a 'On-Hangup' script. Saving data from a 'On-Hangup' script is the usual way of saving information or doing 'tidy-up' work at the end of the call.