Friday, 25 September 2015
- RE: Issue 246: Incoming RTX payload ambiguity
- Issue 246: Incoming RTX payload ambiguity
- RE: Re: Issue 218: DTLS: Problem with forking
Thursday, 24 September 2015
- Issue 230: Stats API: getStats on the IceGatherer??
- Issue 242: DataChannel / implementation IETF conflict even / odd port problem
- Issue 244: Changing ICE servers on an RtcIceGatherer
- RE: Issue 243: RtpListener / mux id and RTP header extension issues
- Issue 243: RtpListener / mux id and RTP header extension issues
Tuesday, 22 September 2015
- Re: Issue 195: Certificate Management API
- RE: Issue 195: Certificate Management API
- Re: Issue 195: Certificate Management API
- Re: Issue 195: Certificate Management API
- Re: Issue 218: DTLS: Problem with forking
- Issue 222: RTCIceCredentialType
- Issue 219: No "failed" state in DtlsTransport
- Issue 224: RTCIceGatherPolicy harmonization with WebRTC and Issue 244: Changing iceServers on an RTCIceGatherer
- Issues 225 and 229: spelling
- Issues 235 and 237: Examples 5, 6 and 7
- RE: Issue 236 (API for CSRCs and audioLevels)
- Issue 240: when initiator can send message via DataChannel (Example 22)
Saturday, 19 September 2015
Friday, 18 September 2015
Monday, 14 September 2015
- RE: DataChannel: negotiated behaviour appears to be not possible to implement (#233)
- Re: Issue 231: DataChannel: short vs. long data types
Saturday, 12 September 2015
Friday, 11 September 2015
- Re: Issue 236 (API for CSRCs and audioLevels)
- RE: Issue 236: add API to get SSRC and audio level
- Issue 236: add API to get SSRC and audio level