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.

The fields.xml Settings are server-side CRM Settings.

Basically there are two ways to activate debugging:

Solution 1: Activating debugging via the TI-Setup

Solution 2: Activating debugging on your Client via the Registry

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. 

To downgrade the KDTele-tools in order to use the previous event-model, simply donwload the downgrade package from:

http://62.99.232.162/TI/downgrade.zip

and extract the package into a “downgrade” folder within the installation directory of the TelephonIntegration (TI) - Client component.