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/tmp has been updated discards f8a6033124af552ea78bcd1a6bc38027dded8592 (commit) discards 11c6ae4cd6dba71c69534ebc23061cc42238ba88 (commit) discards 9acb2dc98a369c17151099e9e405e9c64e3e55a3 (commit) via 620251cdc3160b647cb7433a7001d54f0ce7fece (commit) via 80f3a0bc24ff22603012df791315b057c9e73c22 (commit) via d2313ad4103a4850f4976a41433d46f4c0c4ade6 (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 (f8a6033124af552ea78bcd1a6bc38027dded8592) \ N -- N -- N (620251cdc3160b647cb7433a7001d54f0ce7fece)

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=620251cdc3160b647cb7433a7001...

commit 620251cdc3160b647cb7433a7001d54f0ce7fece Author: Max msuraev@sysmocom.de Date: Fri Apr 29 11:54:23 2016 +0200

Set connected mode after setting remote 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.

Fixes: OS#1661

http://cgit.osmocom.org/libosmo-abis/commit/?id=80f3a0bc24ff22603012df791315...

commit 80f3a0bc24ff22603012df791315b057c9e73c22 Author: Max msuraev@sysmocom.de Date: Mon Apr 25 16:54:16 2016 +0200

Fix RTCP port allocation

Force use of random RTCP port if random RTP port is used. Before port 0 could be selected for RTCP.

http://cgit.osmocom.org/libosmo-abis/commit/?id=d2313ad4103a4850f4976a41433d...

commit d2313ad4103a4850f4976a41433d46f4c0c4ade6 Author: Max msuraev@sysmocom.de Date: Thu Apr 28 14:08:02 2016 +0200

Do not send RTP to port 0

Previously it was possible to send RTP data to port 0. This produce multiple errors during the beginning of RTP transmission.

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#1662

-----------------------------------------------------------------------

Summary of changes:

hooks/post-receive