Vg Calling And Loader Problems

[rickccc]

Hello,

 

We have three problems as follows:

 

1) We are experiencing problems in the VG for TAPI driver installation. We

have monitored many instances in which the first introduction part of our

script is never played by VG when calling out! The VB script in concern is

3_hm_800.vgs which is supposed to play call_3_800HUM.wav sound file first

but many of the times it does not play at all and skips to play the

replay_prompts.wav sound file in the next part of the script. In a one

single day we have random incidences of skipping to play the

call_3_800HUM.wav file and proceed to the replay prompts file and

sometimes we have even found that the VG is not playing the first file for a few

hours continously when calling a list of phone numbers.

 

We are not planning to move to VG as the sound file format required for

Dialogic card version is not good quality and also we require to order

more than a dozen of files to re-create at the studio.

 

2) We are also experiencing other problems. Please check the logs I am sending. On 24th May at about a little after 4:00 PM EST VG had stopped calling and had a mesage waiting for call in three lines and hanging up the call in 1 line and the dialing was stopped. The computer was not freezed and the VG was also responding but not calling. I am sending you the log files as an attachement.

 

3) We are also getting errors in the loader module once a day when it says something like 'Error code XXXX and something like ..locked by user admin...'. Any idea why does this happen often? I am sending you a doc with the image with this.

 

 

The zip file attachement has the 2 log files and the screen shot of the loader error.

 

Thanks in advance for your help!

0524vgm_1600hrs.txt

0524tw_1600hrs.txt

vgError.doc

[SupportTeam]

1) We are experiencing problems in the VG for TAPI driver installation. We

have monitored many instances in which the first introduction part of our

script is never played by VG when calling out!

Dialogic's TAPI drivers have playback problems.

 

That is why Dialogic discontinued their TAPI drivers a number of years ago.

 

We recommend not using the Dialogic's TAPI drivers.

 

You will not have these playback problems when using "VoiceGuide for Dialogic".

 

Have you had a listen to the system sound files which come with "VoiceGuide for Dialogic" when running that version? The will show you that the sound quality achieved by v6.x is the same as by v5.x.

 

We can look at the traces capturing the calls on which you have the " first introduction part of our script is never played" problem to confirm that this is the actual problem.

 

2) We are also experiencing other problems. Please check the logs I am sending. On 24th May at about a little after 4:00 PM EST VG had stopped calling and had a mesage waiting for call in three lines and hanging up the call in 1 line and the dialing was stopped.

Trace shows that about 10 seconds after dialing on all lines the TAPI layer reported that the DISCONNECTED tone (or loop current drop) occurred on the line. This could be because the telephone company would not connect the call, or that the TAPI layer was falsely reporting that the DISCONNECTED tone (or loop current drop) occurred.

 

3) We are also getting errors in the loader module once a day when it says something like 'Error code XXXX and something like ..locked by user admin...'.

Hard to say as the error massage does not give any filename.

Is it possible that one of the Telephone Number Loader output files is open by another process?

How are you loading new calls into the system?

Do you have other processes opening and reading any of the Telephone Number Loader output files?