You use only one route point and have one menu like "press 1 for Billing, 2 for emergency..."
The you can try to "put" the can in the billing queue(with the Select Resource step). If its full(stays in the queued step) then you dequeue this call and "put" it in the overflow queue(with the select resource step).
An addition to the response would be to nest select resource steps thus creating simultaneous queuing on the backup groups. You gain little if you deque from the primary routed to CSQ, this is where you prefer the call to be answered. By nesting a second, third, select resource within the primary select resource step, you increase the possible agents available to handle the influx of calls rather than shifting calls (by dequing) to backup groups which have their own call volumes to handle.
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.