Hello Everyone,
We were able to upgrade from CUSP 8.5.5 to 8.5.9 with some hiccups.. Here's what worked for us. This is just to update everyone about the upgrade steps and the issues faced.
Note: This is based on personal experiences. So, this is not authenticated by Cisco. You can add or suggest any improvements to the procedure.
Step 1. Backup of configuration from CLI and GUI:
CLI:
A. Take basic backup from module after logging in to service module sm X/X. Log the output.
CUSP2#
CUSP2# show run
Generating configuration:
B. Take detailed backup of configuration from CUSP:
CUSP2# cusp
CUSP2(cusp)# show configuration active verbose
GUI:
Take the backup of full data and configuration from GUI to destination backup device as well.
Step 2. You might want to stop all the incoming traffic to the current CUSP to avoid the production impact.
Shut down the respective dial-peer on each gateway which point to this CUSP . If there are multiple CUSP servers, you can edit dial-peer priority to route all the traffic to the other CUSP.
Note: In our case, we had redundancy option available. So, we were able to complete the upgrade without impacting any calls going to Contact centre.
Step 3: On the CUSP which is under maintenance, Start a clean install of 8.5.9 by calling .pkg file available on FTP server. It may take 15-20 minutes to complete the installation. Once complete, it gives you an option to "restore saved configuration". It restores the basic configuration for example the hostname, users etc. So, you can select this option. Then create an admin account.
Step 4. Restore the detailed configuration(server groups, triggers etc):
Now we have the basic configuration and the CUSP has been upgraded to latest version. The next question is to restore the detailed configuration. Two methods available:
CLI >> Little complex and prone to mistakes when we copy paste detailed configuration.
GUI >> easy way but this method runs into a known defect where the indexing gets overwritten due to upgrade and the CUSP is not able to find a backup files on destination folder(at FTP).
Defect and the workaround is listed below: To make restore work, we need to do a workaround.
1. Do a backup of new install.
2. once the backup path is there, delete the newly backed up files.
3. Copy and paste the backup taken earlier. This should match the backup ids.
Once you are done through this, it's just a matter of seconds to fix the indexing and restore old configuration(8.5.5 in our case). So, GUI way still works.
Step 5. The restore process will ask for reload of CUSP module. Once its back, give it about 5 minutes and every thing should be back. Then do a commit and WR to make sure that you are saving the configuration.
Step 6. You can check the restore history and it should display "success" to your last restore.
Step7:. Then you can do basic and detailed config backup from CLI as done in step 1 and match it using any notepad compare software(a good one is "CompareIT". ).
Step 8: Don't forget to re-configure dial-peers to send the traffic to newly updated CUSP server. You can take some logs to make sure the traffic is routing correctly. Dashboard itself gives good indication of "calls routed" and "calls failed" etc.
Step 9. Repeat same steps for other CUSP server.
Note: The only drawback of CUSP upgrade is , that the upgrade command doesn't work and the quick fall-back option to old version(8.5.5) won't be available in case there is an issue.
Hope this helps,
Amarjeet
If you ordered a new module with Cisco Unified SIP Proxy Release 8.5 included, it is shipped with the Cisco Unified SIP Proxy image and the corresponding licenses preinstalled for the packages and features that you specified. You do not need to activate or register the software prior to use. The module stores the software license file on the flash memory. You do not need to do anything.