RE: problems with record route on strict routers

"M. Ranganathan" <[email protected]>
Newsgroups gmane.comp.voip.nist-sip
Organization NIST
Message-ID <[email protected]>
OK this one is fixed and cvs is updated.

Ranga

On Tue, 2006-09-05 at 16:14 +0300, Hagai Sela (TA) wrote:
> I found out why this happens, but I don't know how to fix it.
> 
> When sending a subsequest request you have to first get a client
> transaction (using SipProvider.getNewClientTransaction) and then use
> Dialog.sendRequest to send the request.
> 
> This means that the router's getNextHop method is called twice: the
> first call is at SipProviderImpl.java, line 317, and then at
> SIPDialog.java, line 1669.
> 
> This is a bug, because the default router will perform "Route
> Information Postprocessing" twice instead of once, and this leads to
> using the one-before-last record route header instead of the last one
> (DefaultRouter.java, line 183).
> 
>  
> 
> Hagai.
> 
>  
> 
>                                    
> ______________________________________________________________________
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Hagai Sela (TA)
> Sent: Tuesday, September 05, 2006 11:23 AM
> To: [email protected]
> Subject: [nist-sip] problems with record route on strict routers
> 
> 
>  
> 
> Hi,
> 
> I have a problem with an upstream strict router. I send an outbound
> INVITE to it, and it responds with two record route headers and a
> contact address in the 200 OK. The ACK I send is sent according to the
> bottom route header, as it should, but when I send BYE it is sent
> according to the top route header.
> 
>  
> 
> An ethereal capture is attached, and also a modification of the simple
> call setup example which reproduces this bug (not accurately).
> 
>  
> 
> Hagai.
> 
> 
> _______________________________________________
> nist-sip mailing list
> [email protected]
> http://www-x.antd.nist.gov/mailman/listinfo/nist-sip
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.