You can certainly install an additional Unity server at Site B. You could either configure it for failover or let it handle the users at that site assuming the connection between your sites would meet latency guidelines. Assuming your message store is at Site A and the connection is down, the Unity server at Site B will hang on to messages locally until connectivity is restored.
Our Exchange Server is also stored in the same server as Unity (site A).
Is this a problem in case of failure of site A? Or is there some kind of backup server that we can also install?
I'm sorry for all this questions, but I have small info about Unity and this is for a Disaster Recovery Project.
We have this configuration.
CCM Publisher and TFTP
Unity (Voice Mail and Exchange)
The Backup server of site A is CCM Subscriber of Site B.
The Backup server of site B is CCM Subscriber of Site A.
All CCM users created are stored in the same server as Unity (where Exchange is installed).
Imagine that Site A becomes Unavailable. All communications in this site will be down.
Site B will make and receive calls, but not TFTP path will be reached, no AD will be reached, no Unity will be reached.
If we configure a Secondary Unity Server with failover in Site B, will he continue working normally? All Voice Mail will be received or only for site B? What can we do for users? Is there anyway of having everything replicated (Exchange and Unity) and make it as a secondary server?
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: firstname.lastname@example.org 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 ...