Expose error definitions about sctp HOT 6 CLOSED

This is most likely as side effect of #183

I'm not sure if we should skip the callback or expose the errors, but exposing the errors makes sense to me as it's a smaller change (easier to reason about).

from sctp.

webrtc.DataChannel.OnError(err error) often receives

• abort chunk, with following errors: (User Initiated Abort: Close called).
• sending reset packet in non-established state: state=Closed

which seems be intended results. (Maybe by the recent updates?)

#183 seems related

from sctp.

We're seeing these errors (specifically sending reset packet in non-established state plenty of the time now and are logging them as such. Is there a way to quiet these if they are normal operating errors?

from sctp.

@jeremija any idea about above error?

from sctp.

Released v1.8.6

from sctp.

Using exposed errors in my product works as expected now

from sctp.