This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Osmocom network interface library".
The branch, pespin/osmux-lostpkt has been created at cd7503ab81e6bcaacab15d4509a865ee30a33255 (commit)
- Log ----------------------------------------------------------------- http://cgit.osmocom.org/libosmo-netif/commit/?id=cd7503ab81e6bcaacab15d4509a...
commit cd7503ab81e6bcaacab15d4509a865ee30a33255 Author: Pau Espin Pedrol pespin@sysmocom.de Date: Mon Aug 14 14:44:28 2017 +0200
osmux: Change log level of message to debug
This message is expected as all code filling batches call osmux_batch_enqueue() and checks for error to know if it must tell the user of the lib to call osmux_xfrm_input_deliver.
Change-Id: Icbd0fdeef0adb0b44255805ddbc6e41903f48b04
http://cgit.osmocom.org/libosmo-netif/commit/?id=4f750265fa6f466ba08dfdbed95...
commit 4f750265fa6f466ba08dfdbed959a405d55572bd Author: Pau Espin Pedrol pespin@sysmocom.de Date: Mon Aug 14 14:16:41 2017 +0200
osmux: Improve code handling lost packets
With previous implementation, only up to a maximum of 6-7 rtp lost packets can be replayed in best-case scenario. In other scenarios, big gaps can easily occur, for instance if a lot of packets are lost when the current batch is still empty.
If we forget to replay some lost RTP packets, then those are not taken into account in the Osmux stream, which means sequence numbers and timestamps will become different when Osmux re-generates the frames into RTP packets on the other side, and some receivers may not play nice with this jumps in time, eg. audio delays.
This new implementation tries to maintain status on the whole circuit level rather than only on current batch. To simplify things, it clones payload from latest packet to enqueue rather than last previosuly packet enqueued.
Change-Id: I3b77d372cedadfd5588384bea0e5d3fd475195ce
-----------------------------------------------------------------------
hooks/post-receive
osmocom-commitlog@lists.osmocom.org