Wave Driver Problems

[briesmith]

I've installed the zip file as suggested [ in thread http://voiceguide.com/forums/index.php?showtopic=1227 ] and my script won't run at all now, with and without logging switched on.

 

This what I get in the log file window

 

181418.60 6 linedevstate 2048 0 0

181418.60 6 callstate OFFERING 66356 0 4

181418.60 6 Answer the call at 16/03/2004 18:14:18

181418.62 6 lineAnswer(66356) => 66305

181418.62 6 callinfo CALLEDID

181418.62 6 callinfo ORIGIN

181418.62 6 ring 0

181419.16 6 callstate CONNECTED 66356,1,0

181419.16 6 WorkingModeTAPI@Connected=

181419.16 6 WorkingModeScript@Connected=

181419.20 6 Inband detection not enabled

181419.20 6 StartLoadedVgs at 16/03/2004 18:14:19

181419.20 6 rv add [$RV_STARTTIME]{16/03/2004 18:14:19}

181419.20 6 rv add [$RV_DEVICEID]{6}

181419.20 6 rv add [$RV_CIDNAME]{}

181419.20 6 AddRVns [PathApp]{C:\Program Files\VoiceGuide\}

181419.20 6 rv add [$RV_CIDNUMBER]{}

181419.20 6 tapi Reply (LineEvReply) ok 66305 0

181419.20 6 callinfo MONITORMODES

181419.21 6 TimeoutClear

181419.21 6 [Welcome] Playing

181419.21 6 [Welcome] Playing (C:\Program Files\VoiceGuide\TTS\Prompts\welcome.wav)

181419.21 6 PlaySoundStart err=[0 play PlaySoundStart ResetWavOutAndContinuePlay=>4,play pss EnsureWaveOutIsOpenAndReady=>tr 5 waveOutOpen(id=1) MMSYSERR_ALLOCATED but hWaveOut = NULL] [C:\Program Files\VoiceGuide\TTS\Prompts\welcome.wav]

181419.21 6 PlaySoundStart err=[0 play PlaySoundStart ResetWavOutAndContinuePlay=>4,play pss EnsureWaveOutIsOpenAndReady=>tr 5 waveOutOpen(id=1) MMSYSERR_ALLOCATED but hWaveOut = NULL] [C:\Program Files\VoiceGuide\system\voice\ErrorPlayingFile.wav]

181419.21 6 For Dialogic use: PCM 11Khz 8bit Mono

181419.23 6 rv add [Hangup Time]{16/03/2004 18:14:19}

181419.23 6 Hanging up call... [srlib PlaySoundStart]

181419.23 6 RecSoundStop ok

181419.23 6 PlaySoundStop err=0

181419.23 6 TimeoutSet 2 EV_TIMEOUT_WAITFORIDLEAFTERLINEDROP

181419.23 6 fnHangupCall end

181419.23 6 RunModule PLAY end

181419.24 6 tapie PlayEnd old line=6 0 418171

181419.24 6 tapie PlayEnd old line=6 0 418171

181421.20 6 linedevstate 2048 0 0

181421.20 6 callstate IDLE 66356 0 0

181421.20 6 WorkingMode@Idle=

181421.20 6 TimeoutClear

181421.21 6 TimeoutSet 1 EV_TIMEOUT_TIMETOREINITLINE

181421.21 6 tapi Reply (LineEvReply) ok 66322 0

181422.27 6 Timer fired EV_TIMEOUT_TIMETOREINITLINE

181422.27 6 ScriptEventCode 9008 iLineState=900

181422.27 6 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE

181422.27 6 ReinitTelephony due to IDLE

181422.27 6 tapic lineDeallocateCall(MainCall:66356) 0

181422.42 6 lineOpen(6)=>

181422.42 6 Waiting for a call...

181422.42 6 LineHandle=66287

181422.44 6 TimeoutSet 3 EV_TIMEOUT_ATERIDLE_ALLOWOUT

181426.06 6 Timer fired EV_TIMEOUT_ATERIDLE_ALLOWOUT

181426.06 6 ScriptEventCode 9013 iLineState=900

 

Help!

Edited 03/24/2004 02:23 PM by SupportTeam

[SupportTeam]

Trace shows that something has gone wrong with the wave drivers:

181419.21 6 PlaySoundStart err=[0 play PlaySoundStart ResetWavOutAndContinuePlay=>4,play pss EnsureWaveOutIsOpenAndReady=>tr 5 waveOutOpen(id=1) MMSYSERR_ALLOCATED but hWaveOut = NULL] [C:\Program Files\VoiceGuide\TTS\Prompts\welcome.wav]

Did you make any changes or install any other sound-related software at the same time?

 

Can you try re-installing the wave drivers for your telephony device?

[briesmith]

It's now Wednesday 24 March, some 3 working days since our VG system stopped working. We have, only just now, managed to re-establish telephone contact with the outside world via the Dialogic card and, although we are vey pleased to be back in business, we don't know what caused the original problem nor what we did that fixed things and we still have a residual problem which, while not causing any apparent difficulties, we would like to get to the bottom of.

 

