I have be requested to set up the following:- If all Agents are logged out of the attendant Console, the Call routes to a hunt Group, (to achieve this I had to create a CTI Route point that forwards to the Hunt List) which is selected to an always route member. This hunt list contains the option to Log in/out. If all members are busy or logged out the call queues on the Attendant console pilot point and caller hears music on hold.
This issue I have is as follows when all agents are logged out of the attendant console :- All works well until a user has been in the queue for more than around 50 to 60 seconds; the system just keeps the caller on hold indefinitely regardless if the call can be routed or not. When a second call comes in it routes fine (until the 50/60 second hold time is reached.)
Has anyone experienced this as well or is there an enterprise parameter that needs to be adjusted.
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.