Ivg Shuts Off

[Guest Phillip]

I have a problem with IVG shutting down (exiting). How can I diagnose as the trace closes too.

 

Can IVG run as a service in win 2000 pro.

 

Is there a way to have IVG restart automatically or force a reboot on exit?

 

Often, after a call has ended, the line device State indicates, “Hanging up call (X)” for several minutes.

 

Thanks

 

My System

1. IVG 4.8.47

2. Dialogic 5.1.1 SP1

3. Board: Dialogic D4/PCI

4. OS: Windows 2000

5. Phone Line type: Centrex lines from Qwest

6. Location: New Mexico (USA)

[SupportTeam]

I have a problem with IVG shutting down (exiting).

Is the software just crashing on you? We have not heard anybody else having this issuse... How does it crash? Is thre an error box or DrWatson message?

There is an option to have the trace saved to a file continually - just click that option box when you bring up the Trace window and net time this happens please post the trace file which captured events up to that point...

 

Can IVG run as a service in win 2000 pro.

There is a workaround, plz see these two related posts:

http://katalinatech.com/forums/index.php?a...act=ST&f=2&t=31

http://katalinatech.com/forums/index.php?a...ct=ST&f=2&t=113

 

Is there a way to have IVG restart automatically or force a reboot on exit?

We haven't implemented such methods at this stage - we have not had anyone report issues with VoiceGuide just crashing on them before...

 

Often, after a call has ended, the line device State indicates, “Hanging up call (X)” for several minutes.

Could you please post a copy of VoiceGuide's Debug Printout which captures the problem, this will allow us to see what is going wrong. Please include in the trace the few last calls made on the problem line.

 

(When running the script click on VoiceGuide's View menu and select 'Event Trace Log' option - any log information will then appear in this window. You must open the trace window before making the call.)

[Guest retroblu]

Actually ive had that happen also...we would come in some mornings and vg would not be running, like someone just exited out of the program, and we couldnt figure why it was happening, its happen on several occassions, this was ver.4.7.25

oh and yes sometimes it would saying "Hanging up call" and just hang there...and when you try to force a hangup it goes "Hangin up call (2)"....

[SupportTeam]

If you are having such a problem then please post a copy of VoiceGuide's Debug Printout which captures the problem that is happening on your system. This will allow us to see what is going wrong.

 

(When running the script click on VoiceGuide's View menu and select 'Event Trace Log' option - any log information will then appear in this window.)

 

There is an option to have the trace saved to a file continually - just click that option box when you bring up the Trace window and net time this happens please post the trace file which captured events up to that point...

 

There was an issue with the v4.7.x which may be responsible for what you were seeing - but that and the "Hanging up call (2)" problem which was happening on some configurations has been resolved.

 

If you are having any such issues first please download and install the latest version of VoiceGuide (v4.9 at the time of writing this post), and then capture the problem that is happening.