mscrm-addons.com - Blog

IMPORTANT INFORMATION

This blog is deprecated since July 2020.The articles below are no longer maintained and might contain outdated information. 
You can find the most acutal and relevenat information in our Knowledge Base at support.mscrm-addons.com

News.mscrm-addons.com Blog

rss

Hello and welcome to our blog! What can we do for you? Are you looking for further technical information or step-by-step instructions to our products? Or would you like to read the latest news on mscrm-addons? Please feel free to browse our blog for detailed information and to share our posts!


Calling out from a CRM Entity by pressing the [Call Number]-button triggers no reaction

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.


The Entity or PhoneCall activity does not open when a call is made

Before an entity or PhoneCall activity can be opened by an incoming/outgoing phone call, the phonenumber must be resolved.


What to do when the Lync / OCS wrapper does not support outgoing calls?

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.


How to open the fields.xml settings?

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


MSCRM Addons Installation for CRM 2011 Online

This blog is on how to install DocumentsCorePack (DCP) and TelephoneIntegration (TI) for CRM 2011 Online. When using CRM 2011 Online, it is important that the server part of the addon is installed somewhere on your network. It can be installed locally on a computer or anywhere else on one of the supported operating systems listed below. The following steps explain how to install the serverpart of DocumentsCorePack and TelephoneIntegration on your system. Please note, that both, client and server must be installed!


Repair WScript.Shell ActiveX

In some rare cases the WScript.Shell ActiveX component is not correctly registered. This causes, that the DocumentsCorePack Print in Word and TelephoneIntegration Call Number buttons are not working properly. To resolve the issue open a command prompt and enter regsvr32.exe wshom.ocx

That’s it! 


WindowsXP and WIF (WindowsIdentityFoundation)

!! 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. 


How to enable debugging for TelephoneIntegration

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Please note:
This article applies to TelephoneIntegration 
for MS CRM 2011, 2013 and 2015, as well as to CRM 2015/2016.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

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 & TrendMicro 2010 blockiert Popup-Fenster

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.