On Fri, 2009-06-26 at 21:58 +0200, Mikael Magnusson wrote:
> Hi,
> there is a problem with the transaction matching code. If Yxa receives
> an INVITE request over TCP and CANCEL over UDP, then Yxa is not able to
> find the INVITE transaction and instead forwards the CANCEL in a new
> transaction. This new transaction in turn receives a 481 response, since
> it didn't match the INVITE Yxa sent earlier.
> I think the problem is in the sipheader:via_sentby/1, which should
> ignore the transport protocol since there is no guaranteed that the
> INVITE and CANCEL are received over the same transport protocol. The
> sender might have switched to TCP for the INVITE because of its size,
> and defaults to UDP for CANCEL.
> Patch included.
> Regards,
> Mikael

New patch includes updated tests. Let me know if there are any problems
with the patch.


Attachment: fix_via_sentby_proto.dpatch
Description: application/shellscript

Yxa-devel mailing list

Reply via email to