This document describes the specific commands required to collect the output from either CallManager servers or Cisco IOS® gateways and phones. Many documents are referenced in the collection of Pulse Code Modulation (PCM) and packet captures from different platforms.
Packet Capture on CallManager, Unity Connection, or CUPS
In order to run the packet capture, complete these steps:
- Secure Shell (SSH) to the CallManager, Unity Connection, or Cisco Unified Presence Server (CUPS) for which you would like to run the capture.
- Once you are logged in with the platform administrative rights, enter this command:
utils network capture size all count 1000000 file ciscotacpub
- After the packet capture is collected from the Servers Console/SSH Terminal, collect it with the Real-Time Monitoring Tool (RTMT). Log in to the RTMT and choose these options:
System > Tools > Trace > Trace & Log Central > Collect Files > Check the Packet Capture Logs check box
For further information about Unified CallManager packet captures, refer to Packet Capture on Unified Communications Manager Appliance Model.
Packet Capture on Phones
In order to enable the PC port on the phone at the phone's device level configuration in the Unified CallManager configuration interface, complete these steps:
- Log in to the CallManager Administration web interface with administrative rights and complete these tasks:
Choose the Device > Select the phone > PC Port * > Set to Enable > Save > Apply or Reset the phone
- Connect a work station to the PC port on the back of the phone and run Wireshark on the work station. Wireshark collects Skinny Client Control Protocol (SCCP) packets from the phone.
This command reference is used to enable a PC Port on a CallManager Express registered IP Phone.
Packet Capture on Cisco IOS Gateways
Packet Capture with IP Export
- This does not work well with the first generation Integrated Services Routers (ISRs) (2800 and 3800 Series routers). The first generation ISRs truncate large packets that cause the Real-Time Protocol (RTP) headers to loose details when troubleshooting Audio RTP related issues.
- Works very well in ISR G2 (2900 and 3900 Series routers).
- Optional - access list to filter out any un-wanted captures:
access-list 100 permit ip any any
access-list 100 permit udp any any
access-list 100 permit tcp any any
ip traffic-export profile TACCAPTURE mode capture
incoming access-list 100
outgoing access-list 100
ip traffic-export apply TACCAPTURE size 100000000
traffic-export interface <type-number> clear
traffic-export interface <type-number> start
traffic-export interface <type-number> stop
traffic-export interface <type-number> copy
- The traffic export is collected directly from the buffer into the flash/tftp/ftp. For example:
traffic-export interface <type-number> copy ftp://<ftp-ip address>/filename.pcap
traffic-export interface <type-number> copy flash://filename.pcap
- For further details on Cisco IOS packet captures, refer to Router IP Traffic Export Packet Capture Enhancements.
Embedded Packet Capture
PCM Capture on Cisco IOS Gateway
Earlier than Cisco IOS Release 15.2(2)T1
Cisco IOS Release 15.2(2)T1 and Later
SIP and H.323 Gateways
Triggered PCM Capture on Cisco IOS Gateway