I'm just curious what ways people have come up with to deal with huge traffic spikes. For example if your application runs at 70% capacity (I'm talking personnel capacity here) for the vast majority of the time but every once in a blue moon you get flooded with calls. Carrying staff to handle those peak loads all of the time is not an option. I considered a scaling solution that would behave differently based on how much traffic was incoming compared to how many agents were logged in. Potentially I could just generate a busy signal for people calling in past a certain load point. My thinking is I would rather have people get a busy signal (something everyone understands) then get stuck in some seemingly infinite queue with no hope of ever getting their call answered.
I am assuming that you are talking about IPCC. First, you do not want a busy signal to a customer. Will that be nice? You should have enough IVR ports to handle busy period calls. Queue them and after a certain limit, give an option of going to voicemail or send them to voicemail directly. This will depend on your business requirements.
The busy signal would be under "redline" conditions, let's say for sake of discussion 400% load. Anything less than that would be queued (with a very long expected wait time). What I would like to avoid is giving people false hope that their call is going to be answered under these conditions. The reality is, under that kind of load they are not going to get through unless they are prepared to wait a few hours.
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.