Simple Hotel Style Wake-Up Calls – THE MODULE

[Hat]

1.2.2 Works

Latest version installs and works, thanks Tony.

Tom

 

[stucker]

Upgrade in tests were successful. Thanks tshif!

 

[tshif]

Latest version installs and works, thanks Tony.

Tom

Upgrade in tests were successful. Thanks tshif!

Its amazing how well it all works when I don't leave typos in the code! Thanks for being patient -

-tshif

 

[tshif]

No /etc/sysconfig folder on Ubuntu. Time is in /etc/timezone.
I created the file date.php with the following contents:

<?php
echo date('l jS \of F Y h:i:s A');
?>

and it echos the correct time/date, now I am relly puzzeled?

-J

I don't see a solution to this posted - was one found?

 

[tshif]

Thanks to user patrick_elx, we can now add Elastix to list of known and tested distributions for Hotel Style Wakeup Calls! Thanks Patrick!

This module upgrade has been tested against and been verified to be functional, and compatible with the security models used in the following distributions:

Fonicatec PABX
Foncordiax
PBX In A Flash
TrixBOX CE
Elastix

Asterisk Version Compatibility
This module has been tested and found to work correctly with Asterisk versions 1.4 and 1.6.

 

[tshif]

Hotel Style Wakeup Calls Module Maintenance Release 1.2.3

Hotel Style Wakeup Calls Module Maintenance Release 1.2.3

The Hotel Style Wakeup Calls module has been updated.

This is a maintenance release. Upgrading is not required.
Please get the upgrade here.

This maintenance release has four changes:

1. Provide pop-up flyout help text when hovering over field prompts

2. Canceling your wakeup call gets you hung up on (rude)

3. Some configuration options are not flexible enough

4. amportal.conf parsing grabs wrong data for dbname

This module upgrade has been tested against and been verified to be functional, and compatible with the security models used in the following distributions:

Fonicatec PABX
Foncordiax
PBX In A Flash
TrixBOX CE
Elastix

Asterisk Version Compatibility
This module has been tested and found to work correctly with Asterisk versions 1.4 and 1.6.

 

[witdirect]

I have tried to follow instruction to install module and it keep getting this error.

The following error(s) occurred processing the uploaded file:

File must be in tar+gzip (.tgz or .tar.gz) format
You should fix the problem or select another file and try again.

Any ideas?

 

[VaHam]

Ampdbname

I was having a problem getting callerid to show as entered in the database and also with some other functionality.

I poked around and noticed that wake.inc looks for a variable in /etc/amportal.conf call AMPDBNAME.

For some reason I didn't have that variable in the amportal.conf so I just added it and made it the same as AMPDBENGINE which is asterisk.

Voila all features and the caller id now work!

 

[trevorlc]

Detect callerID instead of channel

Awesome module. Use it everyday. Thanks for all your hardwork!!!!
I have a slight problem.
I've switch to useranddevice mode with trixbox.
This way I have extension 200 which I reference in my IVR, business cards etc etc.
Then I have 3 devices, 1201 (ATA), 1202 (Softphone), 1203 (IPhone via siphon)
Now all three devices can register and ring, buy having extension 200
as a fixed user on each of the devices. This gets around the multiple
devices registered to the same extension. Allows all my devices to ring
at the same time when someone dials 200.
Anyhow. With this method, if you try to dial the device 1201, it will not ring.
I assume you cannot dial a device, only a extension. So to ring 1201
you just dial extension 200. ok fine that the way I want it. The device
numbers I can forget about, they are only for backend purposes.
However, with the wakeup call module. When I dial from the device 1201 (ATA) the device has a fixed user logged on which is extension 200. So
the callerID or extension the wakeup call should detect and call back should be 200, however it detects and wants to call back 1201, which cannot be ringed. I've done a little research and found that in wake.inc, which your wakeupphp file looks to, has a setting for
$parm_chan_ext = 0;
0 will use callerID info and 1 will use channel. I assume the module is ignoring this as it seems to be trying to wakeup call me on the channel and not the callerID. When I dial from this device to another extension internally, I see my CallerID as extension 200. So I know the device is presenting the correct CallerID from the fixed user 200.
Any ideas as to what could be causing this. I did find a work around as to enable device 1201 as a operator, thus when calling into the wakeup call I could specifiy manually the extesnion 200 that I want to ring for wakeups, but I would like to get it working automatically as also though you would like to be aware of this bug as it may help other things.
Let me know. And thanks again from some great software.
Trevor.

 

