Heartbeat timeout issue in CISCO CTI logs
With the following configuration details:
- Pega 7.1.8.
- CPM - 7.1.3
- PegaCall - 220.127.116.115 - 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.
Message in logs - Device : XXXXXXX has exceeded heartbeat timeout.
Steps to Reproduce
- Log into application.
- Log into CTI.
- Make Agent available.
- Change status.
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: