- osmocom-commitlog - lists.osmocom.org

gr-osmosdr.git branch master updated. v0.1.4-31-gb3fdf5b
by gitosis＠osmocom.org 27 May '15

27 May '15

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 "GNU Radio block for interfacing with various radio hardware". The branch, master has been updated via b3fdf5b83dc79575405f524df889d92908fecc72 (commit) via 594391982845b4ac0e4e48bbb91b4b85552f2af6 (commit) from 44c223cb5d473a760877e8c8b2d58e2638173192 (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/gr-osmosdr/commit/?id=b3fdf5b83dc79575405f524df889d… commit b3fdf5b83dc79575405f524df889d92908fecc72 Author: Marcus Müller <Marcus.Mueller(a)ettus.com> Date: Thu May 21 23:46:58 2015 -0700 Fix config error with CMake version 2.8.7 Replace find_package(SoapySDR CONFIG) with find_package(SoapySDR NO_MODULE), which has an identical effect but is supported by CMake 2.8.7 on Ubuntu 12.10 http://cgit.osmocom.org/gr-osmosdr/commit/?id=594391982845b4ac0e4e48bbb91b4… commit 594391982845b4ac0e4e48bbb91b4b85552f2af6 Author: Dimitri Stolnikov <horiz0n(a)gmx.net> Date: Wed May 27 23:55:00 2015 +0200 hackrf: introduce bias=0|1 and bias_tx=0|1 parameters ... to support antenna/phantom power via a new device argument "bias" (to match Airspy's existing bias power syntax). 0=disable and 1=enable. I also added a device argument to control bias power at transmit time. I named this option differently - "bias_tx" - to avoid accidentally enabling bias power in transmit mode when an LNA may be attached in an input amplifier configuration. Original patch provided by Brad Hein ----------------------------------------------------------------------- Summary of changes: CMakeLists.txt | 2 +- grc/gen_osmosdr_blocks.py | 2 +- lib/hackrf/hackrf_sink_c.cc | 18 ++++++++++++++++++ lib/hackrf/hackrf_source_c.cc | 18 ++++++++++++++++++ 4 files changed, 38 insertions(+), 2 deletions(-) hooks/post-receive -- GNU Radio block for interfacing with various radio hardware

1 0

openbsc.git branch fairwaves/rebase-no-queue updated. 0.14.0-82-g90459a0
by gitosis＠osmocom.org 27 May '15

27 May '15

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, fairwaves/rebase-no-queue has been updated via 90459a0507b7b0fc66a7c764c48c8f244ce66989 (commit) from ade03887bbfee19b970dcaed1220cc3a19867eaf (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=90459a0507b7b0fc66a7c764c48c8f24… commit 90459a0507b7b0fc66a7c764c48c8f244ce66989 Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com> Date: Sun May 17 20:52:26 2015 -0400 libmsc: Update 'max_power_red' VTY command. Changes: * Apply change even if the supplied value is odd, just warn that it is rounded. * Apply change even if the supplied value is higher than the 24dB maximum suggested by the standard, just warn about this. * Apply change to the BTS over OML immediately. ----------------------------------------------------------------------- Summary of changes: openbsc/src/libbsc/bsc_vty.c | 33 ++++++++++++++++++++++++--------- 1 file changed, 24 insertions(+), 9 deletions(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

openbsc.git branch fairwaves/rebase-no-queue updated. 0.14.0-81-gade0388
by gitosis＠osmocom.org 27 May '15

27 May '15

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, fairwaves/rebase-no-queue has been updated via ade03887bbfee19b970dcaed1220cc3a19867eaf (commit) from d38e96df2a94c74304540b9cd6ec6a2d5f95f77e (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=ade03887bbfee19b970dcaed1220cc3a… commit ade03887bbfee19b970dcaed1220cc3a19867eaf Author: Ivan Kluchnikov <kluchnikovi(a)gmail.com> Date: Wed May 27 16:15:37 2015 +0300 debian: build only osmo-nitb package - enable smpp support - disable the gbproxy test (failing) ----------------------------------------------------------------------- Summary of changes: debian/control | 88 ++-------------------------------------------- debian/rules | 8 +---- openbsc/tests/testsuite.at | 6 ---- 3 files changed, 3 insertions(+), 99 deletions(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

osmo-bts.git branch fairwaves/debian updated. 0.3.0-255-g6fc4521
by gitosis＠osmocom.org 27 May '15

27 May '15

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, fairwaves/debian has been updated discards 28a0d6e6e342e1e882ca0930c80daff7081ee18d (commit) discards ce8fee2baa964dcb1b42b2f9ad0e1080eb6aabb4 (commit) discards 0de292473551733229ac2947dc7ab72d6e2038bf (commit) via 6fc45218417a738a2e25da8f25b1d43c84c39e31 (commit) via 16c55999ca4d3fd6dde57a02297b301b6b7f4b27 (commit) via 6fe1aa9b302c637ff250a48240c1cba8ff888ec7 (commit) via 90b4e07e425198bbe651461c0fb259f7fecf33dd (commit) via 209e33a8fb437b1ae388e4e96ec02cc20044e849 (commit) via e510c8486082c9434b981358866f93878c0f7258 (commit) via 9b7e7f76220410be755d27c05486ee3ddfc49bb8 (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 (28a0d6e6e342e1e882ca0930c80daff7081ee18d) \ N -- N -- N (6fc45218417a738a2e25da8f25b1d43c84c39e31) 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/osmo-bts/commit/?id=6fc45218417a738a2e25da8f25b1d43… commit 6fc45218417a738a2e25da8f25b1d43c84c39e31 Author: Ivan Kluchnikov <kluchnikovi(a)gmail.com> Date: Tue Sep 23 14:34:02 2014 +0400 debian: Add gsm_data_shared.h file to make packaging possible http://cgit.osmocom.org/osmo-bts/commit/?id=16c55999ca4d3fd6dde57a02297b301… commit 16c55999ca4d3fd6dde57a02297b301b6b7f4b27 Author: Ivan Kluchnikov <kluchnikovi(a)gmail.com> Date: Tue Sep 23 13:49:09 2014 +0400 debian: Add debian directory to ease building packages http://cgit.osmocom.org/osmo-bts/commit/?id=6fe1aa9b302c637ff250a48240c1cba… commit 6fe1aa9b302c637ff250a48240c1cba8ff888ec7 Author: Ivan Kluchnikov <kluchnikovi(a)gmail.com> Date: Tue Sep 23 13:40:11 2014 +0400 debian: Add gsm_data_shared.c file to make packaging possible ----------------------------------------------------------------------- Summary of changes: src/common/abis.c | 1 + src/common/oml.c | 2 +- src/osmo-bts-trx/gsm0503_coding.c | 322 +++++++++++++++++++------------------- src/osmo-bts-trx/gsm0503_coding.h | 37 ++++- src/osmo-bts-trx/l1_if.c | 33 ++-- src/osmo-bts-trx/l1_if.h | 6 +- src/osmo-bts-trx/scheduler.c | 78 +++++---- tests/bursts/bursts_test.c | 39 +++-- tests/bursts/bursts_test.ok | 20 +++ 9 files changed, 327 insertions(+), 211 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

1 0

osmo-pcu.git branch jerlbeck/wip/ms-struct updated. 0.2-439-gc299cee
by gitosis＠osmocom.org 27 May '15

27 May '15

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 "UNNAMED PROJECT". The branch, jerlbeck/wip/ms-struct has been updated discards 20296a48676094a09c7928006e62e890c2e69e0f (commit) discards 87e6ed022df45b70d93c96581cc1c99b76a80718 (commit) discards 6e3311b641b51cb4cc790f2e488e45602724ce36 (commit) discards 7044acabf5ac371a4e80bb1fc81650b36187deaa (commit) discards 7e64d5f11482efb55766ea1696e799fde6b66b2b (commit) discards 95abc21ff352cff1c57453262b998e32b8ea7afd (commit) discards 50b6e02a859561d2044a5e6bc20af2f11f6ebaad (commit) discards 8a26db1dd366a540288cec634f6a02afc851fb3e (commit) discards a12e11c98d30f075c7e2f33cc4400c34d446f541 (commit) discards f0045d04d3cd03579005231b7dcbbac3cac3b83b (commit) discards 2ee112c2e134146c501601e0faf01014393bd7b7 (commit) via c299cee15cabb2a8c2ad7eb54da182f2b73d3f16 (commit) via aa9c1199e40d19c2f65dfcb6d3239483b2dbc2bf (commit) via 1c96d98d9c392f60e457d3dac310e5826489c50e (commit) via d4b882dd013c6a2069995a7cb89eecde283d92e1 (commit) via 1c674ff4826c18741acf685c0073236e2f431fb6 (commit) via 0ef422fe0307183b6281aca77074827cb61f2024 (commit) via 24ebf9022f7d76b00771b32c9557a50106329ba3 (commit) via 69381940f40a2d42f75e060e79d63feed54ff609 (commit) via 9a2845d491b088cb9e1962ba6dc8af5a4e279401 (commit) via 0e50ce614569b9ae7bcc6e7becc4aeec46e8369d (commit) via 767193e20b4172dfb0e76ec63444115dc5ae8806 (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 (20296a48676094a09c7928006e62e890c2e69e0f) \ N -- N -- N (c299cee15cabb2a8c2ad7eb54da182f2b73d3f16) 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/osmo-pcu/commit/?id=c299cee15cabb2a8c2ad7eb54da182f… commit c299cee15cabb2a8c2ad7eb54da182f2b73d3f16 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Fri May 22 18:02:51 2015 +0200 tbf: Remove TimingAdvance storage Currently the TA storage stores up to 30 TLLI->TA mappings, if more entries are created the oldest one is dropped. In theory this can lead to missing TA information if many MS are present. This commit removes the TimingAdvance class completely, since the TA value is now stored in the GprsMs objects. Note that the GprsMs objects are currently not kept after the TBFs have detached from them, so the TA values are now kept for a shorter time than before. Ticket: #1674 Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=aa9c1199e40d19c2f65dfcb6d323948… commit aa9c1199e40d19c2f65dfcb6d3239483b2dbc2bf Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Fri May 22 17:48:04 2015 +0200 tbf: Store the timing advance (TA) value in the GprsMs object The TA value rather relates to an MS and not to a single TBF. So all TBFs share the same TA value. Currently the TA value is stored per TBF and eventually copied from an old TBF to a new one. It is in general only passed with an RACH request when the TLLI and thus the MS is not yet known. This commit adds a TA member to the GprsMs class and uses that one when the TBF is associated to an MS object. Since the TBF is not always associated with an MS object (after RACH or when it has been replaced by another TBF), the TA value is still stored in each TBF and that value is used as long as no MS object is being associated. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=1c96d98d9c392f60e457d3dac310e58… commit 1c96d98d9c392f60e457d3dac310e5826489c50e Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Wed May 27 13:03:15 2015 +0200 tbf/test: Add tests for single and two phase access These tests cover the message exchange from receiving from the first RACH request to the first data block when establishing an uplink TBF. This will be used to check, whether TA and other values are passed to an MS object correctly. In addition, the RX RACH log message in rcv_rach is extended to contain the single block fn. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=d4b882dd013c6a2069995a7cb89eecd… commit d4b882dd013c6a2069995a7cb89eecde283d92e1 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Fri May 22 15:47:55 2015 +0200 tbf: Remove TBF chaining (m_new_tbf and m_old_tbf) Currently a new TBF is chained to an existing older one, either of the other direction (active or releasing) or of the same direction (releasing). This does not work properly work if and uplink and a downlink TBF are being established at the same time while an old TBF is being released. In that case, one of them is thrown away and the pending procedure is cancelled. The chaining is no longer necessary since the GprsMs objects have been introduced which keep track of the active TBFs. This commit removes the TBF members m_new_tbf and m_old_tbf and the related methods and code paths. Note that a new TBF can replace an older TBF entry of the same direction within an MS object when it is associated with an MS (e.g. by TLLI or because it is assigned via another, already associated TBF). In that case, the old TBF is no longer associated with an MS object. Ticket: #1674 Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=1c674ff4826c18741acf685c0073236… commit 1c674ff4826c18741acf685c0073236e2f431fb6 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Fri May 22 15:40:08 2015 +0200 tbf/test: Attach TLLI and MS objects to TBFs Currently the DL TBF's TLLI are not set. This will have to change in the future, when the m_new_tbf chaining is replaced by the usage of MS object to group TBFs. This commit just calls update_ms() on newly created TBFs. This changes many of the lines written to stderr due to the TLLI change, but doesn't change other aspects or messages beside creating and destroying MS objects. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=0ef422fe0307183b6281aca77074827… commit 0ef422fe0307183b6281aca77074827cb61f2024 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Thu May 21 11:10:15 2015 +0200 tbf: Remove IMSI handling from trigger_dl_ass Currently the BTS::trigger_dl_ass() method assigns the IMSI to the MS object. This should be (and is already) done earlier where the MS object is retrieved/created. This commit removes the corresponding code along with the 'imsi' parameter from trigger_dl_ass. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=24ebf9022f7d76b00771b32c9557a50… commit 24ebf9022f7d76b00771b32c9557a50106329ba3 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Thu May 21 11:07:53 2015 +0200 ms: Use the IMSI to retrieve the MS object This commit extends get_ms() to really compare the IMSI if it has been given. Note that the MS object list will be traversed only once and that the first entry with a matching TLLI or a matching IMSI will be returned. Thus there is no precedence. Ticket: #1674 Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=69381940f40a2d42f75e060e79d63fe… commit 69381940f40a2d42f75e060e79d63feed54ff609 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Thu May 21 11:07:16 2015 +0200 tbf: Move IMSI to MS object Currently the IMSI is stored in the TBFs. Since it directly refers to an MS, it should rather be stored in an MS object. This patch move the m_imsi field from gprs_rlcmac_tbf to GprsMs, changes gprs_rlcmac_tbf::imsi() to get the IMSI from the associated MS object, and adds getter and setter to GprsMs. Note that the assign_imsi() method is now called set_imsi() for consistency within the GprsMs class. Ticket: #1674 Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=9a2845d491b088cb9e1962ba6dc8af5… commit 9a2845d491b088cb9e1962ba6dc8af5a4e279401 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Thu May 21 12:06:58 2015 +0200 tbf/test: Fix IMSI creation Currently the generated IMSI contains blanks due to a missing '0' flag in the corresponding snprintf statement. In addition, the buffer is effectively limited to 15 bytes which is shorter than the generated character sequence, such that the last character of the IMSI is removed. This patch fixes both issues. Since snprintf itself will add a terminating \0 character, the whole buffer can be passed to snprintf. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=0e50ce614569b9ae7bcc6e7becc4aee… commit 0e50ce614569b9ae7bcc6e7becc4aeec46e8369d Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Thu May 21 16:58:22 2015 +0200 tbf: Always call set_tlli/confirm_tlli in update_ms Currently the m_tlli member in GprsMs is set by the constructor, circumventing the TLLI confirmation mechanism. This commit replaces the get_or_create_ms() method by a create_ms() method which takes the TLLI and the direction (UL or DL) as parameters to select either set_tlli() or confirm_tlli(). The MS object is instantiated with TLLI = 0, and therefore GprsMs::tlli() is extended to return the DL TLLI if both of the other TLLI are not set. Note that create_ms() will not check whether an MS object with a matching TLLI is already stored in the list, so it should only be called after a corresponding get_ms() in general. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=767193e20b4172dfb0e76ec63444115… commit 767193e20b4172dfb0e76ec63444115dc5ae8806 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Wed May 20 12:06:46 2015 +0200 tbf: Remove the TLLI from the TBFs Currently the TLLI is stored in each TBF. Since each MS is now represented by a GprsMs object which takes care of TLLI updating, and each TBF that has been associated with an TLLI also contains a reference to a GprsMs object, per TBF TLLI handling is no longer needed. Keeping all TBF m_tlli members up to date is complex and doesn't currently work correctly in all circumstances. This commit removes m_tlli and related members from the TBF class and the tbf_by_tlli functions from the BTS class. Ticket: #1674 Sponsored-by: On-Waves ehf ----------------------------------------------------------------------- Summary of changes: src/bts.h | 1 - 1 file changed, 1 deletion(-) hooks/post-receive -- UNNAMED PROJECT

1 0

osmo-pcu.git branch jerlbeck/wip/ms-struct updated. 0.2-439-g20296a4
by gitosis＠osmocom.org 27 May '15

27 May '15

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 "UNNAMED PROJECT". The branch, jerlbeck/wip/ms-struct has been updated discards 35558a89aa5d3f8eb8c805d2c8412f409e090b88 (commit) discards e4947f1bb86a251dce68cb695d9fca16adff6bf4 (commit) discards 89cde650e249e9791455a3752caa5af2f2923ce8 (commit) via 20296a48676094a09c7928006e62e890c2e69e0f (commit) via 87e6ed022df45b70d93c96581cc1c99b76a80718 (commit) via 6e3311b641b51cb4cc790f2e488e45602724ce36 (commit) via 7044acabf5ac371a4e80bb1fc81650b36187deaa (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 (35558a89aa5d3f8eb8c805d2c8412f409e090b88) \ N -- N -- N (20296a48676094a09c7928006e62e890c2e69e0f) 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/osmo-pcu/commit/?id=20296a48676094a09c7928006e62e89… commit 20296a48676094a09c7928006e62e890c2e69e0f Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Fri May 22 18:02:51 2015 +0200 tbf: Remove TimingAdvance storage Currently the TA storage stores up to 30 TLLI->TA mappings, if more entries are created the oldest one is dropped. In theory this can lead to missing TA information if many MS are present. This commit removes the TimingAdvance class completely, since the TA value is now stored in the GprsMs objects. Note that the GprsMs objects are currently not kept after the TBFs have detached from them, so the TA values are now kept for a shorter time than before. Ticket: #1674 Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=87e6ed022df45b70d93c96581cc1c99… commit 87e6ed022df45b70d93c96581cc1c99b76a80718 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Fri May 22 17:48:04 2015 +0200 tbf: Store the timing advance (TA) value in the GprsMs object The TA value rather relates to an MS and not to a single TBF. So all TBFs share the same TA value. Currently the TA value is stored per TBF and eventually copied from an old TBF to a new one. It is in general only passed with an RACH request when the TLLI and thus the MS is not yet known. This commit adds a TA member to the GprsMs class and uses that one when the TBF is associated to an MS object. Since the TBF is not always associated with an MS object (after RACH or when it has been replaced by another TBF), the TA value is still stored in each TBF and that value is used as long as no MS object is being associated. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=6e3311b641b51cb4cc790f2e488e456… commit 6e3311b641b51cb4cc790f2e488e45602724ce36 Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Wed May 27 13:03:15 2015 +0200 tbf/test: Add tests for single and two phase access These tests cover the message exchange from receiving from the first RACH request to the first data block when establishing an uplink TBF. This will be used to check, whether TA and other values are passed to an MS object correctly. In addition, the RX RACH log message in rcv_rach is extended to contain the single block fn. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/osmo-pcu/commit/?id=7044acabf5ac371a4e80bb1fc81650b… commit 7044acabf5ac371a4e80bb1fc81650b36187deaa Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de> Date: Fri May 22 15:47:55 2015 +0200 tbf: Remove TBF chaining (m_new_tbf and m_old_tbf) Currently a new TBF is chained to an existing older one, either of the other direction (active or releasing) or of the same direction (releasing). This does not work properly work if and uplink and a downlink TBF are being established at the same time while an old TBF is being released. In that case, one of them is thrown away and the pending procedure is cancelled. The chaining is no longer necessary since the GprsMs objects have been introduced which keep track of the active TBFs. This commit removes the TBF members m_new_tbf and m_old_tbf and the related methods and code paths. Note that a new TBF can replace an older TBF entry of the same direction within an MS object when it is associated with an MS (e.g. by TLLI or because it is assigned via another, already associated TBF). In that case, the old TBF is no longer associated with an MS object. Ticket: #1674 Sponsored-by: On-Waves ehf ----------------------------------------------------------------------- Summary of changes: src/bts.cpp | 7 +-- src/tbf.cpp | 3 ++ tests/tbf/TbfTest.cpp | 144 ++++++++++++++++++++++++++++++++++++++++++++++++++ tests/tbf/TbfTest.err | 98 ++++++++++++++++++++++++++++++++++ tests/tbf/TbfTest.ok | 4 ++ 5 files changed, 253 insertions(+), 3 deletions(-) hooks/post-receive -- UNNAMED PROJECT

1 0

openbsc.git branch fairwaves/rebase-no-queue created. 0.14.0-80-gd38e96d
by gitosis＠osmocom.org 26 May '15

26 May '15

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, fairwaves/rebase-no-queue has been created at d38e96df2a94c74304540b9cd6ec6a2d5f95f77e (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/openbsc/commit/?id=d38e96df2a94c74304540b9cd6ec6a2d… commit d38e96df2a94c74304540b9cd6ec6a2d5f95f77e Author: Ivan Kluchnikov <kluchnikovi(a)gmail.com> Date: Tue May 26 13:36:58 2015 +0300 gsm_04_08: Use osmo_assert for transt->conn and conn only in case of paging succeeded setup_trig_pag_evt function can receive parameter conn = NULL, if T3113 expires. http://cgit.osmocom.org/openbsc/commit/?id=8d0f77c8ffe328cd80b6f01e721220cd… commit 8d0f77c8ffe328cd80b6f01e721220cd6867a98d Author: Andreas Eversberg <jolly(a)eversberg.eu> Date: Sun Mar 31 12:01:25 2013 +0200 osmo-nitb support for codec negotiation The caller's most preferred codec is selected out of the union of codecs, which both parties support. Since codec negotiation is done automatically, there is no need to define codec for TCH/F and TCH/H via VTY anymore. Conflicts: openbsc/src/libmsc/gsm_04_08.c openbsc/src/libmsc/vty_interface_layer3.c http://cgit.osmocom.org/openbsc/commit/?id=4e3a2670550ef0cabd8e682395ea3859… commit 4e3a2670550ef0cabd8e682395ea385967824049 Author: Andreas Eversberg <jolly(a)eversberg.eu> Date: Sun Mar 31 11:57:38 2013 +0200 If requested TCH/H channel is not available, try assigning TCH/F If MNCC application requests a half rate channel, the channel might not be available, due to different cell configuration, so the full rate channel is used instead. http://cgit.osmocom.org/openbsc/commit/?id=3b1cd6dd8152dff1e3e4e2045d359b7d… commit 3b1cd6dd8152dff1e3e4e2045d359b7d1bb0495e Author: Andreas Eversberg <jolly(a)eversberg.eu> Date: Sun Mar 31 11:44:34 2013 +0200 Fix: If paging for half rate was requested, use hr, if supported by MS http://cgit.osmocom.org/openbsc/commit/?id=1a3dd31c3b3dcf927f0f600888d765e9… commit 1a3dd31c3b3dcf927f0f600888d765e95c1a17c3 Author: Andreas Eversberg <jolly(a)eversberg.eu> Date: Sun Jan 19 11:47:44 2014 +0100 Add full AMR multirate IE support with VTY config for MS and BTS side Conflicts: openbsc/include/openbsc/gsm_data_shared.h openbsc/src/libbsc/bsc_vty.c openbsc/src/libbsc/chan_alloc.c http://cgit.osmocom.org/openbsc/commit/?id=dfd8d0cde07a3d08e93bc8b6fa17d0f5… commit dfd8d0cde07a3d08e93bc8b6fa17d0f561549b5b Author: Andreas Eversberg <jolly(a)eversberg.eu> Date: Thu Mar 14 09:41:18 2013 +0100 Drop bad speech frames rather than forwarding them via RTP Some RTP endpoints may not check for bad frame indications, so a frame that is marked as bad may be still forwarded, which creates anoying noise. This patch drops these frames. It depends on the other RTP endpoint how dropped frames are handled. (insert silence, extrapolate speech...) http://cgit.osmocom.org/openbsc/commit/?id=f4d336e2c4208c10c107b23826df95c2… commit f4d336e2c4208c10c107b23826df95c27d0661ac Author: Andreas Eversberg <jolly(a)eversberg.eu> Date: Mon Mar 11 08:20:48 2013 +0100 Add check for non existing lchan at tch_frame_down() Traffic cannot sent to BTS, if there is (currently) no logical channel associated with the transaction. This happens, if TCH traffic is received from upper layer, but there is no lchan available before completing immediate assignment, handover or assignment process. http://cgit.osmocom.org/openbsc/commit/?id=ce7437e27c3da61dc5bd112285295440… commit ce7437e27c3da61dc5bd112285295440ada45ea6 Author: Andreas Eversberg <jolly(a)eversberg.eu> Date: Sun Mar 10 11:50:19 2013 +0100 Send RADIO LINK TIMEOUT value via OML attribute to BTS The same radio link timeout value is used for BTS and MS side. http://cgit.osmocom.org/openbsc/commit/?id=b402dad7f1451b88154f777b5aead4d5… commit b402dad7f1451b88154f777b5aead4d5f5c7621e Author: Andreas Eversberg <jolly(a)eversberg.eu> Date: Sun Mar 10 11:49:35 2013 +0100 Add option to set RADIO LINK TIMEOUT value via VTY http://cgit.osmocom.org/openbsc/commit/?id=39494b875165848fa16d3e7b328677dd… commit 39494b875165848fa16d3e7b328677dd8d26163b Author: Andreas Eversberg <jolly(a)eversberg.eu> Date: Fri Feb 17 15:20:59 2012 +0100 Allow dynamic RTP payload types between application and MNCC interface Since EFR/AMR/HR codecs use dynamic RTP payload, the payload type can be set. If it is set, the frame type must be set also, so OpenBSC knows what frame types are received via RTP. This modification only affects traffic beween application and MNCC interface, not the RTP traffic between OpenBSC and BTS. Conflicts: openbsc/src/libtrau/rtp_proxy.c http://cgit.osmocom.org/openbsc/commit/?id=bc1aaacf7412e7a042e28be75139a72d… commit bc1aaacf7412e7a042e28be75139a72de3324c93 Author: Andreas Eversberg <jolly(a)eversberg.eu> Date: Mon Jan 16 09:29:28 2012 +0100 Add traffic forwarding via RTP to remote application Instead of forwarding traffic through MNCC interface, traffic can be forwarded to a given RTP peer directly. A special MNCC message is used to control the peer's destination. The traffic can still be forwarded through MNCC interface when this special MNCC message is not used. It also works with E1 based BTSs. In conjunction with LCR's "rtp-bridge" feature, the RTP traffic can be directly exchanged with a remote SIP endpoint, so that the traffic is not forwarded by LCR itself. This way the performance of handling traffic only depends on OpenBSC and the remote SIP endpoint. Also the traffic is exchanged with the SIP endpoint without transcoding, to have maximum performance. Increment MNCC version to 5. Conflicts: openbsc/tests/gbproxy/gbproxy_test.c ----------------------------------------------------------------------- hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

openbsc.git branch fairwaves/no-queue created. 0.14.0-91-g34522ae
by gitosis＠osmocom.org 26 May '15

26 May '15

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, fairwaves/no-queue has been created at 34522ae3d9c1dca38bb2d2849a33b2524d97fda3 (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/openbsc/commit/?id=34522ae3d9c1dca38bb2d2849a33b252… commit 34522ae3d9c1dca38bb2d2849a33b2524d97fda3 Author: Ivan Kluchnikov <kluchnikovi(a)gmail.com> Date: Tue May 26 13:36:58 2015 +0300 gsm_04_08: Use osmo_assert for transt->conn and conn only in case of paging succeeded setup_trig_pag_evt function can receive parameter conn = NULL, if T3113 expires. ----------------------------------------------------------------------- hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

1 0

libosmocore.git branch master updated. 0.8.0-40-g91ff17c
by gitosis＠osmocom.org 25 May '15

25 May '15

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, master has been updated via 91ff17c9ef7dd4a29bb13d6b9995100ffc65b72a (commit) from a6ea50c4ff58d8389b40ca6169c3ca826500abf2 (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/libosmocore/commit/?id=91ff17c9ef7dd4a29bb13d6b9995… commit 91ff17c9ef7dd4a29bb13d6b9995100ffc65b72a Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com> Date: Tue May 26 00:11:37 2015 +0800 osmo-auc-gen: '-a' is already the algorithm. Fix the help ----------------------------------------------------------------------- Summary of changes: utils/osmo-auc-gen.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

1 0

libosmocore.git branch master updated. 0.8.0-39-ga6ea50c
by gitosis＠osmocom.org 25 May '15

25 May '15

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, master has been updated via a6ea50c4ff58d8389b40ca6169c3ca826500abf2 (commit) from 908085ccbc6383e95f2c80134bcaf2e9816b7187 (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/libosmocore/commit/?id=a6ea50c4ff58d8389b40ca6169c3… commit a6ea50c4ff58d8389b40ca6169c3ca826500abf2 Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com> Date: Mon May 25 14:17:29 2015 +0200 debian: New development release with APN changes for the SGSN ----------------------------------------------------------------------- Summary of changes: debian/changelog | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

1 0