I’ve noticed that when a new timecondition gets created and then deleted, somehow the system keeps track of the ID and featurecode because when I create a new one again (considering no time conditions exist in the system) the new Time Condition gets created with a new feature code and ID instead of using the first one available (0 & *270).
This must be a bug because otherwise such behavior wouldn’t make sense to me. I’ve looked into the timeconditions SQL table and there are no existing time conditions when I create a new one, so this information must be stored somewhere else. Same goes with featurecode table. I’ve also looked up for any old config left under /etc/asterisk but there do not seem to be existing time conditions that could prevent freepbx from reutilizing the first available feature code.
It can be considered a cosmetic issue but I’m a bit picky about this - could a developer waste some time and look into this? I would troubleshoot the php code and see where it goes to check for pre-existing id’s & featurecodes when creating a new time condition but I have no dev skills unfortunately.
PS: I’ve tried to raise a bug in the tracker system but I’m unable to login, doh!