Open Source Training Seminar FreePBX Paid Support

Ticket #2719 (closed Bugs: worksforme)

Opened 6 months ago

Last modified 2 months ago

Timeconditions seems to be broken ?!

Reported by: oddjobz Assigned to:
Priority: blocker Milestone: 2.5
Component: Time Conditions Version: 2.4-branch
Keywords: Standard Ubuntu 7.10 base Cc:
Confirmation: Need Feedback SVN Revision (if applicable):
Backend Engine: Asterisk 1.4.x Backend Engine Version:

Description

Once I create a time condition (say "Daytime") and divert an incoming trunk to it, the incoming trunk signals busy and the asterisk log file says;

WARNING[27021] pbx.c: Channel 'SIP/100-00770120' sent into invalid extension '1' in context 'timeconditions', but no invalid handler

The raw config says; /etc/asterisk/extensions_additional.conf:exten => s,n,Goto(timeconditions,1,1)

It looks like the time conditions module just isn't doing what it's supposed to .. I have an earlier version of Freepbx / Timeconditions that works just fine with the same config.

(I've ripped down my my time conditions, added 1 condition called daytime with no spec and fallover to two known working destinations, then diverted all inbound calls to it, then tested with 7777)

Change History

05/31/08 12:32:56 changed by lazytt

  • status changed from new to closed.
  • resolution set to worksforme.

do you have a destination set in that time condition? I would recommend posting this question in the forums as that is usually a better place to receive community support.

05/31/08 15:14:36 changed by oddjobz

Interesting. I've been running live asterisk PABX's for around three years, much of that time using Freepbx in either it's current or previous guise.

do you have a destination set in that time condition?

Ok, that's just plain insulting. Do you think I sit here and log tickets for fun? Does anything I've said indicate I'm an idiot?

Did you read the bit that said;

I have an earlier version of Freepbx / Timeconditions that works just fine with the same config.

??

I would recommend posting this question in the forums as that is usually a better place to receive community support.

Right, so we wait three months and effectively say "it's not a problem, must be you...". Why do you even bother running a tracker?

I have the problem on two clean installs, it may be me - but if I got it twice and it's just me, there's a flaw somewhere given I've not had it on the previous 30 installs on previous versions.

05/31/08 15:37:06 changed by lazytt

oddjobz: I understand your frustrations! I also have tickets open here for quite a while and no one seems to be paying any attention (silent install - hello? Any mass produced system needs this!). However the dev's have their hands full as of late.
Being that I have plenty of systems working just fine with time conditions, I would like to suggest that there is a problem somewhere with your configuration. That does not mean that there is - and I presume you noticed the option to reopen this bug if you feel differently. If you post your log file of the call to the forum, Im sure someone will have a look. Then you can decide for sure that there really is a bug somewhere (and post a link to the forum topic to convince anyone with reservations such as mine). However the bug tracker is NOT the place for such a discussion, and being that I havn't seen this bug I decided to close the ticket.

06/01/08 03:20:32 changed by oddjobz

Ok,

Time conditions is a module, it's automatically installed - I have no chance to screw the config. Every thing else works fine .. I have two companies using these setups (without time conditions) live with no problems and 100% reliability.

There's nothing else that's "odd" in the log file bar the line posted.. What else would you suggest I post?

06/01/08 10:30:09 changed by pnlarsson

Could you post the timeconditions context from extensions_additional.conf? That would make it possible to see whats happened.

06/02/08 10:33:32 changed by p_lindheimer

  • status changed from closed to reopened.
  • confirmation changed from Unreviewed to Need Feedback.
  • resolution deleted.
  • milestone changed from Cut Line to 3.0.

oddjobz, I'll be glad to reopen the ticket until a few more details are hashed out. We get lots of tickets of many types, and some of them slip through the cracks. There are also a lot of people who help us manage the tickets and have the ability to close them. This may or may not have been closed in error but that is no big deal because it does not disapear. Also - please don't take any questions or responses that people make as attacks on you or your knowledge. People don't know who you are and often the questions may be completely appropriate to try and understand. The range of user experience we get is across the board - one never knows.

Now on to the issue, here is a question as I addressed something similar to this just a few weeks ago. Are you using database mode for authentication? And, does your user who created the timecondition have a Department Name assigned in the Administrators Module?

Please have a look at: #2820 and the related checkin: r5752 and let us know if that may be the issue, otherwise, as requested, more data is needed to dig in.

06/21/08 15:28:15 changed by p_lindheimer

  • status changed from reopened to closed.
  • resolution set to worksforme.

re-closing since no feedback.

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads