I have a 400 user customer that is currently Unified Messaging on Exchange 5.5. They want to be able to network between unity and Octel. They can't do this because of the AD and E2K limitation with the Unity Bridge. The customer needs to have networking available for transfers to users on the octel system.
I am wondering what my options are:
1. If I convert them to Unity VMO, I would need E2K and AD. Does Cisco support Unity VMO, the bridge, E2K, and AD all on the same server? Just need some clarification on that.
2.) If I approach this at a different angle and keep the customer on Unity 3.15 with Unified Messaging (Exchange 5.5). I could possibly network the Unity server and Octel server via AMIS. I have heard some bad things about the AMIS option (doesn't work very well).
3.) If the customer has multiple Octel voice mail servers and you want to utilize AMIS for networking, would you need to provide and AMIS connection to all the Octel servers, or just one (I believe just one is needed for the Unity Bridge)
also on #3, you need to set up communication between the Cisco Unity Bridge and all Octel servers, just as you have to set up AMIS communication with all Octel servers. Octel Analog Networking is a point to point protocol where each node must be configured to communicate with all other nodes.
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.