Starting with version 5.23 / TI and version 5.19 / DCP in combination with LicenseManager 5.2, the ribbon buttons will be disabled on perUser licensing, if the user is having the acccess flag for the product set to no.
Licensemanager 5.2 creates a new setting, IsPerUserLicense with value true|false when importing a licensekey.
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!
Sometimes, you may be asked to create a new settingskey for one of our products. This article outlines how to do so.
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.
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!
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