Wake-up calls (1.2.4): Problem if invalid extension specified

[LesD]

I have been using this just fine till the grandchildren arrived and broke it!

First, it allows you to enter and invalid extension number.

Not the end of the world (except you may not get woken up!) but the consequences are a problem.

I have a landline connected to a OpenVox card. I found that I could not make or receive calls on the line. I decided to shut down Asterisk to do a reset and found it started to do a 120 second countdown while I know that there were no calls in progress.

Checking Channels in Asterisk Info it showed

Channel Location State Application(Data)
Zap/1-1 400@from-internal:1 Up AGI(wakeconfirm.php)
1 active channel
0 active calls


Basically a wake up call had been set for non-existent extension 400, the time had expired and for some reason the Zap/1-1 channel then just hung. This has now happened several times.

Stopping Asterisk and restarting the zaptel service solved the problem (I have not tried doing just an Asterisk restart)

Using FreePBX 2.9.0.2

 

[LesD]

The home page for this module is here, but it won't do you any good. There are no active members left on the dev team, and the site is pretty much ignored these days. I have added your bug to the issue tracker, but I would not expect any action on it.

Thanks. The temporary solution will just have to be duct tape if I catch them fiddling!

You are running FreePBX 2.9, do you know about this bug?

Yes thank you. I came across it in an earlier thread.

 

[LesD]

The home page for this module is here, but it won't do you any good.

There is a ticket there (#144) to which I would like to add a comment (just in case it is ever actioned) but can't see how to post anything nor how to set up a login account. How can I post something there?

 

[rossiv]

Speaking of porting to GitHub, I made some changes a while back on my system that let me make multiple wake up calls. Interested? Sorry-OT I know.

 

[LesD]

Post it here and I will link it. New registrations require manual activation and site admin is AWOL.

The topic there is related to when someone answers a wake-up call but does not key a response - either hangs up or leaves the phone off the hook.

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 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.

 

[tm1000]

Go go go github

Speaking of porting to GitHub, I made some changes a while back on my system that let me make multiple wake up calls. Interested? Sorry-OT I know.

 

[rossiv]

Done and done. I think I did it properly.

 

[rossiv]

That makes you one of the few active members that has worked on this module. The project needs a new caretaker, interested? You can create your own job title, how about High Commander.

I can't take it on alone, but I will certainly help.

 

[LesD]

Looks like we can hopefully look forward to some action on this so I have taken the liberty to post my wish-list.

0. Option to store more than one alarm (already requested)

1. Option for repeating alarms - repeating untill cancelled.

2. Option to select the day(s) of the week for a particular alarm

The combination of the above would provide for most situations.

3. Quick path to set up a simple one off alarm

4. Option to record a message to be played back when the alarm goes off.

5. The existing General Config options pull-down lists are too restrictive (I have had to modify the database by hand).

6. The General Config Ring-Time/Retry-Time/Max-retries should ideally be changeable for each alarm.

My background is in Mainframe and subsequently Windows based commercial software predating web development so I can't offer to help with the coding but I would be happy to do any necessary testing.

 

[LesD]

1. Ring time starts at 20 seconds. Much too long for my usage.

2. Max Retries: Starts at 2. I need 1. Zero could also be useful sometimes.

Why does it have to be drop-downs?

What is wrong with manual entry plus some validation in code? I assume writing validation code is not a major issue.

I feel that the name should change from Wake Up Calls to a more generic Alarm system - the old name hinders the functionality.