Recording Problem

[ktruk]

After setting up a simple recording script, as soon as the recording module is run, I get an error:

 

151511.83 15 RecSoundStart err[6]

 

And the call goes to "Hangup" mode.

 

What is err[6] please?

 

151511.75  15 timer clear

151511.76  15 state [Record 1] Recording

151511.77  15 play set playid=213358

151511.78  15 PlaySoundStart ok [C:\Program Files\VoiceGuide\system\voice\beep1.wav]

151511.78  15 timer clear

151511.80  15 play  end current play (playid=213358)

151511.80  15 ScriptEventCode 8001 iLineState=1200

151511.81  15 LsRecPlayBeep EV_PLAY_FINISHED

151511.82  15 rv    lg add [Record 1]{C:\Program Files\VoiceGuide\Scripts\ktr\testrec1.wav}

151511.83  15 RecSoundStart err[6]

151511.84  15 rv    lg add [Hangup Time]{25/01/2006 15:15:11}

151511.85  15 state Hanging up call...

151511.86  15 RecSoundStop ok

151511.87  15 PlaySoundStop err=0

151511.88  15 timer set 2  EV_TIMEOUT_WAITFORIDLEAFTERLINEDROP

151511.89  15 fnHangupCall end

151511.89  15 eng  RecSoundStart after beep [C:\Program Files\VoiceGuide\Scripts\ktr\testrec1.wav]

151511.90  15 timer set 30  EV_TIMEOUT_GOTOMODULE

151521.21  15 tapi  callstate start

151521.22  15 tapi  callstate DISCONNECTED 66486 1 0

151521.23  15 ScriptEventCode 9250 iLineState=1201

151521.24  15 LsRecRecording EV_REMOTEPARTY_DISCONNECT

151521.25  15 RecSoundStopTruncBytes ok

151521.26  15 rec length RV: Record 1_RecLen100ms = 94

151521.27  15 rv    lg add [Record 1_RecLen100ms]{94}

151521.27  15 rv    lg add [Record 1_EndRecCause]{disconnect}

151521.28  15 rv    lg add [Hangup Time]{25/01/2006 15:15:21}

151521.29  15 state Hanging up call... [During LsRecRecording]

151521.30  15 RecSoundStop ok

151521.31  15 PlaySoundStop err=0

151521.32  15 timer set 2  EV_TIMEOUT_WAITFORIDLEAFTERLINEDROP

151521.33  15 fnHangupCall end

151521.35  15 tapi  callstate start

151521.35  15 tapi  callstate IDLE 66486 0 0

151521.36  15 WorkingMode@Idle=

 

(I am using v5.2.5015, and an Eicon wave driver/hardware)

[SupportTeam]

We'll need to see the tw trace to see what is happening on the driver level.

[ktruk]

Just reran the app and zipped up the files. Really appreciate any insight on this issue. Thx.

125vglogs.zip

[SupportTeam]

The wave driver returned an error when VoiceGuide tried to start recording.

We can see in tw trace:

 

222307.559 fn rec waveInOpen failed.

 

You should contact the manufacturer of the driver to see why it had failed...

 

Trace shows that you are using 4 BRI lines for a total of 8 voice channels.. You'd be better off just getting an E1/T1 ISDN line instead and using a Dialogic card...

[ktruk]

Actually, it looks like VG returned the error... based on these lines, looks like the ocx does the call recording setup.

 

222307.519 wavec waveOutUnprepareHeader(0x39f4eb0, 0x39f40f0, 0x20) call non-unimodem

222307.519 wavec waveOutUnprepareHeader(0x39f4eb0, 0x39f40f0, 0x20) => 0 (MMSYSERR_OK) non-unimodem

222307.519 fn OnFirePlayPlayWdogClearEvent start

222307.519 ocxev PlayWdogClear(dwLineId=21, dwPlayId=0xd6f2f4)

222307.519 ocxev PlayEnd(dwLineId=21, dwPlayId=0x22645)

222307.549 ocxfn SilenceDetectSet(sLineId=21, sTimeLen=30, sVolumeLevel=10)

222307.559 ocxfn RecStart(sLineId:21, strFile:C:\Program Files\VoiceGuide\Scripts\ktr\testrec1.wav)222307.559 wavec waveOutReset(0x39f4eb0) call, caller: RecSoundStart

222307.559 wavec waveOutReset(0x39f4eb0) => 0 (MMSYSERR_OK), caller: RecSoundStart

222307.559 wavec waveOutClose(0x39f4eb0) call, caller: RecSoundStart

222307.559 wavec waveOutClose(0x39f4eb0) => 0 (MMSYSERR_OK), caller: RecSoundStart

222307.559 fn rec waveInOpen failed.

222307.579 ocxfn RecStop(sLineId:21)

222307.579 wavec waveInReset(0x0) => 5

222307.579 linec lineMonitorTones(0x10104, 0x0, 1) => 0x80000049 (disabling monitoring for silence/tones)

222307.589 ocxfn PlayStop(sLineId=21)

222307.589 fn PlaySoundStop start

222307.589 fn PlaySoundStop line not playing a sound file. 0x0

222307.609 ocxfn LineDrop(sLineId=21, sOpt=0)

222307.609 tapic lineDrop(0x10104, , 0) call in ocxfn_LineDrop

222307.609 tapic lineDrop(0x10104, , 0) => async:65847 (65847)

222308.120 tapie LINE_REPLY(21, 0x0, 0x10137, 0x0)

 

Earlier in the tapi traces, you can see that VG queries the wave/driver capabilities as part of the device initialization and setup. (see attached log zip higher up in thread) and appears to return the requested information. Then VG asks the ocx to setup for recording (by setting silence detection) and next thing I get is an error when recording starts.

 

Looking closely at the events logged, there appears to be some wave driver initialisation done out of sequence, the correct sequence should be something like:

waveOutReset(x,x,x)

waveOutUnprepareHeader(x,x,x)

waveOutClose(x)

But these events seem out of sequence. (I'm guessing here, but if the driver is not closed off after playing, it can't be turned around for recording).

 

Can you please ask the developers to check the proper block-mode wave setup and what the error code actually means? I am pretty sure it is not a waveError message from the wave Driver. Also, in addition to the above (or an alternative)can we describe the device capabilities that VG requires in order to do recording? Without this information, I cannot give the Eicon people anything to go on. Perhaps this information is available in the logs already? But having the exact description of what VG is asking the wave driver to do is the only way I am likely to get this problem fixed by Eicon (if it is their problem)!

[SupportTeam]

You can check for correct Wave driver operation by seeing VG run with other hardware - voice modems and Dialoigc cards (in TAPI mode).

 

This does appear to be an Eicon issue.

[ktruk]

Okay - its an eicon issue, but they can't look into it without knowing what calls (and parameters) you are making to the driver. So I will ask again, can you tell me what error 6 means as returned by your OCX? Or what capabilities are required by the wave driver for VG to be able to use it?

[SupportTeam]

The error code 5 is returned by Eicon drivers in response to VG's waveInReset call to the Eicon drivers.