Hi Driss,
As per documentation:
Version alignment
Release 9.0(1) provides a tighter integration between IM and Presence and Cisco Unified Communications Manager (Unified CM). From Release 9.0(1) onwards, IM and Presence and Unified CM software versions must match. For two software versions to match, they must have the same major and minor release number. Major and minor release numbers are defined as follows:
9.x.y
where 9 = major release number, x = minor release number and y = maintenance release number.
For example, IM and Presence Release 9.0.2.10000-1 is compatible with Unified CM Release 9.0.12.30000-3, but it is not compatible with Unified CM Release 9.1.1.10000-5. Similarly, Unified CM Release 8.6.2.10000-6 is not compatible with IM and Presence Release 9.0.1.10000-1.
For fresh installations, Unified CM 9.0(1) must be installed before IM and Presence 9.0(1) is installed. For upgrades, Unified CM must be upgraded to Release 9.0(1) before IM and Presence is upgraded. Upgrades must be performed within the same maintenance window.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/9_0_1/CUCM_BK_I87B437D_00_installing-cucm-90_chapter_010.html#CUCM_RF_V2A4278A_00
Can you provide the complete version of CUCM you have up and running?
Also, it appears that CUP isn't able to fetch the version from the CUCM:
ERROR: The CUCM Publisher must have 9.0 installed before upgrading CUCM IM and Presence to 9.0.1.10000-21|<:INFO>
12/14/2012 01:13:52 upgrade_manager.sh| CUCM Publisher currently has installed:|<:INFO>
12/14/2012 01:13:52 upgrade_manager.sh| Active Version: |<:INFO>
12/14/2012 01:13:52 upgrade_manager.sh| Inactive Version: |<:INFO>
Normally, you should see the active and inactive version on these log lines. The fact they are blank means that the icup.sh api was not able to fetch the version from the CUCM. The first thing I would check would be the connectivity with the CUCM publisher (admin gui, system->cucm publisher is an easy way). Also check cli network connectivity and/or /etc/host file. Quite often the issue is really a security password or configuration issue. (The same page can be used to reset/update the values of the hostname/ipaddress/security password).
If you are certain the security password is correct and the /etc/hosts has both the cup and cucm nodes, I would advise opening a TAC case so this can be investigated further via root access.
HTH.
Regards,
Harmit.
