29 Apr
2016
29 Apr
'16
12:59 p.m.
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, laforge/pending has been updated
discards 26c974681b0cd6fda0bd3255c02851d4143fbdfb (commit)
discards aee9302264b82d6361a922b9cce6bee0174a11f5 (commit)
discards 5c4e7d8d553c0e0fe6cb351c0a96adb01ede717d (commit)
via 9ed7ca5b86240313dc4df8dbf4ff67be112084c1 (commit)
via 12814b96367ca4ef7e94fb5fb18609d5fabd33a1 (commit)
via b2d727a10256ed133f0db7f6760bfef73f8b9f6e (commit)
via 8c119f7a0510b75e7fa1b96a37f2a6650e13824f (commit)
via 80f7c0465fd244c26b037aaee92458c8dce86c6e (commit)
via e54d7bcef534461f794f98fa186f8afd8f8c318d (commit)
via d8026ec1b7be7922fd1c3122d2407a783cdab163 (commit)
via 7c9337b7755bfa51bdcba5cc76682217202fd635 (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 (26c974681b0cd6fda0bd3255c02851d4143fbdfb)
\
N -- N -- N (9ed7ca5b86240313dc4df8dbf4ff67be112084c1)
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=9ed7ca5b86240313dc4df8dbf4f…
commit 9ed7ca5b86240313dc4df8dbf4ff67be112084c1
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Thu Apr 28 11:10:01 2016 +0200
ipa_bts_id_resp(): handle non-existing members of ipacces_unit
Just because the IPA server is requesting certain identities via the CCM
protocol, doesn't mean that the client actually has those fields
available and initialized in struct ipaccess_unit.
Instad of segfaulting the client, let's check if the respective
identities are known. If yes, send them. If not, send the empty string
for that particular identity.
http://cgit.osmocom.org/libosmo-abis/commit/?id=12814b96367ca4ef7e94fb5fb18…
commit 12814b96367ca4ef7e94fb5fb18609d5fabd33a1
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Thu Apr 28 07:54:31 2016 +0200
ipa_server_conn: Add server-side CCM handling
An ipa_server implementation may call ipa_server_conn_ccm for
the CCM processing on the server side of the connection. This
function in turn will call a conn->ccm_cb() function for messages to be
handled by the server implementation, such as the ID_RESP message,
which contains the Unit ID of the client that has just connected.
http://cgit.osmocom.org/libosmo-abis/commit/?id=b2d727a10256ed133f0db7f6760…
commit b2d727a10256ed133f0db7f6760bfef73f8b9f6e
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Thu Apr 28 07:53:49 2016 +0200
ipa_server_conn: Add remote (peer) address to struct
This is better than every implementation calling getpeername()
on its own.
-----------------------------------------------------------------------
Summary of changes:
Makefile.am | 2 ++
contrib/jenkins.sh | 19 +++++++++++++++++++
include/osmocom/trau/osmo_ortp.h | 1 +
src/trau/osmo_ortp.c | 24 ++++++++++++++++++------
4 files changed, 40 insertions(+), 6 deletions(-)
create mode 100755 contrib/jenkins.sh
hooks/post-receive
--
Osmocom A-bis protcol interface library