Dialing After Blaster.worm

[Guest bdking]

I just got through wrestling with the blaster.worm. Everything seems to be working again, except for my voiceguide software. I've tried a few calls, it dials out but hangs up before playing any messages. Here's the trace log, for two calls, one with the machine answering and one with a voice answering:

 

120753.56 7 callstate DISCONNECTED 66355,16,0

120753.57 7 LsWaitAfterDialingOut EV_REMOTEPARTY_DISCONNECT

120753.57 7 Answering machine, wait for end of welcome message...

120753.57 7 dial call answered by answering machine

120753.57 0 dial callque delete id=31

120753.62 7 RecSoundStart file[C:\Program Files\VoiceGuide\data\RecAm_7.wav] ok

120756.63 7 LsDialoutRecAnswerMachineWelcMsg EV_SILENCE_DETECTED

120756.64 7 RecSoundStop ok

120756.67 7 LsDialoutRecAnswerMachineWelcMsg EV_REC_FINISHED

120756.67 7 Play Answer Machine message [C:\Documents and Settings\Brad\Desktop\MU LAW WAVES\long one test.wav]

120756.69 7 PlaySoundStart err=[0 wavec waveOutOpen(0x0, 0x0, 0x3961a48, 0x0, 0x0, 0x1) => 32 (WAVERR_BADFORMAT) - format query] file[C:\Documents and Settings\Brad\Desktop\MU LAW WAVES\long one test.wav]

120756.69 7 ERROR 5.0.1054 Error_ScriptEventCode: 0:9: Subscript out of range code:8003

120756.69 7 Hanging up call... [Error_ScriptEventCode]

120756.69 7 RecSoundStop ok

120756.70 7 PlaySoundStop ok

120756.70 7 Waiting for a call...

120756.70 7 fnHangupCall end

120756.74 7 linedevstate 2048 0 0

120756.74 7 callstate IDLE 66355 0 0

120756.74 7 WorkingMode@Idle=

120756.74 7 LineState(iLineId).iVgsIdx = 0

120756.74 7 tapi Reply 66338 0

120757.73 7 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE

120757.73 7 ReinitTelephony due to IDLE start

120757.73 7 tapic lineDeallocateCall(MainCall:66355) 0

120757.95 7 lineOpen(7) => 0

120757.95 7 Waiting for a call...

120757.95 7 lineOpen(7)LineHandle=66321

120938.17 0 dial callque update id=32 next call time 0308151409

120938.18 7 dial found entry: tel[4294470] ann[NONE] vgs[C:\Documents and Settings\Brad\Desktop\MU LAW WAVES\NEW MU1.wav] am[C:\Documents and Settings\Brad\Desktop\MU LAW WAVES\NEW MU1.wav]

120938.18 7 Dialing: 4294470

120938.18 7 MakeCall => 66303

120938.18 7 TapiCbTrigSet 66303 7002

120939.03 7 tapi Reply 66303 0

120939.03 7 TapiCbTrigClear

120939.04 7 linedevstate 2048 0 0

120939.04 7 callstate DIALTONE 66269 0 0

120939.04 7 callstate DIALING 66269 0 0

120939.04 7 callstate PROCEEDING 66269 0 0

120939.05 7 callinfo CALLEDID

120939.05 7 callinfo REASON

120939.05 7 Lev_CallerID [0000,]

120939.05 7 callinfo ORIGIN

120941.00 7 LsWaitAfterDialingOut EV_TIMEOUT_BRIDGEAFTERDIALING

120949.61 7 callstate CONNECTED 66269,1,0

120949.61 7 WorkingModeTAPI=

120949.61 7 WorkingModeScript=

120949.64 0 dial callque delete id=32

120949.64 7 Live person answered, playing C:\Documents and Settings\Brad\Desktop\MU LAW WAVES\NEW MU1.wav

120949.68 7 PlaySoundStart err=[0 wavec waveOutOpen(0x0, 0x0, 0x3961a48, 0x0, 0x0, 0x1) => 32 (WAVERR_BADFORMAT) - format query] file[C:\Documents and Settings\Brad\Desktop\MU LAW WAVES\NEW MU1.wav]

120949.68 7 ERROR 5.0.1054 LineEvCallState_Connected_Error:Subscript out of range

120949.68 7 Hanging up call... [LineEvCallState_Connected_Error]

120949.68 7 RecSoundStop ok

120949.70 7 PlaySoundStop ok

120949.70 7 Waiting for a call...

120949.70 7 fnHangupCall end

120949.73 7 linedevstate 2048 0 0

120949.73 7 callstate IDLE 66269 0 0

120949.73 7 WorkingMode@Idle=

120949.73 7 LineState(iLineId).iVgsIdx = 0

120949.75 7 tapi Reply 66252 0

120950.71 7 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE

120950.71 7 ReinitTelephony due to IDLE start

120950.72 7 tapic lineDeallocateCall(MainCall:66269) 0

120950.92 7 lineOpen(7) => 0

120950.93 7 Waiting for a call...

120950.93 7 lineOpen(7)LineHandle=66235

[Guest bdking]

Okay, so it looks like the 'Dialogic Wave Driver 1.X' is not functioning. I try to reinstall the driver but the computer can't locate it and I can't seem to find it manually. What do I do?

[Guest bdking]

Alright, got the driver re-installed. Did some dialing, but I found that once in a while it would 'sieze up' on a number and not go any further. It seemed to randomly happen after between 2 and 25 numbers. It still read 'dialing xxx-xxxx' but the trace log wasn't doing anything and it didn't move forward. Here's the trace log:

 

0300.21 7 Dialing: 3051577

170300.23 7 MakeCall => 65862

170300.23 7 TapiCbTrigSet 65862 7002

170301.07 7 tapi Reply 65862 0

170301.07 7 TapiCbTrigClear

170301.08 7 linedevstate 2048 0 0

170301.08 7 callstate DIALTONE 65896 0 0

170301.08 7 callstate DIALING 65896 0 0

170301.09 7 callstate PROCEEDING 65896 0 0

170301.09 7 callinfo CALLEDID

170301.09 7 callinfo REASON

170301.10 7 Lev_CallerID [0000,]

170301.10 7 callinfo ORIGIN

170303.08 7 LsWaitAfterDialingOut EV_TIMEOUT_BRIDGEAFTERDIALING

[SupportTeam]

What value is the answer timeout set to on these outgoing calls?

(it settable on the "Redial Config" tab)

 

When using the "Send Phone Message" module that timeout is set quite high (90 seconds).

 

How did you queue the calls and did you wait for more then 90 seconds after dialing to await a result?

 

Another trace would be useful here - could you please place the attached file in "C:\" and next time you get this problem can you please forward us the resulting C:\TapiWrapLog.txt

TapiWrapLogSelect.txt