Skip to content

Commit

Permalink
Code cleanup for 0.1.0 release
Browse files Browse the repository at this point in the history
  • Loading branch information
Kaian committed Oct 21, 2014
1 parent 7dd22d8 commit e7eaf27
Show file tree
Hide file tree
Showing 29 changed files with 307 additions and 425 deletions.
14 changes: 14 additions & 0 deletions ChangeLog
Original file line number Diff line number Diff line change
@@ -1,3 +1,17 @@
2014-10-21 Ivan Alonso <kaian@irontec.com>

* sngrep 0.1.0 released

* Remove ngrep compatibility. Force libpcap during compilation
* Added TCP support
* Allow saving selected dialogs into pcap
* New UI design to maximize screen usage
* Added a serach box in Call List window
* Added Funtion Keys keybindings
* Added command line arguments
* Fixed some memory bugs


2013-04-22 Ivan Alonso <kaian@irontec.com>

* sngrep 0.0-alpha released.
Expand Down
78 changes: 0 additions & 78 deletions README

This file was deleted.

14 changes: 2 additions & 12 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,26 +38,16 @@ You can configure some options using a sngreprc file
<dl>
<dt>Why a new tool from network filtering?</dt>
<dd>Don't know. I didn't find any console tool that will display call flows.</dd>
<dt>Why dont you filter packages in online mode instead of using ngrep?</dt>
<dd>You can actually capture disabling ngrep using only pcap filters (see Installing options above)</dd>
<dt>Why only parsing SIP Messages?</dt>
<dd>Because it's useful for us</dd>
<dt>Extended Call flow window doesn't work</dt>
<dd>If you want to make relations between different dialogs (extended callflow)
a header must be present in of the dialogs referencing the other one.
This header can be X-CID or X-Call-ID and must contain the Call-ID of the
other related dialog.</dd>
<dt>I have found a bug, what should I do?</dt>
<dd>There are LOTS of bugs. The strange thing will be you haven't found one.
Just write an issue at github and I will try to fix it.</dd>
<dt>I think the idea is better than the tool.</dt>
<dd> I think that too. If you want to start a new tool with the same purpose
send me an email, I'll want to contribute.</dd>
</dl>

## License
sngrep - SIP callflow viewer using ngrep
Copyright (C) 2013 Irontec S.L.
sngrep - SIP Messages flow viewer
Copyright (C) 2013,2014 Irontec S.L.

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
Expand Down
23 changes: 8 additions & 15 deletions TODO
Original file line number Diff line number Diff line change
@@ -1,32 +1,25 @@
ToDo List
=========
This program is not even alpha stage, so there are TONS of improvements, which most
probably will not be done, or maybe yes, who knows.

=========
exec:
* Capture SIP messages using libpcap
In online mode, we're spawning a ngrep process that is responsible
to write the captured messages to stdout.
If we dont use correct ngrep filters (like udp or port 5060), most
probably sngrep will fail to parse.
We could remove this thread and capture the packages ourself.
capture:
* Add support for TLS (At least 1.0)

sip:
* Remove all ngrep rubbish
We still use ngrep header format. I like that for displaying
raw data but not for parsing data from capture packets
into sip_message structures.

* Change parsing functions for something more efficient (osip2?)
Parsing with sscanf is not the best way, but the simplest. If
we require to parse more headers in the future, it will start
to be worse and worse;
to be worse and worse

ui:
* Change panels initialization
Right now, all panels are initializated at the same, because
each panel can only be invoked once (it is not possible to have
two call details panel right now)

* Improve scrolling in all panels
Don't redraw panels if it's not required... just keep them.

* Show call duration and Finish status
It would be great to show this two columns on main screean.
First one can be calculated from the difference between first
Expand Down
Loading

0 comments on commit e7eaf27

Please sign in to comment.