Monday, 29 February 2016
- [ortc] STUN/TURN error codes
- [ortc] Pull Request: Change log updates
- [ortc] Pull Request: Garbage collection clarifications
- Closed: [ortc] N rtpSenders sharing SSRC on same transport
- [ortc] RTCRtpSender and RTCRtpReceiver state
- [ortc] Merged Pull Request: Change log fix for Generic NACK Issue
- [ortc] Pull Request: For Generic NACK, RTCRtcpFeedback.parameter is unset
- [ortc] Pull Request: Clarification for Generic NACK
- [ortc] N rtpSenders sharing SSRC on same transport
- [ortc] Merged Pull Request: Add FEC/RTX/RED support to "RTP matching rules"
- Closed: [ortc] No .kind in RTCRtpCodecParameters?
- [ortc] RTCRtcpFeedback.parameter should be optional
- [ortc] Pull Request: Add FEC/RTX/RED support to "RTP matching rules"
- [ortc] No .kind in RTCRtpCodecParameters?
- [ortc] Merged Pull Request: Reference fixes
- [ortc] Pull Request: Reference fixes
- [ortc] Closed Pull Request: Typo fix in respec.js
- [ortc] Pull Request: Typo fix in respec.js
- [ortc] Merged Pull Request: Revert "RFC 7675 updates (was CONSENT reference)"
- [ortc] Pull Request: Revert "RFC 7675 updates (was CONSENT reference)"
- [ortc] Merged Pull Request: Revert "Reference updates"
- [ortc] Pull Request: Revert "Reference updates"
- [ortc] Merged Pull Request: RFC 7675 updates (was CONSENT reference)
- [ortc] Pull Request: RFC 7675 updates (was CONSENT reference)
- [ortc] Merged Pull Request: Reference updates
- [ortc] Pull Request: Reference updates
- Closed: [ortc] RTCRtpReceiver.getParameters() needed
- Re: Need SDP to ORTC good example code
- Re: Need SDP to ORTC good example code
- Re: Need SDP to ORTC good example code
- Re: Need SDP to ORTC good example code
- Re: Need SDP to ORTC good example code
- Re: Need SDP to ORTC good example code
- Need SDP to ORTC good example code
- [ortc] RTX and ssrc indication
Monday, 22 February 2016
- Closed: [ortc] DTMF Support
- [ortc] Merged Pull Request: Required DTMF Tone Support
- [ortc] Pull Request: Required DTMF Tone Support
- [ortc] DTMF Support
Sunday, 21 February 2016
- Closed: [ortc] level-asymmetry-allowed and profile-level-id capabilities and settings
- Closed: [ortc] RTCIceGathererEvent needs url member
- Closed: [ortc] encodingId syntax
- Closed: [ortc] RangeError for resolutionScale < 1.0
- [ortc] Merged Pull Request: level-asymmetry-allowed
- [ortc] Merged Pull Request: Fix change logs
- [ortc] Merged Pull Request: RangeError for resolutionScale < 1.0
- [ortc] Merged Pull Request: encodingId syntax
- [ortc] Merged Pull Request: RTCIceGathererEvent needs url member
- [ortc] Pull Request: level-asymmetry-allowed
Saturday, 20 February 2016
Tuesday, 16 February 2016
- [ortc] Pull Request: Fix change logs
- [ortc] Pull Request: RangeError for resolutionScale < 1.0
- [ortc] RangeError for resolutionScale < 1.0
- [ortc] Pull Request: encodingId syntax
- Closed: [ortc] Something is wrong with document anchor links
- Closed: [ortc] What does RTCRtpEncodingParameters.active=false in a RtpReceiver?
- Closed: [ortc] Certificate checking
- [ortc] Merged Pull Request: Certificate checking
- [ortc] Pull Request: RTCIceGathererEvent needs url member
Friday, 12 February 2016
Thursday, 11 February 2016
Sunday, 7 February 2016
- [ortc] Merged Pull Request: WebRTC 1.0 as normative reference
- [ortc] Pull Request: Certificate checking
Saturday, 6 February 2016
Thursday, 4 February 2016
Wednesday, 3 February 2016
- Closed: [ortc] RTCRtpParameters: unclear requirements
- [ortc] Pull Request: WebRTC 1.0 as normative reference
Tuesday, 2 February 2016
- Re: [ortc] [non rtcp-mux pain] Doesn't RTCRtpReceiver belong to RTCDtlsTransport?
- Closed: [ortc] [non rtcp-mux pain] Doesn't RTCRtpReceiver belong to RTCDtlsTransport?