john_lo Report post Posted 11/19/2007 08:19 PM VG 6.0.3310 24 line for Dialogic. Purchased the product and registered back in June. Been building scripts and taking calls just fine. For some reason today, when I try to launch VG it tells me that my registration is not valid. No changes were made to hardware or software, but this machine was rebooted over the weekend. Now it won't work at all, and won't let me open the script that I need to edit (it's actually less functional than the eval mode??). Dialogic board tests fine. The unique ID it's providing is different that the one I registered, so my previous code doesn't work. I've already emailed sales@voiceguide.com and haven't heard anything back yet. It's critical that I get this service back online as soon as possible. I appreciate any help you can provide on this, and hope to have a speedy resolution. I would also hope to have some reason or solution to this so I can feel confident moving this service into production. Up to this point I haven't really minded that you have no telephone number for sales or support, but I can't have this type of outage once it's in production. I don't believe we did anything here to cause it, but if we did I need to know what it was. We've rebooted this server before with no issue. Thanks, John Share this post Link to post
SupportTeam Report post Posted 11/19/2007 08:39 PM Most likely the Dialogic card service has not been fully started before starting VoiceGuide. Please reboot system and before starting VG make sure the Dialogic service is started. Use the Dialogic Configuration Manager to ensure the Dialogic service is started. won't let me open the script that I need to edit That a bit strange as the script editor is not affected by licensing. Same script editor is used in the evaluation and registered versions, the script editors features are not affected by whether a license is present or not. What error messages do you see when trying to open the script? Share this post Link to post
john_lo Report post Posted 11/19/2007 09:13 PM Your initial suggestion corrected it. I can't remember the exact verbage, but it sounded like it either couldn't access the script file, or possibly didn't know which one to open (although it didn't prompt for location or anything like that). I appreciate your quick help with this. Other than this issue, it's been a very stable product here. Thank you, John Share this post Link to post
