VBScript For Unanswered Calls

[Guest rmonicat]

Please.

 

CAn you give me some sample code for coding vg.Dialer_OutDialQueAdd instructing it to call a VB script with some VG variables as parameters when the call is not answered.

Thank you.

[SupportTeam]

The sample code at the bottom of the VG Help file's entry on Dialer_OutDialQueAdd in the Help file shows just that:

http://www.voiceguide.com/vghelp/html/com_...tDialQueAdd.htm

 

The RV's set for the call are available on the "Run On Not Connected" program/script's command line - so you can then pass their values as parameters into your "Run On Not Connected" program or script.

[Guest rmonicat]

I've tried the following code. Vb_noatiende contains a string that is acceptable in vb to call llamadanoatendida.vbs with a couple of parameters, a directory and the Outdial result.

 

sc_persona = "c:\ivraplic\fuentes\llamadaatendida.vgs"

vb_noatiende = "c:\ivraplic\fuentes\llamadanoatendida.vbs ""%dirlinea% "" ""$RV[OutDial_Result] "" "

vars = "[rol]{cliente}[conectarcon]{%lineidoper%}[dirlinea]{%dirlinea%}"

vg.Dialer_OutDialQueAdd ("101", 0, 0, 0, "", "", 1, "",sc_persona, sc_persona,vars , 0, 0, 0, vb_noatiende )

:f_vg_lanzar_llamada_para_oper

 

 

 

When the call is not answered vb script engine issues the following error message:

 

There is no file extension in "c:\ivraplic\fuentes\llamadanoatendida.vbs d:\ivr\ivr\lineas\lineaout01 Uncontactable_Busy"

 

It seems like strings beeing changed.

The example you mentioned does not use the "Run On Not Connected" facility.

[SupportTeam]

Please update v5.2.2 installation with attached .exe and try again.

 

As the script you are calling:

 

c:\ivraplic\fuentes\llamadanoatendida.vbs

 

does not have any spaces in filename then you should be able to run things correctly after just updating the .exe

 

If your script had some spaces in it, eg if it was called:

 

c:\ivr aplic\fuentes\llamadanoatendida.vbs

 

then you would need to ensure that vb_noatiende looked like this:

 

vb_noatiende = """c:\ivr aplic\fuentes\llamadanoatendida.vbs"" ""%dirlinea% "" ""$RV[OutDial_Result] "" "

 

Notice the extra "" in two places.

 

It was VG's attempt to add double quotes around the entire "Run On Not Connected" command line that was causing problems if parameters were used. I understand attached .exe fixes this issue.

VgMulti_5.2.2001.zip

[Guest rmonicat]

It worked fine.

Thanks a lot.

[Guest rmonicat]

After testing it deeply I found that, some times, VG calls the routine for unanswered calls twice.

Attached is the trace.

Line 6 called routine at 20:31:45 and at 20:31:59

Line 5 called it only once at 20:31:58

 

Thank you in advance.

 

Note: All traces I sent you this morning show errors. I cannot state that they cause the problems reported but, by sure, they do not contribute to system stability.

llama_dos_veces.zip

[SupportTeam]

Please update your v5.2.2 install with attached .exe

 

This version fixes the "VG calls the routine for unanswered calls twice." bug

 

And you should not longer see the other errors listed in the previous trace.

VgMulti_5.2.2003.zip

[Guest Guest]

After executing the following code Lines start ringing and vgmulti.exe cancels.

 

 

#definesubroutine VG_lanzar_llamada_para_oper(lineidoper,numero,dirlinea,timestamp)

 

sc_persona = "c:\ivraplic\fuentes\llamadaatendida.vgs"

vb_noatiende = "c:\ivraplic\fuentes\llamadanoatendida.vbs ""%dirlinea% "" ""$RV[OutDial_Result] "" "

vars = "[rol]{cliente}[conectarcon]{%lineidoper%}[dirlinea]{6}[tst]{""}"

vg.Dialer_OutDialQueAdd (numero, 0, 0, 0, "", lineidoper, 1, "",sc_persona, sc_persona,vars , 20, 0, 0, vb_noatiende )

:f_vg_lanzar_llamada_para_oper

 

return

#endsubroutine

 

 

vg = ObjectOpen("VoiceGuide.CommandLink")

dd = VG_lanzar_llamada_para_oper("5","101","5","333")

dd = VG_lanzar_llamada_para_oper("6","9,,48992314","6","333")

ObjectClose(vg)

 

 

Trace is attached.

cancela.zip

[Guest Guest]

I forgot to say that after reinstalling previous version, vgmulti did not cancel any more.

[SupportTeam]

This version works fine on our test servers. We've tried multiple queuing like yours as well (changed a bit to make sure it works on our server) and single call queuing.

Does the problems occur on your system when straightforward call queuing like below is done?

What is the programming language you are using? Can you try using the script below and see if there is a problem:

 

.VBS script used on our test system:

set vg = CreateObject("VoiceGuide.CommandLink")
vg.Dialer_OutDialQueAdd  23, 0, 0, 0, "", 5, 1, "","C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs", "C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs","" , 20, 0, 0, "c:\test.vbs" 
set vg = nothing

Call is then made OK, here is the trace:

075742.36  0 cl    Dialer_OutDialQueAdd 23, 0, 0, 0, , 5, 1, , C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs, C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs, , 20, 0, 0, c:\test.vbs,

075742.36  0 DialListDB_AddCall '23', 0, 0, 0, MoTuWeThFrSaSu, 5, 1, , C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs, C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs, , 20, 0, 0, c:\test.vbs ESCALATION:

075743.22  5 dial  [5,23,0,0,2359,MoTuWeThFrSaSu,,5,,1,NONE,C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs,C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs,none,20,0,0,c:\test.vbs,none]

075743.22  0 dial  callque update id=5 next call time 0405160759

075743.22  0 dial  callque DB update returned

075743.22  5 dial  found entry: tel[23] ann[NONE] vgs[C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs] am[C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs]

075743.22  5 Dialing: 23

075743.22  5 MakeCall => 66509

075743.22  5 TimeoutSet 20 EV_TIMEOUT_MAKECALL_NORESPONSE

075743.22  5 TapiCbTrigSet 66509 7002

075743.81  5 tapi  Reply (LineEvReply) ok 66509 0

075743.81  5 TapiCbTrigClear

075743.81  5 linedevstate 2048 0 0

075743.81  5 callstate DIALTONE 66475 0 0

075743.81  5 callstate DIALING 66475 0 0

075743.81  5 callstate PROCEEDING 66475 0 0

075743.81  5 callinfo CALLEDID

075743.81  5 callinfo REASON

075743.81  5 Lev_CallerID [0000,,23]

075743.81  5 rv    add [DNIS]{23}

075743.81  5 callinfo ORIGIN

075751.94  5 callstate CONNECTED 66475 1 0

075751.94  5 callstate CONNECTED 66475,1,0

075751.94  5 WorkingModeTAPI@Connected=

075751.94  5 WorkingModeScript@Connected=

075751.94  5 rv    add [OutDial_RetriesLeft]{0}

075751.94  5 rv    add [$RV_STARTTIME]{5/16/2004 7:57:51 AM}

075751.94  5 rv    add [$RV_DEVICEID]{5}

075751.94  5 rv    add [$RV_CIDNAME]{}

075751.95  5 AddRVns [PathApp]{C:\Projects Parallel\vg32 5.2.1\}

075751.95  5 rv    add [$RV_CALLEDNUMBER]{23}

075751.95  0 dial  callque delete id=5

075751.95  5 AddRVns [OutDial_Result]{Contacted_Human}

 

.... etc

[Guest rmonicat]

It also cancels when calling COM interface from VB (using the code provided).

Attached is the related trace.

Please note that this does not happen when I go back to previous version.

In case it helps, after crash, I restarted VG again and, aparently, it tried to redial and cancelled again.

0515vgm.txt

[Guest rmonicat]

URGENT.

 

Sirs, there is a problem.

This time, replacing by old version does not work.

Simply, it does not start nor cancel, VG screen is not shown.

Task administrator shows it as not reponding.

I need to get back inmediately to some working software.

 

Thank you for your fast response.

[SupportTeam]

Sounds like there is something wrong with the overall system setup.

 

It all works fine for us with both old and new version, and it all worked fine for you before with the old version - but now you say that all of a sudden it does not work for you with the old version... you should see what was changed on your system between the time when it was working and now...

[SupportTeam]

Please try placing attached OCX in Windows' System32 directory when using the new version of .exe (VgMulti_5.2.2003.zip)

TapiWrap_CallerID_fix_for_D82JCT.zip

[Guest rmonicat]

It is now working again.

Thank you very much.

 

 

Note: related to my other post. In this test, script did again start before line was picked up. I´ll send you a record file as you suggested.