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!


How to start the TAPI Test Tool

This article describes the two different ways how the TAPI Test Tool can be started. 


CTI does not resolve phone number

If the calling/called phone number is stored in Microsoft Dynamics CRM, then the number should be resolved to the corresponded CRM record. If the number does not resolve, make sure that the number is stored in the "MSCRM-ADDONS.com CTI CallInfos" entity. 


Gantt Printpreview for GroupCalendar

GroupCalendar version 4.84 offers a print preview of the Gantt View. This requires a small client side installation.


Execute Fetch from CRM 2011

Sometimes it can happen, that you want to execute a fetch simply to see if it works. And also see the results.

With the attached solution, you have the possibility to execute a fetch. Please note that this solution is not designed to generate fetches!


DocumentsCorePack Client save locations
There are three major save locations for files that are used by the DocumentsCorePack Client.


How to change the save location of the metadata.bin file

Per default, CRM metadata information for DocumenstCorePack is stored here:

%APPDATA%\DCP\metadata

The above location equals to C:\Users\[YourUsername]\AppData\Roaming\DCP\metadata.
If you want to change this location, you have to generate a new SettingsKey.

 


What to do if the TAPI wrapper is not working properly

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.


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.