Select NAL unit of the H.264 layer, and then select Prepare a Filter >.Right-click Source port of the User Datagram protocol layer, and then select Prepare a Filter >.Right-click Source (IP address) of the Internet Protocol Layer, and then select Prepare a Filter > Selected from the menu.In this example, enter 96 in dynamic payload types for the H.264 protocol.Ĭreate the filter to search for I-frame as follows: To decode H.264 RTP packets as H.264, open Edit > Preference from the WireShark menu. NAL unit with "Sequence parameter set (7)" is the I-frame of H.264.Click "RTP (RTPType-96)" to transit to the corresponding packet.This is the duo video packets from MCU to the terminal. You can also see "RTP (RTPType-96)" is located under OLC and the corresponding OLC ACK at Step.4.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.The screen will transit to the corresponding packet on the WireShark packet list. 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 following signaling sequence appears. Select the stream you want to verify and click the Flow button.
From the menu, go to Telephony > VoIP Calls.Open the packet capture file with WireShark.I used Wireshark Version 1.8.2 for verification in this article. It includes the communication between VCS and MCU. The captured packet was acquired by the terminal used to watch the duo video. I am using the duo video (content channel, sharing materials) stream between MCU and EndPoint as an example here. I will show you how to find I-frame from the H.264 RTP packets using Wireshark here. We often perform a packet capture analysis for troubleshooting of H.323 video conferences.
0 kommentar(er)
