Vb Script Not Ran On Outbound

[yanky]

Using VoiceGuide V6.

 

There are three calls in the attached file to the same person (17778889999), 15 minutes apart. The first two work exactly perfect, but the 3rd call doesn't run the VB Script it is supposed to. Could you please tell my why? (I've changed the actual phone numbers from the original for security purposes.)

 

VB_Script_Not_Run.txt

[SupportTeam]

Is the VBScript that you refer to in module [schedule Retry], ran from the AfterHangup script ?

 

In v6 there is a limit on the number of modules that can be executed in the AfterHangup script. Please try rationalizing the Evaluate Expression modules or placing all the various expressions/scripts into one larger VBScript and running that script.

 

v7 can handle much larger AfterHangup scripts.

[yanky]

Is the VBScript that you refer to in module [schedule Retry], ran from the AfterHangup script ?

Yes

 

 

In v6 there is a limit on the number of modules that can be executed in the AfterHangup script.

 

All three calls were supposed to be handled exactly the same way. If all three calls were going through the exact same modules, why would they work the first two times but not the third?

 

We have been using these modules without any problems for a week or so. This is the only call that has ended abruptly like this. I was hoping you could tell by the log file what happened to this particular call.

[SupportTeam]

It isn't possible to fully tell from v6 traces what events lead to this state, but the events in log around the module [schedule Retry] show that the number of modules executed in a row exceeded the limit.

[yanky]

This situation happened again. Again, same script for the for all 3 calls, but just the 3rd was not made.

 

but the events in log around the module [schedule Retry] show that the number of modules executed in a row exceeded the limit

 

How can we read the log to find if the modules executed exceeded the limit?

 

thanks,

yanky

[SupportTeam]

In version 6 of VoiceGuide you will see log entries like these that are a side effect of too many modules being used in the After Hangup script:

 

151746.24 6 timer set 0.1 CMD_RUN_SAME_MODULE_AGAIN

151746.24 6 timer set ignored - waiting for line re-init to occur first (EV_TIMEOUT_TIMETOREINITLINE)

 

You should condense the chain of Evaluate Expression and VBScript modules into one VBScript module. (or upgrade to v7 which allows using long After Hangup scripts).

 

 

 

[yanky]

So if this "After Hangup" script works fine on the 1st two calls, is something not refreshing/releasing on the 3rd attempt?

 

"too many modules being used in the After Hangup script"

 

Or just the opposite.....

Is it possible it isn’t a limitation on the number of modules, but the length of time since the hang-up? Maybe too much time passes between the hang-up and the modules running?

 

This is only happening to about 2% of our calls.

 

Thanks again for all your help,

yanky

[SupportTeam]

It is possible that the time since hangup is affecting this as well.

 

In v6 compressing the AfterHangup script to as few modules as possible is your best option. Ultimately it is possible to do everything that you require from a single VBScript module so that is what you should aim for to ensure that all the required work gets done.

 

As mentioned before v7 does not have such limits.