I want to do a migration of unity connection 1.1 to 7.0 on a different and new installed box.
There is a documentation available ("reconfiguration and upgrade guide for cisco unity connection 7.x") which describes the steps in detail.
Due to this documentation a migration is only possible using the "connection 1.x to 2.x migration export tool" rather than COBRAS (available for connection 1.2 at least...)
Anyway, the export and import to the 7.0 connection works fine. There is just one issue with my user passwords and PINs.
If I understand this reconfiguration guide correct, the PINs and passwords should remain, as long as the users set passwords in the connection 1.1. Only if a password field has left blank, the connection 7.0 sets a new one according to the template.
But my experience was, that even if I export all user data fields (which includes the hashes for PINs and passwords, the user isn't able to logon at the connection 7.0 system (after migrating them to 7.0)
Does someone has any idea why? Did I unsderstand the documentation wrong (and it isn't possible to keep the passwords), or did I make any mistake during migration?
And if it isn't possible to keep the passwords, is there possibly a way to change the passwords after migration at a per user basis? (E.g. via script or via access to the informix database)?
I have just performed a Connection 1.2 to Connection 7.0 migration using COBRAS and the passwords were migrated correctly. The users had no problems the next morning other then the prompt changing to tell them to enter their "pin" instead of "password" even though it was the same number.
I would recommend upgrading to UCON 1.2 first (minor upgrade) and then using COBRAS to upgrade to 7.0. I just did this last weekend successfully. Few things to keep in mind though is that COBRAS does not restore everything as documented in its help files. It does not restore directory handlers, routing rules, COS, templates, phone system integration. Really all it restores is subscriber data including PINs, messages, greetings, call handlers, interview handlers, and distribution lists, it is still more than the migration tool though.
There is really no software upgrade from UCON 1.2 to 7 as you need to rebuild the box since you are going from windows to appliance. There is a tool called COBRAS (look it up at ciscounitytools.com) that will let you do the migration, so here are my suggested steps:
1. Run COBRAS to export your data (review the help file to see what's not going to be migrated, i.e. COS/Routing Rules/Templates, etc)
2. Copy the export file to another box, you should probably install COBRAS on it as you will need to run it again for restore
3. Replace your drives, RAM, etc
4. install new UCON 7
5. Restore data using COBRAS
6. Manually build items that do not get migrated.
Make sure you have the licnese file ready before you perform the upgrade/migration by contacting firstname.lastname@example.org
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...