<br><br>
<div class="gmail_quote">On Mon, May 10, 2010 at 1:09 PM, Martin Vít <span dir="ltr"><<a href="mailto:vit@lam.cz">vit@lam.cz</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div class="im">On 8.5.2010 00:40, Jeff Brower wrote:<br>> Martin-<br>><br>><br>>> checkout new open source <a href="http://voipmonitor.org/" target="_blank">voipmonitor.org</a> SIP packet sniffer. I've<br>
>> developed it for my telco company and I've decided to share it.<br>>> Testing and contributions are welcome!<br>>><br>>> VoIPmonitor is open source live network packet sniffer which analyze<br>
>> SIP and RTP protocol. It can run as daemon or analyzes already<br>>> captured pcap files. For each detected VoIP call voipmonitor<br>>> calculates statistics about loss, burstiness, latency and predicts MOS<br>
>> (Meaning Opinion Score) according to ITU-T G.107 E-model. These<br>>> statistics are saved to MySQL database and each call is saved as pcap<br>>> dump. Web PHP application (it is not part of open source sniffer)<br>
>> filters data from database and graphs latency and loss distribution.<br>>> Voipmonitor also detects improperly terminated calls when BYE or OK<br>>> was not seen. To accuratly transform latency to loss packets,<br>
>> voipmonitor simulates fixed and adaptive jitterbuffer.<br>>><br>> How many channels can it handle simultaneously?<br><br></div>I've not tested limits but capturing 15 voip calls takes 3-4% on Core2<br>
2.40GHz. Complexity in worst case is O(N^2) where N is number of calls.<br>Packets are matched as llinear list of IP and port. If this will be<br>limit, it could be rewriten to hash table O(N)<br>
<div class="im"><br>> How does it do MOS prediction if low bitrate codecs are being used<br>> (G729, AMR, etc)?<br>><br><br></div>It is calibrated only to G.711 with PLC for now but I'm planing adding<br>equations for G.729 and iLBC.<br>
</blockquote>
<div>when are you expecting to release</div>
<div> </div>
<div>Ram</div></div>