[cisco-voip] Unity Connection 7 Cluster MWI

[Pat Hayes]

How are you triggering this failover to test? I think I've seen
something similar in the lab if you hit the 'stop taking calls' button
for the primary while it is still in the primary role. MWI is only
dialed out from whatever server currently has the primary role, so if
you disable calls on that box, you'll break MWI. Try hitting the 'make
primary' button on your secondary server (or just shut it down) and
retest. This should activate the Notifier service on the secondary,
which handles MWI dialouts.

Also, you might want to give your config a once over, I believe you're
supposed to have all of the ports from both servers in the same port
group.

On Thu, Jul 16, 2009 at 10:19 AM, Michael Back<Michael.Back at nisd.net> wrote:
> I am in the process of adding HA servers to my Connection Clusters.
> When I force the primary to stop taking calls, the secondary works
> without a hitch, except that it will not send out MWI updates to the
> phone.  After adding the HA server I created a new port group for the HA
> ports.  That port group has MWI enabled.  MWI on and off extensions are
> the same on both port groups.  All the new ports are configured so that
> they can dial out MWI, and all the new ports are associated with the
> default phone system.  If I watch port status monitor on the primary, I
> can manually refresh MWI on a mail box using the primary admin page and
> see one of the ports dialing out to the phone.  If I switch port status
> monitor to look at the HA server, I manually refresh MWI for a mail box
> using the HA admin page, and nothing is sent out.  Am I missing some
> configuration on the HA server to get MWI to function properly?
>
> Thanks,
>
> MB
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>