Windows 8 has the WIF Framework built in, therefore our installers will fail for now trying to update the WIF on windows 8 clients.
This is a known issue with versions previous to 5.28.
Please upgrade to at least this version : http://22.214.171.124/ti2011/tic530.zip to fix the problem.
That’s it! We appreciate your feedback! Please share your thoughts by sending an email to firstname.lastname@example.org.
This article describes the two different ways how the TAPI Test Tool can be started.
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.
Please select the product and CRM version form the table below and follow the link to get redirected to a description of how to debug.
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.