Cisco Systems 30 VIP manual Self-Starting Processes

Page 56

Cisco IP Telephony Troubleshooting Guide for Cisco CallManager Release 3.0(1)

∙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 CCMCMProcMon - CallManagerState Changed - Initialization Started.

16:02:47.796 CCMNodeId: 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 CCMdBProcs - Adding SdlLink to NodeId: [2], IP/Hostname: [172.16.70.229]

16:02:51.031 CCMNodeId: 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 CCMMulicastPointManager - Started

16:02:51.031 CCMUnicastBridgeManager - Started 16:02:51.031 CCMMediaTerminationPointManager - Started 16:02:51.125 CCMMediaCoordinator(1) - started

16:02:51.125 CCMNodeId: 1, EventId: 1543 EventClass: 2 EventInfo: Database manager started

16:02:51.234 CCMNodeId: 1, EventId: 1542 EventClass: 2 EventInfo: Link manager started

16:02:51.390 CCMNodeId: 1, EventId: 1541 EventClass: 2 EventInfo: Digit analysis started 16:02:51.406 CCMRoutePlanManager - Started, loading RouteLists

16:02:51.562 CCMRoutePlanManager - finished loading RouteLists 16:02:51.671 CCMRoutePlanManager - finished loading RouteGroups 16:02:51.671 CCMRoutePlanManager - Displaying Resulting RoutePlan

16:02:51.671 CCMRoutePlanServer - RouteList Info, by RouteList and RouteGroup Selection Order 16:02:51.671 CCMRouteList - RouteListName=’’ipwan’’

16:02:51.671 CCMRouteList - RouteGroupName=’’ipwan’’

16:02:51.671 CCMRoutePlanServer - RouteGroup Info, by RouteGroup and Device Selection Order 16:02:51.671 CCMRouteGroup - 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

© 2000 Cisco Systems, Inc.

56

Page 55 Page 57
Image 56
Page 55 Page 57
Contents SDI Trace Output Configuring Traces Reorder Tone Through Gateways Gateway Registration Problems Page Purpose Documentation Checklist Acronym/Term Cnf Law mu-law Channel Calling Search Space CCAPiCisco IOS Cluster Codec ChannelPartition Flow Full duplex 711 729 225 245 323 Half Duplex HookflashJitter Law mu-law Silence Suppression Voice Activation Detection 931Route Filter Route Group Route List Route Pattern Translation Pattern Voice Activation Detection Silence Suppression VoIPCisco CallManager Administration Details Microsoft Performance View ReportMicrosoft Event Viewer SDI Trace Configuring Traces SDL Trace Page SDLTraceTypeFlag Value Definition SDLTraceDataFlag ValueSniffer Trace Call Detail Records CDR and Call Management Records CMRSelect Service Service Parameters CDRs Problem Categories Voice QualityPage Packet Number Time absolute ms Time delta ms Button Help John Check Your Loads Phone Resets Dropped Calls Page Page Cisco CallManager Feature Issues Locations Conf Bridge Region1 Region2 MTP Resource Problems MTP Dial Plans Dialing DOES-NOT-EXIST Page Name DialPlanWizardG ClausePattern Partition Pattern Device Name Device Description UsageSlow Server Response Reorder Tone Through GatewaysGateway Registration Problems CFG Booting Dhcp for dynamic configuration Module.portTracyclose mod port tracystart mod port TaskID Cmd show dhcp Gmsg ***TFTP Error File Not Found Gatekeeper Problems Gmsg CCM#0 CPEvent = Loadid -- CPState = LoadResponseRegistration Rejects RRJ Sample Topology Cisco IP Phone Initialization ProcessPage Skinny Station Registration Process Station Reset Message Description Station Register Station IP Port AcknowledgePage Cisco CallManager Initialization Process Self-Starting Processes Cisco CallManager Registration Process Cisco CallManager KeepAlive Process Cisco CallManager Intra-Cluster Call Flow Traces Cisco Systems, Inc CCMStationD stationOutputStopTone tcpHandle=0x4fbbc30 Cisco Systems, Inc Call Flow Traces Page Cisco Systems, Inc Following debug messages show that the call is in progress Debug Messages and Show Commands on the Cisco IOS Gateway Gatekeeper Endpoint RegistrationCisco Systems, Inc Page Cisco IOS Gateway with T1/PRI Interface Cisco IOS Gateway with T1/CAS Interface Cisco Systems, Inc Inter-Cluster H.323 Communication Call Flow Traces Failed Call Flow Cisco Systems, Inc Writing Records Reading RecordsTable Schema Removing RecordsKnown Issues Fields in a Call Detail RecordDeciphering the Time Stamp Global Call Identifier Origination leg call identifierDate/time of call origination Originator’s node IDIsdn location value Calling party cause Of call terminationIP address for the originator’s media connection Port for the originator’s media connectionDestination span or port IP address to which the call was delivered unsigned integerIP port to which the call was delivered Called party’s partitionIP address for the destination outgoing media connection Codec type used by the destination on sending sideDate/time of connect Date/time of disconnect unsigned integerGlobal Call Identifier for this call Cisco CallManager node identifierCall Identifier Directory number used on this callLatency experienced during this connection Lost RTP packets during this connectionInterarrival jitter during this connection Normal Calls Cisco IP Phone-to-Cisco IP Phone Call Management Records Logged By Call Type Codec Types Compression / Payload types Codec Cause Codes DescriptionNumber changed Alarms Calling Cisco Technical Assistance Center TAC Index Debug messages and show commands Page Topology
Top Page Image Contents