These routes go to the same time check before heading to three different queues (if the time matches)
Queues:
1111
2222
3333
Question
This works fine, no problem. What I was hoping to do was as efficiently as possible, in the GUI, have a single call flow control to override the time check and force calls to queue no matter what. I have a call flow control: (*280 CHECKOVERRIDE)
if the value is night. I want to ignore the time check and go straight to queue. I think this could work in Dynamic Routes, but my question is how to make it as efficient as possible (fewest Dyn routes).
I can use: ${DB(DAYNIGHT/C5)}) to see the day/night value
I need to write something to the effect of:
If ${DB(DAYNIGHT/C5)}) = Day
RETURN 0
else RETURN ${CALLERID(dnid)6:4}
I could make an entry for each queue based on the returned result, 0 would go to the time condition like normal.
Question: How would I write that into a Dyn Route?
Thanks for any help or insights you can provide here.
Based on what you’ve told us so far, the desired functionality is built into Time Conditions and you have no need for a dynamic route. In your Time Conditions, see the tool tip for Call Flow Toggle Associate with. .
If I understand the ask, you want all calls from all DIDs to go to a single Call Flow Control. After the call flow control, you need to branch the call by DID to go to separate queues, so a single dynroute will do that if you use the Asterisk variable ${FROM_DID}.
@Stewart1 I never noticed this function, but it looks like it might work. I looked at the wiki but I am still lacking understanding.
I made:
Time Condition: test1 (*271)
Time Condition: test2 (*272)
Time Condition: test3 (*273)
When I dial the feature codes they toggles between temporally unmatched and no override
Is that because I am currently in the matched hours? If I tried this outside of the matched hours, would it move to temporally matched since the time conditions current state would be unmatched?
Questions:
How can I make it toggle between temporally matched and no override?
You will first be adding a Call Flow Control (default feature code starts with *280). Then, you would reference this single Control in each of your three Time Conditiions.
I am not understanding how to tie the single call flow control to the three time conditions, I am not seeing it in the GUI (FreePBX 16), but I could be completely missing it.
Possibly, it doesn’t display until you have created at least one Call Flow Control.
Or, maybe your system is older than when this was implemented.
Or, maybe it’s somehow broken.
Edit: Sorry, this post is all wrong; see @lgaetz next post.
Ditto, I’ve done a fair amount and read a lot, but I still have a lot to learn. I’ve been trying to stay out of custom destinations, because I miss things like this. Thanks @david55 & @lgaetz
This feature predates me and I can’t find any discussion around it. If I had to guess, it was probably added mid life cycle and there was some concern that it might break or affect exiting setups, so they chose to leave it disabled by default.