Kaian

Hi @yezongming I have been debugging the attached captured. Thanks for the testing data. It seems your SIP messages are a bit strange, not sure what tool you've been used...

Umm, sorry for the lack of feedback on this one. I could change the regexp to be less strict yes, but I think I will leave that for a future...

While this could be handy for some scenarios, I don't like the idea of filtering to much at capture level. I prefer all capturing tools using libpcap produce the same...

Hi @dovi5988 For 1.4.0, I think the RTP streams are expecting the IP and port described on SDP content or the source IP of the SIP message and the port...

Hi @michael2009 Can you provide a pcap file captured with other raw tool with two full connections that doest display properly in sngrep? Thanks!

So, If I understand correctly the problem occurs when multiple TLS connections are captured? The first one is displayed but not the rest? Thanks!

Hi @michael2009 Check #220 for how to configure new setting `capture.tlsserver`. I highly doubt this will fix this problem, but just for your information. Regards

Hi @ishmaelen This may be interesting, but maybe something enabled by a keybinding. Right now we display the request method or response text extracted directly from the message. In order...

Hi @brettnem This sounds like a nice feature for the future releases. Right now we only implement standard headers that are part of a RFC, but it would be nice...

Hi @brettnem Currently 1.x version of sngrep is just receiving bug fixes, so no enhancement or new feature is planned. In the other hand, I'm working in me free time...