I have two Unity 184.108.40.206.3.5 systems running in a single CallManager 3.12c Cluster. Each Unity server provides VM services to it's own unique group of users, no simple failover. The customer wants callers to be able to call any internal number, and when the VM system answers they want to be able to dial an extenstion and be transfered. This works in the current configuration as long as you choose a number in the same network as the Unity system that answered the call. If you choose a number that the second Unity system handles, you get fast busy. Is there a way to tie the two Unity systems together so calls can be transfered between the two?<br><br>Thanks!!!<br><br>Adam W. Moore<br>CCNP, CCDA, MCP
2.x doesn't have a slick mechanism to do this. The only way to do this would be to create internet subscribers or call handlers for each extension on Unity B you wanted folks to be able to dial when they called Unity A. The advantage of using internet subscribers (basically custom recipients that are voice mail enabled) is they can appear in the alpha directory for external callers to find by name as well as handle auto attendant dials directly as you want.
The way to do this properly is with dialing domains which are offered in 3.x. See the Networking Overview 2002 document for more on this... you can get the latest copy off the General Tools page on AnswerMonkey.net.
Simple fail over in 2.4.x is a little klunky and TAC doesn't support it any longer I don't believe. Basically you "fool" the backup server into thinking it's really installed into the same primary location as the first server. Essentially it's the same Unity server running on another box. If you can set this up, you could have set this configuration up on one box then. Assuming there was some reason you needed to do this acrosss two servers in the first place, that would mean a simple failover configuration wouldn't work here regardless.
You situation is tailor made for dialing domains... this is what they're for. I'd strongly consider getting yourself up to 3.1x if possible.
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...