McDewey

issue reproduction. Reproduce the Issue and Take Notes In this scenario, you can place test calls to generate a failure. It helps the TAC Engineer to analyze the call if you provide information on the set of traces that have no information about the test calls. Also, you risk the collection of data for the wrong time frame and if that happens, you have to start over. For each test call, record this information: The phone number for the party that called. • The called party phone number. • The call start time. • The call end time. • Time and description for any issues you experienced during the call • As CUCM traces can be very lengthy, TAC needs those call details in order to find your test calls in the data. Gather the Requested Traces After the issue was reproduced, gather the traces requested by TAC immediately. If you do, the files are not overwritten before you can gather them. In this scenario, you need to collect CallManager traces, CTI Manager traces, and all Event Viewer logs. Unless TAC has given you other instructions, you need to collect those files from all servers for the complete time range that covers your test call or calls. This prevents the lost of traces from a server that you did not know was in the call flow. 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. Choose System > Tools > Trace & Log Central. 4.