[reSIProcate] [repro-devel] Open issue: Server transaction lifetime

Jason Fischl jason at counterpath.com
Tue Aug 8 14:10:05 CDT 2006


On 8/8/06, Byron Campen <bcampen at estacado.net> wrote:
>
> You have missed my point; sometimes the TU can't send a failure
> response because the request is too garbled, and there is no other
> interface for terminating transactions. There is nothing the TU can
> do in this situation.
>

If the request was too garbled to generate a response, how was it able
to make it through the SipStack? It should be possible to construct a
failure response to any SipMessage that makes it to the TU. We may
need to make the Helper method that generates a failure response more
robust but I think that should be all that is required. Can you
provide some more concrete issues that exist in the current
implementation? Perhaps a test case.

Jason



More information about the resiprocate-devel mailing list