Problems With Unity Transfering Calls To Auto Attendant Console Pilot Point
We have Unity 4.0(4) and CCM 4.1(3). In our configuration (I didn't design it, I just have to support it) all of the calls that come into our main line get answered by Unity and the users get the whole calling menu. Option 3 of the menu sends the caller to a subsciber that is configured to just ring a "phone" and the Transfer Type is set to Supervise the Transfer. The phone is actually an Attendant Console Pilot Point. Every now and then people will have problems when selecting option 3. Today when someone would hit option 3, the phoen would ring twice and the call would just drop. I changed the Rings to Wait For to 20 and the phone would just ring and ring, but nobody could pick it up. I then changed the Transfer Type to Release to switch and everything worked perfect again. Every now and then it will quit working and I have to switch it back to Supervise. Anyone have ANY ideas of what might be going on? Thanks!
Re: Problems With Unity Transfering Calls To Auto Attendant Cons
Someone would need to look at diags to say exactly what's going on but speaking blindly... you should try running the latest TSP on Unity. Over the years the transfer logic has had a few tweaks to address some corner cases that were seen with the Att Console. If you're still having problems with the latest TSP then your best bet might be to open a TAC case and get someone digging into the diags.
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.