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 A-bis protcol interface library".
The branch, max/ortp has been updated discards d7063c98853e4a412d0a8fd44dc2c4dc7a22ad25 (commit) via 1569cba59f00745c38405f330215781b1f3fc5ba (commit) via 337e39d5a2f3a9fdc22ec494e3f822c2c0166577 (commit) via 0d6db6fa4d44551eab31919026160222428e6794 (commit) via 9966f5246870bef69aea57eef8ea3dff59d37e45 (commit) via b811e514af1fc1126fa6a6019806defb74a69813 (commit) via 968f3f877bc9aa5a6fc0588ac8027bda219acde5 (commit)
This update added new revisions after undoing existing revisions. That is to say, the old revision is not a strict subset of the new revision. This situation occurs when you --force push a change and generate a repository containing something like this:
* -- * -- B -- O -- O -- O (d7063c98853e4a412d0a8fd44dc2c4dc7a22ad25) \ N -- N -- N (1569cba59f00745c38405f330215781b1f3fc5ba)
When this happens we assume that you've already had alert emails for all of the O revisions, and so we here report only the revisions in the N branch from the common base, B.
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=1569cba59f00745c38405f330215...
commit 1569cba59f00745c38405f330215781b1f3fc5ba Author: Max msuraev@sysmocom.de Date: Tue Apr 26 17:22:22 2016 +0200
Set non-blocking mode explicitly
ortp: do not rely on library default - set non-blocking mode explicitly.
http://cgit.osmocom.org/libosmo-abis/commit/?id=337e39d5a2f3a9fdc22ec494e3f8...
commit 337e39d5a2f3a9fdc22ec494e3f822c2c0166577 Author: Max msuraev@sysmocom.de Date: Wed Apr 27 18:53:06 2016 +0200
Only update TX timestamp for successful RTP send
http://cgit.osmocom.org/libosmo-abis/commit/?id=0d6db6fa4d44551eab3191902616...
commit 0d6db6fa4d44551eab31919026160222428e6794 Author: Max msuraev@sysmocom.de Date: Wed Apr 27 18:35:05 2016 +0200
Do not send RTP to port 0
Previously it was possible to send RTP data to port 0. To address this introduce OSMO_RTP_F_DISABLED flag and use it by default. When set this flag prevents transmission and reception of RTP frames for the session. The flag is unset when session is bound to non-zero remote port.
http://cgit.osmocom.org/libosmo-abis/commit/?id=9966f5246870bef69aea57eef8ea...
commit 9966f5246870bef69aea57eef8ea3dff59d37e45 Author: Max msuraev@sysmocom.de Date: Wed Apr 27 18:45:43 2016 +0200
Set connected mode after address
ortp: according to oRTP documentation rtp_session_set_connected_mode() uses the address set by rtp_session_set_remote_addr() - move the function call accordingly.
http://cgit.osmocom.org/libosmo-abis/commit/?id=b811e514af1fc1126fa6a6019806...
commit b811e514af1fc1126fa6a6019806defb74a69813 Author: Max msuraev@sysmocom.de Date: Wed Apr 27 18:43:03 2016 +0200
Expand network error callback
ortp: add extra parameters for network_error callback described in oRTP documentation and use them for log message.
http://cgit.osmocom.org/libosmo-abis/commit/?id=968f3f877bc9aa5a6fc0588ac802...
commit 968f3f877bc9aa5a6fc0588ac8027bda219acde5 Author: Max msuraev@sysmocom.de Date: Wed Apr 27 12:17:11 2016 +0200
Fix log message
ortp: use log message which properly describe funcion name and its parameters to simplify troubleshooting.
-----------------------------------------------------------------------
Summary of changes: include/osmocom/trau/osmo_ortp.h | 1 + src/trau/osmo_ortp.c | 26 +++++++++++++++++++------- 2 files changed, 20 insertions(+), 7 deletions(-)
hooks/post-receive