good chemistry is complicated, and a little bit messy -LW |
|
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Hi Jettero Many thanks for responding, the main reason for using tshark, I guess is a lazy one, I can apply simple thresholds to the various rTCP fields that I am interested in to cut down the amount of traffic reported (I am not interested in capturing all traffic due to the volume) - the source of the rTCP data should be sending out senders reports every 5 secs so perhaps this is not an issue. I'll definately take a look at your suggestion as I would certainly like to control this natively as you suggested rather than via pipe, I was just a bit worried about the load produced when having to filter through all traffic manually, do you see any problems with this? TSHARK has failed me a little as I wanted to capture ALL SDES Item 'text' fields but unfortunately it only seems to return the last 'text' field using the 'rtcp.sdes.text' filter so I am hoping your method would give me the ability to return them all, that would be a big plus also for me Thanks again! In reply to Re^2: tshark RTCP capture via PERL
by FirtyFree
|
|