Problems With Dialer

[MannyTC]

I have some random numbers that I am having VG dial that seem to get "lost" sometime during the process after VG dials them. I fed VG 193 numbers to dial today and one of them didn't seem to process properly through all the steps. I have an entry in the OutDial_Dialed log file that shows it was dialed and also entries in the answered 0919vgm.log file that shows it was dialed and answered. I do not have any entries in any of the other OutDial*.log files that show what the result was. I also have a module that runs on hang up that updates a database on my MS SQL Server to show the results of the call and that record was never updated. I have run across this a few times already and am not quite sure what it is. I am planning on feeding many more numbers thru VG daily and I am worried that this is going to come up more. Below is the portion of the 0919vgm.log that shows entries that are related to the dialing of that number. Any advice you can give is appreciated.

 

181844.32 5 ReinitTelephony due to IDLE

181844.37 5 tapic lineDeallocateCall(MainCall:66272) 0

181845.10 5 lineOpen(5)=>

181845.13 5 Waiting for a call...

181845.15 5 LineHandle=66033

181845.20 5 timer set 3 EV_TIMEOUT_ATERIDLE_ALLOWOUT

181845.38 0 dial start any summary:|5:rdy=0|6:idx=0|7:idx=0|8:idx=0|

181846.41 0 dial start any summary:|5:rdy=0|6:idx=0|7:idx=0|8:idx=0|

181847.45 0 dial start any summary:|5:rdy=0|6:idx=0|7:idx=0|8:idx=0|

181848.46 0 dial start any summary:|5:rdy=0|6:idx=0|7:idx=0|8:idx=0|

181848.51 5 timer fired EV_TIMEOUT_ATERIDLE_ALLOWOUT

181848.52 5 ScriptEventCode 9013 iLineState=900

181849.49 5 dial [303,*82,(602) 861-9488,409181148,1800,2030,MoTuWeThFrSaSu,,dxxxB1C1,,0,,C:\RemPlus\Human.vgs,C:\RemPlus\Ans_Mach.vgs,none,60,2,30,C:\RemPlus\No_Ans.vb script:[C:\RemPlus\DBHuman.vgs]

181955.13 0 LoadedVgs_Find C:\RemPlus\DBHuman.vgs at idx=3

181955.18 5 tapi Reply (LineEvReply) ok 66050 0

181955.23 5 timer clear

181955.24 5 [update Database] Running VB Script...

181955.27 5 rv replace start (strlen>500)

181955.29 5 rv ns none[OutDial_RetriesLeft]{2}[OutDial_Result]{Contacted_Human}[scriptEnd_Time]{9/19/2004 6:19:13 PM}[scriptEnd_Goto_Script]{C:\RemPlus\Human.vgs}[scriptEnd_Goto_Module]{}[scriptStart_Time]{9/19/2004 6:19:13 PM}[scriptStart_CalledFrom_Module]{Update Database}[scriptsPath]{C:\RemPlus\}[On Human Answer]{5}[Hangup Time]{9/19/2004 6:19:54 PM}

181955.32 5 eng copy of script ran: vbs_5_1.vbs

181955.37 5 Run Script waiting. iRunWait=1 (shellid=1872, process=152)

181955.38 5 timer set 1 EV_TIMEOUT_CHECKONSTATE

181956.40 5 timer fired EV_TIMEOUT_CHECKONSTATE

181956.41 5 ScriptEventCode 9007 iLineState=1501

181956.43 5 LsRunWaitTillFinished EV_TIMEOUT_CHECKONSTATE

181956.46 5 task completed (shellid=1872, process=152) vgm=17, iRunWait=1, iRunWait_ExeResult_NextVgm=0

181956.48 5 No information returned from program to VG (no VGRUNRESULT_5.TXT or SHLRESLT.TXT)

181956.51 5 rv add [Hangup Time]{9/19/2004 6:19:56 PM}

181956.52 5 Hanging up call... [WaitTillFinished - next module not specified]

181956.55 5 HangupCall_Common Mode=AfterHangupRun

181956.57 5 ReinitTelephony due to IDLE

181956.60 5 tapic lineDeallocateCall(MainCall:66015) 0

181957.34 5 lineOpen(5)=>

181957.37 5 Waiting for a call...

181957.38 5 LineHandle=65947

181957.43 5 timer set 3 EV_TIMEOUT_ATERIDLE_ALLOWOUT

181957.48 0 dial start any summary:|5:rdy=0|6:idx=0|7:idx=0|8:idx=0|

181958.51 0 dial start any summary:|5:rdy=0|6:idx=0|7:idx=0|8:idx=0|

181959.54 0 dial start any summary:|5:rdy=0|6:idx=0|7:idx=0|8:idx=0|

182000.55 0 dial start any summary:|5:rdy=0|6:idx=0|7:idx=0|8:idx=0|

182000.74 5 timer fired EV_TIMEOUT_ATERIDLE_ALLOWOUT

182000.76 5 ScriptEventCode 9013 iLineState=900

[SupportTeam]

I see the number dialed was: "(602) 861-9488"

 

Do you always use telephone numbers with brackets and hyphens in them?

 

Trace shows that call was answered and the recipient of call seemed to press the '5' key. Later the trace shows that the 'on hangup' script (C:\RemPlus\DBHuman.vgs) was called at the end of the call, and the VBScript in the module [update Database] was ran...

 

You may want to place some tracing from within VBScript using the Admin_TraceLogAdd COM commands - that way you'll be able to see in the trace which parts of the VBScript have completed and which parts have not. - This may aid you in determining what is happening.

[MannyTC]

Yes all of the numbers I have been sending have had brackets in them because the database they are originating from has them that way. I did alot of testing early on and never noticed hyphens or brackets causing problems. If you recommend that I remove them then I will.

 

I can put in some tracing in my vbscript but it still doesn't answer the question as to why there is no entry for that dialed number in any of the OutDial logs (OutDial_Contacted_AM, OutDial_Contacted_Human, OutDial_SIT_Unknown, OutDial_Uncontactable_Busy or OutDial_Uncontactable_NoAnswer). All my other dialed numbers seem to have a corresponding entry in one of those OutDial files. Thanks again for your help.

[SupportTeam]

It's pretty strange that the number in the call trace above did not get added to the OutDial_Contacted_Human file. Addition to file should have occurred between these two lines in the trace:

 

181913.66 5 AddRVns [OutDial_Result]{Contacted_Human}

181913.68 5 Live person answered, starting C:\RemPlus\Human.vgs

 

This could be happening if the file is locked by another process and cannot be written to. The attached .exe has extra debugging in this area and will log an error if it cannot write a record to the file. please update your v5.2.3 install with attached .exe

 

You also mentioned that some MSSQL database was not getting updated from the 'on hangup' script as well? Is that still the case or was that record found OK?

VgMulti_5.2.3035.zip

[MannyTC]

I will go ahead and try the new executable and see what happens. My first clue to all of this was the fact that the vbscript that was run from the 'on hangup' script did not update the related record in the MSSQL database.

 

I will let you know if it occurs again and will see if the additional logging helps to pinpoint things.

[MannyTC]

I just noticed from looking at the log I attached that my RV variables that feeds the persons name to the script is empty. I then looked at the original XML file that was sent to VG and found the entire <RV> section to be missing. That would explain why the MSSQL database could not get updated. I will have to find out why that section of the XML did not come over and the other 192 records did. Still leaves us wondering why the OutDial_Contact_Human file was not updated.

[SupportTeam]

The missing RV values could definitely explain why MSSQL update did not happen, as for why the OutDial_Contact_Human did not get updated - have you started using the new .exe?