New built-in SCTP stack

[ibc]

Details

• New built-in SCTP stack that replaces usrsctp.
• Breaking change: Remove useBuiltInSctpStack option in WorkerSettngs.
• Breaking change: Remove SctpCapabilities type. No longer needed.
• WebRtcTransport, PlainTransport, PipeTransport: Add sctpNegotiatedCapabilities() getter.
• Breaking change: WebRtcTransport, PlainTransport, PipeTransport options: Remove numSctpStreams and maxSctpMessageSize, and add maxSendMessageSize, maxReceiveMessageSize, sctpPerStreamSendQueueLimit and sctpMaxReceiverWindowBufferSize.
• Breaking change: DirectTransport options: Remove maxMessageSize, and add maxSendMessageSize and maxReceiveMessageSize.
• Breaking change: Change SctpParameters type from { port, OS, MIS, maxMessageSize } to { port, maxSendMessageSize, maxReceiveMessageSize, sendBufferSize, perStreamSendQueueLimit, maxReceiverWindowBufferSize, isDataChannel}.

Notes

• There are some tasks to do, but those are detailed in a separate task (to be done later, this PR is not blocked by those tasks): TODO for new built-in SCTP stack #1808
• There are also changes to be done in mediasoup-client, although for now everything is backwards compatible: Adapt SCTP to changes in mediasoup and call datachannel.close() when a DataProducer/DataConsumer is closed mediasoup-client#374
• Here a PR in mediasoup-demo project with the changes required to work with the new mediasoup SCTP API: Adapt to new SCTP stack mediasoup-demo#197

[ibc]

@jmillan I've pushed those typo fixes mentioned above in my last commit plus Rust part 1.

[threema-lenny]

Apologies for hijacking this thread to ask a question related to the SCTP rework: We (Threema) use the data channels fairly extensively via mediasoup. Would you be interested in getting feedback, and if so, when would be a good place to start testing?

[ibc]

Apologies for hijacking this thread to ask a question related to the SCTP rework: We (Threema) use the data channels fairly extensively via mediasoup. Would you be interested in getting feedback, and if so, when would be a good place to start testing?

There will be another PR after this to complete pending TODO items. See TODO_SCTP.md file in this branch.

I will announce it in Announcements category in the mediasoup forum.

The useBuiltInSctpStack option in createWorker() (defaults to false for now) will exist until this is fully tested and feedback is received.

[github-actions]

clang-tidy made some suggestions

[ibc]

TODO 1

UPDATE: Fixed.

rust/integration/smoke.rs test gets stuck:

cargo test --test integration smoke::

    Finished `test` profile [unoptimized + debuginfo] target(s) in 0.19s
     Running tests/integration/main.rs (/Volumes/src-cs/mediasoup/target/debug/deps/integration-e713b03692d22943)

running 1 test (forever)

[ibc]

The useBuiltInSctpStack option in createWorker() (defaults to false for now) will exist until this is fully tested and feedback is received.

Note: Radical change here. This PR will NOT keep usrsctp or the useBuiltInSctpStack option in createWorker(). Please re-read the updated PR description above.

[github-actions]

clang-tidy made some suggestions

[ibc]

@threema-lenny this branch is ready to test. Please read the PR description and take into account that, even if I didn't say it in there, the SCTP parameters generated by this mediasoup branch are still compatible with those that mediasoup-client requires.