stream reset and data sending about usrsctp HOT 4 CLOSED

I behaviour should be that A sends all messages on the outgoing stream, which is marked to be reset. Once all of these messages are acknowledged by the peer, the stream reconfiguration message gets sent. So B would get the data first, and then the stream reset event.

If you are not seeing the above described behaviour with the current sources it is a bug. Please let me know how to reproduce the problem.

There was a bug in the library such that the above was not happening but the event was delivered before the data or even the association broke. However, this was fixed in July.

from usrsctp.

I think I have solved the problem, By respecting the RFC advice: only send SCTP_STREAM_RESET_OUTGOING

I was initially doing it like chrome does it. Look at line 919 here:
https://android.googlesource.com/platform/external/chromium_org/third_party/libjingle/source/talk/+/android-m-preview/media/sctp/sctpdataengine.cc

The code looks like this:
resetp->srs_flags = SCTP_STREAM_RESET_INCOMING | SCTP_STREAM_RESET_OUTGOING;

Mine is now looking like this:
resetp->srs_flags = SCTP_STREAM_RESET_OUTGOING;

from usrsctp.

I agree, the specification talks only about resetting outgoing streams (intentionally).

Best regards
Michael

from usrsctp.

Doesn't seem to be an issue with usrsctp.

from usrsctp.