[tshif]

I have tried to follow instruction to install module and it keep getting this error.

The following error(s) occurred processing the uploaded file:

File must be in tar+gzip (.tgz or .tar.gz) format
You should fix the problem or select another file and try again.

Any ideas?

Did you get this working?

 

[tshif]

Awesome module. Use it everyday. Thanks for all your hardwork!!!!
I have a slight problem.
I've switch to useranddevice mode with trixbox.
This way I have extension 200 which I reference in my IVR, business cards etc etc.
Then I have 3 devices, 1201 (ATA), 1202 (Softphone), 1203 (IPhone via siphon)
Now all three devices can register and ring, buy having extension 200
as a fixed user on each of the devices. This gets around the multiple
devices registered to the same extension. Allows all my devices to ring
at the same time when someone dials 200.
Anyhow. With this method, if you try to dial the device 1201, it will not ring.
I assume you cannot dial a device, only a extension. So to ring 1201
you just dial extension 200. ok fine that the way I want it. The device
numbers I can forget about, they are only for backend purposes.
However, with the wakeup call module. When I dial from the device 1201 (ATA) the device has a fixed user logged on which is extension 200. So
the callerID or extension the wakeup call should detect and call back should be 200, however it detects and wants to call back 1201, which cannot be ringed. I've done a little research and found that in wake.inc, which your wakeupphp file looks to, has a setting for
$parm_chan_ext = 0;
0 will use callerID info and 1 will use channel. I assume the module is ignoring this as it seems to be trying to wakeup call me on the channel and not the callerID. When I dial from this device to another extension internally, I see my CallerID as extension 200. So I know the device is presenting the correct CallerID from the fixed user 200.
Any ideas as to what could be causing this. I did find a work around as to enable device 1201 as a operator, thus when calling into the wakeup call I could specifiy manually the extesnion 200 that I want to ring for wakeups, but I would like to get it working automatically as also though you would like to be aware of this bug as it may help other things.
Let me know. And thanks again from some great software.
Trevor.

Trevor - I noticed this was your first post here in the forums. Welcome! Ward, Tom, and Joe have built a wonderful community for us to enjoy - and it works best when everyone feels free to chime in - so thanks for asking. And thanks for the kind words about the module. It was my first one!

The simple answer is - yes, you are correct. Currently, the module hard codes $parm_chan_ext = 0 which I agree is not making your like much easier.

I have not tested the module when $parm_chan_ext = 1. Its been a while since I looked at the code. What happens if you try setting $parm_chan_ext = 1?

-tshif

 

[Lost Trunk]

This is a great module but I think I just uncovered a serious flaw - it doesn't handle time changes! Set it for a 7:50 AM wake up call last night and was awakened bright and early this morning - at 6:50 AM standard time!

This, of course, means that one day each year it will wake people up an hour early, and most likely, one day a year it will wake people up one hour late - but only in places where Daylight Saving Time is observed.

