reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] repro TLS : sending responses

I am not seeing any code that would cause what you're describing. For responses, the port in the sent-by portion of the Via is ignored entirely. rport can override the port we send back to, but that should never be set by anything other then the receiver of the request, and it will be set to the same port as the source anyway. Could you provide a message trace? 

Best regards,
Byron Campen


RFC 3261 defines at "18.2.2 Sending Responses"

"If the "sent-protocol" is a reliable transport
protocol such as
         TCP or SCTP, or TLS over those, the response
MUST be sent using
         the existing connection to the source of the
original request
         that created the transaction, if that
connection is still open.
         This requires the server transport to
maintain an association
         between server transactions and transport
connections."

I noticed that repro is trying to locate connection
for sending response based on data retrieved from Via
header of request (REGISTER in my case). Since Via
header has 5061 port and REGISTER was sent from
different port it failed to locate already established
connection for sending response. Should it be fixed?

Thanks,
Boris




_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel

Attachment: smime.p7s
Description: S/MIME cryptographic signature