VoiceGuide IVR Software Main Page
Jump to content

Program Crash

Recommended Posts

Hi, I am having a problem with a script. the computer answers the phone and

miday thru the first wav recording it crashes.

Below are the steps the program listed.

it crashes to a blue screen that says something about VXD

 

Thanks

Jim Benson

 

150540.26 0 callstate OFFERING 4342232 0 4

150540.26 0 ring 1

150544.16 0 ring 2

150544.21 0 Answer the call at 7/31/2004 3:05:44 PM

150544.21 0 lineAnswer(4342232) => 1

150544.21 0 tapi Reply (LineEvReply) ok 1 0

150544.21 0 callstate ACCEPTED 4342232 0 0

150545.48 0 callstate CONNECTED 4342232,0,0

150545.48 0 WorkingModeTAPI@Connected=

150545.48 0 WorkingModeScript@Connected=

150545.48 0 Inband detection not enabled

150545.48 0 StartLoadedVgs at 7/31/2004 3:05:45 PM

150545.48 0 [hello intro] Playing

150545.48 0 [hello intro] Playing (hello_intro_bi.wav)

150545.64 0 PlaySoundStart ok [C:\Roomtalk\voiceguide\Scripts\roomtalk

script\hello_intro_bi.wav]

150545.64 0 RunModule PLAY end

150608.54 0 wb(12001400)

150608.82 0 Play End line[0] (id=120014)

150608.82 0 LsPlayMsg EV_PLAY_FINISHED

150630.73 0 LsPlayMsgFinished EV_TIMEOUT_HANGUP

150630.73 0 Hanging up call...

150630.79 0 RecSoundStop ok

150630.79 0 PlaySoundStop ok

150630.79 0 fnHangupCall end

150630.84 0 callstate IDLE 4342232 0 0

150630.84 0 WorkingMode@Idle=

150630.95 0 tapi Reply (LineEvReply) ok 2 0

150632.82 0 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE

150632.82 0 ReinitTelephony due to IDLE start

150632.82 0 tapic lineDeallocateCall(MainCall:4342232) 0

150633.64 0 lineOpen(0) => 0

150633.64 0 Waiting for a call...

150633.64 0 lineOpen(0)LineHandle=4342040

150648.53 0 sys cleanup Start

150648.58 0 sys cleanup End

Share this post


Link to post

A 'Blue Screen' type error is not something which can be caused these days at an application software level (like VoiceGuide) - it is an error on the 'kernel' level of Windows or it's hardware drivers.

 

These days it is most often caused by faulty memory or faulty hardwre drivers - in your case as the error message says someting about a VXD then I'd suspect a hardware driver.

 

Dialogic SR5.1.1 drivers do not have any reported 'blue screen' issues.

(are you using SR5.1.1 or some older drivers?)

 

Sometimes reformatting the computer changes the area of memory where the kernel and the various hardware drivers are loaded in memory which can stop the blue screen from happening

 

Next time you see the blue screen I'd recommend having a good look at what it says and what hardwre driver has caused the error.

 

You can read some other peoples experiences when they encountered problems on their systems and how they were resolved here:

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

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

 

Which version of Windows are you using?

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×