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

Heartbeat timeout issue in CISCO CTI logs



With the following configuration details:
  • Pega 7.1.8.
  • CPM - 7.1.3
  • PegaCall - - running CTI Link engine (Windows Service) with Pega-CTI : 07.13

User is not able to change status, even login problem few times. The issue apart from the status not getting updated in front end, is that CTI gets crashed.
But this is resolved after restarting the CTI servers. The expected behavior is user should be logged in CTI, any change performed in CTI should get reflected.

Error Messages

Message in logs - Device : XXXXXXX has exceeded heartbeat timeout.

Steps to Reproduce

  1. Log into application.
  2. Log into CTI.
  3. Make Agent available.
  4. Change status.

Root Cause

A defect or configuration issue in the operating environment, it working as documented.


PegaCALL has preconfigured behaviours upon heartbeat timeout. The below has been documented:


Suggest Edit

Published July 2, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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