I have a Unity 8 environment with Exchange 2003 and my company is going to be migrating to a new AD (2008) and Exchange 2010. We are looking to take this opportunity to move to Unity Connection as well.
In my lab, we have stood up a Unity Connection box in the new AD/Exchange environment while the Unity box still exists in the current AD/Exchange environment. We have been able to get cross server transfer working pretty reliably, but I have a question about the direct to voicemail feature we currently use.
We have the route pattern *xxxx set up to drive a voicemail profile for Unity that allows callers to use the direct to VM feature. Since we will be migrating users gradually over the course of weeks and possibly a couple months, this will create a problem for this feature that is commonly used. Once a user has been migrated to Connection, the direct to VM will not work anymore since the subscriber is no longer homed on Unity.
I understand that I can't have the same route pattern pointed to two different locations, but was wondering if either Unity or Connection would be able to leverage cross server transfer and handle this. I am looking for the ablility for a user to be able to use that pattern and have the Unity or Connection server be able to route directly to VM regardless of where the called party is homed.
I currently have a TAC case open and it hasn't produced any solutions yet, so I figured it was at least worth a shot to create a post for it. Has anyone come across this or a similar situation? Right now it just doesn't seem to work so any potential workaround would be worth a little investigating.
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...
[toc:faq]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 discusse...