This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-commitlog@lists.osmocom.org/.
gitosis at osmocom.org gitosis at osmocom.orgThis 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 A-bis protcol interface library". The branch, master has been updated via 9e992c24357dc19e6b0044584c553e802e0aebd1 (commit) from 524923a96a9892445234248623d8be642eb5229d (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://cgit.osmocom.org/libosmo-abis/commit/?id=9e992c24357dc19e6b0044584c553e802e0aebd1 commit 9e992c24357dc19e6b0044584c553e802e0aebd1 Author: Pau Espin Pedrol <pespin at sysmocom.de> Date: Thu Jun 29 18:04:18 2017 +0200 osmo_ortp.c: Duration of a RTP frame affects timestamp of the next one Duration of an RTP frames dictates the timestamp used for the next frame, not for the one being sent now. It was done like this before to account for possible losses. Implementation wise, the duration was understood as "duration between last frame was sent and now when current one is sent". It makes more sense to use it as the duration in number of sampling ticks as described on the function documentation, specially now that we can account for extra time by means of osmo_rtp_skipped_frame. Change-Id: Ib8f5fa5509059fe908c09a4381844c613d478548 ----------------------------------------------------------------------- Summary of changes: src/trau/osmo_ortp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- Osmocom A-bis protcol interface library