Peter Lemenkov
Peter Lemenkov
@MikaelX could be a zero-length file.
Thanks for reviving it!
This isn't a "bug" report - rather a tracking ticket. cc @sobomax @jevonearth
Initial preparations: - Updated list of version strings (wireshark/wireshark@edce10bf734a5c04747671f69c113ccbeae95164) - Updated list of error codes (wireshark/wireshark@9c64fdb7e7ad1c9198917aebc3df41fe6f33b2ad)
- Parse 'n' command parameter properly ( wireshark/wireshark@ca921fd961164f3f91fa958706507bb0d6fac2f1 ) - Clarify 's' command parameter meaning ( wireshark/wireshark@6d17456208af52b7ec98b82962193263fc020100 ) - Decode Il command properly ( wireshark/wireshark@12ec6c4482950dafab1701e709a0a0fee37e399c )
@sobomax @sandrogauci the problem that a client's port (and IP address) will likely change during session at least in some 4G networks. So it's a legitimate behaviour, and if rtpproxy...
Any progress here? @ricmoo could you please tag the latest 1.6.1?
> Ah yes. I should be able to get to this today and will try to tag the older releases too. I have a script somewhere I used for backfilling...
@ricmoo this ticket can be closed now I believe :)
Hello! Any news here?