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/no-queue has been updated discards 48b3aec416eebc1d0d76b97d169931fd2c1ed40b (commit) discards 63e2a7352f499c5eeeae81c5f868bdbbc86b6219 (commit) discards adaee02787c631541bd9b2b1d6a00fb6d0fc043c (commit) discards 82ac7cce66d5d39dc223f7a3bd905ea39ead1d02 (commit) via 017e093b6df76b3363f7dd5c59a286240f535a05 (commit) via b978b0fc9633ec7e721c76eba16e13fcf37ce660 (commit) via 62fe7bbfec22b74b462b279c26a50b2f6853be58 (commit) via 08da23bf4e5acbe5effe6c98684d5b641a699315 (commit) via 7ffa7b095fbea0f7f52a4179402edb04249c60d0 (commit) via 322b1499cd4d34b0148a15cb615ad6dff8203ed2 (commit) via 5b512051870017aebd79ff2ca05ad8be671728b2 (commit) via 9ed6fd25dde40e3079c5b278f543714b0d78a9f0 (commit) via 08ea4d87f6c5db1ce68ef58040a35271358fa6d8 (commit) via 0ac00c15b9fd667da80670440916ce2982eece20 (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 (48b3aec416eebc1d0d76b97d169931fd2c1ed40b) \ N -- N -- N (017e093b6df76b3363f7dd5c59a286240f535a05)

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=017e093b6df76b3363f7dd5c59a286240...

commit 017e093b6df76b3363f7dd5c59a286240f535a05 Author: Holger Hans Peter Freyther holger@moiji-mobile.com Date: Mon Apr 6 12:03:45 2015 +0200

sub: Remove the queue from the subscriber code

The idea of "subscriber_get_channel" was that different requests would be coordinated. At the same time we have seen that the "queue" can get stuck at both 31C3 and the rhizomatica installations.

Voice calls and SMS do not need coordination. We should be able to send SMS on a voice channel and switch the MS from a SDCCH to a TCH in case we establish a voice call. The SMS code itself needs to coordinate to obey the limit of one SMS per direction but this should be enforced in the sms layer and not on the subscriber.

Modify the code to have a simple paging coordination. The subscriber code will schedule the paging and register who would like to know about success/failure.

This allowed to greatly simplify the paging response handling for the transaction code (and in fact we could move the transaction list into the subscriber structure now). The code gained to support to cancel the notification of a request (but not the paging itself yet).

TODO: Cancel paging request in case no one cares about it anymore.

http://cgit.osmocom.org/openbsc/commit/?id=b978b0fc9633ec7e721c76eba16e13fcf...

commit b978b0fc9633ec7e721c76eba16e13fcf37ce660 Author: Holger Hans Peter Freyther holger@moiji-mobile.com Date: Mon Apr 6 09:55:10 2015 +0200

sub: Remove introspection of the "channel queue"

Over the next commits the queuing of commits will be completely modified to remove the queue and move the scheduling/limits to the outer callers.

http://cgit.osmocom.org/openbsc/commit/?id=62fe7bbfec22b74b462b279c26a50b2f6...

commit 62fe7bbfec22b74b462b279c26a50b2f6853be58 Author: Holger Hans Peter Freyther holger@moiji-mobile.com Date: Mon Apr 6 16:54:55 2015 +0200

sub: Remove paging requests before dispatching

The dispatching might lead to the removal of more paging requests and makes "request" invalid. Remove it before calling the callback.

http://cgit.osmocom.org/openbsc/commit/?id=08da23bf4e5acbe5effe6c98684d5b641...

commit 08da23bf4e5acbe5effe6c98684d5b641a699315 Author: Holger Hans Peter Freyther holger@moiji-mobile.com Date: Mon Apr 6 17:54:34 2015 +0200

mncc: Select the codec similar to the modify handling

In case the default TCH/F codec is "EFR" and we do an early assignment from SDCCH to a TCH we would assign the TCH/H codec. This is because the lchan_type will be neither a TCH/H nor a TCH/F.

At the same time the _gsm48_lchan_modify code to check for half vs. full-rate is the other way around. Align both.

It is full-rate if it is not a TCH_H. This will have some other complications down the way (early assignment on cells with only TCH/H). So the mode should not depend on the _current_ channel but the kind of channel we want.

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

Summary of changes: openbsc/src/gprs/gprs_subscriber.c | 3 ++- openbsc/src/libcommon/gsm_subscriber_base.c | 3 +-- openbsc/src/libmsc/db.c | 4 ++-- openbsc/src/libmsc/vty_interface_layer3.c | 14 ++++++++++++++ openbsc/src/osmo-bsc_nat/bsc_nat.c | 4 ++-- openbsc/src/osmo-bsc_nat/bsc_nat_ctrl.c | 9 ++++++++- openbsc/src/osmo-bsc_nat/bsc_nat_vty.c | 2 +- openbsc/src/osmo-bsc_nat/bsc_ussd.c | 2 +- openbsc/tests/sgsn/sgsn_test.c | 12 ++++++++++++ openbsc/tests/vty_test_runner.py | 26 ++++++++++++++++++++++++++ 10 files changed, 69 insertions(+), 10 deletions(-)

hooks/post-receive