Upgrading the CallManager in a BOC DeploymentThe basics of upgrading CallManager with a BOC deployment are as follows.
Most likely, the Cisco TSP on the BOC server will not auto-upgrade correctly. It must match the CUCM version.
You will need to verify that it gets upgraded completely.
We recommend the TSP troubleshooting at the bottom of this email. But you may want to check the other parts as well.
Verify the following steps.
If your BOC TAPI2 service is current, it works fine with newer CallManagers.
Specific current version numbers can be found here.
BOC Client and Server versions
If you need to upgrade your BOC Tapi Connector 3.x Windows Service
Download x64
The latest clients can be downloaded from here.
BOC Client 3.x for Windows
Download x64
In the Windows Services tool
- Stop the BOCWatchdog service and set to disabled
- Stop the BOC Tapi Connector and set to disabled
- Stop any BOC options you may have, such as Exchange Connectors.
- Upgrade the Cisco TSP following the Cisco documentation for your new version of CallManager. This may be a simple upgrade if the versions are close. However, it may require and uninstallation and reinstall of the new version if they are too far apart.
- Reboot the BOC Server.
- Run Microsoft Dialer. (Start->Run->Dialer.exe)
- Verify you see Cisco devices in the "Connect Using" pull down
- Use Windows Event Viewer Application Log to identify any issues.
- Once Cisco devices are showing in Dialer, you can go back into Windows Services tool and re-enable the Bridge OC services. You can manually start each of them, or reboot a final time to start everything once again.
Very often with the upgrades the Cisco TSP does not upgrade or re-configure successfully. If you find this to be the case, you can use our TSP troubleshooting tips found here.
Repairing Cisco Tsp Installation