[SIPForum-techwg] Quetion about how registration mode works

[Elwell, John]

> -----Original Message-----
> From: Cullen Jennings [mailto:fluffy at cisco.com] 
> Sent: 18 February 2009 23:13
> To: Elwell, John
> Cc: Hadriel Kaplan; Spencer Dawkins; Francois Audet; 
> techwg at sipforum.org
> Subject: Re: [SIPForum-techwg] Quetion about how registration 
> mode works
> 
> 
> On Feb 18, 2009, at 1:12 , Elwell, John wrote:
> 
> > Because replacement of the target URI with the contact URI happens  
> > only
> > on the last hop,
> >
> 
> I don't buy this - loosely speaking, it happens by the proxy that  
> authoritative for  the AOR. You can have any number of proxies and  
> B2BUA in between the point where the replacement happens and the UA.  
> 3GPP is a pretty clear demonstration of that.
[JRE] I would say that the last hop is from the enterprise domain
proxy/registrar (the SIP-PBX), via any enterprise edge proxies, to the
UAS. UAs register with the SIP-PBX, not with the SP.

John


> 
> > from the domain proxy to the UAS. SIPconnect is not the
> > last hop.
> >
> > John
> >
> > > -----Original Message-----
> > > From: Cullen Jennings [mailto:fluffy at cisco.com]
> > > Sent: 17 February 2009 20:15
> > > To: Elwell, John
> > > Cc: Hadriel Kaplan; Spencer Dawkins; Francois Audet;
> > > techwg at sipforum.org
> > > Subject: Re: [SIPForum-techwg] Quetion about how registration
> > > mode works
> > >
> > >
> > > On Feb 16, 2009, at 7:24 , Elwell, John wrote:
> > >
> > > > > right solution.
> > > > [JRE] There is one major difference. In IETF we were 
> talking about
> > > > delivering requests from a proxy to a UA. In SIPconnect we
> > > are talking
> > > > about delivering requests from a SP proxy to a SIP-PBX proxy (or
> > > > B2BUA).
> > > > So keeping the target URI in Request-URI is RFC 3261-compliant.
> > >
> > > I am failing to understand why this makes a difference.
> > >
> > >
> > >
> 
>