I’ve been wrestling with the Cisco Telephony Service Provider (TSP) today. We’re doing an install of ARC console, and having set everything else up, it wouldn’t start. I traced back and found that the issue lay in the TSP module itself. ARC tell you to try a utility called TAPI Soft Phone. Every time I ran it I got a vague error about not being able to connect.
I found the TSP was actually dropping logs into C:\Temp. I found these lines:
CiscoTSP001.tsp| CSelsiusTSPWaveList::GetAvailWave() *ERROR* No wave available|<LVL::Error><MASK::0001>
CiscoTSP001.tsp| CSelsiusTSPDevice::OpenDevice() [ARC-SrvQueue3] *ERROR* GetAvailWave() returned WAVELIST_NOT_ASSIGNED|<LVL::Error><MASK::0001>
I was aware there was a Wave driver in there, but it supposedly gets installed when the TSP installed.
Right?
Well, it would seem not. Whether it’s meant to or not, I don’t know. I could find plenty of reference to reinstalling it, but not a lot of mention of how to install it in the first place (or reinstall it for that matter). A bit more digging, and I found this Cisco document which tells you how to install.
It mentions Windows 2000, but it’s roughly the same for 2003, which I’m using. I selected Add New Device, Game and Audio controllers, and just pointed it at the driver.
One thing that struck me is that Windows claims the driver is unsigned. I’m wondering if the TSP installer is trying to shoe-horn the unsigned driver in, failing, and just silently giving up. Like I say, that’s assuming it actually does it in the first place.
Anyway it now works. A simple thing, but it took me a while to find the root cause and fix it.
[...] See the original post here: Cisco TSP – Wave goodbye [...]