Try this, then:
Download/obtain the ciscotsp.exe installer from your CCM installation. Place it in a folder on a test machine - for this purpose let's say C:\cisco
Since this TSP software is distributed via PackageForTheWeb, you can create an answer file to help automate the install.
To do that, run this from a command prompt: C:\Cisco>ciscotsp.exe /a /r
This should record a setup.iss answer file and drop it in C:\Windows. Pull that answer file from there and place it in your C:\Cisco folder where your PFTW installer is located for the time being. Then, I suggest that you uninstall the TSP from your test machine. From here, re-run the ciscotsp.exe installer but don't step all the way through the install. Browse to your temporary folder (probably something like C:\Documents and Settings\user\Local Settings\Temp) and look for a folder by the name of pft###~tmp... copy that folder into your C:\Cisco folder and check to see if there is a setup.iss file in that folder. If there is, then compare that setup.iss with the one you created and copied from C:\Windows. They should be identical.
Once you have that 'temp' folder, you can simply rename it and then just call setup.exe /s from a login script. It should install the TSP silently in the background without problem.
Keep in mind that you will still have to have your users put the correct info in that TAPI object for your CallManager including their username/password, etc, but that's not too bad. ;-)
hope this helps.
Dennis
