VoiceGuide IVR Software Main Page
Jump to content

System Re-boot, Deletes Script Assignments

Recommended Posts

Since upgrading to a newer version of VG (5.5.3072 Enterprise version) We have been having trouble with maintaining the line device configuation. Whenever the system has to be re-booted, we lose the line device configuations and get the message no script specified on our second device line. When we use the VG configuation wizzard, the correct path is visible there. We have to complete the wizzard, exit VG then re-launch to set the paths correctly again.

 

Before upgrading this was never a problem. Is there a bug in this version? Or do you have any other suggestions on how to stop this from happening?

Share this post


Link to post

VG.INI shows the script paths defines as:

[TapiDevice1]

Name=Analog Line 1(dxxxB1C1)

Script=C:\VoiceGuide\AAD\Scripts\ValidateAADOutbound.vgs

 

[TapiDevice2]

Name=Analog Line 2(dxxxB1C2)

Script=J:\IVR\VoiceGuide\PreDiabetes\Scripts\IncomingInitCallValidateHRN.vgs

 

[TapiDevice3]

Name=Analog Line 3(dxxxB1C3)

Script=J:\IVR\VoiceGuide\PreDiabetes\Scripts\TestAnsweringMachine.vgs

 

[TapiDevice4]

Name=Analog Line 4(dxxxB1C4)

Script=C:\VoiceGuide\JonahTest\Scripts\TestScript.vgs

I suspect that the network drive J is just not available immediately after the reboot. I'd try moving the script to a local C drive - that way you'll avoid all the problems associated with trying to run applications from drives not local on your machine.

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
×