Re: [reSIProcate-users] State Tracking Dialogs
Scott Godin wrote:
> What kind of state do you want to track? SIP Transactions, SIP
> Dialogs, or both? In my opinion, the effort you would need to get
> this to actually work with the existing SIP Stack Transaction and DUM
> (Dialog) layers would be greater than just building your own state
> tracking engine. Using the existing DUM/transaction layer will be
> complicated by the fact that they will want to generate SIP responses,
> and that will not make sense for your scenario, since you already have
> all of the messaging off the wire. Building something new to track
> transaction and DialogSet/Dialog state for an existing flow of SIP
> messages should be a reasonably straight forward thing to do.
>
>
I am certainly missing the straightforward part about this setup. There
are so many possible transitions and steps and allowed methods and
operations from each level. If you're building a state machine, here's
a case to consider. Starting with identifying the parties, is there
enough detail in the sip message to do so, or are you required to use
something external such as an ip/port pair to demarcate? Another case
is something like onOffer. If you're processing messages and have
callbacks at each point, do you call onOffer again if you get a 302 and
then another invite is sent out? Nothing I imagine prevents the UAC
from changing the sdp before and after the 302.
The sideways point of view for implementing this is very confusing to
implement for sure.
Dan
> Scott
>
> On Fri, Feb 5, 2010 at 11:56 AM, Dan Weber <dan@xxxxxxxxxxxxxx> wrote:
>
>> Hey guys,
>>
>> I currently have an application that takes uses libpcap to extract call
>> flows off the wire. I currently use resiprocate for parsing the
>> messages, however, I wonder if it's possible to use it in an expanded role.
>>
>> Is it possible to feed DUM messages that came over the wire and use it
>> for state tracking?
>>
>> Dan
>>
>> _______________________________________________
>> resiprocate-users mailing list
>> resiprocate-users@xxxxxxxxxxxxxxx
>> List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>>
>>