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, achemeris/uhd-args has been updated
discards 66e74ffe931e0cabcc99087a89259faf398e6ade (commit)
discards f0efdebbd7a2193c4d756857f615d778156e8091 (commit)
via 743cf16febbc8062298eb29b49f317dc2cf150cc (commit)
via 63cd7705a9bf04e33f33fb26f25ef23a23a1e9a6 (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 (66e74ffe931e0cabcc99087a89259faf398e6ade)
\
N -- N -- N (743cf16febbc8062298eb29b49f317dc2cf150cc)
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-trx/commit/?id=743cf16febbc8062298eb29b49f317d…
commit 743cf16febbc8062298eb29b49f317dc2cf150cc
Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com>
Date: Tue Apr 28 12:20:49 2015 -0400
A hack to pass all dev.args to UHD.
-----------------------------------------------------------------------
Summary of changes:
hooks/post-receive
--
OpenBTS' transceiver retro-fit
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/master has been updated
via 63cd7705a9bf04e33f33fb26f25ef23a23a1e9a6 (commit)
from 00cc772f90b274bb75232f29b20c31d5b552cfde (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-trx/commit/?id=63cd7705a9bf04e33f33fb26f25ef23…
commit 63cd7705a9bf04e33f33fb26f25ef23a23a1e9a6
Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com>
Date: Tue Apr 28 13:26:07 2015 -0400
uhd: Update UmTRX specific code to work with PA Tx gain.
-----------------------------------------------------------------------
Summary of changes:
Transceiver52M/UHDDevice.cpp | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
hooks/post-receive
--
OpenBTS' transceiver retro-fit
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, achemeris/uhd-args has been updated
discards 79a5adf366a456bab5d7866f5960beaa22925c4b (commit)
discards db203c0008535bbd0649925a02225b13ba191c3f (commit)
discards c107d930f9269a1b5267bce0b7112cf332104534 (commit)
via 66e74ffe931e0cabcc99087a89259faf398e6ade (commit)
via f0efdebbd7a2193c4d756857f615d778156e8091 (commit)
via 00cc772f90b274bb75232f29b20c31d5b552cfde (commit)
via 34333e8919d02fd1e4177917dd425a9ee6e615e1 (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 (79a5adf366a456bab5d7866f5960beaa22925c4b)
\
N -- N -- N (66e74ffe931e0cabcc99087a89259faf398e6ade)
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-trx/commit/?id=66e74ffe931e0cabcc99087a89259fa…
commit 66e74ffe931e0cabcc99087a89259faf398e6ade
Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com>
Date: Tue Apr 28 13:26:07 2015 -0400
uhd: Update UmTRX specific code to work with PA Tx gain.
http://cgit.osmocom.org/osmo-trx/commit/?id=f0efdebbd7a2193c4d756857f615d77…
commit f0efdebbd7a2193c4d756857f615d778156e8091
Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com>
Date: Tue Apr 28 12:20:49 2015 -0400
A hack to pass all dev.args to UHD.
-----------------------------------------------------------------------
Summary of changes:
debian/rules | 3 +++
1 file changed, 3 insertions(+)
hooks/post-receive
--
OpenBTS' transceiver retro-fit
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/master has been updated
via 00cc772f90b274bb75232f29b20c31d5b552cfde (commit)
from 34333e8919d02fd1e4177917dd425a9ee6e615e1 (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-trx/commit/?id=00cc772f90b274bb75232f29b20c31d…
commit 00cc772f90b274bb75232f29b20c31d5b552cfde
Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com>
Date: Tue Apr 28 23:09:02 2015 -0400
uhd: Set RF frontend bandwidth for UmTRX to improve signal quality.
-----------------------------------------------------------------------
Summary of changes:
Transceiver52M/UHDDevice.cpp | 10 ++++++++++
1 file changed, 10 insertions(+)
hooks/post-receive
--
OpenBTS' transceiver retro-fit
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, shared/packages/testing has been updated
discards e337faa88b55d82e7ecc354c9449d286ce930903 (commit)
discards d8f45ca8052984ea23743fae67b1c6d77807718e (commit)
discards 4a2846592e716d5ffcb49d293752550c3d04684c (commit)
discards c540284eaff7d9c3a39ca66c8d5ebd16ae710300 (commit)
discards 8b27cb5ba19ee14780c95add33b63a74d2993373 (commit)
discards e3933ac46d76122dde8aa01b5efb1ba58d25442d (commit)
discards e34deab3899caf213180c1b013ce6918a748467c (commit)
discards 7265fc3348a5a03d07fe566026b175f70aa3ef94 (commit)
discards 7eafe7a018a8307dfd15606c4229415234c9fcb5 (commit)
discards 3cece9917978f05910b30ca4478532ccb3b1b9cf (commit)
discards b21c17ce674ca4a17fb7673b7c3a9f8946aef550 (commit)
discards dd01a4e37b8706f35273edda7636b9c1efa634b2 (commit)
discards 19006ea1190b6ca68acccccd19161bfdb81782f6 (commit)
discards 809d48c15e8578fd94b4fa301bd51f63f972cadd (commit)
via 1943e410ac13c22f26f8775bf9c26320b2d4a570 (commit)
via 7acddc19675b168b710547aa45efe80d4e915308 (commit)
via 457ccb8c44dff69dd3c84e3623b2e67f6011dfa7 (commit)
via 36ebb28e14576618c329ad69cb30e0556b4ab2ed (commit)
via fe32e4deaab28598fe6654059a35ed9beb173747 (commit)
via c15c61c401e6f934fbf35c0c87d0777ff857f7c6 (commit)
via 4f5b8237ec2182861fbe075f4cce56a9c7caf904 (commit)
via b100895557af0980d5910a3dc81903179dea615e (commit)
via 20de3ae17cbb61f831ca8f06a4cf7436441cfdc6 (commit)
via b448dd849a96fd1b736ee183385d7a6a9ea1863e (commit)
via 4c8e8f990a24fc5ecb24c5c21c944d8ab4dc7c1e (commit)
via d05e06989def81f886c673956da476e626a27af5 (commit)
via f7b3826f03772d57d1d1a1153c5684f7d4799b60 (commit)
via 4bd931f96d75d3e71b73a06e67f84ffdcab9caf6 (commit)
via 8cedded88c9a0c4c486f987b818ccba57e96421e (commit)
via 9ba273d365ac731a9c3ff285821062c346724390 (commit)
via 49c1a7156c7e0ced1709aee4a3d3438db60bae41 (commit)
via b927f1c3199b48becb03c0d56926c3b98d6ff5ce (commit)
via 02d8c472bdff0a085cbedd9d902f7ced29e5d712 (commit)
via e448554568fb4244a1b95e2e8666714f9498d69a (commit)
via 337343d159888886eaa68476b70dbe19db93845b (commit)
via d26b8fcbe22eb4a56c87f0114a0e826551243511 (commit)
via ec0cb7c64d5d42e8d0d599b209a3eabacfceba60 (commit)
via d6332809d8313903c65ccd28646f41b7c1aa6b99 (commit)
via c652913674ecc30f8d234878a17baa623cbacf99 (commit)
via 06a88fa0ae1f86cef0a23a1462bfef950418ea36 (commit)
via 4e8176d0c9c9a98f32cb4541b4f986de0011d4b9 (commit)
via c09f8a3b7fb94ccef41e33c32bfe2bff1ffe0e44 (commit)
via 81dbfe412c8196df443f38bf4fbea4f9897607ef (commit)
via 71857d72426c75e4bb71c3843a9eeeff53eca37d (commit)
via a0478814bc1c56a9e5648ffecd7c11671804e6ff (commit)
via 4ba947bf4b80b553a3411ec1fd29c45430bd6c40 (commit)
via c36a6d5705830a6fd6e41e684dc031db35165e04 (commit)
via 14b2cd9f321974e211f3291a6ccc2d1aaaf948d1 (commit)
via a1e6bd6768e61828823da3ba774e55b6f89559fc (commit)
via d7e04b9956bb7d579697604fff6ba67fc6b9e52d (commit)
via d04d009f473d89a426c16dd24e5a4c692caf0017 (commit)
via 4579bb1ed7464d66343d84846314ec66e6f8cccd (commit)
via 973dbaeebdbdbd8fed417cdfd169644093389d05 (commit)
via 4247cead2b77b2ad8ae2a6c1b48a450309185bb3 (commit)
via 38159428d2b1e95a2c6fa91775f7b3678aef2f1f (commit)
via 4a8b938348b9503decd2794b33a71d340fe9414f (commit)
via d6d7affa6eb9e9e158d2e0f0108ef154e24867a5 (commit)
via 0759b1b9522f0a4f8256671b9098f7bc493c3a99 (commit)
via 0ae564d9b1fcee46cd77ccc83c570376d0526c8c (commit)
via 1e28eb83c0c2f1b362114199e70b6d454fa2d08b (commit)
via b396b69cb2ac93b6e4b53c4252fe809658acd8bd (commit)
via ddc0e05604d2c004c08c23fe3c3e2e6ce9b7eabb (commit)
via 5a2484b10e8aeec3841833b79a8973cacb37bcee (commit)
via cb43a9ac4489040185addd528a3143655ea349be (commit)
via c57b5507b21d12f656ec1667a8a875485344fe8d (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 (e337faa88b55d82e7ecc354c9449d286ce930903)
\
N -- N -- N (1943e410ac13c22f26f8775bf9c26320b2d4a570)
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=1943e410ac13c22f26f8775bf9c26320…
commit 1943e410ac13c22f26f8775bf9c26320b2d4a570
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Thu Apr 23 20:26:27 2015 -0400
debian: New release with new NAT command
http://cgit.osmocom.org/openbsc/commit/?id=7acddc19675b168b710547aa45efe80d…
commit 7acddc19675b168b710547aa45efe80d4e915308
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Thu Apr 23 17:47:26 2015 -0400
debian: Build new packages
http://cgit.osmocom.org/openbsc/commit/?id=457ccb8c44dff69dd3c84e3623b2e67f…
commit 457ccb8c44dff69dd3c84e3623b2e67f6011dfa7
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Fri Oct 17 10:08:02 2014 +0200
sgsn: Do not die in _bssgp_tx_dl_ud on TLLI mismatch (TODO)
Currently an OSMO_ASSERT fails, if the message's and the mmctx's
TLLIs do not match.
This commit turns the assertion into an ERROR log message and uses
the default values for IMSI, DRX, and RA CAP instead of the MM
context values in this case.
TODO:
- find the real source for the problem
- add test cases derived from what is being described in the ticket
Ticket: OW#1322
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=36ebb28e14576618c329ad69cb30e055…
commit 36ebb28e14576618c329ad69cb30e0556b4ab2ed
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Tue Sep 30 13:53:26 2014 +0200
sgsn: Added TODOs (TODO)
TODO:
- fix and remove TODOs
- add test cases for Detach(reattach)
- add test cases for PDP context deletion (OW#1311)
- add test cases for Cancel pending timer in sgsn_mm_ctx_free
- remove this commit
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=fe32e4deaab28598fe6654059a35ed9b…
commit fe32e4deaab28598fe6654059a35ed9beb173747
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Fri Dec 19 19:11:20 2014 +0100
sgsn: Add logging to connect_timer_cb (TODO)
TODO:
- LOGLevel ?
Sponsored-by: On-Waves ehf
-----------------------------------------------------------------------
Summary of changes:
debian/changelog | 6 +-
debian/control | 14 +-
openbsc/configure.ac | 1 +
openbsc/doc/examples/osmo-bsc/osmo-bsc.cfg | 5 +
openbsc/doc/sgsn-remote-protocol.txt | 24 +-
openbsc/include/openbsc/Makefile.am | 2 +-
openbsc/include/openbsc/bsc_msg_filter.h | 107 ++++++
openbsc/include/openbsc/bsc_nat.h | 82 +----
openbsc/include/openbsc/bsc_nat_sccp.h | 7 +-
openbsc/include/openbsc/debug.h | 1 +
openbsc/include/openbsc/gprs_gsup_messages.h | 6 +-
openbsc/include/openbsc/gprs_sgsn.h | 6 +-
openbsc/include/openbsc/gsm_data.h | 1 -
openbsc/include/openbsc/gsm_subscriber.h | 19 +-
openbsc/include/openbsc/mgcp.h | 2 +
openbsc/include/openbsc/mgcp_internal.h | 2 +-
openbsc/include/openbsc/osmo_bsc.h | 5 +
openbsc/include/openbsc/osmo_msc_data.h | 4 +
openbsc/include/openbsc/sgsn.h | 14 +
openbsc/include/openbsc/signal.h | 21 +-
openbsc/include/openbsc/transaction.h | 2 +-
openbsc/src/Makefile.am | 2 +-
openbsc/src/gprs/Makefile.am | 2 +-
openbsc/src/gprs/gprs_gmm.c | 65 +++-
openbsc/src/gprs/gprs_gsup_messages.c | 11 +-
openbsc/src/gprs/gprs_sgsn.c | 21 +-
openbsc/src/gprs/sgsn_cdr.c | 254 ++++++++++++++
openbsc/src/gprs/sgsn_libgtp.c | 17 +
openbsc/src/gprs/sgsn_main.c | 1 +
openbsc/src/gprs/sgsn_vty.c | 36 ++
openbsc/src/libbsc/paging.c | 14 +-
openbsc/src/libcommon/debug.c | 5 +
openbsc/src/{libcommon => libfilter}/Makefile.am | 10 +-
openbsc/src/libfilter/bsc_msg_acc.c | 116 +++++++
.../bsc_msg_filter.c} | 190 +++++------
openbsc/src/libfilter/bsc_msg_vty.c | 140 ++++++++
openbsc/src/libmgcp/mgcp_transcode.c | 20 +-
openbsc/src/libmgcp/mgcp_vty.c | 47 +++
openbsc/src/libmsc/gsm_04_08.c | 95 ++----
openbsc/src/libmsc/gsm_04_11.c | 8 +-
openbsc/src/libmsc/gsm_subscriber.c | 199 +++--------
openbsc/src/libmsc/mncc_builtin.c | 2 +-
openbsc/src/libmsc/osmo_msc.c | 8 -
openbsc/src/libmsc/transaction.c | 7 +-
openbsc/src/libmsc/vty_interface_layer3.c | 83 +----
openbsc/src/osmo-bsc/Makefile.am | 4 +-
openbsc/src/osmo-bsc/osmo_bsc_api.c | 91 ++++-
openbsc/src/osmo-bsc/osmo_bsc_main.c | 9 +
openbsc/src/osmo-bsc/osmo_bsc_vty.c | 66 +++-
openbsc/src/osmo-bsc_nat/Makefile.am | 3 +-
openbsc/src/osmo-bsc_nat/bsc_nat.c | 31 +-
openbsc/src/osmo-bsc_nat/bsc_nat_ctrl.c | 11 +-
openbsc/src/osmo-bsc_nat/bsc_nat_filter.c | 370 ++-------------------
openbsc/src/osmo-bsc_nat/bsc_nat_utils.c | 123 +------
openbsc/src/osmo-bsc_nat/bsc_nat_vty.c | 127 +------
openbsc/src/osmo-bsc_nat/bsc_ussd.c | 20 +-
openbsc/tests/bsc-nat/Makefile.am | 8 +-
openbsc/tests/bsc-nat/bsc_nat_test.c | 59 ++--
openbsc/tests/channel/channel_test.c | 12 +-
openbsc/tests/gprs/gprs_test.c | 6 +-
openbsc/tests/mgcp/mgcp_transcoding_test.c | 2 +-
openbsc/tests/sgsn/sgsn_test.c | 6 +-
openbsc/tests/vty_test_runner.py | 28 ++
63 files changed, 1450 insertions(+), 1210 deletions(-)
create mode 100644 openbsc/include/openbsc/bsc_msg_filter.h
create mode 100644 openbsc/src/gprs/sgsn_cdr.c
copy openbsc/src/{libcommon => libfilter}/Makefile.am (52%)
create mode 100644 openbsc/src/libfilter/bsc_msg_acc.c
copy openbsc/src/{osmo-bsc_nat/bsc_nat_filter.c => libfilter/bsc_msg_filter.c} (61%)
create mode 100644 openbsc/src/libfilter/bsc_msg_vty.c
hooks/post-receive
--
The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)
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 9385d1e01bd05c7099e3e441248ce0b10a6d02e2 (commit)
from 455d34f4767df3bcd0eccdd4ac42a755c016e0ed (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=9385d1e01bd05c7099e3e441248c…
commit 9385d1e01bd05c7099e3e441248ce0b10a6d02e2
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Wed May 6 09:29:32 2015 +0200
bssgp: Fix bssgp_tx_fc_bvc parameter type
Currently large values for Bmax default MS get sliced since a uint16_t is
used as the type of the corresponding parameter of bssgp_tx_fc_bvc.
GSM 48.018, 11.3.2 which in turn refers to 11.3.5 specifies a maximum
of 6MB (0xffff * 100).
This commit changes the type to uint32_t to cover the full value
range.
Sponsored-by: On-Waves ehf
-----------------------------------------------------------------------
Summary of changes:
TODO-RELEASE | 1 +
include/osmocom/gprs/gprs_bssgp_bss.h | 2 +-
src/gb/gprs_bssgp_bss.c | 2 +-
tests/gb/gprs_bssgp_test.c | 75 +++++++++++++++++++++++++++++++++++
tests/gb/gprs_bssgp_test.ok | 4 ++
5 files changed, 82 insertions(+), 2 deletions(-)
hooks/post-receive
--
An utility library for Open Source Mobile Communications
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, zecke/features/cdr has been created
at c15c61c401e6f934fbf35c0c87d0777ff857f7c6 (commit)
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/openbsc/commit/?id=c15c61c401e6f934fbf35c0c87d0777f…
commit c15c61c401e6f934fbf35c0c87d0777ff857f7c6
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Wed May 6 17:46:08 2015 +0200
sgsn: Add VTY configuration for the CDR module
Make it possible to set a filename to use for the CDR. By
default no CDR will be generated. Forbid to set the interval
of 0 seconds as this will cause a lot of work. Add a very
basic VTY test.
http://cgit.osmocom.org/openbsc/commit/?id=4f5b8237ec2182861fbe075f4cce56a9…
commit 4f5b8237ec2182861fbe075f4cce56a9c7caf904
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Tue May 5 22:25:48 2015 +0200
sgsn: Create an initial and limited CDR module
This is consuming the new signals and allows to install several
different CDR/observing/event/audit modules in the future. For
getting the bytes in/out the code would have had to undo what the
rate counter is doing and at the same time adding a "total" to
the ratecounter didn't look like a good idea, the same went for
making it a plain counter.
Begin writing the values one by one and open/closing a new FILE
for every log messages. This is not efficient but easily deals
with external truncation/rotation of the file (no fstat for and
checking the links and size). As usual we will wait and see if
this is an issue.
Add some new members to our PDP context structure to see what it
is about.
http://cgit.osmocom.org/openbsc/commit/?id=b100895557af0980d5910a3dc8190317…
commit b100895557af0980d5910a3dc81903179dea615e
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Sat May 2 19:55:38 2015 +0200
sgsn: Add various signals consumed by CDR or other client code
http://cgit.osmocom.org/openbsc/commit/?id=20de3ae17cbb61f831ca8f06a4cf7436…
commit 20de3ae17cbb61f831ca8f06a4cf7436441cfdc6
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Tue May 5 22:52:40 2015 +0200
sgsn: Extract the MSISDN from the subscr data structure
In case there is a subscr attached to the MM context and there
is an encoded MSISDN we will attempt to decode it and in case
of an international number prepend a '+'. Assume that the array
size of gsm_mmcc_called->number is as big as ctx->msisdn for the
strncpy.
http://cgit.osmocom.org/openbsc/commit/?id=b448dd849a96fd1b736ee183385d7a6a…
commit b448dd849a96fd1b736ee183385d7a6a9ea1863e
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Sun May 3 11:46:58 2015 +0200
sgsn: Make the free function internal
All calls should and do go through the
sgsn_mm_ctx_cleanup_free function.
-----------------------------------------------------------------------
hooks/post-receive
--
The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)
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/flow-control has been updated
discards b218b819202556ed86cd1c428aee16fa778914ac (commit)
discards 68f7d29a5a4d7688a0e5737e7e6d94d72154e773 (commit)
discards 0f3882d233837bd74add250fc81aeeb5c9e71839 (commit)
via 6eeb7c7e74ed8cc1e23b19453012f43563055e12 (commit)
via 6e4ccec6c4b69681e94e4d3b27ef022e4aab81a9 (commit)
via 0288cdb0a8d4011905da55a5b74319e38e27e70d (commit)
via 3d62fc55d89fe1f2da0f0ca1950ab97da7e07418 (commit)
via 87d7341fbe290582ac4a03f67349496e5306eb04 (commit)
via 29d91e92715945f53aff4530602add765d63946e (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 (b218b819202556ed86cd1c428aee16fa778914ac)
\
N -- N -- N (6eeb7c7e74ed8cc1e23b19453012f43563055e12)
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=6eeb7c7e74ed8cc1e23b19453012f43…
commit 6eeb7c7e74ed8cc1e23b19453012f43563055e12
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Wed May 6 15:26:08 2015 +0200
bssgp: Increment BSSGP flow control tag value
Currently the tag value in FLOW CONTROL BVC messages is always 1.
This commit changes the implementation to increment that value with
each of the FLOW CONTROL BVC messages that is sent to the SGSN.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/osmo-pcu/commit/?id=6e4ccec6c4b69681e94e4d3b27ef022…
commit 6e4ccec6c4b69681e94e4d3b27ef022e4aab81a9
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Wed May 6 14:24:36 2015 +0200
bssgp: Compute and transmit queue delay
The specification 28.018, allows to transmit the average LLC downlink
queueing delay in FLOW CONTROL BVC messages (BVC Measurement IE, see
GSM 28.018, 10.4.4 and 11.3.7).
This commit extends gprs_bssgp_pcu.cpp to compute the average delay
time between two subsequent FLOW CONTROL BVC messages. The average is
implemented as an arithmetic average without any weighting.
Ticket: OW#1432
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/osmo-pcu/commit/?id=0288cdb0a8d4011905da55a5b74319e…
commit 0288cdb0a8d4011905da55a5b74319e38e27e70d
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Wed May 6 10:47:30 2015 +0200
bssgp: Add VTY command to Limit the bucket size by time
Currently the bucket size is by default being computed based on the
leak rate and the expected life time of LLC frames. The latter is
either taken from 'queue lifetime' (if given) or a fixed value is
used. Using 'queue lifetime' has the drawback that it sets a 'hard'
limit, since frames will be dropped if they stay in the queue
for a longer time.
This commit adds a VTY command to specifically set the time used for
the computation of the bucket size advertised to the SGSN. It does
not affect the PCUs queue handling in any way. If the bucket time is
not set (or if the 'no' command has been used), the old behaviour
(see above) is applied.
The following VTY commands are added (config-pcu node):
- flow-control bucket-time <1-65534> Sets the time in centisecs
- no flow-control bucket-time Don't use this time
Ticket: OW#1432
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/osmo-pcu/commit/?id=3d62fc55d89fe1f2da0f0ca1950ab97…
commit 3d62fc55d89fe1f2da0f0ca1950ab97da7e07418
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Thu Apr 30 15:01:15 2015 +0200
bssgp: Compute BVC bucket size and leak rate
Currently the PDCH assignment and coding scheme does not influence
the values transmitted by the FLOW-CONTROL-BVC messages.
This commit adds the computation of those values. If the leak rate is
not given explicitly, it is derived from the number of PDCH and the
allowed coding scheme. If the BVC bucket size is not given
explicitly, it is derived from the leak rate and the maximum buffer time.
The latter is taken from the 'queue lifetime' command (or 10s if this
has not been used). The MS default bucket size is set to 50% of the
BVC bucket size. The MS default rate computation assumes, that each MS
only supports up to 4 time slots for GPRS RX.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/osmo-pcu/commit/?id=87d7341fbe290582ac4a03f67349496…
commit 87d7341fbe290582ac4a03f67349496e5306eb04
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Tue Apr 21 12:56:48 2015 +0200
bssgp: Make BVC bucket size / leak rate configurable
Currently the FLOW-CONTROL_BVC message contains fixed values: The tag
is 1, the BVC bucket size is 6MB, the BVC bucket leak rate is
820kbit/s, the MS bucket size is 50kB, and the MS leak rate is
50kbit/s.
This commit makes the BVC parameters configurable and adds the
following VTY commands:
- flow-control force-bvc-bucket-size <1-6553500>
- no flow-control force-bvc-bucket-size
- flow-control force-bvc-leak-rate <1-6553500>
- no flow-control force-bvc-leak-rate
- flow-control force-ms-bucket-size <1-6553500>
- no flow-control force-ms-bucket-size
- flow-control force-ms-leak-rate <1-6553500>
- no flow-control force-ms-leak-rate
The 'no' variants restore the default behaviour.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/osmo-pcu/commit/?id=29d91e92715945f53aff4530602add7…
commit 29d91e92715945f53aff4530602add765d63946e
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Wed Apr 29 14:46:52 2015 +0200
tbf: Added calls to llc_dropped_frame
Currently this function which increments the corresponding counter is
just called in gprs_llc::clear(). It is not called on places where
LLC DISCARDED messages are sent.
This commit adds calls to llc_dropped_frame() at these places.
Sponsored-by: On-Waves ehf
-----------------------------------------------------------------------
Summary of changes:
src/bts.h | 1 +
src/gprs_bssgp_pcu.cpp | 162 +++++++++++++++++++++++++++++++++++++------------
src/gprs_bssgp_pcu.h | 8 +++
src/pcu_vty.c | 28 +++++++++
src/tbf_dl.cpp | 16 +++--
5 files changed, 171 insertions(+), 44 deletions(-)
hooks/post-receive
--
UNNAMED PROJECT
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 4c8e8f990a24fc5ecb24c5c21c944d8ab4dc7c1e (commit)
via d05e06989def81f886c673956da476e626a27af5 (commit)
via f7b3826f03772d57d1d1a1153c5684f7d4799b60 (commit)
via 4bd931f96d75d3e71b73a06e67f84ffdcab9caf6 (commit)
via 8cedded88c9a0c4c486f987b818ccba57e96421e (commit)
via 9ba273d365ac731a9c3ff285821062c346724390 (commit)
via 49c1a7156c7e0ced1709aee4a3d3438db60bae41 (commit)
via b927f1c3199b48becb03c0d56926c3b98d6ff5ce (commit)
via 02d8c472bdff0a085cbedd9d902f7ced29e5d712 (commit)
via e448554568fb4244a1b95e2e8666714f9498d69a (commit)
from 337343d159888886eaa68476b70dbe19db93845b (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=4c8e8f990a24fc5ecb24c5c21c944d8a…
commit 4c8e8f990a24fc5ecb24c5c21c944d8ab4dc7c1e
Merge: 337343d d05e069
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Tue May 5 21:16:19 2015 +0200
Merge branch 'zecke/features/gprs-gsup-fixes'
When communicating with a GGSN that is not the OpenGGSN
the PDP context activation does fail. This is because on
the activation of the first PDP context we need to supply
a MSISDN. Extend the protocol, parse the MSISDN and then
send it to the GGSN. The second item is that we have only
forwarded the requested QoS of the subscriber. In most
cases this is 0x0, 0x0, ... which means one requests a
rate 0 byte/sec which the GGSN will not allow. Make it
possible to receive, store and use the subscribed QoS of
the Subscriber.
http://cgit.osmocom.org/openbsc/commit/?id=d05e06989def81f886c673956da476e6…
commit d05e06989def81f886c673956da476e626a27af5
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Thu Apr 23 16:59:04 2015 -0400
sgsn: Show the QoS that has been assigned
http://cgit.osmocom.org/openbsc/commit/?id=f7b3826f03772d57d1d1a1153c5684f7…
commit f7b3826f03772d57d1d1a1153c5684f7d4799b60
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Thu Apr 23 16:58:33 2015 -0400
sgsn: Dump the E164 (encoded) assigned to the subscriber
http://cgit.osmocom.org/openbsc/commit/?id=4bd931f96d75d3e71b73a06e67f84ffd…
commit 4bd931f96d75d3e71b73a06e67f84ffdcab9caf6
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Thu Apr 23 11:50:41 2015 -0400
sgsn: Handle different levels of QoS
If QoS is only three bytes it does not include the allocation/
retention policy. Otherwise it does. Copy it depending on that.
We should have a macro for the clamping to reduce code duplication.
The insanity does come from the MAP data and this seems to be
the easiest in terms of complexity. It is an array of bytes that
is transported from MAPProxy to the SGSN and then simply forwarded.
The case of more than three bytes is neither unit nor manually
tested so far.
http://cgit.osmocom.org/openbsc/commit/?id=8cedded88c9a0c4c486f987b818ccba5…
commit 8cedded88c9a0c4c486f987b818ccba57e96421e
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Thu Apr 23 11:33:35 2015 -0400
sgsn: Store subscribed QoS and attempt to use it
sgsn_create_pdp_ctx should use the subscribed QoS. When selecting
the PDP context we inject the QoS to be used into the TLV structure
and use it during the request. Assume a "qos-Subscribed" structure
only with three bytes and prepend the Allocation/Retention policy
to the request.
http://cgit.osmocom.org/openbsc/commit/?id=9ba273d365ac731a9c3ff285821062c3…
commit 9ba273d365ac731a9c3ff285821062c346724390
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Thu Apr 23 09:53:53 2015 -0400
sgsn: Copy the msisdn to the sgsn_data and use it in PDP activation
The MSISDN should be present for "security" reasons in the first
activation of a PDP context. Take the encoded MSISDN, store it for
future use and then put it into the PDP activation request.
The MM Context contains a field for a decoded MSISDN already. As
we need to forward the data to the GGSN I want to avoid having to
store TON and NPI in another place. Simply store the data in the
encoded form.
http://cgit.osmocom.org/openbsc/commit/?id=49c1a7156c7e0ced1709aee4a3d3438d…
commit 49c1a7156c7e0ced1709aee4a3d3438db60bae41
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Thu Apr 23 09:13:01 2015 -0400
gsup: Extract the QoS field
Add roundtrip test for the new QoS IE. It will be consumed in
later commits.
http://cgit.osmocom.org/openbsc/commit/?id=b927f1c3199b48becb03c0d56926c3b9…
commit b927f1c3199b48becb03c0d56926c3b98d6ff5ce
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Wed Apr 22 23:09:41 2015 -0400
gsup: Extract the new MSISDN string
Extract the new MSISDN IE from the GSUP message and verify that
it is read/written to the message.
http://cgit.osmocom.org/openbsc/commit/?id=02d8c472bdff0a085cbedd9d902f7ced…
commit 02d8c472bdff0a085cbedd9d902f7ced29e5d712
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Wed Apr 22 22:42:23 2015 -0400
gsup: Specify the QoS service for the PDP info
QoS is a mess. In MAP there is qos-Subscribed which is then extended
using ext-QoS-Subscribed, ext2-QoS-Subscribed, ext3-QoS-Subscribed
and maybe even ext4-QoS-Subscribed by now. The MAP ASN1 files defined
how these need to be "linearized". Instead of copying this I have
decided to include the two semantics with/without the Allocation/Retention
policy using the size of the data.
http://cgit.osmocom.org/openbsc/commit/?id=e448554568fb4244a1b95e2e8666714f…
commit e448554568fb4244a1b95e2e8666714f9498d69a
Author: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Date: Wed Apr 22 22:10:44 2015 -0400
gsup: Document passing MSISDN as part of the response
When asking the GGSN to create/open a PDP context one needs
to send a MSISDN. The MSISDN can only be provided through the
GSUP interface.
-----------------------------------------------------------------------
Summary of changes:
openbsc/doc/sgsn-remote-protocol.txt | 45 ++++++++++++++++++++++++++++
openbsc/include/openbsc/gprs_gsup_messages.h | 7 +++++
openbsc/include/openbsc/gprs_sgsn.h | 5 ++++
openbsc/include/openbsc/gsm_04_08_gprs.h | 1 +
openbsc/src/gprs/gprs_gsup_messages.c | 21 +++++++++++++
openbsc/src/gprs/gprs_sgsn.c | 15 ++++++++++
openbsc/src/gprs/gprs_subscriber.c | 23 ++++++++++++++
openbsc/src/gprs/sgsn_libgtp.c | 41 ++++++++++++++++++++-----
openbsc/src/gprs/sgsn_vty.c | 8 ++++-
openbsc/tests/gprs/gprs_test.c | 5 +++-
openbsc/tests/sgsn/sgsn_test.c | 9 ++++++
11 files changed, 170 insertions(+), 10 deletions(-)
hooks/post-receive
--
The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)
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/flow-control has been updated
discards 5e1a8403564b2af351ad8a8d462488cc25648dd8 (commit)
discards fe865b1887d58302e7a68b6b01b5de69f35b0870 (commit)
discards 47e945161b06edf51f19ec4d7b7baec1f09ce8b8 (commit)
discards bcfa2f67b4b19174964d64992f34fae12adbcc84 (commit)
discards fcb8e6560c5e12f55518479c6fd22344d233e9cb (commit)
via b218b819202556ed86cd1c428aee16fa778914ac (commit)
via 68f7d29a5a4d7688a0e5737e7e6d94d72154e773 (commit)
via 0f3882d233837bd74add250fc81aeeb5c9e71839 (commit)
via 801d6fe40cd5bd11257074c7aaf113a57919fb2d (commit)
via 0494c75a53f05a5ec4c4b3830672ef2451396f27 (commit)
via 0d39dc92b5cfe6e8be9b2a68eaf50c94cae97355 (commit)
via 1f33294b1c1394c6ff0dd109ff10bb65886c1a44 (commit)
via 2acfbebfd3b7fc24ccaf2115e7c8d55e94cd1450 (commit)
via c0c580c414e4fe0bd82ebc78ff12bb1014cd5a9c (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 (5e1a8403564b2af351ad8a8d462488cc25648dd8)
\
N -- N -- N (b218b819202556ed86cd1c428aee16fa778914ac)
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=b218b819202556ed86cd1c428aee16f…
commit b218b819202556ed86cd1c428aee16fa778914ac
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Thu Apr 30 15:01:15 2015 +0200
bssgp: Compute BVC bucket size and leak rate
Currently the PDCH assignment and coding scheme does not influence
the values transmitted by the FLOW-CONTROL-BVC messages.
This commit adds the computation of those values. If the leak rate is
not given explicitly, it is derived from the number of PDCH and the
allowed coding scheme. If the BVC bucket size is not given
explicitly, it is derived from the leak rate and the maximum buffer time.
The latter is taken from the 'queue lifetime' command (or 10s if this
has not been used). The MS default bucket size is set to 25% of the
BVC bucket size.
http://cgit.osmocom.org/osmo-pcu/commit/?id=68f7d29a5a4d7688a0e5737e7e6d94d…
commit 68f7d29a5a4d7688a0e5737e7e6d94d72154e773
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Tue Apr 21 12:56:48 2015 +0200
bssgp: Make BVC bucket size / leak rate configurable
Currently the FLOW-CONTROL_BVC message contains fixed values: The tag
is 1, the BVC bucket size is 6MB, the BVC bucket leak rate is
820kbit/s, the MS bucket size is 50kB, and the MS leak rate is
50kbit/s.
This commit makes the BVC parameters configurable and adds the
following VTY commands:
- flow-control force-bvc-bucket-size <1-6553500>
- no flow-control force-bvc-bucket-size
- flow-control force-bvc-leak-rate <1-6553500>
- no flow-control force-bvc-leak-rate
- flow-control force-ms-bucket-size <1-6553500>
- no flow-control force-ms-bucket-size
- flow-control force-ms-leak-rate <1-6553500>
- no flow-control force-ms-leak-rate
The 'no' variants restore the default behaviour.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/osmo-pcu/commit/?id=0f3882d233837bd74add250fc81aeeb…
commit 0f3882d233837bd74add250fc81aeeb5c9e71839
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Wed Apr 29 14:46:52 2015 +0200
tbf: Added calls to llc_dropped_frame
Currently this function which increments the corresponding counter is
just called in gprs_llc::clear(). It is not called on places where
LLC DISCARDED messages are sent.
This commit adds calls to llc_dropped_frame() at these places.
Sponsored-by: On-Waves ehf
-----------------------------------------------------------------------
Summary of changes:
src/bts.cpp | 2 +-
src/sysmo_l1_if.h | 10 ++++++++++
tests/alloc/AllocTest.cpp | 16 +++++++---------
tests/emu/pcu_emu.cpp | 6 +++---
tests/emu/test_pdp_activation.cpp | 4 +---
tests/emu/test_replay_gprs_attach.cpp | 2 +-
tests/tbf/TbfTest.cpp | 2 +-
tests/types/TypesTest.cpp | 2 --
8 files changed, 24 insertions(+), 20 deletions(-)
hooks/post-receive
--
UNNAMED PROJECT