- From: Mini Doges via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 Feb 2024 20:22:12 +0000
- To: public-webrtc-logs@w3.org
> What you might try is the following: 1/ not send any candidates from the offerer 2/ tweaking the DTLS a=setup attribute in the SDP to be "active" instead of "actpass" before setting the offer at the remote end. This means the answerer will become the DTLS server. Might work but will still be brittle. Thanks, so i tried : 1/ not send any candidates from the offerer 2/ tweaking the DTLS a=setup attribute in the SDP to be "active" instead of "actpass" before setting the offer at the remote end. No luck, I can't figure how to connect. Same with this repo: https://github.com/fippo/paste after few seconds delay, the connection state will change to failed. How can I prevent the answerer to try to connect first and still provide candidates from the host ? Ideally the connection should only start when the host gets its answer back. Is there no solution but to use a signaling server ? thanks again -- GitHub Notification of comment by minidogenft Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2945#issuecomment-1967527979 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 27 February 2024 20:22:13 UTC