Introduction
We often perform a packet capture analysis for troubleshooting of H.323 video conferences.
I will show you how to find I-frame from the H.264 RTP packets using Wireshark here.
----------------------------------------------------------------------------------------------------------------------
I am using the duo video (content channel, sharing materials) stream between MCU and EndPoint as an example here.
The captured packet was acquired by the terminal used to watch the duo video. It includes the communication between VCS and MCU.
I used Wireshark Version 1.8.2 for verification in this article.
![](/legacyfs/online/media/1_2.png)
- Open the packet capture file with WireShark.
- From the menu, go to Telephony > VoIP Calls. The following panel opens.
![Wireshark-TelePhony-VoIPCalls.PNG](/legacyfs/online/legacy/4/0/1/137104-Wireshark-TelePhony-VoIPCalls.PNG)
Select the stream you want to verify and click the Flow button. The following signaling sequence appears.
- Find extendedVideoCapability (for the duo video, shown in the red box of the figure) among the OLC (Open Logical Channel) transmitted towards the terminal, and then click on it. The screen will transit to the corresponding packet on the WireShark packet list.
![](/legacyfs/online/media/2_8.png)
- You can see that the extendedVideoCapability packet is trying to use H.264 at Channel Number 64 and that the MCU IP address: port (192.168.97.6:55269) specifies media control channel and dynamic payload type of 96.
![Wireshark-OLCextendedVideoCapabilityDetail.PNG](/legacyfs/online/legacy/4/2/1/137124-Wireshark-OLCextendedVideoCapabilityDetail.PNG)
- You can also see "RTP (RTPType-96)" is located under OLC and the corresponding OLC ACK at Step.4. This is the duo video packets from MCU to the terminal.
- Click "RTP (RTPType-96)" to transit to the corresponding packet.
![](/legacyfs/online/media/3_11.png)
- NAL unit with "Sequence parameter set (7)" is the I-frame of H.264.
![Wireshark-H.264RTP-IframeDetail.PNG](/legacyfs/online/legacy/6/2/1/137126-Wireshark-H.264RTP-IframeDetail.PNG)
To decode H.264 RTP packets as H.264, open Edit > Preference from the WireShark menu. In this example, enter 96 in dynamic payload types for the H.264 protocol.
![Wireshark-Edit-Preference-H.264.PNG](/legacyfs/online/legacy/2/3/1/137132-Wireshark-Edit-Preference-H.264.PNG)
Create the filter to search for I-frame as follows:
- Select the corresponding RTP packet.
- Right-click Source (IP address) of the Internet Protocol Layer, and then select Prepare a Filter > Selected from the menu.
- Right-click Source port of the User Datagram protocol layer, and then select Prepare a Filter > ... and Selected from the menu.
- Select NAL unit of the H.264 layer, and then select Prepare a Filter > ... and Selected from the menu.
![Wireshark-H.264RTP-IframeCreatingFilter.PNG](/legacyfs/online/legacy/9/2/1/137129-Wireshark-H.264RTP-IframeCreatingFilter.PNG)
- As a result, the filter ((ip.src== 192.168.97.6) && (udp.srcport == 55268)) && (h264.nal_unit_hdr == 7) will be created.
You can now narrow down the I-frame among the duo video H.264 packets from MCU to the terminal using this filter.
![Wireshark-H.264RTP-IframeFiltered.PNG](/legacyfs/online/legacy/1/3/1/137131-Wireshark-H.264RTP-IframeFiltered.PNG)
Related Information
Original Document: https://supportforums.cisco.com/ja/document/137666
Author: Junya Nishida
Posted on April 24, 2013