Re: [Standards] XEP-0167: What happened with

Am 13.04.20 um 13:21 schrieb Daniel Gultsch: Hi, webrtc uses rtcp-mux but to my knowledge XMPP has no way of signaling that a party wants to use that. Jitsi apparently just assumes that rtcp-mux is being used when bundles are used [1] however that isn’t necessarily correct in all cases. That

Re: [Standards] XEP-0167: What happened with

For bundling we already have https://xmpp.org/extensions/xep-0338.html Only mux is w/o XEP. Best Regards, Sergey пн, 13 апр. 2020 г. в 14:41, Daniel Gultsch : > Am Mo., 13. Apr. 2020 um 11:33 Uhr schrieb Sergey Ilinykh < > rion...@gmail.com>: > > > > I can't say anything about the history. But

Re: [Standards] XEP-0167: What happened with

Am Mo., 13. Apr. 2020 um 11:33 Uhr schrieb Sergey Ilinykh : > > I can't say anything about the history. But I like Jitsi's implementation and > will add support to Psi soon. Bundling and rtcp muxing is not the same thing. They are often used together but not always. Is there any down side in

Re: [Standards] XEP-0167: What happened with

I can't say anything about the history. But I like Jitsi's implementation and will add support to Psi soon. Best Regards, Sergey пн, 13 апр. 2020 г. в 14:23, Daniel Gultsch : > Hi, > > webrtc uses rtcp-mux but to my knowledge XMPP has no way of signaling > that a party wants to use that. > >

[Standards] XEP-0167: What happened with

Hi, webrtc uses rtcp-mux but to my knowledge XMPP has no way of signaling that a party wants to use that. Jitsi apparently just assumes that rtcp-mux is being used when bundles are used [1] however that isn’t necessarily correct in all cases. Philipp Hancke apparently wrote a patch for XEP-0167