When restarting the PC, Windows XP reports that an "Other PCI Bridge Device has been found". If I click NEXT on the install wizard it tries to install a Dialogic D 4PCI card which I cancel. If I look in System Devices I find the yellow question mark for "other PCI bridge devices" has an exclamation mark over it. Checking the properties for this device revelas that the drivers have not been installed.

 

But the Dialogic card is working fine and our script plays perfectly. The sound system works fine and will play any CD/DVD or the help scripts via TextAloud so I'm very reluctant to possibly bugger things up - again - by trying to install the "missing" other PCI Bridge device.

 

I would appreciate your comments though as the whole business of installing Dialogic cards and managing them in an XP environment seems to be a bit of a mystery (not helped by the absence of definitive instructions from yourselves).

[SupportTeam]

The "Found New Hardware Wizard keeps popping up" situation which for some reason happens on some systems is covered in the VoiceGuide installation instructions for Dialogic systems in VG Help file.

 

The link to the relevant page of the Help file is also listed on the Recommended Hardware page in the section dealing with Dialogic cards.

 

The link to online version of Help file's page is : http://voiceguide.com/vghelp/html/InstallDialogic.htm

 

and on that page it says:

Found New Hardware Wizard on Win2000

 

If the Found New Hardware Wizard keeps popping up every time you start Windows, and you are unable to stop it by pressing Cancel please read:

 

http://resource.intel.com/telecom/support/...winnt/tn383.htm

 

or:

 

http://voiceguide.com/forums/index.php?showtopic=1147

 

There is also see another previous post relating to this issue:

http://voiceguide.com/forums/index.php?showtopic=390

 

Procedure for installting wave drivers on WinXP is the same as Win2000 - see: http://www.voiceguide.com/vghelp/html/Inst...vStepByStep.htm

[briesmith]

Yes, thanks for that. I did find the information you mention after I'd posted my query.

 

I keep including Wn(dows) XP in my search target and your documentation doesn't really cover XP yet; you're still firmly with 2000 and NT which, given that XP has been around for at least a couple of years, is a bit surprising. I suppose you're where you are because Dialogic haven't found XP yet?

 

Notwithstanding any of my posts, I have to say that we are getting on really quite well with VG now and having assigned someone with current VBSCript and SQL skills to our project, we've started discovering things about VG which are helpful and which have come as pleasant surprises.

 

One question I have concerns ruggedness. Is there anyway I can construct some kind of link whereby another version of something(VG?) running on another m/c could constantly check to make sure that my VG script was working OK and notify somebody if it wasn't?

 

I am thinking about out of hours and weekend operations where you would want to be sure that everything was working OK but you wwouldn't want to keep ringing in to check.

 

We're still looking into the ins and outs of running VG as a service so that we can be sure that if the host PC (telephony server) is running then so is our VG application.

 

Any thoughts/pointers re the above would be gratefully received.

[SupportTeam]

In terms of installation and operation WinXP is pretty much the same as Win2000.

 

I had a search through the help file and the few times that Win2000 is mentioned in there WinXP is mentioned as well.

 

Most VoiceGuide users are running WinXP. What gave you the impression that we do not target XP? Because most of the screenshots are shown using 'Classic Windows' frames and not XP frames?

(We do not use XP frames for most screenshots as they look too distracting...)

 

 

One way to check if the system is running OK is to make automated calls into the system - have the calling system send some DTMF code to VG and have the VG script programmed to detect this tone and then respond with an another DTMF tone - if the calling system hears the response tone then all is OK.. else it can raise an alarm (eg: call somebody).

[briesmith]

Gotcha.

 

I set up a minimum script running on another m/c which calls the script I'm interested in checking.

 

To make sure the script being checked doesn't think it's just another caller I set the script to send a very specific string of numbers (dtmf stuff of all 9s say) that I can program for in my main script and take a path to a make a call module appropriately? The make a call module would dial (back to) the checking script and send it an agreed dtmf sequence.

 

If the minimum script doesn't get a response or the right response it can also go to a make a call module, dial a support number and play an appropriate message?

 

Is all I need to set this up in the version of VG we licenced (5.2.1010 Enterprise edition 4 lines) or do I also need to buy something else like AutoDialler?

 

What about the fact that I'm now running VG on 2 m/cs? Would I need to buy a single line licence for the other system running the checking script?

 

To save me starting from scratch can you point me to an example script which automatically calls a number at specified times/intervals and sends the called number a dtmf sequence when answered?

[SupportTeam]

If you want to have another system periodically calling it to check the main system then you will need another Pro+Dialer license running on another machine.

[briesmith]

What about the example script? Any news there?

[SupportTeam]

There are no sample script demonstrating one VG VoiceGuide system 'checking on' another system - but the approach you described in previous post is pretty much it - a couple of DTMF tones exchanged between the systems is enough to confirm that they are operating...