If Cisco Unity subscribers are homed on an Exchange server that is connected with the Cisco Unity server over a WAN, there must be no more than a 40 millisecond delay, regardless of the size of the pipe. This configuration is not a standard design, and is discouraged. In general, Cisco Unity should service local Exchange message stores and possibly one or two remote message stores. The Cisco Unity server, the Cisco Unity partner Exchange server, and other network resources that Cisco Unity requires must be in the same location. The minimum bandwidth between the Cisco Unity server and any Exchange server on which Cisco Unity subscribers are homed is about 24 Kbps per mailbox being serviced, including idle periods.
The bottom line here is that each of the links must be highly available, bandwidth must be reserved between Exchange and Unity using QoS and that latency must be extremely low. If any one of these factors changes at any time Unity will be dramatically impacted in a negative manner. For this reason I HIGHLY encourage that you place a Unity server at each site. Just me that this is not an area where you would want to push the design envelope to save a buck or two.
Ok, I see your point. But here is another question: Whether oOne Cisco CCM can support more than one unity server? If it can, how can CCM tell which Unity it should send the call to, for example, userA on Unity A, User B on Unity B, but there is only one CCM ?I heard CCM 3.2 support multiple pilots, does that solve my question?
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 ...