[reSIProcate] Passive SIP Traffic Analyzer

[Scott Godin]

If you need transaction or dialog level data that is a good idea and might
work nicely.  :)

On Thu, Nov 21, 2019 at 5:53 AM Mihai Codrean <mihaicodrean at gmail.com>
wrote:

> So basically just the dissector is easily reusable, with no
> conversation/participants support, right?
> What if there would be an interface added to decouple the sockets API, so
> that the SIP replies could go through a dump stub?
>
> Thanks,
> -Mihai
>
> On 2019-11-19 17:24, Scott Godin wrote:
>
> Not really.  Homer support ( https://sipcapture.org/ )  was added, but
> that still doesn't allow you to listen passively to SIP traffic.  You could
> definitely build a passive listener outside of resiprocate, then just use
> the resip SIP message parsing routines to parse and analyze the SIP message
> contents.  This would be essentially by passing the resip transports,
> transaction state machine and DUM layers.
>
> Scott
>
> On Mon, Nov 18, 2019 at 10:11 AM Mihai Codrean <mihaicodrean at gmail.com>
> wrote:
>
>> Hi,
>>
>> Scott Godin wrote back in 2011:
>>
>> resip is great choice for a SIP message parser, however there will be a *reasonable
>> amount of work* required to separate things in order to try and reuse
>> the resip transaction, dialog and dum callback engine in a passive way (ie.
>> without generating any responses).
>>
>> Has this changed over the years, making such an endeavor easier?
>>
>> Thanks,
>> Mihai
>>
>> _______________________________________________
>> resiprocate-devel mailing list
>> resiprocate-devel at resiprocate.org
>> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20191128/0164f676/attachment.htm>