Scheduled Job Has Never Been Started

[Guest pernellwb]

 

Hello Support Team,

 

 

There is a job that has been scheduled to make calls today this morning at 9:00 AM but no call was made, not even once, until now... sometimes this happened in the past but eventually it kicked in later in the day..later than the scheduled time.. but today it has never kicked in... were wondering whats happening..

 

attached is the log... please have a look,

 

 

0304_0814_vgEngine_log.zip

 

 

 

your response would be greatly appreciated

 

 

thanks

 

 

[SupportTeam]

It's a pretty big log file (10 MB) and shows calls being made continuously on all ports from 8:14AM until the log finishes at 9:30AM (logging was rolled over to another file).

 

The system looks like it's busy making calls, so maybe you have so many calls loaded that the system that system was busy dialing older calls before it got to dialing the more recently loaded calls?

 

If you want us to look at a particular call then please provide information what would allow us to find in trace file what call you would like us to look at. (eg; Phone number etc).

[Guest pernellwb]

 

 

Hello Support Team,

 

 

We are scheduling a certain job with a higher priority but we guess FIFO queue is being followed in higher order than having the highest priority thats why a certain job only kicks in when the other already-executed jobs are nearing its completion.

 

Are there issues regarding this? Like in our present logs, supposedly a job is scheduled to start at 9:00 AM but it only started kicking in around 12:00nn to 1:30pm the same day,

 

please have a look at the logs with the name of the logs as file names and a little description with it

 

logs_nas.zip

 

 

thanks a lot!

 

[SupportTeam]

If you want to prioritise the outgoing calls then you will need to add the following to the <OutDialQue_SqlSuffix> entry in the <Dialer> section of the Config.xml file:

 

ORDER BY "Priority" ASC

 

eg:

 

<OutDialQue_SqlSuffix>ORDER BY "Priority" ASC</OutDialQue_SqlSuffix>

 

Are you using VoiceGuides own default CallQue database or have you setup your own? What is the max number of calls queued?

 

Ordering by Priority degrades database record retrieval speed if you have a large number of calls loaded, so see if this is something that is going to affect you. If it does then you may want to look at using a server database, like MySQL or MSSQL Server.

 

Looks like the Config.xml that ships with the current version of VoiceGuide did not include this <OutDialQue_SqlSuffix> entry and hence the call priority was not enabled. We will fix the Config.xml distributed in future versions to include this, so call prioritisation will be enabled by default in future versions.