Instead of opening contact/account/lead CRM records in InternetExplorer, the CRM records are opened in the USD client.
When you open a new PhoneCall activity (without the always store option), the TelephoneIntegration (TI) Client automatically fills the from and to field with the actual sender and the recipient. The functionality is provided with the TelephoneIntegrationServerCore2013.16 solution.
If it does not work, you must check the checkSender function.
Principal user (Id=56f329cd-2a1f-e511-8118-c4346bad624c, type=8) is missing prvReadptm_ticallinfodata privilege (Id=f83d0785-3924-421b-ad25-9ee898c13b7d)
This blog article explains what to do if the TIUpdateService is still processing data from previous configuration in TelephoneIntegration (TI) for Microsoft Dynamics CRM 2013.
This article outlines how to enable/disable the TelephoneIntegration PowerDialing functionality for TelephoneIntegration (TI) for Microsoft Dynamics CRM 2013.
This short blog article explains how to use the TelephoneIntegration (TI) Client for Microsoft Dynamics CRM with a default web browser instead of Internet Explorer (IE).
When calling over TAPI line, you sometimes need to predial a specific number to make an external call. In some cases, the TAPI driver is also passing this number to the TelephoneIntegration (TI) Client. If the TI Client Balloon then shows the PREDIAL NUMBER + REGULAR PHONE NUMBER instead of only the PHONE NUMBER.
When phone numbers are not being resolved correctly, the cause is sometimes an incomplete phone number index table (to be found in the MSCRM-ADDONS.com CTI CallInfos) in CRM.
It is recommended to rebuild this table from scratch. This includes removing all existing data in that table. To do so, we use the Telephone Integration update service. This article outlines how to do so.
This article describes the two different ways how the TAPI Test Tool can be started.