El Viernes, 25 de Julio de 2008, Martin Hoffmann escribió:
> Iñaki Baz Castillo wrote:
> > But anyway, "received"/"rport" in TCP is completely useless in a
> > transaction,
> > don't you think?
>
> If you follow the layered modell very closely, the transaction layer
> doesn't know about the connect
Yes, I think you can put it that way.
Nenad
-Original Message-
From: Iñaki Baz Castillo [mailto:[EMAIL PROTECTED]
Sent: Friday, July 25, 2008 10:15 AM
To: Nenad Milidrag
Cc: sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] Is "received" and "
El Viernes, 25 de Julio de 2008, escribió:
> I think you are forgetting that TCP connection from proxy to router is not
> persistent and after it is lost server will not know where to forward
> incoming call for the phone behind the NAT. However, if phone used rport
> it will send its public ip/po
: sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] Is "received" and "rport" used in SIP TCP?
El Jueves, 24 de Julio de 2008, Nenad Milidrag escribió:
> Hi,
>
> I am pretty sure it is still useful in certain cases, for example, if you
> have a NAT
El Jueves, 24 de Julio de 2008, Brett Tate escribió:
> I'm not very familiar with the rport RFC; however the following are a few
> comments excluding rport support.
>
> My understanding is that the received is still used with TCP. Although not
> explicitly mentioned, it is implied within rfc3261 s
El Jueves, 24 de Julio de 2008, Nenad Milidrag escribió:
> Hi,
>
> I am pretty sure it is still useful in certain cases, for example, if you
> have a NAT and NAT device is not SIP aware. Using rport/received together
> with you can get your public ip/port seen by the proxy and when
> reregistering
To: sip-implementors@lists.cs.columbia.edu
Subject: [Sip-implementors] Is "received" and "rport" used in SIP TCP?
Hi, I'm realizing that "received" and "rport" are completely useless in SIP
TCP:
- The client MUST reply using the existing conecction t
bia.edu
> Subject: [Sip-implementors] Is "received" and "rport" used in SIP TCP?
>
> Hi, I'm realizing that "received" and "rport" are completely
> useless in SIP
> TCP:
>
> - The client MUST reply using the existing conecction that
El Thursday 24 July 2008 02:31:28 Sanjay Sinha (sanjsinh) escribió:
> RFC 3581 implies that these two are for UDP, though not explicitly called
> out.
Humm, but even if "received" and "rport" si useless in TCP, the RFC makes it
mandatory to implement. :(
--
Iñaki Baz Castillo
[EMAIL PROTECTED]
edu
>Subject: [Sip-implementors] Is "received" and "rport" used in SIP TCP?
>
>Hi, I'm realizing that "received" and "rport" are completely
>useless in SIP
>TCP:
>
>- The client MUST reply using the existing conecction that
>creates
Hi, I'm realizing that "received" and "rport" are completely useless in SIP
TCP:
- The client MUST reply using the existing conecction that creates the
incoming request. So for now "received" and "rport" are not used at all.
- If the connection fails during the reply then the UAS/proxy must per
11 matches
Mail list logo
