Cust has an IPCC 3.5(3) and one of the options on his script gives an
error message of technical difficulties intermittantly... At the same
time of the error, we get the following on the Subscriber (that the CTI
route-point this is pointing to):<br>
<br>
Error: kCtiProviderCloseHeartbeatTime
<div id="mb_0">out - CTI heartbeat timeout;<br>provider closing.<br> App ID: Cisco CTIManager<br> Cluster ID: StandAloneCluster<br> Node ID: <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://192.168.100.4/" target="_blank">
192.168.100.4</a><br> CTI Application ID: JTAPI[122]@SWS030<br> Process ID: 712<br> Process Name: CtiHandler<br>Explanation: CTI heartbeat timeout occurred. This causes CTIManager to<br>close the application connection.
<br>Recommended Action: CTI application will need to reconnect; contact TAC<br>if problem persists..<br>
<br>
<br>
The Subscriber is running 4.0(2a)sr2b<br>
<br>
The issue clears after a few minutes and normal function returns.<br>
<br>
I have the confirmed that the JTAPI subsystem is in-service, and I have enabled detailed CTI traces.<br>
<br>
Also, I have confirmed that the JTAPI versions are the same on the CCM and IPCC.<br>
<br>
<br>
Any ideas?<br>
<br>
<br>
<br>
Jonathan<br>
</div>