I need to merge phones that are running on an old 3.2(2c) cluster into a 4.1.2 cluster. 3.2 only supports BAT 4.3(4) which doesn't have an export function. I hate to manually enter all these phone devices. Does anyone know of a workaround?
If you have a running 4.1(2) Cluster, then I dont think there is a way around this limitation. If this would have been an upgrade from CM 3.2(2c) to CM 4.1(2), which is a multi-step upgrade, Data from CM 3.2 would have been migrated to CM 4.1(2).
These are both production clusters. We tried the upgrade path on the 3.2 cluster but it failed every time with DC directory errors. My first thought was to upgrade the old cluster to 4.1.2 and then export the phones out with BAT and import them to the other system. The failed upgrades killed that idea.
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...