By the way, I was still using version 1.2.2 (didn't know there had been a version bump) and have just upgraded to 1.2.3, but would that have addressed this issue?

 

[completetech]

This is a great module but I think I just uncovered a serious flaw - it doesn't handle time changes! Set it for a 7:50 AM wake up call last night and was awakened bright and early this morning - at 6:50 AM standard time!

This, of course, means that one day each year it will wake people up an hour early, and most likely, one day a year it will wake people up one hour late - but only in places where Daylight Saving Time is observed.

By the way, I was still using version 1.2.2 (didn't know there had been a version bump) and have just upgraded to 1.2.3, but would that have addressed this issue?

just a thought.. but it is most likely a system time issue. not the module.

 

[tshif]

just a thought.. but it is most likely a system time issue. not the module.

Actually - there quite a few messages in this very thread about this topic. Just a page or two backwards from here in fact. I just re read them. (LostTrunk, Did you? )

From the software's perspective, there is no time or date. It uses values for these provided by the underlying system. It doesnt do any time or date calculations beyond the 5,10, and 15 minutes snooze functions. It knows nothing whatsoever of daylight savings, time zones, or day of the week. In short - this is not a situation the module can address.

It seems the general concensus from others earlier in this thread is that each OS handles dates and times in its own way. As I recall you run Elastix, which im not very familiar with - but it may be that you answer lies in researching the underlying OS's way of dealing with daylight savings time.

 

[networks]

Trevor - I noticed this was your first post here in the forums. Welcome! Ward, Tom, and Joe have built a wonderful community for us to enjoy - and it works best when everyone feels free to chime in - so thanks for asking. And thanks for the kind words about the module. It was my first one!

The simple answer is - yes, you are correct. Currently, the module hard codes $parm_chan_ext = 0 which I agree is not making your like much easier.

I have not tested the module when $parm_chan_ext = 1. Its been a while since I looked at the code. What happens if you try setting $parm_chan_ext = 1?

-tshif

I have tryed it both ways, with $parm_chan_ext = 1 and $parm_chan_ext = 0 It does not seem to make a difference. It seems to ignore $parm_chan_ext = 0; 0 will use callerID
Thats the way is should be. But instead it only looks at the channel and takes that. Thus if I am using devices. When I call from Device 1201 on extension (CallerID 200) it tries to call me back at Device 1201 which cannot be communicated to so it fails.

 

[tshif]

I have tryed it both ways, with $parm_chan_ext = 1 and $parm_chan_ext = 0 It does not seem to make a difference. It seems to ignore $parm_chan_ext = 0; 0 will use callerID
Thats the way is should be. But instead it only looks at the channel and takes that. Thus if I am using devices. When I call from Device 1201 on extension (CallerID 200) it tries to call me back at Device 1201 which cannot be communicated to so it fails.

Ok - Ill add this information to the module home page. I will note that it does not work in device mode.

Thanks for the feedback.

 

[ou812]

I have tried to follow instruction to install module and it keep getting this error.

The following error(s) occurred processing the uploaded file:

File must be in tar+gzip (.tgz or .tar.gz) format
You should fix the problem or select another file and try again.

Any ideas?

I just tried the same module install on a new system and got the same error.
Did you find a fix for this.

Gary.

* Running Asterisk Version : Asterisk 1.4.21.2
* Asterisk Source Version : 1.4.21.2
* Zaptel Source Version : 1.4.12.1
* Libpri Source Version : 1.4.10
* Addons Source Version : 1.4.7

CentOS release 5.3 (Final) :32 Bit Kernel: 2.6.18-128.el5

 

[tshif]

Gary;

Make sure the file name is exactly hotelwakeup-1.2.3.tgz when you upload it to freepbx. Windows likes to rename it sometimes when you download it.

Its extreemly straightforward - I'm sure it doesnt feel that way right now, LOL, but truly it is.

Download the module from the dev site, make sure Windows doesn't mess with the name, and then upload it via the FreePBX module manager screen.

Let us know how you make out

 

[bpps]

Ok - Ill add this information to the module home page. I will note that it does not work in device mode.

Thanks for the feedback.

maybe add this to the beging of the dialplan
exten =>1,1,Macro(user-callerid) that should set the right callerid in device and user mode

 

[tshif]

maybe add this to the beging of the dialplan
exten =>1,1,Macro(user-callerid) that should set the right callerid in device and user mode

NICE - Do you have a version of this working with the mods you have suggested?

A ticket has been created to explore this. Can you post your solution?