johnr Report post Posted 12/13/2007 06:43 PM Hi, I'm running VoiceGuide 6.0.3243 Professional, on Windows 2000, with a Dialogic 4-port card. Everything works perfectly EXCEPT: After the user hangs up (or reaches a "hangup" point in the script"), Voiceguide returns that phone line to "Waiting for a call" again very briefly, then immediately starts the script over again. It does not detect that there's nobody on the line, and it doesn't hang up the line. In fact, to a caller who doesn't hang up, they're immediatelly re-entered into the start of the script. Manually hitting "hang up" on the VoiceGuide panel doesn't work, either - it drops the line briefly, then immediately picks it up again. Even if this worked, it would not be a practical solution. Restarting VoiceGuide fixes the problem. Calling in on the line that's "hung" open causes a busy signal for the caller, but VoiceGuide immediately drops the line and returns to "Waiting For A Call" status. Suggestions? Share this post Link to post
SupportTeam Report post Posted 12/13/2007 08:40 PM This is most likely caused by a Dialogic card falsely reporting a phantom "Ring" on hangup - which causes VoiceGuide to start a new call as it thinks a new call has arrived on the line. A fix for this situation has been provided a while ago. Updating to the latest version of v6 will fix this issue. If you are still seeing problems after updating to latest version of VoiceGuide the please post the trace logs from the system which will allow us to see what is happening on the system. Share this post Link to post
johnr Report post Posted 12/27/2007 03:43 PM This is most likely caused by a Dialogic card falsely reporting a phantom "Ring" on hangup - which causes VoiceGuide to start a new call as it thinks a new call has arrived on the line. A fix for this situation has been provided a while ago. Updating to the latest version of v6 will fix this issue. If you are still seeing problems after updating to latest version of VoiceGuide the please post the trace logs from the system which will allow us to see what is happening on the system. That fixed the problem, Thank you. Share this post Link to post
