Open Source Training Seminar FreePBX Paid Support

Ticket #2811 (closed Feature Requests: fixed)

Opened 4 months ago

Last modified 2 months ago

A more efficent way to manage Time Conditions

Reported by: bulgarion Assigned to:
Priority: trivial Milestone: 2.5
Component: Time Conditions Version: 2.5-branch
Keywords: Cc:
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: Asterisk 1.4.x Backend Engine Version:

Description

Hi everybody, I'm using FreePBX pretty much lately, and I found out that the Time Condition statements writing is quite a pain. One of my customer needed some complex timing sequence, I had to write down a flow-chart to ensure to not leave something off, and in the end it took me 20 statements, each one calling another, almost unreadable without its original schema. I know that the dialplan format is something like "if-then-else", but should be AMAZING if FreePBX could take input in an "easier" format and translate it in the simple 2-way logic.

Change History

05/02/08 18:59:38 changed by rogerluo

Agreed. The time-condition is not flexible. Suggest to have a fomat like:

Monday start till _, go to _, otherwise go to Tuesday start till _, go to , otherise go to _ Wednesday start till _, go to , otherise go to _ Thursday start till _, go to , otherise go to _ Friday start till _, go to , otherise go to _ Saturday start till _, go to , otherise go to _ Sunday start till _, go to , otherise go to _

07/12/08 22:28:31 changed by p_lindheimer

  • status changed from new to closed.
  • confirmation changed from Unreviewed to Confirmed.
  • resolution set to fixed.
  • version changed from 2.4-branch to 2.5-branch.
  • milestone changed from Cut Line to 2.5.

fixed timegroups added.

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads