[cisco-voip] CMBE 6.1 - heartbeat timeout error

[Ryan Ratliff]

Some application of yours using the TSP (process id CiscoTSP001)  
failed to send heartbeats to CTI so CTI dropped the connection.    
Highly unlikely this is the cause of your quality problem, especially  
since internal only calls are affected.   That said if you are doing  
something crazy where all of your internal calls use a software MTP  
all bets are off.

-Ryan

On Sep 15, 2008, at 4:31 PM, Joe Cisco wrote:

Background: CMBE 6.1 - single server also running UConn. About every 3
or 4 days we get the following email from RTMT:

At <<WEEKDAY>> <<MONTH>>  <<DAY>> <<TIMESTAMP>> <<TIMEZONE>> <<YEAR>>
on node <<IP-OF-SERVER>>, the following SyslogSeverityMatchFound
events generated: SeverityMatch - Critical CTIManager: 1: <<MONTH>>
<<DAY>> <<TIMESTAMP>> UTC :
%CCM_CTI-CTI-2-kCtiProviderCloseHeartbeatTimeout: CTI heartbeat
timeout; provider closing. App ID:Cisco CTIManager Cluster
ID:StandAloneCluster Node ID:<<SERVERNAME>> Process
ID:CiscoTSP001-<<IP-OF-SERVER>>9 Process ID:11532 Process
Name:CtiHandler

After we receive this error users begin complaining about quality of
calls, both inside (cisco phone to cisco phone) as well as calls out
to the PSTN. They say the calls sound "garbled". Any ideas as to what
is causing this?

A simple reboot resolves the issue, but that's not practical.

Thanks,

-Joe C.
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080916/bf77e69f/attachment.html>