Skip to content

Comments

Separate RTP capabilities for sending and receiving#360

Merged
ibc merged 1 commit intov3from
separate-rtp-capabilities-for-sending-and-receiving
Feb 17, 2026
Merged

Separate RTP capabilities for sending and receiving#360
ibc merged 1 commit intov3from
separate-rtp-capabilities-for-sending-and-receiving

Conversation

@ibc
Copy link
Member

@ibc ibc commented Feb 17, 2026

Details

TODO

  • In the documentation website, document that device.rtpCapabilities getter is now deprecated and instead the app should use device.recvRtpCapabilities and device.sendRtpCapabilities.

# Details

- Fixes #141
- This PR replaces PR #359 but it's basically a copy&paste of it with some minimal cosmetic changes. So absolutely all credits to @6uliver.
- Now we generate different RTP capabilities for sending and receiving and the only change in the public API is that `device.rtpCapabilities` getter is now deprecated and instead the app should use `device.recvRtpCapabilities` and `device.sendRtpCapabilities`.

# TODO

* [ ] In the documentation website, document that `device.rtpCapabilities` getter is now deprecated and instead the app should use `device.recvRtpCapabilities` and `device.sendRtpCapabilities`.
@ibc ibc merged commit 7d1d0af into v3 Feb 17, 2026
7 checks passed
@ibc ibc deleted the separate-rtp-capabilities-for-sending-and-receiving branch February 17, 2026 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Incorrect reporting for the RTP capabilities if the 'Device' is used only for consuming streams

2 participants