I have a customer who'd like to implement a simple dn-based hunt group. They want to balance the calls between all three members so I'm looking for suggestions on what to do with the call if all three members are busy since TCD will route to VM if it happens to be the longest idle.
What happens if I check the "always route" box on the last user extension in the list? Will the call follow the cfb action if the line is busy or will the caller get reorder?
It's permissible to chain TCD hunt groups, so you can create an assembly like this:
Pilot Point 1 (First Available)
-> Pilot Point 2
Pilot Point 2 (Longest Idle)
-> Member 1
-> Member 2
-> Member 3
This should create the effect I think you're looking for, which is longest idle routing to all three members going to voicemail only if all three are busy. As an FYI, if you're planning an upgrade to CallManager 4.0 for this customer, it allows some other approaches with more flexibility.
Good suggestion. I played with this a little and notice that I get reorder unless I click "always forward" on the pilot point 2 entry in the first hunt group. Will calls still go to the second member of the first huntgroup (voicemail) if all members of huntgroup 2 are busy?
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.