Inbound Route combines Schedule and Operator Managed Night Switch

if its a public holiday you knew it was coming months ahead of time, just make a schedule for those holidays.

Dear eeman,

Thank you for your prompt response.

But are there any ways to combine those two features though?

Thanks again.

Dan

only if you were to take one did with one format and loop it through the other did with the other style.

Dear eeman,

Thank you for your advice.

We have also raised another thread in regards to CID display setting.

Can you please be so kind to remind us what need to be done in order to display correct CID? We have set "External Caller ID Number" on every extension and "Caller ID" on trunk, but still appear as "unknown" each time calls out.

Thank you very much again for your assistance.

Dan

do your sip captures confirm 'unknown'? it could be a failure on your upstream provider

asterisk -rx "database show" | grep "callerid"
This will tell you the name and # that asterisk should be kicking out.

this idea can solve a requirment I have to provide?
a customer has two branches with two queues,
both has inbound routes to the queues.
both has auto timing for day/night.
but they need a feature code for one branch to be forwarded to the other (because they leave earlly or some one sick or whatever)
now we do it in the inbound routh everytime switching the queue.

any suggestions?

You could make QueueA's static members be dynamic members of QueueB and vice versa. Then clone the tl-queue-member-add-base script twice making one to 'login' all of QueueA's agents and the other to 'login' all QueueB's agents. Do the same for tl-queue-member-remove-base to remove members. Create feature codes to associate with these new scripts: *21 - Add All Agents to QueueA; *22 - Remove All Agents from QueueA; *23 - Add All Agents to QueueB; *24 - Remove All Agents from QueueB
Then whenever you want to 'forward' QueueA to QueueB you can do so through these feature codes. It requires some scripting on your part but it sounds kind of fun to do. Especially if you can figure out how to pull the list of agents assigned to the queue. As I was writing this out I was just picturing hard coding in each extensions into the script, which would be sloppy but it would get the job done. Anywho, just food for thought.

or even easier.. chance the queue options so that you cannot enter a queue if it has no members.. then stack both queues back-to-back in your huntlist, giving it a really long timeout of 30min or so.

huntlist-

step 1 QueueA, timeout 1800

step 2 QueueB, timeout 1800

then if everyone logs out of the queue, the first queue should be skipped all togeather. This wont work for static members though, only dynamic ones.

TX

The ideal solution for this case is to combine the two of your suggestions,
1. Create a feature code to login all and remove all
2. Huntlist as described.

since its my first time that I'm dealing with the dynamic agents, I don't know how to use it.

my question is:

how can I create the login all/remove all script? where in the script I choose the extensions?