I know we can setup active/active failover in Unity connection, but I am not sure about Unity. we need to setup active/active failover in Unity 7.0, to have double number of ports, for example 24 ports in primary and 24 ports in secondary.
The active-active clustering model is a feature that is unique to Unity Connection. At least, within the realm of Cisco messaging solutions. Unity supports an active-standby failover model and a cold standby model.
The maximum calls the system can accept is 24. Now, your implementation may limit this even further because, if you are following best practice, you have some ports dedicated for outcalling and MWI (which do not accept ingress calls). Whether you do this or not I am not sure. By default, this type of separation is not enforced.
With respect to failover behavior on the secondary Unity system when it happens to catch a call, I recommend reading through this document:
It explains the behavior when the secondary Unity server handles a call in good detail. The summary is that when the primary and secondary nodes are both on line, one of of two things could happen when the secondary Unity host receives a call:
1. A failover is initiatied and the primary Unity ports are shutdown while control of services are transferred to the secondary node. This is configurable and you can disable it.
2. If auto-failover when the secondary node receives a call is disabled, then the secondary will answer the call and transfer it to the next available port on the primary Unity system. If, the primary Unity system is 100% utilized (i.e. all ports configured to answer calls are actively handling calls) then the secondary system will NOT answer the call (i.e. fast busy).
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.