We have an existing 3.1.5 Unity VM only setup with a pre 3.0 bridge. This bridge provides networking into an Octel VM network.
We are installing a remote site and would like this remote site to utilize that bridge. We have verbally confirmed from Cisco that we need to go to 4.0.3/Unity and 3.0/bridge on the existing setup and join it's AD...the new code allows multiple Unity Boxes to talk through a bridghead to a single Bridge, right?
We don't think we are going to be able to upgrade the existing Unity Server and Bridge before we deploy the location (we don't control the existing one).
My questions are:
1. Was our SE right about the multiple Unity to Bridge statement above?
2. Can we join our new 4.0.3 server into the existing 3.1.5/3.0 Unity/Bridge setup's AD. Then when we are ready to upgrade the old 3.1.5/3.0 to the latest code, will we be able to get this working...Are there implications here?
I believe you can join your 4.0(3) server into your existing AD structure and network with your 3.1(5) server (i.e. create a dialing domain and access your shared directory). However, the 4.0(3) server will not talk to the Unity bridge until the bridge has been upgraded to 3.0 and the Internet Voice Connector, which is probably running on your 3.1(5) server today in an Exchange onbox mode, has been upgraded to 11.0. Note that once you configure a 4.0(3) server to communicate with the bridge, all networked Unity servers must also be upgraded to 4.0(3). Here's another good doc - http://www.cisco.com/en/US/customer/products/sw/voicesw/ps2237/prod_pre_installation_guide09186a0080145e42.html#55642
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...