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):

Error: kCtiProviderCloseHeartbeatTime out - CTI heartbeat timeout;
provider closing.
App ID: cisco CTIManager
Cluster ID: StandAloneCluster
Node ID: 192.168.100.4
CTI Application ID: JTAPI[122]@SWS030
Process ID: 712
Process Name: CtiHandler
Explanation: CTI heartbeat timeout occurred. This causes CTIManager to
close the application connection.
Recommended Action: CTI application will need to reconnect; contact TAC
if problem persists..


The Subscriber is running 4.0(2a)sr2b

The issue clears after a few minutes and normal function returns.

I have the confirmed that the JTAPI subsystem is in-service, and I have
enabled detailed CTI traces.

Also, I have confirmed that the JTAPI versions are the same on the CCM and
IPCC.


Any ideas?



Jonathan

Attachment:
This has been downloaded 0 time(s).

[ Post a follow-up to this message ]

Heartbeat is exchanged between client and CTI Manager (TCP:2748) on
callmanager server.  How's the interim connectivity?  Is CTI
communication also prioritized in your QoS policy?  The CTI SDL
traces on the callmanager server (traces\sdl\cti\*) will show the
other side of the handshake.

/Wes
On Jan 27, 2006, at 3:31 PM, Jonathan Charles wrote:

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):

Error: kCtiProviderCloseHeartbeatTime
out - CTI heartbeat timeout;
provider closing.
App ID: cisco CTIManager
Cluster ID: StandAloneCluster
Node ID: 192.168.100.4
CTI Application ID: JTAPI[122]@SWS030
Process ID: 712
Process Name: CtiHandler
Explanation: CTI heartbeat timeout occurred. This causes CTIManager to
close the application connection.
Recommended Action: CTI application will need to reconnect; contact TAC
if problem persists..


The Subscriber is running 4.0(2a)sr2b

The issue clears after a few minutes and normal function returns.

I have the confirmed that the JTAPI subsystem is in-service, and I
have enabled detailed CTI traces.

Also, I have confirmed that the JTAPI versions are the same on the
CCM and IPCC.


Any ideas?



Jonathan
 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Attachment:
This has been downloaded 0 time(s).

[ Post a follow-up to this message ]