Cyril Moore

I am seeing a similar issue. The bug seems to be in RTCP packet processing. It seems to be getting lost in its packet offset lengths. Eventually hitting a random...

One more thing to note is that connection will only close if the stream is video only. For some reason the logic for BYE receipts only match SSRC on connections...

Wow this looks like its the key! From the **Buffer WITH UnprotectRtcpPacket call with forced SSRC:** The values from [32 - 55] look correct! [32]: 143 [33]: 206 [34]: 0...

I am currently looking into how this gets set. It seems we are not properly communicating our SSRC number to remote connections. In the use case where I see this...

I used the chromium diff tool and narrowed the the version down some more: You are probably looking for a change made after 1271606 (known good), but no later than...

Here are a few more details on we have tried so far: Looking at this issue: https://github.com/sipsorcery-org/sipsorcery/issues/1036 We pulled in this code here: https://github.com/BorgGames/sipsorcery/commit/7dd537518f5b2f160e97039cd014d61328e295a9 After still having issues we ended...

We found the issue: Chrome is now checking certificate type and needs to be passed the correct one in Certificate Request, Apparently WebRTC should be using ECDSA. In DtlsSrtpServer.cs line...

This may be resolved with this pull request. https://github.com/sipsorcery-org/sipsorcery/pull/1105 I was informed that the mismatch would be an issue with newer versions of Bouncy Castle which seems to be what...