| 2022-09-26 13:34:30 +0000 | received badge | ● Famous Question (source) |
| 2021-09-24 03:40:34 +0000 | received badge | ● Notable Question (source) |
| 2021-09-24 03:40:34 +0000 | received badge | ● Popular Question (source) |
| 2018-03-06 07:12:52 +0000 | marked best answer | rtp.timestamp-offset field Hi, My purpose is finding a RTP problem because of wrong "RTP packet timing" (not frame time). Probematic device should sending all its RTP with correct RTP sequence number ,this part is correct. however packet timing should follow the same intervals such as increasing each RTP timing 160,320,480,640 etc based on codec and settings. Sending some RTPs with timing difference 160 and then sending rest of it 640 for same conversation violating RFCs and causing distortions. I want to find these kind of packeges quickly with a filter. The "info" section at wireshark is showing "MARK" I tried to filter based on "info" section without success. I want to learn usage of "rtp.timestamp-offset" filter option.I couldn't find any details information for rtp.timestamp-offset Your help will be appreciated. Regards, |
| 2018-03-06 07:12:52 +0000 | received badge | ● Scholar (source) |
| 2018-03-06 07:04:38 +0000 | commented answer | rtp.timestamp-offset field "rtp.timestamp-offset" is display filter command actually like ip.addr == 1.1.1.1 However I couldn't use it successfully |
| 2018-03-05 12:31:04 +0000 | asked a question | rtp.timestamp-offset field rtp.timestamp-offset field Hi, My purpose is finding a RTP problem because of wrong "RTP packet timing" (not frame tim |
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.