Ccm_callmanager Callmanager 3 Tsperror Error
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 failure
Stationconnectionerror Reason Code=8
in the Cisco CallManager system. Additional Text [Optional][String] Host name of hosting node.[String] IP ciscotspnotifier bind socket failed address of hosting node.[String] Reason code.[Enum] ExplanationThis alarm indicates that some failure occurred in the Cisco CallManager system. Recommended ActionMonitor for other alarms and
System Error Messages For Cisco Unified Communications Manager 11
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 : SDL link system error messages cucm 10 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 a nonrunning remote Cisc
Cisco Bug: CSCse47199 - CCM 5.0 Callmanager fails to initialize static devices after upgrade Last Modified Oct 01, 2011 Product Cisco Unified Communications Manager (CallManager) Known Affected Releases
Uc_callmanager 6 Stationconnectionerror
5.0(3.9911.52) Description (partial) Symptom: After a CCM 5.0 to 5.X upgrade Callmanager
Endpointtransientconnection
does not fully initialize Statically initialized devices such as trunks and H.323 gateways. Conditions: In the Callmanager Application logs large rtmt number of TspError alarms are seen as following. Jun 6 22:59:07 sfo-ord-sub-1 local7 3 : 0: Jun 07 22:59:07.582 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-TspError: Error in TSP. Port IsoEthPort:0 Port DSL:0 Name of Device:10.3.198.130 http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/err_msgs/6_x/alarm601.html App ID:Cisco CallManager Cluster ID:SFO-ORD Node ID:sfo-ord-sub-1 Jun 6 22:59:07 sfo-ord-sub-1 local7 3 : 1: Jun 07 05:59:07.600 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-TspError: Error in TSP. Port IsoEthPort:0 Port DSL:0 Name of Device:10.3.193.242 App ID:Cisco CallManager Cluster ID:SFO-ORD Node ID:sfo-ord-sub-1 At the time of the subscriber CCM initialization replication setup was not complete and due to unknown reasons DBL failed over to local database. View Bug Details https://quickview.cloudapps.cisco.com/quickview/bug/CSCse47199 in Bug Search Tool Why Is Login Required? Bug details contain sensitive information and therefore require a Cisco.com account to be viewed. Bug Details Include Full Description (including symptoms, conditions and workarounds) Status Severity Known Fixed Releases Related Community Discussions Number of Related Support Cases Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract. Learn More About Cisco Service Contracts Information For Small Business Midsize Business Service Provider Executives Industries Automotive Consumer Packaged Goods Education Energy Financial Services Government Healthcare Hospitality Life Sciences Manufacturing Materials and Mining Public Sector Retail Smart+Connected Communities Sports and Entertainment Transportation Workspace Transformation Marketplace Contacts Contact Cisco Meet our Partners Find a Reseller News & Alerts Newsroom Blogs Field Notices Security Advisories Technology Trends Cloud Internet of Things (IoT) Software Defined Networking (SDN) Support Downloads Documentation Communities DevNet Learning Network Support Community Video Portal Certifications Events Industries Inside Cisco Products Service Provider Services Technology Trends TechWiseTV About Cisco Investor Relations Corporate Social Responsibility Environmental Sustainability Trust and Transparency Center The Next Wave of The Internet Our People Careers Search
Us Newsletter Instagram YouTube Facebook Twitter Google + LinkedIn DirectoryNetwork InfrastructureWAN, Routing and Switching LAN, Switching and Routing Network Management Remote Access Optical Networking Getting Started with LANs https://supportforums.cisco.com/discussion/10793356/tsperror-every-20-minutes-empty-name-device-field IPv6 Integration and Transition EEM Scripting Other Subjects SecurityVPN Security Management Firewalling Intrusion Prevention Systems/IDS AAA, Identity and NAC Physical Security MARS Email Security Web Security Other http://puck.nether.net/pipermail/cisco-voip/2008-September/038502.html Subjects Service ProvidersMetro MPLS Voice Over IP XR OS and Platforms Video Other Subjects Collaboration, Voice and VideoIP Telephony Video Over IP Jabber Clients Unified Communications Applications system error TelePresence Digital Media System Contact Center Conferencing UC Migrations Other Subjects Wireless - MobilitySecurity and Network Management Wireless IP Voice and Video Getting Started with Wireless WLCCA Other Subjects ServicesCisco ServiceGrid Connected Analytics Smart Call Home Smart Net Total Care Operations Exchange Mobile ApplicationsCisco Proximity Cisco Technical Support Online Tools and ResourcesCisco Bug Discussions Technical system error messages Documentation Ideas Cisco CLI Analyzer Support Community Help Data CenterApplication Centric Infrastructure Application Networking Intelligent Automation Server Networking Storage Networking Unified Computing Wide Area Application Services (WAAS) Other Subjects Small BusinessNetwork Storage Routers Security Surveillance Switches Voice and Conferencing Wireless Solutions and ArchitecturesBorderless Networks Collaboration Cisco User GroupsSeattle Cisco User Group (SEACUG) Silicon Valley Cisco User Group (SVCUG) Southern California Cisco User Group (SCCUG) Cisco Certifications Cisco.com Idea Center Cisco Cafe Expert CornerTop Contributors Leaderboards Cisco Live! Events Events Community CornerAwards & Recognition Behind the Scenes Feedback Forum Cisco Certifications Cisco Press Café Cisco On Demand Support & Downloads Community Resources Security Alerts Security Alerts News News Video Cisco Support YouTube Cisco YouTube Blogs Technical Documentation Cisco Products Products Services Services Solutions Solutions Global Support Numbers Cisco Support Community Directory Network Infrastructure WAN, Routing and Switching LAN, Switching and Routing Network Management Remote Access Optical Networking Getting Started with LANs IPv6 Integration and Transition EEM Scripting Other Subjects Security VPN
CUCM 6.1 TSP: Port IsoEthPort [UInt], Port DSL [UInt] Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Hello more experienced engineers, I have CUCM running 6.1, 2 MGCP VG, 1 H323 VG. Receiving this error: Error: %CCM_CALLMANAGER-CALLMANAGER-3-TspError: Error in TSP. Port IsoEthPort [UInt], Port DSL [UInt] I have seen that there have been posts in the past about this error and unconfigured FXS/FXO ports. The error is being generated by 11 devices all named SEP+MAC Address, e.g. SEP000123456789. I haven't been able to locate these devices on the network, checked switches and CUCM. I know this is not a service impacting issue, but its recurring and needs to stop, does anyone have experience with this issue? Thanks in advance!! Thanks, Robert Knapp -----Original Message----- From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of cisco-voip-request at puck.nether.net Sent: Thursday, September 25, 2008 8:11 PM To: cisco-voip at puck.nether.net Subject: cisco-voip Digest, Vol 59, Issue 212 Send cisco-voip mailing list submissions to cisco-voip at puck.nether.net To subscribe or unsubscribe via the World Wide Web, visit https://puck.nether.net/mailman/listinfo/cisco-voip or, via email, send a message with subject or body 'help' to cisco-voip-request at puck.nether.net You can reach the person managing the list at cisco-voip-owner at puck.nether.net When replying, please edit your Subject line so it is more specific than "Re: Contents of cisco-voip digest..." Today's Topics: 1. After Hours Calls (Tammie Robertson) 2. max number of num-exp (Chuck) 3. Re: After Hours Calls (Jason Aarons (US)) 4. UCCX call hold problem (Malcolm Caldwell) 5. Re: After Hours Calls (Truelove_John) ---------------------------------------------------------------------- Message: 1 Date: Thu, 25 Sep 2008 16:25:03 -0400 From: "Tammie Robertson"