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 2b18f0850c0b6e40916ae8eb1609478183c4a0ac (commit) discards 4200f66e9ec3acfca4d7c60a8e88b2720e494476 (commit) discards 1a01b217536985f79f71e69e2a2f6d0b38e45270 (commit) discards 801ad99fc9cd7c7df73aa9b2d55b0e6ccf8a5239 (commit) via c87cab8a9e1d8f195f5049d8cd017803ec5d7b77 (commit) via 729f597887bd74318650414ef48d6f405d3de12f (commit) via c80c15d4cfa4458040d22545dbe4623c13429999 (commit) via c08c53206226ae2e6e4b385354715a714709623c (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 (2b18f0850c0b6e40916ae8eb1609478183c4a0ac) \ N -- N -- N (c87cab8a9e1d8f195f5049d8cd017803ec5d7b77) 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=c87cab8a9e1d8f195f5049d8cd0… commit c87cab8a9e1d8f195f5049d8cd017803ec5d7b77 Author: Max <msuraev(a)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. This is not only producing multiple errors but also breaks RTP transmission with newer (>= 0.25) oRTP leading to calls with no audio. To address this OSMO_RTP_F_DISABLED flag was introduced. It's set by default for all new RTP sessions. It can be manually unset after the call to osmo_rtp_socket_create(). When the flag is set it prevents transmission and reception of RTP frames for the session. The flag is unset automatically in osmo_rtp_socket_connect() when session is bound to non-zero remote port. Fixes: OS#1661, OS#1662 http://cgit.osmocom.org/libosmo-abis/commit/?id=729f597887bd74318650414ef48… commit 729f597887bd74318650414ef48d6f405d3de12f Author: Max <msuraev(a)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=c80c15d4cfa4458040d22545dbe… commit c80c15d4cfa4458040d22545dbe4623c13429999 Author: Max <msuraev(a)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=c08c53206226ae2e6e4b3853547… commit c08c53206226ae2e6e4b385354715a714709623c Author: Max <msuraev(a)sysmocom.de> Date: Wed Apr 27 18:43:03 2016 +0200 Expand network error callback ortp: use extra parameter for network_error callback in log message as it's described in oRTP documentation (error string). ----------------------------------------------------------------------- Summary of changes: src/trau/osmo_ortp.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- Osmocom A-bis protcol interface library