I've been experimenting with using transactions in my scenario, and I
thought that by doing so I could shield my controller from having to
deal with received re-transmissions. I've implemented re-transmission
detection logic in my scenario, but it adds more complexity, and I
thought SIPr would have a native capability for handling this for
me.
Do I need to implement my own txn handlers that tell the SM to consume
a retransmission? Is that how it is expected to work?
thanks,
Dave Adams.
--
You received this message because you are subscribed to the Google Groups "Sipper" group.
To post to this group, send email to sip...@googlegroups.com.
To unsubscribe from this group, send email to sipper+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sipper?hl=en.