ISSUE:
I have the Cisco TSP running on a Windows Server 2003 machine. I have my TAPI application running on a Windows Server 2008 R2 machine that is pointing to the Windows 2003 machine as its remote TSP. My application can see the Cisco extensions and open them successfully, however I don't get any events for the extensions that I'm monitoring. If I run my application directly on the Windows 2003 machine, I can see all events for the extensions. I see this same behavior with the Microsoft TAPI browser as well as the Cisco sample application. Any ideas what might be going on here?
SOLUTION:
Sounds like the issue is with the configuration and setup of Remote TSP. You could set up Wireshark to capture packets on your 2003 server and see if the events are being sent to your 2008 server.
TSP OPERATION VERIFICATION:
To verify the TSP operation on the machine where the TSP is installed, use the Microsoft Windows Phone Dialer Application. Find this application in the C:\Program Files\Windows NT directory under the name dialer.exe. When the program is run, a dialog box displays that asks which line and address the user wants to use to connect. If there are no lines in the Line drop down list, then a problem may exist between the TSP and the Cisco Unified Communications Manager. If lines are available, choose one of the lines, keep the Address set to zero (0) and click OK. Enter a Number to dial, and a call should be placed to that number. If call is successful, you know that the TSP is operational on the machine where the TSP is installed. If problems are encountered with installation and setup of Remote TSP, this test represents a good way to verify whether the
TSP is operating properly and that the problem is with the configuration and setup of Remote TSP.
Comments
0 comments
Please sign in to leave a comment.