Failover Problem

[Beth Verish]

Unity 4.0(5), callmanager integration, exchange off box. I screwed up, I set up integration on the secondary server BEFORE I ran failvoer wizard on the primary and secondary servers. The secondary server failover wizard failed. The secondary took control even though no failover occurred. When I ran fallback Unity failed. I deleted both itegrations, shut down the secondary server and added the primary integration. Unity worked fine. I then brought up the secondary server and successfully ran the failover wizard. A failover occurred unbeknownst to me and when a fallback occurred Unity failed. Right now I have the secondary server turned off. What can I do short of reloading the server(s)?

Thanks.

[Hin Lee]

>>I set up integration on the

>>secondary server BEFORE I ran failvoer

I think you are asking about the port configuration. When you built the secondary unity server, you would have used demo license but would have created x number of ports even though the demo allows for two ports. Setting up integration this way would not hurt your unity servers.

You didn't mention the version of callmanager but is it possible that you had configured Fwd Busy for Primary Unity ports to failover to secondary unity server?

see Cisco CallManager Port Configuration for Cisco Unity Failover (Cisco Unity Versions 4.0 and 3.1(2) and Later)

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_white_paper09186a0080114679.shtml