CTI 2011 TAPI wrapper needs a TAPI driver that is suitable to your Phone PBX server.
Each PBX phone-system vendor has its own TAPI driver.
Our TAPI wrapper has not an active role on the TAPI lines, it is just a passive listener to random TAPI driver events and eventually, it triggers them in case of outgoing calls, accepting the incoming offers.
If you outgoing calls are successful when made from CTI client, but not from the CRM entity, simply check the Internet Explorer Security Options. Please make sure that your CRM Server is included in the Trusted Sites Zone.
Before an entity or PhoneCall activity can be opened by an incoming/outgoing phone call, the phonenumber must be resolved.
The CTI supports only one call at the moment.
However, when transferring existing calls to a third party, it can happen that some sessions are not correctly closed. You can compare that with a broken Lync conversation.
!! Please note: This only applies to CTI Versions 5.30 and below !! !! Since Microsoft has changed the EULA of their WIF SDK we are now allowed to include all required files into our setups !!
All of our client products (Telephone Integration and DocumentsCorePack Client) need the WindowsIdentityFoundation Framework to be able to connect to CRM 2011.
Unfortunately the WIF Framework is not officially supported on WindowsXP by Microsoft, but there are 2 ways to make this work on a WindowsXP OS.
CTI does need the server component in a hosted environment as well, but you can launch the CTI Server setup from any Client, as long as you have a user with full access to CRM.
You need to select the hosted options on the Connection dialog.
Trendmicro Officescan (Version 10, Servicepack 1).
Lösung: Mit dem Trendmicro Performance tuning Tool (siehe Link) eine Ausnahme auf die CallInfoCRM4.exe erstellen.
Die Ausnahme wird, obwohl im TM Artikel nicht erwähnt, in die globale Konfiguration aufgenommen.