[VoiceOps] Easy ways to measure PDD

[Calvin E.]

Since you can already parse the pcap, here's a napkin sketch assuming
something like php, bash, tcsh, etc. Were you looking for something more
specific?

Find all INVITEs, store (as in-memory temp data)  timestamps, Call-ID, and
CSeq
Find first matching non-100 response for each INVITE based on Call-ID and
Cseq (in case there are later reinvites)
Calculate difference in timestamp
...
Profit!

On Mon, Apr 20, 2015 at 11:35 AM, Peter Beckman <beckman at angryox.com> wrote:

> Thanks Matthew... but...
>
> "I don't want to manage yet another server or metrics repository in order
> to hold all of this call data..."
>
> This requires a whole pile of new software to be installed AND MySQL to be
> run somewhere. http://www.voipmonitor.org/doc/Architecture
>
> I have .pcap files from tcpdump with the call data. sngrep can parse it
> very fast and very well, but it is a curses-GUI and I need something I can
> automate.
>
> Dream workflow:
>
>     sipgrep --packet-type-start INVITE --report pdd --direction outbound \
>         --input-packet-capture sip07.pcap \
>         | shell-script-mangle \
>         | xargs -n1 push-metrics
>
> This way I can have a graph of PDD per termination partner (the
> shell-script-mangle would translate IP addresses into service provider
> tags/names) and push the metrics to my existing metrics system (statsd +
> graphite +
> grafana) and alert when things pass a threshold.
>
> Beckman
>
> On Mon, 20 Apr 2015, Matthew Crocker wrote:
>
>  www.voipmonitor.org
>>
>> PDD charts and so, so much more.
>>
>>  On Apr 20, 2015, at 5:11 PM, Peter Beckman <beckman at angryox.com> wrote:
>>>
>>> So after a recent discussion about how to quickly diagnose SIP calls from
>>> packets (tcpdump + sngrep for the win!), I'm now wondering if there is a
>>> tool I don't know about that would be able to parse the same .pcap file
>>> that contains all of my port 5060 traffic and output the PDD time for
>>> each
>>> call found within. Bonus points if I can specify a time/date range.
>>>
>>> I don't want to manage yet another server or metrics repository in order
>>> to
>>> hold all of this call data, so some of the larger (and pricier) tools
>>> mentioned before are out for me.
>>>
>>> I've contacted the author of sngrep and though the packet capture code is
>>> already there, he reasonably doesn't want to turn sngrep into sipawk or
>>> sipsed.
>>>
>>> Beckman
>>>
>>> ---------------------------------------------------------------------------
>>> Peter Beckman                                                  Internet
>>> Guy
>>> beckman at angryox.com
>>> http://www.angryox.com/
>>>
>>> ---------------------------------------------------------------------------
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org
>>>
>>> https://urldefense.proofpoint.com/v1/url?u=https://puck.nether.net/mailman/listinfo/voiceops&k=eghE%2F1871Dg5AgRfLcYONw%3D%3D%0A&r=6u4D%2FXrxCS2CFGDR%2F10ITB7whz3CLQp1FhOexohJiTo%3D%0A&m=f3JKNUc1MsE7jFK9faN7F%2Fy8KIJ4OtgCKrTclex%2BqhM%3D%0A&s=7df9cc8d4717ef69b1427ff171b83de29281fb43ab72ffc000daf9311a4c8f73
>>>
>>>
>>
>>
>>
> ---------------------------------------------------------------------------
> Peter Beckman                                                  Internet Guy
> beckman at angryox.com
> http://www.angryox.com/
> ---------------------------------------------------------------------------
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20150420/4a606b1a/attachment-0001.html>