Comment # 12
on bug 11847
from Pavel Uhliar
While I was making the screenshots, I found the problem is in fact NOT related
to file size, it happens even in with that smaller (130MB file).
Disregard my first description of the problem, this one is more acurate.
I was trying to reproduce the problem, and with the SAME file, SAME procedure,
sometimes the RTP is displayed and sometimes it is NOT.
Steps to reproduce:
- I open capture file by double clicking it in Explorer
- I wait for the file to load
- I select menu Telephony -> VoIP Calls
- I wait until the parsing finishes
- I select the call I need
- I click button Flow Sequence
- sometimes the RTP is displayed (see screenshot-flow-RTP-displayed.PNG)
- sometimes the RTP is missing (see screenshot-flow-RTP-missing.PNG)
When RTP is missing (situation BROKEN), and I close the "Flow Sequence (Call
Flow)" window and "VoIP Calls window" to get back to main Wireshark window with
packet list without closing the file, and then do Telephony -> VoIP Calls and
rest of procedure once more, RTP is displayed correctly (situation REPAIRED).
Sometimes it takes even 3 repeats of the procedure for RTP to appear.
It seems once the situation REPAIRED occurs, it never reverts back to BROKEN
again.
Preference "delay SDP changes for tracking media" does not influence the
problem, it happens both with checked and unchecked.
It seems to be rare (I guess 1 run out of 5) for the RTP to be displayed when
displaying call flow for the first time after file is opened.
Next thing is odd, but it seems to be 100% replicable:
If I leave the file open in one WS window and open the same file in another
window, it displays RTP always the first time.
You are receiving this mail because:
- You are watching all bug changes.
