Ccm_callmanager Callmanager 3 Tsperror Error In
Contents |
My Cisco System Error Messages for Cisco Unified cisco tsp notifier initializing socket to listen on port failed Communications Manager 6.0(1) Error Message CCM_CALLMANAGER-CALLMANAGER-3-CallManagerFailure : Indicates some
Stationconnectionerror Reason Code=8
failure in the Cisco CallManager system. Additional Text [Optional][String] Host name of hosting node.[String]
Ciscotspnotifier Bind Socket Failed
IP address of hosting node.[String] Reason code.[Enum] ExplanationThis alarm indicates that some failure occurred in the Cisco CallManager system. Recommended ActionMonitor for other
System Error Messages For Cisco Unified Communications Manager 11
alarms and restart Cisco CallManager service, if necessary. Reason Code - Enum Definitions Enum Definitions - Reason Value Definition 1 Unknown 2 HeartBeatStopped 3 RouterThreadDied 4 TimerThreadDied 5 CriticalThreadDied 6 DeviceMgrInitFailed 7 DigitAnalysisInitFailed 8 CallControlInitFailed 9 LinkMgrInitFailed 10 DBMgrInitFailed 11 MsgTranslatorInitFailed 12 SuppServiceInitFailed Error Message CCM_CALLMANAGER-CALLMANAGER-6-SDLLinkISV : system error messages cucm 10 SDL link to remote application restored. Remote IP address of remote application[String] Unique Link ID.[String] Local node ID[UInt] Local Application ID.[Enum]RemoteNodeID[UInt] Remote application ID.[Enum] ExplanationThis alarm indicates that the local Cisco CallManager has gained communication with the remote Cisco CallManager. Note that the remote Cisco CallManager should also indicate SDLLinkISV with a different LinkID. Recommended ActionNo action is required. Reason Code - Enum Definitions Enum Definitions - LocalApplicationId Value Definition 100 CallManager 200 CTIManager Enum Definitions - RemoteApplicationId Value Definition 100 Call Manager 200 CTI Manager Error Message CCM_CALLMANAGER-CALLMANAGER-3-SDLLinkOOS : SDL link to remote application out of service. Remote IP address of remote application[String] Unique Link ID.[String] Local node ID[UInt] Local Application ID.[Enum]RemoteNodeID[UInt] Remote application ID.[Enum] ExplanationThis alarm indicates that the local Cisco CallManager has lost communication with the remote Cisco CallManager. This alarm usually indicates network errors or
My Cisco System Error Messages for Cisco Unified Communications Manager uc_callmanager 6 stationconnectionerror 7.1(2) Error Message CCM_CALLMANAGER-CALLMANAGER-3-CallManagerFailure : Indicates some failure in the endpointtransientconnection Cisco CallManager system. Additional Text [Optional][String] Host name of hosting node.[String] IP address of hosting rtmt node.[String] Reason code.[Enum] ExplanationThis alarm indicates that some failure occurred in the Cisco CallManager system. Recommended ActionMonitor for other alarms and restart Cisco CallManager http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/err_msgs/6_x/alarm601.html service, if necessary. Reason Code - Enum Definitions Enum Definitions - Reason Value Definition 1 Unknown 2 HeartBeatStopped 3 RouterThreadDied 4 TimerThreadDied 5 CriticalThreadDied 6 DeviceMgrInitFailed 7 DigitAnalysisInitFailed 8 CallControlInitFailed 9 LinkMgrInitFailed 10 DBMgrInitFailed 11 MsgTranslatorInitFailed 12 SuppServiceInitFailed Error Message CCM_CALLMANAGER-CALLMANAGER-6-SDLLinkISV : SDL link to remote application restored. Remote http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/err_msgs/7_x/ccmalarms712.html IP address of remote application[String] Unique Link ID.[String] Local node ID[UInt] Local Application ID.[Enum]RemoteNodeID[UInt] Remote application ID.[Enum] ExplanationThis alarm indicates that the local Cisco CallManager has gained communication with the remote Cisco CallManager. Note that the remote Cisco CallManager should also indicate SDLLinkISV with a different LinkID. Recommended ActionNo action is required. Reason Code - Enum Definitions Enum Definitions - LocalApplicationId Value Definition 100 CallManager 200 CTIManager Enum Definitions - RemoteApplicationId Value Definition 100 Call Manager 200 CTI Manager Error Message CCM_CALLMANAGER-CALLMANAGER-3-SDLLinkOOS : SDL link to remote application out of service. Remote IP address of remote application[String] Unique Link ID.[String] Local node ID[UInt] Local Application ID.[Enum]RemoteNodeID[UInt] Remote application ID.[Enum] ExplanationThis alarm indicates that the local Cisco CallManager has lost communication with the remote Cisco CallManager. This alarm usually indicates network errors or a nonrunning remote Cisco CallManager. Recommended ActionInvestigate why the remote Cisco CallManager is no
sorted by: [ https://puck.nether.net/pipermail/cisco-voip/2012-May/028296.html date ] [ thread ] [ subject https://puck.nether.net/pipermail/cisco-voip/2009-October/006656.html ] [ author ] So I'm deleting a few unused hunt pilots and I got TSP errors for the associated hunt lists. May 16 09 :45:20 iptccm104.cs.uoguelph.ca 23172: system error : ccm: 23034: May 16 13 :45:20.825 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-TspError: Error in TSP. Name of Device:082acb6d-eb6a-41c1-be74-4a6a6be5be8d App ID:Cisco CallManager Cluster ID:iptccm105-Cluster Node ID:iptccm104 Any idea why these would be happening? I can confirm they are unused system error messages because they are in a partition that is not in use by any search space. --- Lelio Fulgenzi, B.A. Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 (519) 824-4120 x56354 (519) 767-1060 FAX (ANNU) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Cooking with unix is easy. You just sed it and forget it. - LFJ (with apologies to Mr. Popeil) -------------- next part -------------- An HTML attachment was scrubbed... URL:
by: [ date ] [ thread ] [ subject ] [ author ] A device not being in the database is only one reason why it won't register. That TSP error is basically a transient device connection, so I'd recommend getting detailed CCM traces that cover one of the errors and see what is going on related to that device. -Ryan On Oct 29, 2009, at 1:22 PM, Ed Leatherman wrote: Ahh thanks for clearing that up. It's CCM 6.1.4, and they are SCCP setup with autoconfiguration. the tech set them in in CCM admin as gateway devices. I do see this in the database using the run sql cmd. shouldn't it just register then or did we miss something? On Thu, Oct 29, 2009 at 12:36 PM, Nick Matthews