VoiceGuide IVR Software Main Page
Jump to content

Not getting Voice Guide to start

Recommended Posts

Hi there,

The system was working before in the setup environment but now not working in the deployed environment. Please assist.

****

091251.306 Task_PollAndDisplay_List vgWcfLink_PortStatus is null
091251.306 Task_PollAndDisplay_List taskA.Start() ConnectAttemptsInRow=0, vgWcfLink_PortStatus=
091251.307 Task_Display_List await Task.Delay call
091251.309 Task_ConnectToService start Task_ConnectToService_isRunning=True vgWcfLink_PortStatus=
091251.309 Task_ConnectToService DataSourceSetWindowVisible not set
091251.313 ConnectToVgEngine_WCF start
091251.323 ConnectToVgEngine_WCF title set to: Status Monitor v7.6.31 [connecting to: net.tcp://192.168.0.12:7134/PortStatus/]
091251.456 ConnectToVgEngine_WCF using NetTcpBinding net.tcp://192.168.0.12:7134/PortStatus/
091251.457 ConnectToVgEngine_WCF CreateChannel call
091251.465 ConnectToVgEngine_WCF CreateChannel returned vgWcfLink_PortStatus=vgServicesInterfaces.IPortStatus
091254.308 Task_PollAndDisplay_List await Task.Delay returned
091256.313 Task_Display_List Error (Generic Exception)
091256.313 Cannot make a call on this channel because a call to Open() is in progress.
091256.314 Task_PollAndDisplay_List_Task_ConnectToService_GeneralExceptionObject reference not set to an instance of an object.
091258.329 Task_Display_List Error (Generic Exception)
091258.329 Cannot make a call on this channel because a call to Open() is in progress.

Share this post


Link to post

Looks like the Line Status Monitor app is unable to view the status of VoiceGuide system at IP address 192.168.0.12

I assume that the Line Status Monitor app is not running on the 192.168.0.12 system as well, and that 192.168.0.12 is some other remote system.

You will need to ensure that the TCP port 7134 communications between the system on which the Line Status Monitor is running and the VoiceGuide system at 192.168.0.12  are not blocked along the way by any firewalls/routers/etc.

In the meantime you can confirm actual operation of 192.168.0.12 system by running the Line Status Monitor app locally on that system and using a remote screen access tool to view the Line Status Monitor running there.

Share this post


Link to post

The Line Status Monitor app is on the same system as the VoiceGuide app.

Where is the IP Address configured for the Line Status?

Share this post


Link to post

Have you tried using any of the the default settings for the Line Status Monitor. Click on the "Source" button on the Line Status Monitor:

image.png.5bd18d93dfc232752d74a1dd7a79fffd.png

and select one of the 'addresses for a locally installed system' :

image.png.6d3a0231842813c2c030fa6039341d4c.png

note how "localhost' is used in address for connecting to VoiceGuide server running on same system.

If you still have problems can you please post a screenshot of the Line Status Monitor from your system.

 

Share this post


Link to post

Can you please .ZIP up and post all the trace files that were created on this system in the last few days.

The trace files are created in VoiceGuide's \log\ subdirectory.

The trace files will let us see what is happening on this system.

Share this post


Link to post

I got it to run on net.tcp://localhost:7134/PortStatus

However, I notice that the Line Status Monitor freezes when I run it from the System Tray icon for the Voiceguide Service. I have to run vgLineStatus.exe from the Voiceguide Folder.

I have attached the log files. I still need to get it to run on the other IP address.

1022_vgService.zip

Share this post


Link to post

Traces shows the VoiceGuide service itself is starting fine.

There should be no difference starting the Line Status Monitor from the System Tray icon or starting it by double clicking on its .EXE in the VoiceGuide folder etc. The same program is started. The same configuration files are read in and used.

What do you mean by "get it to run on the other IP address" ? Do you want to run the Line Status Monitor on another system, different to the one that the VoiceGuide service itself is running on? The comment in earlier answer would then apply:

Quote

You will need to ensure that the TCP port 7134 communications between the system on which the Line Status Monitor is running and the VoiceGuide system at 192.168.0.12  are not blocked along the way by any firewalls/routers/etc.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×