Template for CallManager Traces from RTMT Contents

IntroductionPrerequisitesRequirementsComponents UsedCall FlowsCUCM and MGCP GatewayCUCM and H323 GatewayCUCM and SIP GatewayTrace SettingsGather Traces From RTMTVerify Trace File

Introduction

This document describes different logs required to be collected in case of an inbound/outboundcall failure across gateways.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

Cisco Unified Communications Manager (CUCM) version 10.5 and above●

Real-Time Monitoring Tool (RTMT)●

Components Used

This document is not restricted to specific software and hardware versions.

The information in this document was created from the devices in a specific lab environment. All ofthe devices used in this document started with a cleared (default) configuration. If your network islive, ensure that you understand the potential impact of any command.

Call Flows

CUCM and MGCP Gateway

Call manager detailed level traces●

Event viewer application logs and system logs ●

CUCM and H323 Gateway

Call manager detailed level traces●

Event viewer application logs and system logs ●

Debug from Gateway:

debug h225asn1 ●

debug h245asn1 ●

debug isdnq931 ●

debug voice ccapi inout ●

CUCM and SIP Gateway

Call manager detailed level traces ●

Event viewer application logs and system logs ●

Debug from Gateway:

debug ccsip messages ●

debug voice ccapi inout ●

Trace Settings

Please refer to this image for setting trace to the correct level.

Gather Traces From RTMT

After the issue was reproduced, gather the traces requested by TAC immediately. This preventsthe trace files from being overwritten before you can gather them.

Launch the RTMT.1.

Connect to the IP address of your CUCM Publisher.2.

Log on with the same credentials you use for the CUCM Administration web page.3.

Navigate to System > Tools > Trace & Log Central, as shown in the image.                                                                                                                                                                                                                               

                               

4.

Double-clickCollect Files. The Collect Files window opens to Select UCMServices/Applications.

5.

Under Select UCM Services/Applications, check the box in All Servers column for CiscoCallManager                                                                                                                                                                                                                                                                      

6.

ClickNext. The Collect Files window advances to the Collect File Options screen.7.

Configure your Collection Time: As you have timestamps for your test call(s), clickthe Absolute Rangeradio button.From theFrom Date/Timedrop-down list, choose the timefor one minute before your first test call.From the To Date/Timedrop-down list, choose thetime for one minute after your last test call.

8.

Configure your Download File Options. ClickBrowse in order to configure your DownloadFile Directory and specify a new directory for each trace file collection.

9.

Verify Trace File

Review the files that you have gathered in order to ensure they cover the problem time frame. Thesimplest way to do this is to review theTraceCollectionResult*.xml files.

When RTMT collects a set of files, it writes aTraceCollectionResult*.xml file to the download filedirectory for each server that it collects data from. You will see these files along with subdirectoriesfor each CUCM server. TheTraceCollectionResult*.xml files state which files were successfullydownloaded from each server. The subdirectories contain the actual trace and log files.