Kaian

Hi @michael2009 ! The problem with the attached pcap is that packets are encapsulated using [GRE](https://en.wikipedia.org/wiki/Generic_Routing_Encapsulation) which is not supported by sngrep.  As far as I know, stripping GRE...

Hi @alaertegv sngrep analyze all packets unless you use a BPF filter. Most probably the problem is not in the port but an unsupported protocol header. Could you provide a...

Hi @alaertegv Sngrep can assembly IP and TCP (UDP fragments are split at IP layer). TCP assembly is very basic and has some limitations (like packet received ordered and without...

Hi @michael2009 From the backtrace I see you are receiving a HEP packet while closing. Does this problem also reproduce when HEP listen mode is not enabled? Thanks for the...

I have updated the changes we did for #251 to wait for cancelled capture threads. If you can test if this fixes the problem, it would be great. Thanks @michael2009...

The problem was related with a big response-text in the messages. The above commit should avoid the crash. Thanks for the testing data! :+1:

Hi @alauppe There was an attempt to parse [extended RTCP reports](https://github.com/irontec/sngrep/blob/master/src/rtp.c#L296) that was being displayed when a RTP stream arrow was selected. I may eventually add this feature in a...

Hi!! If I understand this properly, the 200 OK to the UAC1 has 1.1.1.2 as SDP audio address, but the received RTP packets have Destination IP as 192.168.1.200? So, the...

I could give it a try, but I think it would be more a setting in sngreprc file (like the existing alias directive) that a command line option. `dmz 1.1.1.2...

Hi @juradoz This was introduced in https://github.com/irontec/sngrep/pull/154 some time ago. Maybe we should add an extra condition to only check the response code of initial transactions to mark the call...