Problem With Dialing

[Guest elSueco]

Hello!

 

I have 3 machines running vg for dialogic 6.0.3095. I know this version is problably old but it has been working very well until now (so please can you try help me whithout telling me to update?)

As you recommend me a long time ago I have scheduled a vbs (in the scheduled tasks) in each machine to make a call to the other systems. If the script calling receive a dtmf tone then that IVR system is working. So this vbs writes writes into OutDialQue.mdb the following:

columns="PhoneNumber,ActivateTime,DayTimeStart,DayTimeStop,DaysCallAllowed,LineSelec

ion,Priority,AnnounceMessage,Script,OnAnswerMachine,RV,

AnswerTimeout,CallRetriesLeft"

values ="'47',0,1,2359,'',',dxxxB1C4,',1,'','C:\Voice\Monitoring\get_DTMF.vgs','','',0,0"

 

The system calling uses extension 45 and the other systems uses extension 47.

 

In the log file you can see that there are two errors. I´ve checked at the same time when making the call in asterisk and it says that extension 47 answered the call. Can you see anything wrong in the log?

0614vgm.txt

[SupportTeam]

Trace shows that the Dialogic card reported that the FAX tone call was played by the system which answered the call.

 

If no fax tone was played then you should look at tightening the fax tone definition to reduce the likelihood of false fax tone detection.

 

We do recommend updating to latest version as well, but VG version would not affect Dialogic's tone detection.

[Guest elSueco]

What about the two error lines in the vgm text file? Don´t they have anything to do with this behavior? I´ve been looking in the forum (everywhere) but I couldn´t find what is triggering these two error messages. What do they mean?

 

Thank you for your help!

[SupportTeam]

I think that that error means that there was a problem adding an entry to the "Uncontactable_NoAnswer" result file.

 

You should update to latest version of VG - I think this issue has been resolved in the more current versions of the software.

[Guest elSueco]

Hi!

 

I´m trying to use the 'OnNotConnected' option in the OutDialQue.mdb file with just a vb script to hang up the line if nobody answered the call. Voiceguide hangs up the call when it receives [OutDial_Result] {Uncontactable_NoAnswer}, which it is ok. The problem is that I cannot make another call until I press the 'Hangup call' button in the voiceguide window.

 

The vb script just contains this four lines (found it in the tutorial):

Dim vg

set vg = CreateObject("VoiceGuide.CommandLink")

 

vg.Line_Hangup $RV_LINEID

set vg = Nothing

 

In the log file there are some error messages (which I don´t undestand where they are coming from) and I think that´s why I´m having problems. Do you want me to send you my script or something? I´m in a hurry, we can´t trust the system since this is a part of our monitoring system.

 

Thanks!

0618vgm.txt

[SupportTeam]

There should be no need to run a VBScript like that - the call is getting hung up by VG at almost the same time as well. Maybe issuing this hangup form the script at the same time is partially responsible for the issues we see here?

 

It's probably best for you to update to latest version, that way if you still have problems we can try to setup a similar system in our labs for testing.

[Guest elSueco]

Hi!

 

Ok, I´ll try with the latest version. How can I download it? When I try from your site I have to fill a form and I get a link in my email to a .exe file. I have already voiceguide installed on my computers. Could you zip the files and send them to me or give me a link where to download it?

 

Thank you!

[SupportTeam]

and I get a link in my email to a .exe file.

Yes. Download the file pointed to in that link.

 

Then backup you Config.xml/ConfigLine.xml and any script you want to keep and then uninstall the current version of VG. Delete the VG directory then install the new version of VG and re-instate the Config.xml/ConfigLine.xml files and scripts.