SIP Early-Offer Problem - Trace File Name Syntax
Question
You are assisting a customer to troubleshoot a SIP early-offer problem with a SIP service provider.
You have enabled Cisco CallManager trace and set the debug trace level to Detailed for SIP Call Processing trace on their standalone Cisco Unified Communications Manager 9.1 system.
Using the RTMT tool, your customer has remote browsed to the Cisco UCM and asked you which trace file to download.
What is the trace file name syntax in which detailed SIP messages are logged?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D. E.A.
SDL files log SIP messages from CCM.
The correct trace file name syntax in which detailed SIP messages are logged is "SDI" (SIP Detailed Messages).
When troubleshooting a SIP early-offer problem with a SIP service provider, it is important to capture detailed SIP messages for analysis. To do this, you can enable Cisco CallManager trace and set the debug trace level to Detailed for SIP Call Processing trace on the standalone Cisco Unified Communications Manager 9.1 system.
Once this is done, you can use the Real-Time Monitoring Tool (RTMT) to remotely browse the Cisco UCM and download the trace file that contains the detailed SIP messages.
The trace file name syntax for detailed SIP messages is "SDI". This file contains detailed information about the SIP messages exchanged between the endpoints involved in the call.
To download the SDI trace file using RTMT, follow these steps:
- Launch RTMT and connect to the Cisco UCM.
- Navigate to the Trace and Log Central menu and select Collect Files.
- In the Collect Files window, select the appropriate Cisco UCM server from the drop-down menu.
- Select the SDI trace file from the list of available files.
- Choose the appropriate time range for the trace file and click Next.
- Select the destination folder on your local machine where you want to save the trace file.
- Click Finish to start the download.
Once the SDI trace file has been downloaded, it can be analyzed using a tool such as Wireshark to identify any issues with the SIP messages exchanged between the endpoints.
