Article applies to Avaya, CallMedia, EasyContactNow, Interactive Intelligence (ININ), IPFX, MiTAI, Teltronics and Tapi.
For a more comprehensive look at Logging in CallScripter, refer to the main
CallScripter Logging article.
When investigating issues in the agent desktop (CT Provider) integration, the first step is to obtain relevant CallScripter logs.
The steps for this are:
Configure the CT Provider's logging to capture all CT communication on the agent PC
- Ensure CallScripter is closed on the agent PC
- Open the CallScripter CT Provider folder: C:\Program Files (x86)\CallScripter\CallScripter CT Providers
- Make a backup copy of CallScripter.CTI.Management.dll.config
- Open the original of CallScripter.CTI.Management.dll.config
- Replace the section
<root>
<level value="ERROR"/>
<appender-ref ref="DefaultAppender"/>
</root>
with
<root>
<level value="ALL" />
<appender-ref ref="DefaultFile" />
</root>
<logger name="CallScripter.CTI.Management">
<level value="ERROR" />
<appender-ref ref="DefaultAppender" />
</logger>
- Save and close the file
- CallScripter CT Provider logging will now log all activity in full, minus the CallScripter Management elements, leaving only the CT provider elements
Reproduce the error/issue so that the log captures it
- The issue will need to be reproduced now that the appropriate logs are being captured
- After reproducing the issue send the logs to CallScripter Support found in: %localappdata%\CallScripter\CommunicationToolbar
Reset the logging level to default
- Ensure CallScripter is closed on the agent PC
- Open the CallScripter CT Provider folder: C:\Program Files (x86)\CallScripter\CallScripter CT Providers
- Delete the modified file CallScripter.CTI.Management.dll.config
- Rename the backup copy made previously of CallScripter.CTI.Management.dll.config to its original name (the file name you just deleted)
Article ID: 770, Created: April 12, 2016 at 11:09 AM, Modified: June 20, 2016 at 4:46 PM