Vg Service Crashing

[invoso.com]

From few days VG crashing and we have problems to check how VG is working.

 

We set up VG service to automatic restart after crash, so I see now in vg log files thats VG working but LINE MONITOR can't connect to service.

 

It's old problem with connection line monitor to VG service after restart. In this case I have to restart windows.

 

 

ERROR description from Windows Event Viewer:

Nazwa aplikacji powodującej błąd: vgIvrService.exe, wersja: 7.3.3.0, sygnatura czasowa: 0x51575854

Nazwa modułu powodującego błąd: MSVCR80.dll, wersja: 8.0.50727.6195, sygnatura czasowa: 0x4dcddbf3

Kod wyjątku: 0xc000000d

Przesunięcie błędu: 0x0001e898

Identyfikator procesu powodującego błąd: 0xa3c

Godzina uruchomienia aplikacji powodującej błąd: 0x01ce3697fce8b09e

Ścieżka aplikacji powodującej błąd: C:\Program Files (x86)\VoiceGuide\vgIvrService.exe

Ścieżka modułu powodującego błąd: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll

Identyfikator raportu: 8ad512fc-a33d-11e2-9407-24be051afaf3

 

 

Please help with VG line status monitor and localize crashing source.

[SupportTeam]

Can you please post entire ktTel traces from the last few days when you experienced issues.

 

Please .ZIP up all traces before posting.

 

What else is installed on this system apart from Windows and Dialogic drivers and VoiceGuide?

[invoso.com]

Windows Event Viewer reporting errors (crashing VG) at:

 

1. 08:52:30

2. 10:16:13

 

 

other software:

NORTON INTERNET SECURITY

NORTON GHOST

 

Now when traffic is low VG working properly.

 

Is possible to blocking available calls for incoming calls only for 15 connections?

Problem is when incoming calls are more then available channels to forward calls (dial out).

What happen when I declare script only for first 15 channels (in 30 channels VG server)? Will VG dial out on 16-30 channels?

What happen on provider switch (this server using 2nd E1 (31-60th channels) from 3 available trunks in DDI range)?

Will provider see that should use 3rd E1 to answer the call?

0412_ktTel - Kopia.zip

[SupportTeam]

Problem here is caused by the '2-Line-Record' function being called when the calls on the channels which are being recorded have already hung up.

 

Looks like this case is not not handled well by the engine and sometimes leads to an exception (crash) that you observed.

 

From supplied ktTel trace:

777 101508.326 3852 32 ev GCEV_ANSWERED crn=2800208 (ktTel_SR60vista v7.3.3, Mar 30 2013 16:13:42)

869 101510.331 2624 32 fn PlayStart(iLineId=32, sFileList=,C:\Program Files (x86)\VoiceGuide\Scripts\manager\komunikaty\ring_multiple_medivet.wav, sXMLOptions=)

114 101528.156 3852 32 ev GCEV_DISCONNECTED crn=2800208

137 101528.171 3852 32 ev GCEV_DROPCALL crn=2800208

 

176 101528.945 2624 32 fn RecTwoLinesStart(idRec=32, idSrc1=32, idSrc2=68, devRec=dxxxB3C3, devSrc1=dtiB1T11, devSrc2=dtiB1T23, sFileName=C:\callrecord\ID201304121015071611.wav, iActionID=882243, iDataFormatRec=6, iPlayBeep=0, sXMLOptions=)

 

222 101529.591 3852 32 ev GCEV_RELEASECALL crn=2800208

 

342 101532.241 3852 32 ev GCEV_OFFERED crn=2800216 (ktTel_SR60vista v7.3.3, Mar 30 2013 16:13:42) (setting hli->crn for line 32)

362 101532.252 3852 32 ev GCEV_ACCEPT crn=2800216

428 101532.987 3852 32 ev GCEV_ANSWERED crn=2800216 (ktTel_SR60vista v7.3.3, Mar 30 2013 16:13:42)

440 101533.004 2624 32 fn PlayStart(iLineId=32, sFileList=,C:\Program Files (x86)\VoiceGuide\Scripts\manager\\manager4\56001.wav, sXMLOptions=)

