As part of the Cisco TSP initialization when the application issues lineInitializeEx, Cisco TSP queries the current TSP client version information that is available from the Cisco Unified CM server running CTIManager. Cisco TSP compares the installed Cisco TSP version with the client version available on the server. If a newer version is available and Auto-Upgrade is enabled, the Cisco TSP triggers the auto-update process. As part of Auto-Upgrade, Cisco TSP behaves in the following ways on different platforms.
After Cisco TSP detects that an upgradeable version is available, Cisco TSP reports 0 lines to the application and removes the Cisco TSP provider from the provider list. If a new TSP client version is detected during the reconnect time, the running applications receive LINE_REMOVE for all lines, which are already initialized and are in an OutOfService state. Cisco TSP silently upgrades to the new version that was downloaded from Cisco Unified CM and puts the Cisco TSP provider back on the provider list. All the running applications receive LINE_CREATE messages.
Windows XP supports multiple user logon sessions (as part of fast user switching), however, the system supports Auto Upgrade only for the first logged-on User. If multiple User sessions are active, Cisco TSP only supports the Auto Upgrade functionality for the first logged-on user.
If a User has multiple Cisco TSPs installed on the client machine, the system enables only the first Cisco TSP instance to set up the Auto Upgrade configuration. All Cisco TSP clients are upgraded to a common version upon version mismatch. From Control Panel, select Phone & Modem Options>Advanced>Cisco TSP001, the General window displays the options for Auto Upgrade.
The Cisco TSP client plug-in location can be changed to a different machine other than the Cisco Unified CM server (if desired). The default location is //<Cisco Unified CM Server IP address or hostname>//ccmpluginsserver.
If Silent upgrade fails on any listed platforms for any reason, the old Cisco TSP provider(s) do not get put back on the provider list to avoid any looping of the Auto Upgrade process. Ensure that the update options are cleared and the providers added to provider list manually. Update the Cisco TSP manually or fix the issue(s) encountered during Auto Upgrade and reinitialize the Cisco TSP client to re-trigger the Auto Upgrade process.
TSPAutoinstall.exe requires the Telephony Service LocalSystem logon option to Allow Service to interact with Desktop. If the logon option is not set as LocalSystem or logon option is LocalSystem but Allow Service to interact with Desktop is disabled (not selected), then Cisco TSP cannot launch the AutoInstall UI windows and will not succeed.
In the 8.5(1) release, the above services are not enabled as TSPAutoInstall.exe runs as an independent background process. Following the installation, upgrade, or reinstall of Cisco TSP, you must disable the User Account Control before the reboot.
Ensure that the following logon options are set for the telephony service.
Logon as: LocalSystem.
Enable the check box Allow Service to interact with Desktop.
These telephony service settings, when changed, require manual restart of the service to take effect. If the Microsoft Remote Connection Manager service is not disabled, reboot the PC for the changes to take effect.