Timeclock Question

[thirdhatch]

I know this is a favorite of Matt's based on the forum posts.

When agents log out of the vicidial system is there anything in place to clock them out automatically after a certain amount of time? I can see that this was requested several times but have not seen if the feature was implemented or not.

Thanks!
Bill

[williamconley]

Not yet as far as I know. But it should be fairly simple as long as you are content with a timer that checks for logged in agents (timeclock) and compares to logged in agents (Vicidial) and removes timeclock agents who are no longer logged in as agents. Running every minute or 5 minutes or ... whenever.

Also, newbie suggestions:

when you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

Happy Hunting!

[thirdhatch]

Thanks, William. None of the "newbie" suggestions are really pertinent to my question but I will keep it in mind for future posts where those issues might come in to play.

For the record, I have purchased a copy of the manager and agent manual and have read all of the stickies, along with all of the forum posts in regard to the timeclock. I have been using Vicidial for more than three years now, mostly without problems, but have occasionally had questions here and there. I've even exchanged emails with you about security.

[williamconley]

The point of relevance to you is not what I was trying to make. The point of posting your system specifications is considered a cost of the FREE support on this forum. It also may help us answer your questions (because features and capabilities are often Version based!). But make no mistake: the posting of your system specs is not for you, it's for Google! So the next guy with this question can find this post if he happens to have your system specs.

So ... post it if you have an installation and you may find that one day you "locate" someone elses solution to a problem You have because they posted their specs ...

Oh: And if you post your system specs, we can all tell you are likely to know what you are talking about. It takes a certain amount of knowledge just to get all that carp available for the post.

Although I admit I am somewhat ... fussy about it. It has helped quite a bit on many occasions. Besides: it ain't my rule, I am just a (noisy) lurker here. LOL

And *I* am more apt to answer questions in More Detail from those who cooperate in this fashion. It tells me how technically oriented you are. After a fashion.

Back to your question: There have been many who delve into the "log the lazy bum out" area, but to date no one has paid for a completed resolution to any of the suggested scenarios. Nor has anyone posted a doityourself fix that Matt has included. It's not really that complex, but ... for some reason it has just never happened, even though many flavors of solution have been suggested.

[thirdhatch]

That's a fair enough explanation, William. I am a little surprised to find no hooks in the agent or non-agent apis for clock functions. The capabilities built into these are pretty considerable as it is so I almost took it for granted that there would be something there. Perhaps a bounty is necessary?

Anyway, we are using the clock because the Agent Time report is showing inconsistent numbers that seem to resolve themselves when the sql server reboots each night. I will make a seperate post about this which includes all of my specs. Hopefully someone can help.

[williamconley]

Perhaps a bounty is necessary?

Necessary is subjective. Paying someone to add the feature is of course more reliable than "hoping it shows up one day". Paying The Vicidial Group is the only guaranteed way to get it in the codebase (so it'll always be there in an upgrade).

This is not a Windows Licensed product that charges $20k per call center. Upgrades do not net The Vicidial Group any $$. Nor does adding a feature. They do maintain security updates for the good of the community and attempt to resolve any vulnerabilities as quickly as possible. But adding features, even small ones, is based on the need of the community ... which is measured in large part by $$.

Posting a Feature Request in the Issue Tracker is good. Requesting a price (and offering a specific fee you think would be fair, that you are willing to pay right now ...) is a good way to get attention. But remember that there are hundreds of "feature requests" submitted on a regular basis. To stand out and get your feature ... pay someone to generate it and submit a DIFF file! (or pay The Vicidial Group and it's just "in there" at the next upgrade).