Hello All,<br> I have a customer who is looking to split his voicemail port count over two Unity Servers.<br>He figures that:<br>1) The first server will handle the load of his Auto-Attendant functionality<br>2) The second server will handle the load of his VoiceMail functionality<br><br>He expects that he will use a 16-port system for AA, and a 8-port system for VM.<br><br>Is this a supportable configuration within a CallManager environment?<br><br>Are there any issues to be aware of?<br><br>TIA,<br> Pat<br><br><br>
No, this configuration is not supported. Unity is not cluster-capable at this point and thats really whats needed to make this fly. Unity 2.4.x simply does not have load balancing or proper hot-fail over capabilities at this point (the simple fail over is just that very crude).
The problem with handing auto attendant on one box and voice mail on another is that auto attendant functions require knowledge of users created on the voice mail box. For instance alpha directory functionality (one of the key things youll want to do for outside callers) requires we know the names/extensions/transfer strings of the subscribers on the voice mail box.
Further, if someone dials into the auto attendant box and wants to dial the extension number of a user (even if they dont go through the alpha directory) itll need to know the Ids of all the subscribers and call handlers on the other Unity server to do that right.
The short story is that this will be handled smoother in 3.0 with dialing domain support and the like.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...