[reSIProcate] Where is gone the 408 timeout ?

[Derek MacDonald]

Helper had been changed to not generate to tags in makeResponse.  I changed
it back to generate to tags if one wasn't present, as the stack was passing
non 3261 compliant responses back to the TU. 

I'm thinking that 4xx responses with the correct from tags but without a to
tag should probably be dispatched to the correct usage using method&cseq, or
possibly branch. If there is no usage the DialogSet would be destroyed.  

--Derek



> -----Original Message-----
> From: resiprocate-devel-bounces at list.sipfoundry.org [mailto:resiprocate-
> devel-bounces at list.sipfoundry.org] On Behalf Of Dominique Prunier
> Sent: Wednesday, September 08, 2004 7:13 AM
> To: resiprocate-devel at list.sipfoundry.org
> Subject: [reSIProcate] Where is gone the 408 timeout ?
> 
> Hello,
> 
> I was playing with dum when, after a sip address spelling error, i
> noticied
> that i havent got the OnTerminated callback after the timeout (408) error.
> After some (little) investigations, the problem seems to be that there is
> no
> tag in the to field of the 408. The response is not dispatched then. I
> dont
> think this is a normal behaviour...
> 
> dialogset.cxx:void DialogSet::dispatch(const SipMessage& msg):354
>  if(response.header(h_To).exists(p_tag))
> {
>     break;  //dialog creating/handled by dialog
> }
> else
> {
>     //throw away, informational status message eventually <----- 408 go
> there...
>     return;
> }
> 
> Thanks for your answer.
> Regards,
> 
> Dom.
> 
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel