Hotel Style Wakeup Calls

The current behavior is for an answered call to be a "canceled" wake up call - even if no options are selected. An unanswered call is retried the number of times specified in the configuration screen.

Would a check mark box that said "Treat Hang Ups as Retries" - and uses the existing retries be in the ball park of what you hope for?

It seems like wakeconfirm.php is the place to find and do that. I took a quick look and didn't find an obvious quick fix. But I'm sure it could be done.

This could be done by changing wakeconfirm.php so that instead of just hanging up, the call is always snoozed for X minutes (defined by config - let's say 2 minutes for the sake of argument, since we're talking about non-responsive people, they may need extra encouragement) unless specifically canceled. Then we need to keep track of how many times it has gone through and put an upper limit on it (either by time or by iterations) so that we don't ring the extension all day in the room next door to someone who needs their sleep - which happens to me ALL the &^%$#ing time in hotels.

So to sum up:
Have it reschedule for X minutes if not specifically canceled.
Have it count the number of reschedules and either only allow Y minutes worth or Y reschedules (keep it low) before auto-canceling.

This would solve the problem and not take too much to do. The iteration count or original/termination time could be made part of the filename, since call information is not (currently) stored in the database.

Perhaps - but it seems to me, changing it so that a hangup is treated exactly the same as a no answer might be simpler and just as effective.

A "no answer" gets retried according the the already established schedule - until the retry limit is reached.

I have reclassified this as a bug - instead of a feature, increased the severity to HIGH, and marked it reviewed (meaning ready for developer action). The reason is voicemail / answering machines.

Today, if the wakeup call rings longer than the timeout (number of seconds) prior to sending a call to voicemail - it will in fact go directly to voice mail. Voice mail records some of the wakeup call, and then hangs up on the call. This hang up is treated exactly the same as a human being answering and then hanging up - which cancels the wakeup call. This isn't good -

I agree with adding "Treat hangups as Retries".

If this was added, would it offset the retry wakeup call by the amount of time the message was recorded in voicemail? If so i would have another config option to hang up on call in X number of seconds or start the retry wakeup call counter when the call is first answered.

Thanks,

Jason

As envisioned, we really mean to do is treat hangups as no-answers.
A "no answer" gets retried according the the already established schedule - until the retry limit is reached. This way no other options need be specified.

Posted on behalf of LesD from here: http://pbxinaflash.com/forum/showthread.php?t=11552

I do not agree with the proposal that "As envisioned, we really mean to do is treat hangups as no-answers." That may answer the needs of someone in bed who fails to get up but a 'wakeup' call can and is also used for general reminders.

If I set an alarm in the office, I just want to pick up and hang up. I do not want to have to start listening to prompts and pressing buttons.

This really needs to be a setup option as to how a user wants the system to function.

Even better, there should also be an option to override the default as each alarm is set - with a hangup at that point defaulting to the setup default