Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Pega CTI logs created in two filesystem locations

SA-52508

Summary



Two different versions of CTI logs are created on the system. One log created in the Pega log file directory contains less information, while the other created in the server default location contains detailed CTI and debug information.

The version in the Pega directory is a result of the prlogging.xml configuration, while the other is based on the CTILINK engine configuration in the system.



Error Messages



Not Applicable


Steps to Reproduce

  1. Update the CTI log file location in the prlogging.xml configuration file.
  2. Restart the CTILink engine.


Root Cause

The logs configured by the CTILink Engine are not configured with complete details required and are configured in the incorrect location.


Resolution



Perform the following local-changes:

File Location:
  1. Open the CTILINK Engine rule form.
  2. Navigate to the Logging Tab.
  3. Modify the FileNamePattern value to represent the location where the log must be generated.
  4. Save the changes.

Logging Details:

  1. Navigate to Designer Studio > ChannelServices > PegaCall > Tools & Settings.
  2. Click Logging tab > Logging Settings. This is the generic PegaCTI log. 
  3. Modify the FileNamePattern value to represent the location where the log must be generated.
  4. Save the changes.

Published October 12, 2018 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us