José Luis Millán

@geirbakke, PR done #1620. It's working nicely in my tests. Can you please give it a try?

The spec says that the marker must be set: `This bit MUST be set to one for the final packet of the highest spatial-layer frame (the final packet of the...

As said before, we do not signal the decoder what our Target Spatial Layer (or. Current Spatial Layer) is, so setting the marker bit to 1 only for such a...

> how about if bandwidth is too low to send the highest layer/frame and the sender needs to drop it - does that have to be signalled In that case...

Reopening as setting the RTP marker true to all descriptions containing end of frame does not fix the issue. Freezes go away but only the lowest resolution is rendered.

@geirbakke, if I'm not mistaken you claim that when a packet is lost and its first RTX is also lost, and there are no more NACKs for it, then freezes...

Seems like just rewriting the behaviour for timeout for Info.js and DTMF.js would be needed. Could you test this patch? ```diff diff --git a/lib/RTCSession/Info.js b/lib/RTCSession/Info.js index c331c35..dd4fedd 100644 --- a/lib/RTCSession/Info.js...

> I noticed that it will be not possible to handle this timeout on the consumer side. Can you please be specific here?

> this.emit('failed' ... part is internal and cannot be handled by user. mm, it definitely should. `sendInfo()` should return the Info instance so the client can handle it's events.. Otherwise...

Indeed there IS public API for it: https://jssip.net/documentation/api/session/#event_newInfo `RTCSession` `newInfo` will fire with the `Info` instance. So you can: ```js session.once('newInfo', (info) => { info.on('failed', console.log)}); session.sendInfo();