We have a Enghouse QMS call recording server (Version: 7.4.2.20145 ) that uses the Cisco TSP for call control messaging. It quit working after windows updates were applied on 8/10/2020. I reached out to Enghouse support to investigate the issue and they indicated that they are not seeing any TAPI messaging from the Cisco TSP and that this issue is a Cisco problem and should be investigated with Cisco TAC (probably a software issue with the update). we can confirm that the TSP is showing the controlled phones but no status messages are being received. We have rebooted the recording server as well as reinstalled/reconfigured the TSP without success. I also restarted the CTI service on our 2 CUCM Servers with no change. CUCM version 11.5.1.14900-11. TSP version downloaded from CUCM, version11.5(2). Windows server is a currently patched Windows Server 2016.
We're seeing the following in the TSP logs
20:22:04.068 | CSelsiusTSPLink::getMessage() Link read time out. hSocket=3188
20:22:04.068 |<--CSelsiusTSPLink::getMessage()
20:22:04.068 |-->CSelsiusTSPLink::getMessage()
20:22:04.568 | CSelsiusTSPLink::getMessage() Link read time out. hSocket=3188
20:22:04.568 |<--CSelsiusTSPLink::getMessage()
20:22:04.568 |-->CSelsiusTSPLink::getMessage()
20:22:05.069 | CSelsiusTSPLink::getMessage() Link read time out. hSocket=3188
I reached out to Cisco TAC and they basically said pound sand we don't support TSP (even through its used in their own CUAC and CCE products). Apparently a community forum is how we have to try and get resolution for this... absolute joke.
Anyway - if anyone has a suggestion or advice, I'm all for it. I've attached the TSP log and the 2 windows updates that were installed. My next call is to our account manager.
