This is our old Q&A Site. Please post any new questions and answers at

I do Some trouble shooting for our customers,

And i trying wireshark 2.0.2 when i try the option VoIP call i see al the calls in the list Then i can select them but if i use the option decode (play) i get a empty screen with in the left "no audio" . Als in the Callflow graph option i see the 180, 200 etc but i dont see the RTP Packets ? When load the same tracé in wireshark 1.1x the i can use the VoIP call option And here the test call, the tracé is working fine.

Extra info Os: Windows 8.1 Wireshark 2.0.2 64bitt ( download the new version today from the site) Tracé is made in wireshark 2.0.2

asked 15 Mar '16, 11:40

the%20cube's gravatar image

the cube
accept rate: 0%

edited 15 Mar '16, 11:41

You cannot upload the trace here, it is necessary to publish it on cloudhark or any login-free file sharing service (google drive, MS one drive, ...) and edit the Question with a link to it.

(15 Mar '16, 11:45) sindy


It not posible to upload the tracé becourse of privacy of the calls of the company Its not the tracé that is the issue, i can decode it in the old version Wireshark that works fine. I think its a setting of option in the new version that is off ?, becourse i also dont see the RTP Packets in the graph flow in wireshark 2.0.2


(15 Mar '16, 12:25) the cube

It is clear that the trace is not the issue, but it is the only means to demonstrate/illustrate the issue. 2.0.2 can show and play RTP in a SIP call (I've just re-checked that), and does that much better than 2.0.0 and 2.0.1 did, so without the trace there is little chance to identify the issue.

If you choose a call for which the 2.0.2 doesn't show you the audio and look to the SDPs for connection addresses and ports, are the UDP packets running between these sockets shown as RTP or as UDP in the packet list? If as UDP, what happens if you use Decode as... to explain Wireshark that these are RTP, and then go to Telephony -> VoIP calls -> Flow Sequence and/or Play streams again? I.e., does the identification of RTP streams based on SDP contents fail, or does processing of RTP fail?

(15 Mar '16, 12:53) sindy

Another point:

  • right-click a SIP packet with SDP in the packet list and put the mouse cursor over the Protocol preferences line in the context menu (the third one from the bottom). A sub-menu will pop up, is there a checkmark next to Establish Media Conversation? If not, RTP packets are not identified as RTP and the flow graph doesn't show them.

  • right-click a SIP packet without SDP in the packet list and put the mouse cursor over the Protocol preferences. Is the checkmark missing next to Delay SDP changes for tracking media in the sub-menu? If not, you may get funny results too.

(15 Mar '16, 13:25) sindy
Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 15 Mar '16, 11:40

question was seen: 5,335 times

last updated: 15 Mar '16, 13:25

p​o​w​e​r​e​d by O​S​Q​A