Callconnector functionality on Windows Terminal Server
It's been my experience that the CallConnector Client for Windows is not usable on a Windows 2003 Terminal Server. The software works but since the TAPI config is stored in one global place all users of the terimal server use the same phone/extension which is of course not a good thing.
Does anybody know how the CallConnector Server works? The sales literature doesn't mention TAPI. Is it possible that using the server version we can get Callconnector functionality for our terminal server users?
Re: Callconnector functionality on Windows Terminal Server
I've interfaced with development about this, and there are two things to be noted:
1) It's not officially supported
2) They are aware of it and there may be plans in the future to include support.
The best thing you can do is talk to whoever sold you this system and ask for a feature request. Enough customers asking and making a business case for it is the best option for getting it through to development.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...