458 101533.020 2624 32 ERROR play(34, 0x427d168, tpt=0x0, xpb=0xf768624) => -1, err=9:Device busy, hli=0F764920

545 101534.123 2624 32 fn PlayStart(iLineId=32, sFileList=,C:\Program Files (x86)\VoiceGuide\System\voice_LEKTOR\SoundFileNotFound.wav,C:\Program Files (x86)\VoiceGuide\Scripts\manager\komunikaty\ring_multiple.wav, sXMLOptions=)

569 101534.255 2624 32 ERROR play(34, 0x427d2a8, tpt=0x0, xpb=0xf768624) => -1, err=9:Device busy, hli=0F764920

[SupportTeam]

This version should better handle this situation and fix the crash scenario that you were encountering on your system.

Please update this system to version below and post ktTel traces as before (.ZIPed) if you still encounter any crashes.

 

[old link removed]

[invoso.com]

VG crash at 10:24:52

 

 

 

Nazwa aplikacji powodującej błąd: vgIvrService.exe, wersja: 7.3.3.0, sygnatura czasowa: 0x5168a68d

Nazwa modułu powodującego błąd: MSVCR80.dll, wersja: 8.0.50727.6195, sygnatura czasowa: 0x4dcddbf3

Kod wyjątku: 0xc000000d

Przesunięcie błędu: 0x0001e44a

Identyfikator procesu powodującego błąd: 0x9f8

Godzina uruchomienia aplikacji powodującej błąd: 0x01ce3b8dd32afd3b

Ścieżka aplikacji powodującej błąd: C:\Program Files (x86)\VoiceGuide\vgIvrService.exe

Ścieżka modułu powodującego błąd: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll

Identyfikator raportu: 709b08c2-a801-11e2-9386-24be051afaf3

0418_ktTel.zip

[SupportTeam]

Similar scenario seen leading up to the error: 2-line recording started when no call on main line, and subsequently that line has problems on following call.

The ktTel trace did not contain error reports that we would expect to see just prior to a major problem (exception handlers reports etc), so we were not able to better pinpoint actual point of failure form this trace.

Do you need to restart the Dialogic service to restart the system, or just restarting VoiceGuide is sufficient to bring system back up?

We have added more tracing to this version, which should hopefully let us see more next time this happens, and we have now modified software to not allow starting of 2-line recording when there is no call on the line.

Please update system to this version and post ktTel trace (.ZIPed) as before if this happens again.

[old link removed]

[invoso.com]

I don't know what happen when VG crashing, because I don't see data in line monitor.

I set up in windows services aster VG crash - restart service but after several minutes i don't know how VG working because i don't see any changes in log file to check VG condition.

I see in log file that VG working but don't know how long and reason why VG not writing next data in log file is unknown.

 

 

So necessary is repairing VG Line Status Monitor module.

[SupportTeam]

The Line Status Monitor would not display information on exceptions/crashes.

 

This information is in the events summaries that you have been posting and some supporting information usually would be in ktTel traces as well.

 

So if this happens again we need to see the same information as posted here before.

[invoso.com]

next crash:

 

 

Nazwa aplikacji powodującej błąd: vgIvrService.exe, wersja: 7.3.3.0, sygnatura czasowa: 0x517069fa

Nazwa modułu powodującego błąd: MSVCR80.dll, wersja: 8.0.50727.6195, sygnatura czasowa: 0x4dcddbf3

Kod wyjątku: 0xc000000d

Przesunięcie błędu: 0x0001e44a

Identyfikator procesu powodującego błąd: 0xa40

Godzina uruchomienia aplikacji powodującej błąd: 0x01ce426b2a3588c9

Ścieżka aplikacji powodującej błąd: C:\Program Files (x86)\VoiceGuide\vgIvrService.exe

Ścieżka modułu powodującego błąd: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll

Identyfikator raportu: f7ca1d19-b08b-11e2-89a6-24be051afaf3

[SupportTeam]

Can you please .ZIP up and post the ktTel trace file that covers that time.

[invoso.com]

As You wish.

0429_ktTel.zip

[SupportTeam]

Traces show that the older ktTel DLLs were still being used on that system.

Please update to this version:

[old link removed]

And after service restart please confirm that in the starting banner of the ktTel log file build date is "May 2 2013".