Re: [reSIProcate-users] Via port not correct when sending on TCP

[Joegen Baclor <jbaclor@xxxxxxxxx>]

Sending ephemeral port breaks with the connection.  Since 3261 mandates that responses be sent using the same stream the request was received when using reliable transports, the via port only becomes relevant to TCP when there is a need to re-establish the stream.  Thus, giving the listener port in the via is the sane way of doing stuff.

On 08/03/2012 12:16 AM, Scott Godin wrote:

Sorry for the slow response.  I think it's somewhat debatable as to what should be in the Via header when using TCP.  Statements in RFC3261 such as:

"Via contains the address (pc33.atlanta.com) at which Alice is expecting to receive responses to this request."

"A Via header field value contains the transport protocol used to send the message, the client's host name or network address, and possibly the port number at which it wishes to receive responses."

For TCP this is the port we are listening on and not the ephemeral port.  Granted such statements are only important to UDP implementations, I can't find a reference that says otherwise for TCP.

Scott

On Mon, Jul 2, 2012 at 9:19 AM, Nauman Sulaiman <nauman762-home@xxxxxxxxxxx> wrote:

Hi,

I have noticed that the via port is not correct when sending on TCP, is there any way to populate this with the

correct value as opposed to the fixed setting.

Thanks 

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/