There are two types of failover available with Cisco Unity.
Both types require access to the same messaging systems and messaging infrastructure components.
There is local failover, in which both the primary and secondary failover servers are co-located in the same physical site as the messaging system they service.
There is also remote failover, where the primary and secondary failover servers are located in separate physical sites.
In a remote failover configuration, the network connectivity should be no less than 100 Mbps between the sites, and the messaging systems and messaging infrastructure components must be accessible by both Cisco Unity servers. (Note that messaging infrastructure components include domain controllers and/or directory servers, global catalog servers, and name resolution hosts.)
Regardless if your network connectivity bandwidth is at or greater than 100 Mbps, the response time between the Cisco Unity server and the Exchange servers it is connected to should be no more than a 40-millisecond round trip delay in order for Cisco Unity to service subscriber TUI requests normally.
So there should be no problem having Unity servers in different VLANs.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...