Pau Espin e259c8ab18 osmux: Set Marker bit on osmux frame loss detected ... Until this patch, we didn't notify in any way to the RTP reader when an Osmux frame was lost. Instead, we updated the seq&timestamp as if there was no lost, and as a result the RTP reader would only see a steady increase of delay every time an osmux frame was lost. As the batch_factor for the lost packet is unknown, we cannot assume any number of amr payloads lost, and thus we cannot simply increment seq and timestamp for a specific amount. Instead, the only viable solution seems to set the M marker bit in the first rtp packet generated after a non-consecutive osmux frame is received. The implementation may act differently with the first generated RTP packet based on the first osmux seq number used for the stream. In case 0 it's used as first osmux seq number, M will be set depending on request from original RTP packet having the M bit set. If it's not 0, the first RTP packer will unconditionally have the M bit. That's not an issue because it's anyway expect for receiver to sync on the first packet. Related: OS#3185 Change-Id: I2efed6d726a1b8e77e686c7a5fe1940d3f4901a7		2018-04-19 18:24:25 +02:00
..
jibuf	examples: use osmo_init_logging2	2018-04-17 13:55:09 +02:00
osmo-pcap-test	tests: osmo-pcap-test: Fix pcap includes not found in old versions	2018-04-12 16:35:12 +02:00
osmux	osmux: Set Marker bit on osmux frame loss detected	2018-04-19 18:24:25 +02:00
Makefile.am	tests: Add osmux2 testsuite	2018-04-19 18:24:25 +02:00
testsuite.at	tests: Add osmux2 testsuite	2018-04-19 18:24:25 +02:00