[OpenSIPS-Devel] [ opensips-Bugs-2059624 ] "received" parameter is not added in some cases to Via

SourceForge.net noreply at sourceforge.net
Tue Aug 19 14:28:21 CEST 2008


Bugs item #2059624, was opened at 2008-08-19 15:19
Message generated for change (Settings changed) made by bogdan_iancu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2059624&group_id=232389

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
>Group: 1.4.x
Status: Open
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Alex Massover (cupotka2008)
Assigned to: Bogdan-Andrei Iancu (bogdan_iancu)
Summary: "received" parameter is not added in some cases to Via

Initial Comment:
OpenSIPS doesn't add 'recevied' parameter to Via in case that rport is present in original Via, but the address in Via is the same with src_ip.

This behavior brakes RFC 3581:

4.  Server Behavior
   The server behavior specified here affects the transport processing
   defined in Section 18.2 of SIP [1].
   When a server compliant to this specification (which can be a proxy
   or UAS) receives a request, it examines the topmost Via header field
   value.  If this Via header field value contains an "rport" parameter
   with no value, it MUST set the value of the parameter to the source
   port of the request.  This is analogous to the way in which a server
   will insert the "received" parameter into the topmost Via header
   field value.  In fact, the server MUST insert a "received" parameter
   containing the source IP address that the request came from, even if
   it is identical to the value of the "sent-by" component.  Note that
   this processing takes place independent of the transport protocol.

----------------------------------------------------------------------

>Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
Date: 2008-08-19 15:28

Message:
Logged In: YES 
user_id=1275325
Originator: NO

Just made a fix on this - could you check again (against trunk - rev 4621)
to see if it works?

Regards,
Bogdan

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2059624&group_id=232389



More information about the Devel mailing list