Jump to content


< Back to Forum


 

After Hangup Script Did Not Run For One Call


  • Please log in to reply

#1 iTime 02 April 2016 - 06:29 AM

Hi VG support,

Our Script has a "Post Hang Up" script that is set to run after hangup.

It is referring to old path (before 64 bit) like "C:\Program Files\VoiceGuide\Scripts...." without "(x86)", but VG seemed to be able to search through and find its correct path including " (x86)".

However, there was one call that failed to run this:

 

 

224212.079   7   3   1       after hangup script as supplied: [C:\Program Files\VoiceGuide\Scripts\IntelliTime\PostHangUp_Hiring.vgs]

224212.079   7   3   1       FindFullPathToScript_VgsOrVgp start [C:\Program Files\VoiceGuide\Scripts\IntelliTime\PostHangUp_Hiring.vgs]
224212.079   7   3   1 WARN  cannot find any of these scripts [C:\Program Files\VoiceGuide\Scripts\IntelliTime\PostHangUp_Hiring.vgs] or [C:\Program Files\VoiceGuide\Scripts\IntelliTime\PostHangUp_Hiring.vgp] or [C:\Windows\system32\PostHangUp_Hiring.vgs] or [C:\Windows\system32\PostHangUp_Hiring.vgp]
224212.079   7   3   1 WARN  could not find AfterHangup script
224212.079   7   3   1       HangupCall (AfterHangupScriptError_RecordDelay) crn_in=0, L1=Disconnected, L2=Running_Normal, lPlayId=0, lRecId=0
224212.079   7   3   1       HangupCall crn_connected=0, crn_NewCallArriving=0, crn_CurrentMakeCall=0, crn_InProcessOfReleasing=8000001
224212.079   7   3   1       rv    add   Hangup Source|AfterHangupScriptError_RecordDelay
224212.080   7   3   1       HangupCall sScriptToRunOnHangup=[C:\Program Files\VoiceGuide\Scripts\IntelliTime\PostHangUp_Hiring.vgs]
224212.080   7   3   1       no script running on this line. AfterHangup script will not be ran.
224212.080   7   3   1       rv    add   DropCall_Source|Hangup the Call
224212.080   7   3   1       crn 0 set to crn_InProcessOfReleasing 8000001
224212.080   7   3   1 state Hanging up... [AfterHangupScriptError_RecordDelay]

 

 

If you see other calls, it looks like VG was able to find the correct path and ran it successfully like the one below:

 

125946.387   7   7   2       after hangup script as supplied: [C:\Program Files\VoiceGuide\Scripts\IntelliTime\PostHangUp_Hiring.vgs]

125946.388   7   7   2       FindFullPathToScript_VgsOrVgp start [C:\Program Files\VoiceGuide\Scripts\IntelliTime\PostHangUp_Hiring.vgs]
125946.388   7   7   2       after hangup script after searching: [C:\Program Files (x86)\VoiceGuide\Scripts\IntelliTime\PostHangUp_Hiring.vgs]
125946.388   7               LoadedVgs_Find C:\Program Files (x86)\VoiceGuide\Scripts\IntelliTime\PostHangUp_Hiring.vgs at idx=2
125946.388   7   7   2       After Hangup script run first module
125946.388   7   7   2       L2_set Running_AfterHangup  (called from StartAfterHangupScriptIfDefined)
125946.388   7   7   2 t     timer clear (force=False)
125946.388   7   7   2       RunModule start
125946.388   7   7   2       RunModule start Run VB Script, [ProcessFinishUpHiring], iModuleIdx=69, previous: vgm=9, vgs=2:1
125946.388   7   7   2 t     timer set   60 sec : EV_TIMEOUT_GOTOMODULE
125946.388   7   7   2       QueueUserWorkItem vbScript : modVbs
125946.389   7   7   2       HangupCall exit after starting afterhangup script
125946.389  22   7   2 task  runscr Run_VBS vgm=69, file=, engine=[WScript]
125946.389  22   7   2       runscr strIni_moduleRunScript_Engine=WScript
125946.389  22   7   2 state [ProcessFinishUpHiring] RunScript vbs, onhold=

 

 

I have modified the path value of "Script to run when call is finished:" to include "(x86)" now, but I would like to know why this failed only for this call and it would not happen anymore.

Please see the attached files.

Thank you.



#2 SupportTeam 02 April 2016 - 10:22 AM

The specified "After Hangup" script did not exist. That's why no "After Hangup" script was ran.

 

In cases where the specified "After Hangup" script path points to a non-existing file, VoiceGuide will look in the directory where the current script is running to see if the "After Hangup" script is there instead, but in this case no script was even running on the line so that did not happen.

 

In general, when specifying "After Hangup" script path, it should be ensured that it points to a file that exits.



#3 iTime 02 April 2016 - 10:31 AM

Yes, I understand that VG will look for the directory where the script lies, but why failed only on that specific call?

As you can see there are several more calls that detected answering machine, exact same script and same path to find the same "PostHangup_Hiring.vgs." (We only have this post hangup script for all occasions)

 

You can tell (from above) that both failed and successful cases got to:

 

 

 FindFullPathToScript_VgsOrVgp start [C:\Program Files\VoiceGuide\Scripts\IntelliTime\PostHangUp_Hiring.vgs]

 

so I do not understand your explanation:

 

 

in this case no script was even running on the line so that did not happen.

 

Would you elaborate this part? Does it mean there are differences between those 2 cases even if they have got to the same point of process?

Thanks again.



#4 SupportTeam 02 April 2016 - 10:55 AM

The call ended while VoiceGuide was still waiting for the 'answering machine message' to end.

 

The script does not start until the 'answering machine message' ends.

 

As no script was running on system at time the call ended, VoiceGuide did not know what other directories to look in to check if the "After Hangup" script coupld perhaps be there instead.

 

in the provided traces this was the only call that ended while the 'answering machine message' was still playing.

 

(also: most likely in this case it was not an actual voicemail welcome message, but some sort of pre-recorded annoucement and the call was ended immediately afterwards)



#5 iTime 06 April 2016 - 01:39 AM

Thanks for the clarification.

So, does this mean it would be fixed even if I corrected the path for "Run After Hangup" setting in the script?

I am trying to prevent this from happening.



#6 SupportTeam 06 April 2016 - 08:02 AM

 

So, does this mean it would be fixed even if I corrected the path for "Run After Hangup" setting in the script?

 

Yes. If the path to the 'After Hangup' script is set correctly - pointing to an existing script - then VoiceGuide will run that 'After Hangup' script...