osmocom-commitlog April 2016

osmocom-commitlog@lists.osmocom.org

1 participants
289 discussions

openbsc.git branch laforge/pending updated. 0.15.0-256-g5d547a4
by gitosis＠osmocom.org 29 Apr '16

29 Apr '16

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 "The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)". The branch, laforge/pending has been updated discards 5aa9e5bf2ade1f007b753ebc51e60555bc50c679 (commit) discards b7767eaf1b0cc7038a47d1a25e88028c275a1112 (commit) discards 75754afbbe0cdbe36628d0320f8c16ea1ad2fd6b (commit) discards e95cab8501e57173aebafd2407c4b179839f43bd (commit) discards f6552c5b7fea97287645c265f9692d0d2cbae324 (commit) discards e263955bb145a391787eeda78e59e9118c96c9d4 (commit) discards 9ef78ba04efff555929fc63682900c4a865259bf (commit) discards 356cd62d7814860fd3229f05469b5ffadaf3f583 (commit) discards acde4c4f12c854b3b9a78a262bbb3f87a4975599 (commit) discards 50f1554e4401eacd12aa26cae9b22158b5d117a0 (commit) discards 7e20f031902c1cd505f5517476c9ca83442c5f22 (commit) discards 9c25d51a8b094f800a2b155c32bae2b1b4694cd6 (commit) discards 357193be69281963eb7ca659ae8a3674ce4a4da9 (commit) discards 30533b9897b68308b99cbee4ba2a4182b3c1bde1 (commit) via 5d547a4358edbd18744d1996d6ecb40328f09061 (commit) via d8aa412c46638abea05488ebb2e9d70ca7fd628a (commit) via 564c06525b9acb3f4b90d4c92970e7d9cc5b1d8e (commit) via 31760a1f6089fb59475ba79faa3eb97e4cf00f68 (commit) via 23d77d56ea47bbb971bf2fc5d93d6ae2d7d30f03 (commit) via 50f1c0af567423b6ade9a84aaa5197ecf6237819 (commit) via eff215a8bb766e62a02bcc0f4334470a53475001 (commit) via 7ca035decaaed460e66286868b1f14ccd3e00013 (commit) via 85234a32db7ab91f9361d4a54bea9523e2c7a5b9 (commit) via 842674b8b3d245a2eecb352eb89609ed44cb0832 (commit) via 28903a99eae60cee616901fd3863960b1321ff54 (commit) via d3fa84dbba3b67cdbe2d8c789b2833b5ddf42068 (commit) via 53373bca8f9fe79ca981f9fc1ef644586bd5c3b2 (commit) via 121e9a4164e65dfb68b2bf09297a8537a2f659c5 (commit) via 3ffce19cb4929c907460753d302e4720558cc6d2 (commit) via 35697b9a109f08791c00dbb1a8dfaaaff29a8a80 (commit) via 299a9994656e97defea85689467e61ba34e8577e (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 (5aa9e5bf2ade1f007b753ebc51e60555bc50c679) \ N -- N -- N (5d547a4358edbd18744d1996d6ecb40328f09061) 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/openbsc/commit/?id=5d547a4358edbd18744d1996d6ecb403… commit 5d547a4358edbd18744d1996d6ecb40328f09061 Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Apr 27 18:21:16 2016 +0200 osmo_oap_decode(): Use common argument ordering In general, if a function generates output data like a msgb (or in this case filling an osmo_oap_message structure), the output argument precedes the source. This is what we use all over libosmo*, and it is modelled after memcpy(), where dst is the first argument, before src. Let's align osmo_oap_decode(). Intestingly, osmo_oap_encode was already correct, so the encode/decode functions used different conventions before. http://cgit.osmocom.org/openbsc/commit/?id=d8aa412c46638abea05488ebb2e9d70c… commit d8aa412c46638abea05488ebb2e9d70ca7fd628a Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Apr 27 18:17:26 2016 +0200 OAP: Various coding style fixes * we always declare stack variables at the top of the function / block * 'switch' is not a function, so there's space ahead of the opening ( http://cgit.osmocom.org/openbsc/commit/?id=564c06525b9acb3f4b90d4c92970e7d9… commit 564c06525b9acb3f4b90d4c92970e7d9cc5b1d8e Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Apr 27 18:14:14 2016 +0200 OAP: use osmo_oap_ prefix for OAP, rather than plain oap_ this is in preparation of moving related code to libosmocore. http://cgit.osmocom.org/openbsc/commit/?id=31760a1f6089fb59475ba79faa3eb97e… commit 31760a1f6089fb59475ba79faa3eb97e4cf00f68 Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Apr 27 15:17:14 2016 +0200 oap_message.h: Remove dependency to openbsc include This is a first step to moving oap_messages.h to libosmocore http://cgit.osmocom.org/openbsc/commit/?id=23d77d56ea47bbb971bf2fc5d93d6ae2… commit 23d77d56ea47bbb971bf2fc5d93d6ae2d7d30f03 Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Apr 25 19:07:34 2016 +0200 Move osmo_gsup_messages.[ch] to libosmocore This requires the corresponding commit in libosmocore. http://cgit.osmocom.org/openbsc/commit/?id=50f1c0af567423b6ade9a84aaa5197ec… commit 50f1c0af567423b6ade9a84aaa5197ecf6237819 Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Apr 25 19:01:26 2016 +0200 move utils.h functions to libosmocore This needs the corresponding commit in libosmocore which imports the related functions http://cgit.osmocom.org/openbsc/commit/?id=eff215a8bb766e62a02bcc0f4334470a… commit eff215a8bb766e62a02bcc0f4334470a53475001 Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Apr 25 16:01:15 2016 +0200 osmo_gsup_messge.[ch] documentation update (doxygen) http://cgit.osmocom.org/openbsc/commit/?id=7ca035decaaed460e66286868b1f14cc… commit 7ca035decaaed460e66286868b1f14ccd3e00013 Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Apr 25 15:36:08 2016 +0200 gsup_messages: Add UMTS AKA related encoding/decoding support http://cgit.osmocom.org/openbsc/commit/?id=85234a32db7ab91f9361d4a54bea9523… commit 85234a32db7ab91f9361d4a54bea9523e2c7a5b9 Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Apr 25 15:20:51 2016 +0200 move osmo_shift_* / osmo_match_shift_* to libosmogsm http://cgit.osmocom.org/openbsc/commit/?id=842674b8b3d245a2eecb352eb89609ed… commit 842674b8b3d245a2eecb352eb89609ed44cb0832 Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Apr 25 15:14:01 2016 +0200 rename gprs_shift_*() to osmo_shift_*() This rename is the first step of moving the associated functions into libosmocore. Also, rename gprs_match_* to osmo_match_shift_* to indicate that it is not just matching the TLV, but also shifting the data portion. http://cgit.osmocom.org/openbsc/commit/?id=28903a99eae60cee616901fd3863960b… commit 28903a99eae60cee616901fd3863960b1321ff54 Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Apr 25 14:53:43 2016 +0200 Rename gprs_gsup_* to osmo_gsup_* This is a preparation to move the related code to libosmocore, whilst at the same time generalizing it from GPRS Subscriber Update Protocol to the Osmocom Generic Subscriber Update Protoco. http://cgit.osmocom.org/openbsc/commit/?id=d3fa84dbba3b67cdbe2d8c789b2833b5… commit d3fa84dbba3b67cdbe2d8c789b2833b5ddf42068 Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Apr 20 17:50:17 2016 +0200 use new libosmocore gsm_23_003.h for IMEI/IMSI length ... rather than our private definitions everwhere. As an added benefit, gprs_gsup_messages.h is now free of any header dependencies within openbsc. http://cgit.osmocom.org/openbsc/commit/?id=53373bca8f9fe79ca981f9fc1ef64458… commit 53373bca8f9fe79ca981f9fc1ef644586bd5c3b2 Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Apr 20 17:11:43 2016 +0200 move gsm_04_08_gprs.h to libosmocore This requres the corresponding commit in libosmocore. http://cgit.osmocom.org/openbsc/commit/?id=121e9a4164e65dfb68b2bf09297a8537… commit 121e9a4164e65dfb68b2bf09297a8537a2f659c5 Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Apr 20 13:13:19 2016 +0200 Start to use struct osmo_auth_vector from gsm_auth_tuple Rather than having a 'private' structure for kc, sres and rand, we now finally (with 4 years delay) use osmo_auth_vector from libosmogsm, which encapsulates authentication vectors that can be either GSM triplets or UMTS quintuples or a combination of both. gsm_auth_tuple becomes a wrapper around osmo_auth_vector, adding use_count and key_seq to it. key_seq is no longer initialized inside gprs_gsup_messages.c, as there is no CKSN / key_seq inside the message anyway. If a usre of the code needs key_seq, they need to manage it themselves. ----------------------------------------------------------------------- Summary of changes: openbsc/src/libbsc/bsc_vty.c | 11 ++++---- openbsc/src/libbsc/system_information.c | 2 +- openbsc/src/libmsc/gsm_04_08.c | 46 ++++++++++++++++++++++++++++++++- 3 files changed, 52 insertions(+), 7 deletions(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

openbsc.git branch master updated. 0.15.0-242-g3ffce19
by gitosis＠osmocom.org 29 Apr '16

29 Apr '16

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 "The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)". The branch, master has been updated via 3ffce19cb4929c907460753d302e4720558cc6d2 (commit) from 35697b9a109f08791c00dbb1a8dfaaaff29a8a80 (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/openbsc/commit/?id=3ffce19cb4929c907460753d302e4720… commit 3ffce19cb4929c907460753d302e4720558cc6d2 Author: Max <msuraev(a)sysmocom.de> Date: Mon Apr 25 15:22:00 2016 +0200 Disconnect calls with incompatible channel types / modes In case both TCH/H and TCH/F or different codecs are configured and internal MNCC handler is used we might end up in a situation where call legs with incompatible channel types or codecs would be connected resulting in a broken audio. Disconnect such calls with appropriate error message. Fixes: OS#1663 ----------------------------------------------------------------------- Summary of changes: openbsc/src/libmsc/gsm_04_08.c | 46 +++++++++++++++++++++++++++++++++++++++++- 1 file changed, 45 insertions(+), 1 deletion(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

osmo-trx.git branch fairwaves/ext-build-fix created. c88385c69d6a8ed415b7bc2480d13683ac8f6ca0
by gitosis＠osmocom.org 29 Apr '16

29 Apr '16

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 "OpenBTS' transceiver retro-fit". The branch, fairwaves/ext-build-fix has been created at c88385c69d6a8ed415b7bc2480d13683ac8f6ca0 (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-trx/commit/?id=c88385c69d6a8ed415b7bc2480d1368… commit c88385c69d6a8ed415b7bc2480d13683ac8f6ca0 Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com> Date: Fri Apr 29 14:05:59 2016 +0300 makefile: Fix build from an external path. When you build from an external path, compiler can't find convert.h include, because it was specified relative to the current directory. Change this to specify the include dit relative to the Makefile location. ----------------------------------------------------------------------- hooks/post-receive -- OpenBTS' transceiver retro-fit

1 0

libosmocore.git branch laforge/pending updated. 0.9.0-147-g2cf120f
by gitosis＠osmocom.org 29 Apr '16

29 Apr '16

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 "An utility library for Open Source Mobile Communications". The branch, laforge/pending has been updated discards 22c9f6b79869480d58ad9aa9d951ca88af70c60d (commit) discards e8de4610400e299dedd4d143bb4fa9dc12d4e9b8 (commit) discards 5d57360f7a3973dcc49c5d8f7e8f3086ee910441 (commit) discards 01b4115a3dcc806297e6593ac0a01962209e32e2 (commit) discards 85a1009e9f3c2bff8e3625129357e85a5c481cad (commit) discards 197bc3364686881daecde62c3fc3b87bc4f20c4a (commit) discards 0d7aaded15b683a3540ba85299ec8dd4b54ec475 (commit) discards 090f9859b9bb6c0af5c17aca037951360217505a (commit) discards 90d72bb18e6c0e236f22eaa12b52bab182e52bc9 (commit) discards 6291ffafed10bfe31eef28f81ba7019aff4b557a (commit) via 2cf120ff128e2ef10713b7b13149805df9f269fc (commit) via fa128d3c4b7db9c1e6c84d8ffe2c2e843ba20d37 (commit) via b1fc280438f6b8d23b3af7f9ea2cfacb6f51751b (commit) via 4ba1323035d228fbd5146f603962f00854ad1cad (commit) via 44409f9aa997e19e66cfdcefa0f51f66ea286971 (commit) via f1088f7734b0b80ff39fbe09898d5a3cd778f26a (commit) via 05ea145fd99872e1041aa733d2e4dc2a87d53598 (commit) via dbe8e3e3901d67c5fd122cace146464d326e4efa (commit) via 322a2f3874996bd32748b380178bf3e31aac9cf0 (commit) via 1cd0d8af6f66010f2d59196bf227b87989a44282 (commit) via aa16d63c273204dc69108f7361d38b751bfb69e4 (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 (22c9f6b79869480d58ad9aa9d951ca88af70c60d) \ N -- N -- N (2cf120ff128e2ef10713b7b13149805df9f269fc) 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/libosmocore/commit/?id=2cf120ff128e2ef10713b7b13149… commit 2cf120ff128e2ef10713b7b13149805df9f269fc Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Apr 27 18:32:35 2016 +0200 import oap message parsing / encoding from openbsc.git http://cgit.osmocom.org/libosmocore/commit/?id=fa128d3c4b7db9c1e6c84d8ffe2c… commit fa128d3c4b7db9c1e6c84d8ffe2c2e843ba20d37 Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Apr 25 19:09:24 2016 +0200 add doc/*.tag to .gitignore http://cgit.osmocom.org/libosmocore/commit/?id=b1fc280438f6b8d23b3af7f9ea2c… commit b1fc280438f6b8d23b3af7f9ea2cfacb6f51751b Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Apr 25 18:46:22 2016 +0200 import gprs_gsup_message.[ch] from openbsc as gsup.[ch] Move those routines from OpenBSC to libosmogsm, so they can be re-used from other programs. I think it was a mistake to add them only inside the openbsc repository in the first place. We need to pay more attention to this in the future. http://cgit.osmocom.org/libosmocore/commit/?id=4ba1323035d228fbd5146f603962… commit 4ba1323035d228fbd5146f603962f00854ad1cad Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Apr 25 18:47:53 2016 +0200 Import osmo_{encode,decode}_big_endian() from openbsc http://cgit.osmocom.org/libosmocore/commit/?id=44409f9aa997e19e66cfdcefa0f5… commit 44409f9aa997e19e66cfdcefa0f51f66ea286971 Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Apr 25 15:19:35 2016 +0200 tlv: Import osmo_shift_* and osmo_match_shift_* from openbsc These routines have nothing to do with specifically the BSC, so import them to the TLV parser we keep in libosmogsm. http://cgit.osmocom.org/libosmocore/commit/?id=f1088f7734b0b80ff39fbe09898d… commit f1088f7734b0b80ff39fbe09898d5a3cd778f26a Author: Harald Welte <laforge(a)gnumonks.org> Date: Mon Apr 25 12:11:20 2016 +0200 Update doxygen annotations in libosmocore This adds and improves doxygen API descriptions all over libosmocore, reducing the 'white spots' that don't have any documentation. http://cgit.osmocom.org/libosmocore/commit/?id=05ea145fd99872e1041aa733d2e4… commit 05ea145fd99872e1041aa733d2e4dc2a87d53598 Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Apr 20 17:28:03 2016 +0200 add new header file for TS 23.003 http://cgit.osmocom.org/libosmocore/commit/?id=dbe8e3e3901d67c5fd122cace146… commit dbe8e3e3901d67c5fd122cace146464d326e4efa Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Apr 20 17:12:24 2016 +0200 import gsm_04_08_gprs.[ch] from openbsc.git The definitions in this header file (and associated strings in the c file) are generic about the GPRS Layer3 signalling protocols, and thus should be part of the library. http://cgit.osmocom.org/libosmocore/commit/?id=322a2f3874996bd32748b380178b… commit 322a2f3874996bd32748b380178bf3e31aac9cf0 Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Apr 20 10:41:27 2016 +0200 Add log_fini() function to release all memory allocated by logging framework This is e.g. quite useful to call at the end of test code, in order to show that all memory allocated actually is released before exit(). http://cgit.osmocom.org/libosmocore/commit/?id=1cd0d8af6f66010f2d59196bf227… commit 1cd0d8af6f66010f2d59196bf227b87989a44282 Author: Harald Welte <laforge(a)gnumonks.org> Date: Wed Apr 20 10:39:00 2016 +0200 auth_core: Add osmo_auth_3g_from_2g() to compute CK+IK from Kc This function performs the C5+C4 conversion to derive UMTS key material from a 2G-only subscriber. ----------------------------------------------------------------------- Summary of changes: src/gsm/milenage/aes_i.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

1 0

osmo-bts.git branch master updated. 0.4.0-140-ged49444
by gitosis＠osmocom.org 29 Apr '16

29 Apr '16

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 BTS-side code (Abis, scheduling, ...)". The branch, master has been updated via ed494443cc1e9732b43ef99cccf187d17ac931ef (commit) from b61850248adbf717eb323d9ce7a17a817c302544 (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/osmo-bts/commit/?id=ed494443cc1e9732b43ef99cccf187d… commit ed494443cc1e9732b43ef99cccf187d17ac931ef Author: Max <msuraev(a)sysmocom.de> Date: Thu Apr 21 18:55:09 2016 +0200 Ensure TRX invariant There is implicit invariant in trx_phy_instance() which is actively used by various hw-specific implementations to get TRX's phy instance. Let's make sure there's explicit assertion for this because there's been segfaults in the past related to it. ----------------------------------------------------------------------- Summary of changes: include/osmo-bts/phy_link.h | 1 + 1 file changed, 1 insertion(+) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

1 0

openggsn.git branch master updated. 0.92-11-gf89dc4e
by gitosis＠osmocom.org 29 Apr '16

29 Apr '16

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 "The OpenGGSN project". The branch, master has been updated via f89dc4e127eea6addea6a7b45eb96da8c1053ba4 (commit) from b29ff1da554a2654cc593ea243e29cd7883c92da (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/openggsn/commit/?id=f89dc4e127eea6addea6a7b45eb96da… commit f89dc4e127eea6addea6a7b45eb96da8c1053ba4 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Mon Apr 25 13:00:10 2016 +0200 queue_new(): fix NULL dereference on allocation failure Coverity complains about a 'Dereference before null check' on *queue. So, push the NULL check further up. Though I doubt that 'return EOF' is the proper way to handle allocation failure, this patch is only about the NULL dereference. Fixes: CID#57918 ----------------------------------------------------------------------- Summary of changes: gtp/queue.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) hooks/post-receive -- The OpenGGSN project

1 0

libosmo-abis.git branch laforge/pending updated. 0.3.2-10-g9ed7ca5
by gitosis＠osmocom.org 29 Apr '16

29 Apr '16

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

1 0

openbsc.git branch master updated. 0.15.0-241-g35697b9
by gitosis＠osmocom.org 29 Apr '16

29 Apr '16

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 "The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)". The branch, master has been updated via 35697b9a109f08791c00dbb1a8dfaaaff29a8a80 (commit) via 299a9994656e97defea85689467e61ba34e8577e (commit) from e01f5050efbc3828defa2df9b789624854297663 (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/openbsc/commit/?id=35697b9a109f08791c00dbb1a8dfaaaf… commit 35697b9a109f08791c00dbb1a8dfaaaff29a8a80 Author: Max <msuraev(a)sysmocom.de> Date: Fri Apr 29 12:51:31 2016 +0200 Adjust si2quater ranges Change ranges of arguments for si2quater neighbor lists to proper values according to 3GPP spec. http://cgit.osmocom.org/openbsc/commit/?id=299a9994656e97defea85689467e61ba… commit 299a9994656e97defea85689467e61ba34e8577e Author: Max <msuraev(a)sysmocom.de> Date: Thu Apr 28 17:51:15 2016 +0200 Fix comment typo ----------------------------------------------------------------------- Summary of changes: openbsc/src/libbsc/bsc_vty.c | 11 ++++++----- openbsc/src/libbsc/system_information.c | 2 +- 2 files changed, 7 insertions(+), 6 deletions(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

libosmo-abis.git branch master updated. 0.3.2-7-g8c119f7
by gitosis＠osmocom.org 29 Apr '16

29 Apr '16

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, master has been updated via 8c119f7a0510b75e7fa1b96a37f2a6650e13824f (commit) via 80f7c0465fd244c26b037aaee92458c8dce86c6e (commit) via e54d7bcef534461f794f98fa186f8afd8f8c318d (commit) from d8026ec1b7be7922fd1c3122d2407a783cdab163 (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=8c119f7a0510b75e7fa1b96a37f… commit 8c119f7a0510b75e7fa1b96a37f2a6650e13824f Author: Max <msuraev(a)sysmocom.de> Date: Fri Apr 29 12:39:35 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=80f7c0465fd244c26b037aaee92… commit 80f7c0465fd244c26b037aaee92458c8dce86c6e Author: Max <msuraev(a)sysmocom.de> Date: Fri Apr 29 12:39:34 2016 +0200 Fix RTCP port allocation Force use of RTCP port adjacend to random RTP port, if random RTP port is used. Before this patch, port 0 could be selected for RTCP. http://cgit.osmocom.org/libosmo-abis/commit/?id=e54d7bcef534461f794f98fa186… commit e54d7bcef534461f794f98fa186f8afd8f8c318d Author: Max <msuraev(a)sysmocom.de> Date: Fri Apr 29 12:39:33 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: include/osmocom/trau/osmo_ortp.h | 1 + src/trau/osmo_ortp.c | 24 ++++++++++++++++++------ 2 files changed, 19 insertions(+), 6 deletions(-) hooks/post-receive -- Osmocom A-bis protcol interface library

1 0

libosmo-abis.git branch max/tmp updated. 0.3.2-7-g620251c
by gitosis＠osmocom.org 29 Apr '16

29 Apr '16

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=620251cdc3160b647cb7433a700… commit 620251cdc3160b647cb7433a7001d54f0ce7fece Author: Max <msuraev(a)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=80f3a0bc24ff22603012df79131… commit 80f3a0bc24ff22603012df791315b057c9e73c22 Author: Max <msuraev(a)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=d2313ad4103a4850f4976a41433… commit d2313ad4103a4850f4976a41433d46f4c0c4ade6 Author: Max <msuraev(a)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 -- Osmocom A-bis protcol interface library

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-commitlog April 2016