[reSIProcate] Sending 100 trying

[Jason Fischl]

Yeah, I think there's a problem here as Scott describes. I am a bit
concerned about the effects of not transitioning from Trying state to
Proceeding though. I'll take a closer look at this today. Good find!

Michael, can you try setting Timer:T100=0 before you run your test and see
if the 100s go out? This should be a good workaround for you.

Thanks
Jason




On 5/16/06, Scott Godin <slgodin at icescape.com> wrote:
>
> Yeah - I just looked at the code, I think something is not right.
> According to RFC3261 a Server Invite Transaction does not have a Trying
> state - it is supposed to be initialized into the Proceeding state.  If
> we just change the timer code to check for Proceeding, then a 100 will
> be sent even if the TU sends a response.  Perhaps the best solution is
> to just remove the transition to Proceeding on line 266 (despite
> RFC3261) - and use the Trying state for Server Invite Transactions for
> the purpose of detecting if the TU has responded or not.  The rest of
> the code looks setup to handle this.
>
> Does anyone else have any thoughts on this?
>
> Scott
>
>
> > -----Original Message-----
> > From: Michael Baj [mailto:mbaj at bridgeport-networks.com]
> > Sent: Tuesday, May 16, 2006 9:38 AM
> > To: Scott Godin
> > Subject: RE: [reSIProcate] Sending 100 trying
> >
> > Scott,
> >
> > If this is the case, then I am still at a loss as to why I am not
> > receiving the 100 Trying.  From the resip code snippets below, it
> looks
> > like the TransactionState is constructed with the Trying state, but
> > changes the state to Proceeding right away.  Doesn't this prevent the
> > 100 Trying timer from being sent?
> >
> > Mike
> >
> > -----Original Message-----
> > From: Scott Godin [mailto:slgodin at icescape.com]
> > Sent: Tuesday, May 16, 2006 9:34 AM
> > To: Michael Baj; resiprocate-devel at list.sipfoundry.org
> > Subject: RE: [reSIProcate] Sending 100 trying
> >
> > StackThread will take care of calling process for you - what you are
> > doing here looks fine.
> >
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060516/e0659151/attachment.htm>