incomplete export of call flow sequence

edit

tshark was very handy.

The flow windows have one big quality, and it is that it regroups similar packet (count them and give a duration), that take only one line and cleanup the view... I did not found a similar output with tshark, for a 19500 frame capture, "tshark-z flow,any,standard" keep the same output size, so does "tshark -z sip,stat" and "tshark -z expert,sip"

I end up using tshark to convert everything in json and then handle the data in powershell. (could be faster with one of the above switches and some cleanup using regex but I decide to take the long route and handle all the raw data) I had to check the code of the different dissectors in Wireshark github to match the different ID with what they meant, and it was a somewhat fun experiment.

"Save As..." with file type set to ASCII (*.txt) -> I do not know how I miss that, that works well :)