Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(JingleSession) Remove ice restart option and functionality. #2586

Merged
merged 2 commits into from
Oct 11, 2024

Conversation

jallamsetty1
Copy link
Member

Reinvite method in Jicofo is set to restart-jingle (terminate and recreate the whole jingle session) instead of sending 'transport-replace'. The replaceTransport option has never worked because of a bug in Chrome related to TCC sequence numbering after the DTLS transport layer is reset to start a new DTLS handshake with fresh transport on the bride.

Reinvite method in Jicofo is set to restart-jingle (terminate and recreate the whole jingle session) instead of sending 'transport-replace'. The replaceTransport option has never worked because of a bug in Chrome related to TCC sequence numbering after the DTLS transport layer is reset to start a new DTLS handshake with fresh transport on the bride.
@@ -255,40 +249,6 @@ export default class JingleConnectionPlugin extends ConnectionPlugin {
this.eventEmitter.emit(XMPPEvents.CALL_ENDED, sess, reasonCondition, reasonText);
break;
}
case 'transport-replace': {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest adding a log that transport-replace in not supported, just to help people debug if it happens to be used somehow

@jallamsetty1 jallamsetty1 merged commit fac989a into master Oct 11, 2024
2 checks passed
@jallamsetty1 jallamsetty1 deleted the ref-ice-restart branch October 11, 2024 15:52
@fippo
Copy link
Member

fippo commented Oct 12, 2024

Can you remind me of the upstream issue number? Agree that the general behavior after a DTLS restart is pretty underspecified but maybe we can at least get the TWCC sequence number clarified :-)

@jallamsetty1
Copy link
Member Author

Can you remind me of the upstream issue number? Agree that the general behavior after a DTLS restart is pretty underspecified but maybe we can at least get the TWCC sequence number clarified :-)

Sure, here it is - https://issues.webrtc.org/issues/42222276

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants