Description of changes: When setting audio Attendee Capability to 'None' or 'Send' mid call, the backend will cease to send audio RTP packets, leading to reconnections. It will still send RTCPs, so we can use candidate pair stats to keep the connection alive.
Testing:
Dynamically set attendee capability for audio to None. No disconnection occurred.
Can these tested using a demo application? Please provide reproducible step-by-step instructions.
Enable dynamic attendee capability control to any attendee.
Set another attendee to audio capability 'None' or 'Send'.
Wait 30 seconds an ensure that attendee does not reconnect.
Checklist:
Have you successfully run npm run build:release locally?
y
Do you add, modify, or delete public API definitions? If yes, has that been reviewed and approved?
n
Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved?
n
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Issue #: None
Description of changes: When setting audio Attendee Capability to 'None' or 'Send' mid call, the backend will cease to send audio RTP packets, leading to reconnections. It will still send RTCPs, so we can use candidate pair stats to keep the connection alive.
Testing: Dynamically set attendee capability for audio to None. No disconnection occurred.
Can these tested using a demo application? Please provide reproducible step-by-step instructions.
Checklist:
Have you successfully run
npm run build:releaselocally? yDo you add, modify, or delete public API definitions? If yes, has that been reviewed and approved? n
Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved? n
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.