I currently have 5 Unity 4.0(4) servers, each in a different city, but all a part of the same dialing domain as well as AD domain. These are also integrated into Call Manager 4.1(2)sr1.
Currently, when a user travels to an office that does not home his/her Unity account, and they attempt to dial Unity from the phone in a remote office, the user gets a message that says "Unable to reach your unity home server". I also see an error in the application log of the remote office Unity server that says "Cross box handOff failed. Reason: Destination Rings but no Answer. Unable to handoff request to server"
My question is, how would I configure crossbox in a way that would allow the user to enter there own extension to reach voicemail? What is the best way to set this up?
This is not a sporadic problem, but is consistent. The problem is that Unity is receiving the dialed digits from the calling number and is trying to associate the extension to a mailbox.
I tested over the weekend, and when I turned on the crossbox communication, I would dial what would be the Unity home server, and Unity would successfully transfer the call back to the home server for the extension that I was calling from.
What I need to happen is that when Unity in any location is dialed from any extension system wide, it prompts for an extension or something to associate to the correct home Unity 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 ...