Filter
Top Products
Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1)
© 2000 Cisco Systems, Inc. 56
• The second message indicates Cisco CallManager read the default database values,
which, for this case, would be the primary or publisher database.
• The third message indicates Cisco CallManager listened to the various messages on TCP
port 8002.
• The fourth message shows that, after listening to these messages, Cisco CallManager
added a second Cisco CallManager to its list: CCM2 (172.16.70.229).
• The fifth message indicates that Cisco CallManager has started and is running
Cisco CallManager version 3.0.20.
16:02:47.765 CCM|CMProcMon - CallManagerState Changed - Initialization Started.
16:02:47.796 CCM|NodeId: 0, EventId: 107 EventClass: 3 EventInfo: Cisco CM Database Defaults Read
16:02:49.937 CCM| SDL Info - NodeId: [1], Listen IP/Hostname: [172.16.70.228], Listen Port: [8002]
16:02:49.984 CCM|dBProcs - Adding SdlLink to NodeId: [2], IP/Hostname: [172.16.70.229]
16:02:51.031 CCM|NodeId: 1, EventId: 1 EventClass: 3 EventInfo: Cisco CallManager
Version=<3.0(0.20)> started
Self-Starting Processes
Once Cisco CallManager is up and running, it starts several other processes within itself. Some
of these processes are shown below, including MulticastPoint Manager, UnicastBridge Manager,
digit analysis, and route list. The messages described during these processes can be very useful
when troubleshooting a problem related to the features in Cisco CallManager.
For example, assume that the route lists are not functioning and are unusable. To troubleshoot
this problem, you would monitor these traces to determine whether the Cisco CallManager has
started RoutePlanManager and if it is trying to load the RouteLists. In the sample configuration
below, RouteListName=''ipwan'' and RouteGroupName=''ipwan'' are loading and starting.
16:02:51.031 CCM|MulicastPointManager - Started
16:02:51.031 CCM|UnicastBridgeManager - Started
16:02:51.031 CCM|MediaTerminationPointManager - Started
16:02:51.125 CCM|MediaCoordinator(1) - started
16:02:51.125 CCM|NodeId: 1, EventId: 1543 EventClass: 2 EventInfo: Database manager started
16:02:51.234 CCM|NodeId: 1, EventId: 1542 EventClass: 2 EventInfo: Link manager started
16:02:51.390 CCM|NodeId: 1, EventId: 1541 EventClass: 2 EventInfo: Digit analysis started
16:02:51.406 CCM|RoutePlanManager - Started, loading RouteLists
16:02:51.562 CCM|RoutePlanManager - finished loading RouteLists
16:02:51.671 CCM|RoutePlanManager - finished loading RouteGroups
16:02:51.671 CCM|RoutePlanManager - Displaying Resulting RoutePlan
16:02:51.671 CCM|RoutePlanServer - RouteList Info, by RouteList and RouteGroup Selection Order
16:02:51.671 CCM|RouteList - RouteListName=’’ipwan’’
16:02:51.671 CCM|RouteList - RouteGroupName=’’ipwan’’
16:02:51.671 CCM|RoutePlanServer - RouteGroup Info, by RouteGroup and Device Selection Order
16:02:51.671 CCM|RouteGroup - RouteGroupName=’’ipwan’’
The following trace shows the RouteGroup adding the device 172.16.70.245, which is CCM3
located in Cluster 1 and considered an H.323 device. In this case, the RouteGroup is created to
route calls to CCM3 in Cluster 1 with Cisco IOS Gatekeeper permission. If there is a problem