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, jerlbeck/wip/gprs-patching has been updated discards 1789a16e884fa069bc2244791a4659c84efdffc8 (commit) discards 08001dc2d5c02f67622de15fe7b36bc6b7098bda (commit) discards 83c92aca6904b44f129c3aa2dbced8cc0bacea91 (commit) via 70992b3369bb8922d92aabdbd54a33d3a52d8c05 (commit) via 0153212b910a6c01103e1f4dc914457ac733bd9c (commit) via 7d08477daa44919b65bbbaa794947e70bc88e407 (commit) via 8f4a1762c82e25093de13c30fd58d0b3645c8e9f (commit) via 78198111ebf1f60fb369a9788b5f8045d9b0beb8 (commit) via c3f158e84846fc1fbd58aa0e377acd12a78d29ab (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 (1789a16e884fa069bc2244791a4659c84efdffc8) \ N -- N -- N (70992b3369bb8922d92aabdbd54a33d3a52d8c05) 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=70992b3369bb8922d92aabdbd54a33d3a... commit 70992b3369bb8922d92aabdbd54a33d3a52d8c05 Author: Jacob Erlbeck <jerlbeck@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=0153212b910a6c01103e1f4dc914457ac... commit 0153212b910a6c01103e1f4dc914457ac733bd9c Author: Jacob Erlbeck <jerlbeck@sysmocom.de> Date: Wed Dec 17 14:03:35 2014 +0100 sgsn: Add PDP info to subscriber data (TODO) TODO: - commit message - raw binary representation ??? - tests Sponsored-by: On-Waves ehf http://cgit.osmocom.org/openbsc/commit/?id=7d08477daa44919b65bbbaa794947e70b... commit 7d08477daa44919b65bbbaa794947e70bc88e407 Author: Jacob Erlbeck <jerlbeck@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 http://cgit.osmocom.org/openbsc/commit/?id=8f4a1762c82e25093de13c30fd58d0b36... commit 8f4a1762c82e25093de13c30fd58d0b3645c8e9f Author: Jacob Erlbeck <jerlbeck@sysmocom.de> Date: Tue Jan 27 14:56:40 2015 +0100 gprs: Support cancellation type The cancellation type that is part of the UpdateCancellation message is currently ignored. This patch adds the missing glue between the existing GSUP and GMM support. If the type is not present or has the value updateProcedure the subcriber and MM context are siliently removed. Otherwise, a message with cause 'implicitly detached' is sent to the MS. Since the real cause is not known (the specification neither added a cause IE nor defined a static cause value), the MS may get the real cause in the following AttachRej. Added VTY commands: - update-subscriber imsi IMSI cancel update-procedure - update-subscriber imsi IMSI cancel subscription-withdraw the old form without the cause is no longer supported. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/openbsc/commit/?id=78198111ebf1f60fb369a9788b5f8045d... commit 78198111ebf1f60fb369a9788b5f8045d9b0beb8 Author: Jacob Erlbeck <jerlbeck@sysmocom.de> Date: Tue Jan 27 13:47:24 2015 +0100 gprs: Handle PURGE MS ERR/RES without subscr Currently the subscr entry is no longer present, when PURGE MS ERROR/RESULT arrives. In this case, an unspecific notice is logged ('unknown IMSI'). This clutters up the logfile with notices even in perfectly normal operation. This commit changes the code path that is used when a subscr cannot be found for an incoming GSUP message. A check for PURGE MS RESULT and ERROR is added and gprs_subscr_handle_gsup_purge_no_subscr is called for these messages instead of gprs_subscr_handle_unknown_imsi. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/openbsc/commit/?id=c3f158e84846fc1fbd58aa0e377acd12a... commit c3f158e84846fc1fbd58aa0e377acd12a78d29ab Author: Jacob Erlbeck <jerlbeck@sysmocom.de> Date: Tue Jan 27 12:41:19 2015 +0100 gprs: Don't use subscr->keep_in_ram in normal operation Currently the keep_in_ram flag is explicitely reset in gprs_subscr_cleanup to cover the case, that the VTY 'create' sub-command has been used to create the subscriber entry. This commit completely removes keep_in_ram handling from gprs_subscriber.c and adds a VTY 'destroy' sub-command to reset the flag and remove the entry. So 'create' and 'destroy' can be used to manager sticky entries that are kept even when a location cancellation is done. Added VTY command: - update-subscriber imsi IMSI destroy Sponsored-by: On-Waves ehf ----------------------------------------------------------------------- Summary of changes: openbsc/src/gprs/gprs_subscriber.c | 48 +++++++++++++++++++++++++++++++++----- openbsc/src/gprs/sgsn_vty.c | 40 +++++++++++++++++++++++++++++-- openbsc/tests/vty_test_runner.py | 5 +++- 3 files changed, 84 insertions(+), 9 deletions(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)