Consider SIP callflow about termshark HOT 7 OPEN

hi @rafapcarvalho - I'll investigate!

from termshark.

sip calflow can be view with another already existing tool; sngrep

from termshark.

@rakotomandimby In this case, the proposal would be not to go to another tool. Something similar to what termshark gives us, since now I no longer need to download the file from a server to my personal machine to analyze a trace.

from termshark.

I really think we should leverage the use of existing. I work in the callcenter field and sngrerp does a really good job. May I suggest you try it, take a look at the codebase used to achieve that and you might conclude it is not worth it to start another work from scratch. I am not saying rewiting will result in same amount of code.

from termshark.

ok! thanks.

from termshark.

Hi @rakotomandimby and @rafapcarvalho - I didn't know about sngrep - I tried it out and it's very nice! I agree with your opinion that it would be better to use it directly. Maybe termshark could loosely integrate with it. Something like

• if sngrep is available (e.g. PATH), then present a termshark menu option to do SIP analysis, and make it clear it's using sngrep
• if invoked, pass the pcap to sngrep behind the scenes by launching it as a child process, and hand the terminal over to sngrep until the user terminates sngrep

Do you think that would provide extra value? I don't think it would be a lot of work on the termshark side of things.

(The termshark log viewer works similarly - it just launches a gowid terminal widget within termshark and opens the log file with the user's pager)

from termshark.

@gcla In my opinion, it provide extra value.

from termshark.