< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate] Passive SIP Traffic Analyzer

I have actually started on a different path:
For my purposes, I don't really need a TU, but just a way to get notified when sessions are detected (e.g. TransactionState::mState == Completed) and teared down. The state itself is private, so any ideas how to go about this?


On 2019-11-28 23:55, Scott Godin wrote:
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@xxxxxxxxx> 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?


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.


On Mon, Nov 18, 2019 at 10:11 AM Mihai Codrean <mihaicodrean@xxxxxxxxx> wrote:

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?


resiprocate-devel mailing list