[reSIProcate] TransportSelector Route Bug

[Robert Sparks]

Derek (and Jason) -

IIRC, the TransportSelector doesn't have enough information to
pop or not pop (there are application layer checks that have
to do with whether you are responsible for the URI - there may
also be interactions with whether you are processing strict or
loose routes.

>From later in the log:
> rev 1581:  jason | 2003-08-05 10:48:58 -0500 (Tue, 05 Aug 2003) | 2 
> lines
>
> don't pop the route in the TransportSelector - this is a TU function
 
What case did you find that wasn't being handled correctly?

RjS

On Mon, 2004-06-14 at 00:26, Derek MacDonald wrote:
> Well, the bug that Jason orignallly fixed way back in rep ver# 1407 has
> recurred.
> 
> "fixed bug where topmost route wasn't being popped before sending"
> 
> I fixed it and checked it in, but if somebody thinks that the route should
> not be popped please ping the list and plead your case before changing it.
> 
> Thanks,
> 
> Derek
> 
> 
> -----Original Message-----
> From: resiprocate-devel-bounces at list.sipfoundry.org
> [mailto:resiprocate-devel-bounces at list.sipfoundry.org]On Behalf Of Jason
> Fischl
> Sent: Friday, June 11, 2004 6:25 PM
> To: resiprocate
> Subject: [reSIProcate] bug in Data::find
> 
> 
> There was a bug in the Data::find method when the offset was non-zero. I
> fixed it and added a test case.
> 
> 
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
> 
> 
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel