Lukas Report post Posted 10/24/2019 06:46 PM Hi, we have a problem with one serwer VG sometimes we have communique as in the attachment Share this post Link to post
SupportTeam Report post Posted 10/24/2019 09:02 PM This looks like an older version of VoiceGuide Line Status Monitor. Was the VoiceGuide service stopped when this happened? Current versions of the Line Status Monitor handle the VoiceGuide service stop better, with no multiple windows like this displayed when connection to VoiceGuide server is lost. Share this post Link to post
Lukas Report post Posted 10/27/2019 10:31 AM The voiceguide service not stopped then this happend. Share this post Link to post
SupportTeam Report post Posted 10/27/2019 11:53 AM Hard to say why the connection to the status monitoring service was broken. Was the status monitor running on the same system as the VoiceGuide service, or was the monitoring done from a remote machine? Did restarting the Status Monitor fix the issue and the Status Monitor started showing the line status again? As the VoiceGuide service was running during this Status Monitor problem can you post the vgEngine trace log from VoiceGuide that covers the time when the status monitor stopped reading status data, and when it was restarted? Current version of VoiceGuide Status Monitor shows more information in the popup message box about the nature of the connection error, so if current version of VoiceGuide was used we would be better able to tell what was the underlying use of the problem that occurred here based on the screenshot. Share this post Link to post
Lukas Report post Posted 11/04/2019 11:44 AM Can the problem be caused by a small amount of RAM? Share this post Link to post
SupportTeam Report post Posted 11/04/2019 12:04 PM Unlikely. Was the Line Status Monitor running on same machine as the VoiceGuide IVR service it was reporting status of? Or on some other machine? Share this post Link to post
Lukas Report post Posted 11/04/2019 12:35 PM The monitor works on the same machine Share this post Link to post
SupportTeam Report post Posted 11/04/2019 12:41 PM Please advise on these two questions: Did restarting the Status Monitor fix the issue and the Status Monitor started showing the line status again? As the VoiceGuide service was running during this Status Monitor problem can you post the vgEngine trace log from VoiceGuide that covers the time when the status monitor stopped reading status data, and when it was restarted. Share this post Link to post
Lukas Report post Posted 11/04/2019 01:01 PM Did restarting the Status Monitor fix the issue and the Status Monitor started showing the line status again? Yes restarting VG and cards again solved the problem. Part-day logs in the attachment log24102019.rar Share this post Link to post
SupportTeam Report post Posted 11/05/2019 09:04 AM Have you tried just restarting the Status Monitor app? (without restarting the VoiceGuide service itself) Share this post Link to post