New Feature or Addition to T.Conditions: HOLIDAYS MANAGEMENT

FreePBX Development
1

There is no simple way to handle holidays in the current version of freepbx, since there is no module for it, nor time conditions with a holidays table… (to divert calls, to give a closed message, to give a VM option…)

Looks like it’s a missing feature for a simple management like freepbx is…

The only way to do it is to annidate like 50 time conditions to make it wich would be a waste of time and space in the time condition modules with no reusable rules (think of easter wich is different every year, summer vacations… local holidays …)

The best would be to have a default table of common holidays (still activable-deactivable) plus a simple way to add more holidays, closeout days, summer vacations, without having to remember to put up a rule each time a holiday is coming like some ppl out here is doing.

What do you think?

Thanks!

2

yes thanks would be great

3

I have to slightly disagree. I would personally like a slighly more advanced system. Infact, here is the source for a reference of what I’d like to see implemented.

This has the advantage of never having to be updated once you setup the defaults. In the other example, you have to either add 10+ years for thanksgiving, or worry about missing some. This you would just set as “4th thursday of november” and it does the rest automagically. It also rather nicely handles the days after holidays, i.e. If a holida falls on a saturday, observe it on that friday, which most offices do.

http://www.unixreview.com/documents/s=1344/ur0309c/

4

Solves the problem as far as I see.

Just have a small sub-table that allows people to add rows to ad-nauseum
with date and time conditions, an active/deactive override, and maybe
even special contexts/messages so you can handle different announcements.

Solves pretty much well my only reason for NOT using timeconditions

zUlisse wrote:

[quote] There is no simple way to handle holidays in the current version of freepbx, since there is no module for it, nor time conditions with a holidays table… (to divert calls, to give a closed message, to give a VM option…)

Looks like it’s a missing feature for a simple management like freepbx is…

The only way to do it is to annidate like 50 time conditions to make it wich would be a waste of time and space in the time condition modules with no reusable rules (think of easter wich is different every year, summer vacations… local holidays …)

The best would be to have a default table of common holidays (still activable-deactivable) plus a simple way to add more holidays, closeout days, summer vacations, without having to remember to put up a rule each time a holiday is coming like some ppl out here is doing.

What do you think?

Thanks!

Amportal-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amportal-devel

[/quote]

Amportal-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amportal-devel

Post generated using Mail2Forum (http://www.mail2forum.com)

5

what do you mean?

6

Ok… Picture the current TimeConditions module.

Instead of just having ‘Added’ Time conditions, have 2 extra Tables
accessible via say a clickable link/button on the top right hand corner
(or there abouts… distinctly seperate from ‘custom’ TimeConditions).
These could be called “Standard Holidays” and say “Night Mode”.

Clicking either button causes a new ‘page’ to be displayed that contains
essentially a table that has at least the following columns: “Date” (Say
in DD/MM or MM/DD), Time Condition Starts, Time Condition Ends,
Destination Context/IVR/Extensions, Active (Which is a radio button for
Active/Deactive). This is a table that you can just keep adding rows to,
building up a database of “Common” holidays. This ends up producing
eventually some sort of output in the extensions_additional.conf that
looks something like (im ad-libbing here…)

[holiday-times]

include => ivr-3|||1|Jan
include => ivr-3|||2|Jan
include => ivr-3|||26|Jan
include => ivr-3|||20|Mar
include => ivr-3|||14|Apr
include => ivr-3|||17|Apr
include => ivr-3|||25|Apr
include => ivr-3|||12|Jun
include => ivr-3|20:00-07:59|mon-fri||
include => ivr-3|13:00-08:59|sat||
include => TimeConditions

This context would get called BEFORE the normal TimeConditions - allowing you to just ‘override’ on a date/time basis without defining heaps of TimeConditions.

NightMode is also important, and could be handled exactly the same, the only difference being, NightMode should probably be included After [Holiday-Times] but before [TimeConditions].

Nightmode would be a simplier table, listing Days of the week, “Day Times” (i.e, open hours), “Night Times” (i.e, closed) and an option to manually override the current setting. This is much similar to the old AMP style of handling it.

Doing things this way is ideal, because it lets people still maintain complicated options if you need those, but gives a very simple setup for “99%” of people, who just need to worry about “When are we open, when are we closed…”

Does that make more sense ???

zUlisse wrote:

[quote] what do you mean?

Amportal-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amportal-devel

[/quote]

Amportal-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amportal-devel

Post generated using Mail2Forum (http://www.mail2forum.com)

7

Solves the problem as far as I see.

Just have a small sub-table that allows people to add rows to ad-nauseum
with date and time conditions, an active/deactive override, and maybe
even special contexts/messages so you can handle different announcements.

Solves pretty much well my only reason for NOT using timeconditions

zUlisse wrote:

[quote] There is no simple way to handle holidays in the current version of freepbx, since there is no module for it, nor time conditions with a holidays table… (to divert calls, to give a closed message, to give a VM option…)

Looks like it’s a missing feature for a simple management like freepbx is…

The only way to do it is to annidate like 50 time conditions to make it wich would be a waste of time and space in the time condition modules with no reusable rules (think of easter wich is different every year, summer vacations… local holidays …)

The best would be to have a default table of common holidays (still activable-deactivable) plus a simple way to add more holidays, closeout days, summer vacations, without having to remember to put up a rule each time a holiday is coming like some ppl out here is doing.

What do you think?

Thanks!

Amportal-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amportal-devel

[/quote]

Amportal-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amportal-devel

Post generated using Mail2Forum (http://www.mail2forum.com)