Outdialer Vb Script, No Connection

[Guest henrik@abcgroup.dk]

Please excuse me if my questions are basic.

 

I am currently checking if I can use your system for my purposes and until now, everything looks fine.

I use your VG Evaluation for dialogic and use the "Dialogic D41JCT-LS EU"

 

The outdialer will be used in my setup.

 

In this relation, I was wondering how the possibilities are if a call is not connected and the value set for redials has been fulfilled.

What I need to do is to initialize a(n)

- phonecall

- text message (SMS)

- e-mail

- writing it in a database

- or similar

 

on basis of the specific telephonenumber that didn't pick up.

 

Now most of this is a task of programming outside the scope of Voiceguide, but the export of the telephonenumber dialled is vital. The only way I see this can happen is through the "VBScript to run if the call was not connected" on the Tabpage "Redial" in the Telephone Number Loader.

 

I beleive this single line is to specify where the program is (the path).

 

Is there any other way of retrieving the number in the call list that did not answer? in a "notanswered" file?

 

I thank you in advance for your answers.

[SupportTeam]

Is there any other way of retrieving the number in the call list that did not answer? in a "notanswered" file?

Yes. A file will be created in VoiceGuide's \data\ subdirectory:

 

OutDial_Uncontactable_NoAnswer.txt

List of calls which were not answered and rung out awaiting answer.

 

OutDial_Uncontactable_Busy.txt

List of calls which were not answered as the busy tone was heard.

[Guest henrik@abcgroup.dk]

hi.

 

Thank you for your answer.

 

Is it correct assumed that the "VBScript to run if the call was not connected" line is just to specify a path for the script?

 

I have experienced the following problems with the dialer:

 

a.

When dialing, it depends on the specific telephone answering the call whether the dialer registers that the call has been picked up.

A specific example is that VG dials out to a number and the call is answered by a traditional phone. The system works as it should.

Redialling the same number but answering with a different telephone (on the same line) - this time a portable (not cell phone) - and the VG didn't play anything but a single "beep".

Calls retried several times with similar problems.

How come? How can I prevent this?

 

b.

A different number is dialed. First time the VG works. Second time the VG dials and then starts running the VG script after a short while. Unfortunately the phone had not even been ringing before some way through the VG script. The phone was answered and you could hear the VG script at the point it was, not from the beginning.

Case retried several times with similar problems.

How come? How can I prevent this?

 

c.

Last but not least, I called two different cellular phones. On one the line was cut as soon as answered. On the other one the VG script worked perfectly.

Case retried several times with similar problems.

How come? How can I prevent this?

 

All calls are done inside europe, especially Denmark.

 

I hope you will be able to answer / help on my 4 issues and that the issues are questions of setup.

 

Thank you in advance.

 

Henrik

[SupportTeam]

Is it correct assumed that the "VBScript to run if the call was not connected" line is just to specify a path for the script?

Yes.

 

Regarding the problem calls:

Could you please post a copy of VoiceGuide's Trace Logs which captures the outgoing call , this will allow us to see what happened.

 

Enable logging by setting the log levels to 10 in VG.INI as per below:

[Log]

 

VoiceGuide=10

Then restart VG and make a test call which demonstrates the problem.

Trace files will be created in VG's \log\ subdirectory.

Please post the traces.

When posting traces/scripts please .ZIP them up and post them as attachments.

 

When using analog lines the Dialogic card must do frequency analysis when answering the call, and noise or distortion on the lines will sometimes confuse this detection process.

 

Only ISDN lines provide signaling to indicate when the called phone has been picked up. If you must have 100% detection of when call is answered then you should look at using T1/E1 ISDN lines.

[Guest henrik@abcgroup.dk]

Hi again.

 

another basic question on the same subject, I'm still a beginner in the programmers world:

 

When you have a call which is not connected and the "onnotconnect" sctript is run, is it possible to forward the CIDnumber and call time directly to the script instead of making a procedure that collects the information from the "outdial_uncontactable" log file?

My fear is that I one day will have the scenario, where the script is called and before it is looking for the last entry in the "outdial_uncontactable"log, another entry has appeared, so I will retrieve the wrong entry.

Would it be possible to make something like "C:\scrip_to_run_on_not_connect.exe, CIDnumber, CIDtime" ? Would this or a similar entry forward the telephonenumber called to the script?

 

I look forward to your ever helping anwers.

 

Regards

Henrik

[SupportTeam]

The OnNotConnected script should have access to all the Result Variables which were set on the line at the time of the call being made.

This will include the number dialed.

Just use the RVs in the OnNotConnected script and VoiceGuide will replace them with the RV's value before running the script.