Vg 5.1.7001 Crashes

[Guest Guest_sonomaairporter]

VG has crashed for the past two days. We run VG after closing our office at 5 PM.

The first crash occurred while I was retrieving msgs from home. When I pressed 6 to go to the next msg, the system hung up on me. Called back in, but VG wouldn't answer.

 

The second crash occurred last night sometime after 2 AM this morning. We started VG at 5 PM and according to the log browser, it handled about 25 calls, 3 of whom successfully left msgs between 5 pm and 2 am. The last logged call was from one of my employees, who was probably trying to retrieve msgs (haven't had the chance to talk to him yet).

 

On both crashes, VG had shut down, and Dr. Watson reported "VgMulti.exe Access Violation 0xc0000005 Address: 0x01e188e1".

 

I am attaching a part of a trace log saved to disk, 124vgm.txt. (I am including only a part because the file is over 6 megabytes in size, and all the error msgs are the same) I don't know whether these error msgs are the cause of the crash, but I suspect they might have something to do with it.

 

I'm running VG 5.1.7001 on a 400 mHz Celeron with 160 MB of memory under Window NT 4/Service Pack 6. The telephony device is a Dialogic D/41H.

 

I appreciate any help you can provide.

 

Les

[Guest Guest_sonomaairporter]

I'm not sure if attaching the 124vgm.txt was successful or not, so here is the first few lines of it:

 

071138.71 0 Inband Signaling Config file not specified

071138.72 0 Loading VMB data begin

071138.72 0 Loading VMB data - about to delete old entries

071138.75 0 Loading VMB data - sorting/ordering

071138.75 0 Loading VMB data end

071138.86 0 init clear settings on 1 devices.

071138.87 0 Initialising...

071138.87 0 init attach vgs on 1 devices.

071138.87 0 Script Load C:\Program Files\VoiceGuide\Scripts\VoiceMail\Mon-Fri Voicemail.vgs

071138.91 0 init lineopen on 1 devices.

071138.92 0 Calling .lineOpen on device 1

071139.04 0 Calling .GetLineHandle on LineId 0

071139.05 0 hLine=12071096

071139.05 0 Calling .GetProviderInfo on LineId 0

071139.07 0 Line 0 Provider: D41MT.TSP: Dialogic D41 Service Provider

071139.08 0 Calling lineSetNumRings on lLineHandle 12071096

071139.08 0 Waiting for a call...

071139.17 0 ERROR 5.1.7001 DialogicScUnroute => dx_getxmitslot() failed dxxxB1C1(1): Error message = Invalid Switching Handler Bus Mode

071139.84 0 ERROR 5.1.7001 DialListDbFindDueCall [Too few parameters. Expected 2.]

071139.85 0 ERROR 5.1.7001 DialListDbFindDueCall [Object variable or With block variable not set]

071140.86 0 ERROR 5.1.7001 DialListDbFindDueCall [Too few parameters. Expected 2.]

071140.86 0 ERROR 5.1.7001 DialListDbFindDueCall [Object variable or With block variable not set]

071141.87 0 ERROR 5.1.7001 DialListDbFindDueCall [Too few parameters. Expected 2.]

071141.87 0 ERROR 5.1.7001 DialListDbFindDueCall [Object variable or With block variable not set]

071142.89 0 ERROR 5.1.7001 DialListDbFindDueCall [Too few parameters. Expected 2.]

071142.89 0 ERROR 5.1.7001 DialListDbFindDueCall [Object variable or With block variable not set]

071143.91 0 ERROR 5.1.7001 DialListDbFindDueCall [Too few parameters. Expected 2.]

071143.91 0 ERROR 5.1.7001 DialListDbFindDueCall [Object variable or With block variable not set]

071144.92 0 ERROR 5.1.7001 DialListDbFindDueCall [Too few parameters. Expected 2.]

071144.92 0 ERROR 5.1.7001 DialListDbFindDueCall [Object variable or With block variable not set]

071145.93 0 ERROR 5.1.7001 DialListDbFindDueCall [Too few parameters. Expected 2.]

071145.93 0 ERROR 5.1.7001 DialListDbFindDueCall [Object variable or With block variable not set]

071146.94 0 ERROR 5.1.7001 DialListDbFindDueCall [Too few parameters. Expected 2.]

071146.94 0 ERROR 5.1.7001 DialListDbFindDueCall [Object variable or With block variable not set]

 

Also here are the contents of my VG.INI file:

 

[LineConfig]

TapiDeviceCount=1

 

[TapiDevice1]

Id=0

Name=Analog Line 1(dxxxB1C1)

Script=C:\Program Files\VoiceGuide\Scripts\VoiceMail\Mon-Fri Voicemail.vgs

RingsBeforeAnswer=2

PopupCallerId=1

DialoutOK=0

 

[TapiDevice2]

Id=

Name=

Script=

RingsBeforeAnswer=2

PopupCallerId=

DialoutOK=

 

[TapiDevice3]

ID=

Name=

Script=

RingsBeforeAnswer=2

PopupCallerId=

DialoutOK=

 

[TapiDevice4]

ID=

Name=

Script=

RingsBeforeAnswer=2

PopupCallerId=

DialoutOK=

 

 

[PlayRecordConfig]

;DEfault Sound editor used to edit sound files from VoiceGuide.

RecEditor=SNDREC32.EXE

 

;When a recording is finished due to the busy signal being detected

;the recorded message will be truncated to remove the busy tone recording from the message.

;A Dialogic card records 11025 bytes per second, modem records 16000 bytes per second.

;RecCutIfHangupBytes specifies by how many bytes the message should be shorter

RecCutIfHangupBytes=32000

RecCutIfHangupBytes_Dialogic=14000

 

;When a recording is finished due to a DTMF tone being pressed

;the recorded message will be truncated to remove the DTMF keypress sound from the message.

;A Dialogic card records 11025 bytes per second, modem records 16000 bytes per second.

;RecCutIfDtmfStopBytes specifies by how many bytes the message should be shorter

RecCutIfDtmfStopBytes=5000

RecCutIfDtmfStopBytes_Dialogic=4000

 

RecLengthMin=1

RecLengthMax=60

PlayEndPauseDialogic=0

;PlayVolume can be set from 1 (very quiet) to 100 (loudest).

;a setting of 0 disables explicit setting of the volume, keeping the default setting.

PlayVolume=100

 

;For how long will VoiceGudie have to hear silence on the line before reporting it.

;a setting of 30 = 3 seconds

SilenceDetectLength=50

 

;What level of noise on the line is considered as silence. range 1-100

;100 - interpret even loud noise as silence.

;1 - even the slightest noise stops silence detection.

;0 - don't detect silence at all

SilenceDetectLevel=10

 

 

 

[Voicemail]

RecLengthMin=1

RecLengthMax=300

ForwardPhoneRetries=2

ForwardPhoneWait=1

ForwardPhoneAcceptPrompt=VmbForwardAskAccept.wav

 

 

ForwardVmEmailSubject=Voicemail received from $RV_CIDNAME, $RV_CIDNUMBER at $RV_HOUR:$RV_NN $RV_DATE/$RV_MONTH

;this ForwardEmailBody is used if VmEmailForwardBody.txt file is not present

ForwardVmEmailBody=Voicemail received from $RV_CIDNAME, $RV_CIDNUMBER at $RV_HH:$RV_NN $RV_DATE/$RV_MONTH

ForwardVmEmailFromAddress=voiceguide@yourdomain.com

ForwardVmEmailFromName=VoiceGuide Voicemail

 

ForwardVmEmailMechanism_1=MAPI

 

ForwardVmEmailMechanism_2=MAPI

 

;VmSystemUsed - whether the "Builtin" or the "Scripted" voicemail system

;should be used.

;Builtin is built into VoiceGuide itself.

;Scripted is created using the Voiceguide Scritps in \system\vm\ directory.

VmSystemUsed=Scripted

VmScript_LeaveMsg_Script=VmLm.vgs

VmScript_LeaveMsg_Module=VmLmStart

VmScript_SelectVmb_Script=VmLm.vgs

VmScript_SelectVmb_Module=VmMenuStart

VmScript_LoginVmb_Script=VmLogin.vgs

VmScript_LoginVmb_Module=VmLoginStart

VmScript_VmDeliver_Script=vmMsgDeliver.vgs

VmScript_VmDeliver_Module=VmDelivStart

;if VmScript_VmDeliverAM_Script is set to VmMsgOnly

;then outgoing queued call will have just the Vm msg filename

;specified in the 'answering machine answers' field.

;Otherwise the script/module indicated will be used.

VmScript_VmDeliverAM_Script=VmMsgOnly

VmScript_VmDeliverAM_Module=

ForwardVmEmailSendRetries=0

ForwardVmEmailRetriesDelay=0

VmbMaxSize=250

;VmScript_VmDeliverAM_Script=vmMsgDeliver.vgs

;VmScript_VmDeliverAM_Module=VmDelivAMStart

 

 

[PBX]

;Maximum time the system will wait for the extension to be answered. In seconds.

AnnouncedTransfersMaxWaitTime=30

 

;Dtmf tone played by PBX when the call is finshed, only some PBXs indicate end of call

;using this DTMF tone. Please consult your PBX manual if it uses this or other DTMF tone,

;or if it does not use any at all..

HangupOnDtmf=D

 

;Inband signalling configuration file eg: InbandSignaling_SiemensHiPath3000_v1.2.txt

;Inband signalling detection is enabled on Enterprise versions of VoiceGuide only.

InbandSignalConfig=

 

;time for PBX to react to the hookflsh. In 100ms units, eg: 10=1 second

PauseAfterHookflash=10

 

;"TAPI" : TAPI functions calls are made to driver to action transfers and conferences.

;"Generate" : exlilicit tones and signals are generated using TAPI calls

;"AT" : modem AT commands are used

TransferControl_Modem=Generate

TransferControl_TelBoards=Generate

 

;Preferred Lengths of hookflash and DTMF tones.

;will be used if Generate method is selected. In milliseconds.

;If commented out then the default settings for the device will be used.

;Note: Dialogic cards will ignore this setting and use what is in the Dialogic TSP Configuration settings.

;DurationHookflash=100

;DurationDtmfTone=100

 

 

;************************************************

;*** "Generate" is selected for Transfer Control

;************************************************

;generated before playing the destination extension. (Blind and Announced transfers)

Transfer_Prefix=!

;generated after the call transfer is accepted.

;after playing this signal VoiceGuide will hang up the call.

;generated after the call is declined.

;This signal is used to hangup the extension leg of the call and retrieve the call,

Transfer_AnnounceDecline=!

;generated before playing the destination extension. (Blind and Announced conferences)

Conference_Prefix=!

;generated immediately after playing the destination extension

Conference_BlindSuffix=!3

;generated after the call confenrence is accepted.

;after playing this signal VoiceGuide will stay on the line.

Conference_AnnounceAccept=!3

;generated after the call confenrence is declined.

;This signal is used to hangup the extension leg of the call and retrieve the call,

Conference_AnnounceDecline=!

 

 

;************************************************

;*** "AT" is selected for Transfer Control

;************************************************

ModemTransferInit1=AT#VBT=1

ModemTransferHookflash=AT#VTS=!

;ModemTransferDialNumber: this command is suffixed with the destination number separated by commas

ModemTransferDialNumber=AT#VTS=

ModemTransferComplete=AT#VTS=!

;Commands issued to the modem duting a 3-way conference setup

Modem3WayInit1=AT#VBT=1

Modem3WayHookflash=AT#VTS=!

;pause time after sending hookflash to allow PBX enough

;Modem3WayDialNumber : this command is suffixed with the destination number separated by commas

Modem3WayDialNumber=AT#VTS=

Modem3WayComplete=AT#VTS=!

 

;************************************************

;*** "TAPI" is selected for Transfer Control

;************************************************

;set to 1 if lineComplete transfer is not to be called upon announced call transfer being accepted.

;if set to 0 then LineCompleteTransfer will be issued after call transfer is accepted, then call will be hung up.

;if set to 1 then the call will be just hung up after call transfer is accepted.

OnTransferAccept_NoLineCompleteTransfer=0

 

 

;3WayMaxTalkTime is in 1 second units, rg: 1800 = 30 minutes

3WayMaxTalkTime=1800

 

 

 

[VGDialer]

;Dialout announcement replay maximum count.

AnnReplay=10

 

;Guard time between end of incoming and start of any outgoing call on a line.

;ie: How long system waits after end of call before doing any outbound

;calls on the same line (sec)

AfterIdleWait=3

 

;Silence detection is used to judge when the answering machine

;message has stopped talking:

 

;Dialogic cards can detect if an answering machine answers the call.

;To Enable Dialogic's answering machine detection set AM_DetectionMode to "Enabled"

;To Disable Dialogic's answering machine detection set AM_DetectionMode to "Disabled"

AM_DetectionMode=Enabled

 

;AnswerMachine Silence detect length. In 100ms units (20 = 2 seconds)

AM_SilenceDetectLength=20

 

;AnswerMachine SilenceDetectLevel: range: 0-100.

;0 - don't detect silence, 100 - detect loud background noise as silence.

AM_SilenceDetectLevel=10

 

BulkDial_Script=

BulkDial_AnswerMachine=

BulkDial_Announce=

BulkDial_PhoneNumberFile=

BulkDial_PhonePrefix=

BulkDial_Rvs=

BulkDial_AnswerTimeout=60

BulkDial_CallRetries=2

BulkDial_DelayBetweenRetries=120

BulkDial_CallsStart=00:01

BulkDial_CallsEnd=23:59

BulkDial_Days=MoTuWeThFrSaSu

 

 

[VBScript]

UseSafeSubset=1

ShellHandler=wscript

 

[DatabaseWorkspace]

WorkspaceJetUser=admin

WorkspaceJetPassword=

WorkspaceOdbcUser=admin

WorkspaceOdbcPassword=

 

[VgGsd]

DesignAreaHeight=5000

DesignAreaWidth=5000

 

 

[moduleGetNbrs]

;The setting below can be used to force VoiceGuide to continue playing the

;message in the Get Numbers module while the numbers are being entered.

;By default VoiceGudie will stop playing the message when the caller presses

;the first key.

;OnGetNumbersRxDigit=PlayStop_False

Timeout_1stDigit=6

Timeout_Interdigit=6

Timeout_Confirm=6

 

 

[VGsys]

;Used only for CT-Media systems

;AssistingApp=VgControl.exe

 

[OnError]

;OnError_Unavailable possible settings:

;RESTART_TAPI, RESTART_VOICEGUIDE, RESTART_PC

OnError_Unavailable=

 

 

[CTMedia]

DefaultScript=C:\Program Files\VoiceGuide\Scripts\VoiceMail\Mon-Fri Voicemail.vgs

WatchedService=

WatchedFile=

LoadScript1=

LoadScript2=

LoadScript3=

LoadScript4=

LoadScript5=

LoadScript6=

LoadScript7=

LoadScript8=

LoadScript9=

LoadScript10=

 

[TraceLog]

;LogDebugToFile: 0=do not log, 1=always log to file c:\VoiceGuideLogMMDD.txt

LogToFile=1

;TraceLevel : only messages at that trace level or lower will be printed. (max trace level setting is 10)

TraceLevel=10

 

[EmailSender]

;TraceLevel : how many trace messages get saved to c:\VoiceGuideLogMMDD_EmailSender.txt

;0=minimal, 5=full

TraceLevel = 5

[SupportTeam]

Looks like the new version of VG was installed over the top of a previous version of VG.

The "DialListDbFindDueCall" errors are caused by the old version's "DialList" Database files not having been deleted, preventing VG from creating the new version databases...

 

To fix this issue please uninstall VG then delete the directory in which VG was installed, then install VG again (or install in a new directory...).

 

These errors may have played a part in VG crashing...

 

Please place the attached file in "C:\". Once this file is there then log files will be created named: C:\VoiceGuideLogMMDD.txt. If the crash occurs again please post the log file for the day on which the problem occurred.

 

Also... please note that Dialogic drivers are not certified fro WinNT Sp6 - only for WinNT SP4 and Win2000 SP2. (Can you switch to using Win2000 SP2 ?)

TapiWrapLogSelect.txt

[sonomaairporter]

Thanks, your instructions did the trick. No more error msgs are showing up in the trace log.

 

I did keep NT 4.0 SP6 though. I will replace it if the crashes return.

 

Many thanks,

Les

[sonomaairporter]

Unfortunately, VG crashed again after about 4 hours of handling calls. If it's of any significance, the crashes always happen right after we have called in to retrieve voicemail.

 

I did do the reinstall as instructed (first I uninstalled, then deleted the directory, then reinstalled, configured etc.) I also placed TapiWrapLogSelect.txt in C:\.

 

However the log file I am attaching is C:\Program Files\Voiceguide\log\125vgm.txt, not C:\VoiceGuideLogMMDD.txt which I expected to see.

 

You will see several occurrences of these two error msgs:

 

073955.97 0 ERROR 5.1.7001 DialogicScUnroute => dx_getxmitslot() failed dxxxB1C1(1): Error message = Invalid Switching Handler Bus Mode

 

074023.15 0 ERROR 5.1.7001 DialListDbFindDueCall CreateQueryDef [3420:Object invalid or no longer set.]

 

I'd like to try and resolve this without the additional expense of purchasing Windows 2000. Is it possible to download and install Windows NT 4.0 Service Pack 4 on top of Service Pack 6?

 

Thanks,

Les

0125vgm.txt

[SupportTeam]

We can see in the trace that all the calls are arriving on the line which has the TAPI ID of "0" (the line ID is shown right after the timestamp on each line of the log).

 

We have seen TAPI before show some strange problems when the "0" line is used...

 

Please try using a different line and see if this makes any difference...

 

Easiest way to try using a different line is to just move the line going into the first channel on the Dialogic card to a different channel.

 

Otherwise to ensure that the TAPI line ID of "0" is not assigned to any of the lines on the Dialogic card you should uninstall Dialogic then install a modem (dummy modem - there does not really need to be a modem present) before re-installing a Dialogic card - then the IDs of the Dialogic lines will start at 1 and go to 4 - not 0 to 3 like now...

 

As for the log file - there should have been a log file created in "c:\" (name should be TapiWrapLogMMDD.txt) - that log file would contain more relevant info then the VoiceGuide log file. If problem continue after re-installing Dialogic on lines 1-4 please post the 'TapiWrapLog' file.

[sonomaairporter]

OK, I'll give that a try, and get back to you.

 

As for the log file, I do have TapiWrapLogMMDD.txt in C:\ and am attaching the one when VG crashed yesterday. (I'd been looking for VoiceGuideLogMMDD.txt, as specified in your instructions.

 

Les

TapiWrapLog0125.txt

[SupportTeam]

TapiWrapLogMMDD.txt log shows system crashed while calling the Windows' TAPI function lineGetCallInfo:

 

170954.776 tapie LINE_LINEDEVSTATE(0, 0xb63190, 0x800, 0x0, 0x0)

170954.786 tapie LINE_CALLSTATE(0, 0xb635b0, 0x2, 0x0, 0x4)

170954.786 tapic lineMonitorDigits(0xb635b0, 0x2) => 0x0

170954.786 tapic lineMonitorMedia(0xb635b0, 0xfc) => 0

170954.786 tapic lineGetCallInfo(0xb635b0, 0xb14fdd0)

170954.786 eng No CallerId info available at this time

170954.816 tapie LINE_CALLINFO(0, 0xb635b0, 0x8000)

170954.816 tapic lineGetCallInfo(0xb635b0, 0xb154008)

 

Lets see if situation improves when using non-zero line IDs...

[sonomaairporter]

More trouble.

 

Here's what I did:

 

uninstalled Dialogic

rebooted

 

installed dummy modem

rebooted

 

Ran DCM added D/41H device, started the services on it running

Checked Multimedia device for Dialogic wave drive; it was present

Ran Control Panel, clicked on Telephony Device, checked drivers;Dialogic Svc Prov

for NT was present

 

Ran VG configuration to select Dialogic's Line 1

 

Ran my script. All looks OK. But when I called in to the system, VG picked up after the third ring, did not play any wav file, and immediately hung up.

 

Rebooted, and restarted VoiceGuide. It now shows Line Device: Analog Line 1 (dxxxB1C1), and State shows:LINEERR_RESOURCE UNAVAIL[800000.

 

I've attached a text file, TapiLogWrap0126_0126vgm.txt, which is the TapiLogWrap to which I've appended the vgm file.

 

HELP!

TapiWrapLog0126_0126vgm.txt

[SupportTeam]

After reinstalling the Dialogic card you then need to re-install the Dialogic TAPI & Wave drivers - so that they can re-config themselves to point to correct channel on the Dialogic card.

 

Please uninstall and install these again and advise..

[sonomaairporter]

After uninstall/install of VG's TAPI and Wave drivers, VG started right up and ran all night without crashing. So let's hope that solves that problem for good.

 

One last problem, which I suppose I can live with since all else is working OK:

 

When I uninstalled VG's drivers, I also uninstalled my Soundblaster's wave driver, and then tried to reinstall it (all of the uninstalls were done without rebooting). The last part of the process to reinstall SB wave driver is to reboot so it can finish whatever it is doing. However, when I did the reboot, during the shutdown of the system, I get a blue screen with the following err msgs:

 

STOP: (followed by a bunch of memory addresses)

IRQL_NOT_LESS_OR_EQUAL *** ADDRESS 8011637C HAS BASE AT 80100000 - NTOSKERNEL.EXE

 

I have to power off the system to get back to restart. When I do this, everything else is working properly, except the SB wave driver never completes installation. Which is not a giant problem, except the only way to retrieve VG msgs is by phone, because the sound card's driver is not installed.

 

If you have any suggestions, I'd appreciate it. If not, I can live with it since this computer is used exclusively by VG, and we can get msgs by phone.

 

Regards,

Les

[SupportTeam]

Any errors thrown by the NTOSKERNEL.EXE are usually a cause for concern...

 

a quick search on http://www.google.com/groups shows that such errors are in some cases caused by conflicting hardware setups and in some cases caused by flakey hardware altogether - some users ended up replacing the whole RAM in machine to make problem go away, others said replacing CPU finally fixed the problem for them... If you continue to get intermittent NTOSKERNEL.EXE errors then I'd recommend just getting a new PC...

[sonomaairporter]

Final tag to this thread:

 

I switched to Windows XP Professional, and all remaining problems disappeared (i.e. no crashing, no blue screen on system restart/shutdown, VG operates perfectly).

 

I am a happy camper!

 

Les