openbsc.git branch jerlbeck/wip/gprs-patching updated. 0.13.0-867-gea0536b

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 ab5820d6dbbe322de617aaf8a5ccaf0ad0a2bffc (commit) via ea0536bf635e07db2f384781da98be7ab8827e5a (commit) via fcba963099af65e6f193eb6799ccac0a2efb86a9 (commit) via 769b6127cced3e611b9abd1b4ad82cb5be729c35 (commit) via a85733188e7ec86a88042004c033043f0b4ec8d9 (commit) via b316eb4edbd9abbc439796955d6a490bb179d3f7 (commit) via c586e0177e35c2ffde4ca8377be55703d6d0cf5d (commit) via bb25160f1b5e69957114d429279c3ba159b16215 (commit) via 8322ac6f11f4504add91c1a658c4103a5dedcf6b (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 (ab5820d6dbbe322de617aaf8a5ccaf0ad0a2bffc) \ N -- N -- N (ea0536bf635e07db2f384781da98be7ab8827e5a) 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=ea0536bf635e07db2f384781da98be7a… commit ea0536bf635e07db2f384781da98be7ab8827e5a Author: Jacob Erlbeck &lt;jerlbeck(a)sysmocom.de&gt; Date: Thu Jan 8 15:29:01 2015 +0100 gprs: Support the full cancellation procedure (TODO) TODO: - Commit message - Reply to cancellation request (either with RES or ERR) Sponsored-by: On-Waves ehf http://cgit.osmocom.org/openbsc/commit/?id=fcba963099af65e6f193eb6799ccac0a… commit fcba963099af65e6f193eb6799ccac0a2efb86a9 Author: Jacob Erlbeck &lt;jerlbeck(a)sysmocom.de&gt; Date: Thu Jan 8 16:23:25 2015 +0100 gprs: Block other GSUP procedures during PURGE_MS (TODO) TODO: - commit message - move LOGGSUBSCRP fix in gprs_subscr_purge to HEAD^^ - testing Ticket: OW#???? Sponsored-by: On-Waves ehf http://cgit.osmocom.org/openbsc/commit/?id=769b6127cced3e611b9abd1b4ad82cb5… commit 769b6127cced3e611b9abd1b4ad82cb5be729c35 Author: Jacob Erlbeck &lt;jerlbeck(a)sysmocom.de&gt; Date: Thu Jan 8 15:18:39 2015 +0100 gprs: Retry PURGE_MS procedure after timeout Currently, when the PURGE_MS_REQ to the HLR gets lost (e.g. by a connection or peer failure), the expired subscriber entry will not get deleted. This commit adds a retry mechanism then restarts the procedure after a timeout (currently 10s). The maximum number of retries is limited (currently to 3 PURGE_MS messages). If none of these procedures is completed (either with success or error), the subscriber data is deleted. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/openbsc/commit/?id=a85733188e7ec86a88042004c033043f… commit a85733188e7ec86a88042004c033043f0b4ec8d9 Author: Jacob Erlbeck &lt;jerlbeck(a)sysmocom.de&gt; Date: Tue Jan 6 16:32:41 2015 +0100 gprs: Support PURGE MS messages (TODO) When a subscriber entry is going to be deleted by SGSN and when the subscriber info has been optained from a remote peer via GSUP, the peer should be informed before the entry is really deleted. For this purpose, MAP defines the PURGE MS procedure (see GSM 09.02, 19.1.4). This patch adds support for the PURGE_MS_REQ/_ERR/_RES messages and invokes the procedure when the subscriber entry is going to be removed. This only applies, if GSUP is being used, the Update Location procedure has been completed successfully, and the subscriber has not been cancelled. The removal of the entry is delayed until a PURGE_MS_RES or PURGE_MS_ERR message is received. TODO: - commit message - expire ununsed MM contexts (other commit) - blocking (see spec)? Sponsored-by: On-Waves ehf http://cgit.osmocom.org/openbsc/commit/?id=b316eb4edbd9abbc439796955d6a490b… commit b316eb4edbd9abbc439796955d6a490bb179d3f7 Author: Jacob Erlbeck &lt;jerlbeck(a)sysmocom.de&gt; Date: Tue Jan 6 16:32:41 2015 +0100 gprs: Add expiry timeout for subscriber entries (TODO) Set the expiry delay after the subscriber has been deleted (e.g. by freeing the MM context). If cancelled, the subscriber will be deleted immediately and no timeout will be set. If the expiry time is set to SGSN_TIMEOUT_NEVER, no timer will be started and the subscriber entry will be kept until it is cancelled. The following VTY command is added to the sgsn node: - subscriber-expiry-time <0-999999> set expiry time in seconds - no subscriber-expiry-time set to SGSN_TIMEOUT_NEVER The default is an expiry time of 0 seconds, which means that the subscriber entries are wiped out immediately after an MM context is destroyed. TODO: - tests Sponsored-by: On-Waves ehf http://cgit.osmocom.org/openbsc/commit/?id=c586e0177e35c2ffde4ca8377be55703… commit c586e0177e35c2ffde4ca8377be55703d6d0cf5d Author: Jacob Erlbeck &lt;jerlbeck(a)sysmocom.de&gt; Date: Thu Jan 8 14:13:46 2015 +0100 sgsn/test: Fix subscriber cleanup Currently the subscribers are not really deleted by cleanup_subscr_by_imsi, but kept in RAM instead. This patch fixes this and adds a test to verify, that the subscriber is really deleted afterwards. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/openbsc/commit/?id=bb25160f1b5e69957114d429279c3ba1… commit bb25160f1b5e69957114d429279c3ba159b16215 Author: Jacob Erlbeck &lt;jerlbeck(a)sysmocom.de&gt; Date: Thu Jan 8 14:08:16 2015 +0100 gprs/test: Move subscr cleanup code into a separate function Refactor several occurences of the same subscriber cleanup code into a seperate cleanup_subscr_by_imsi function. Sponsored-by: On-Waves ehf http://cgit.osmocom.org/openbsc/commit/?id=8322ac6f11f4504add91c1a658c4103a… commit 8322ac6f11f4504add91c1a658c4103a5dedcf6b Author: Jacob Erlbeck &lt;jerlbeck(a)sysmocom.de&gt; Date: Thu Jan 8 12:02:12 2015 +0100 gprs: Add and use LOGGSUBSCRP macro to log subscriber Currently the LOGMMCTXP is used to log information related to subscribers. This relies on subscr->mm being set to include the IMSI in the output. This also means, that in doesn't show the IMSI in subscr entries that are not attached to an MM context, albeit the IMSI is stored in the gsm_subscriber object. This patch adds a new logging macro, that logs subscrs to DGPRS without using the mm reference. It also replaces all LOGMMCTXP and most LOGP in gprs_subscriber.c by LOGGSUBSCRP. Sponsored-by: On-Waves ehf ----------------------------------------------------------------------- Summary of changes: openbsc/include/openbsc/gprs_sgsn.h | 14 ++ openbsc/src/gprs/gprs_subscriber.c | 249 ++++++++++++++++++++++++++---------- openbsc/src/gprs/sgsn_vty.c | 4 +- openbsc/tests/sgsn/sgsn_test.c | 28 ++-- 4 files changed, 219 insertions(+), 76 deletions(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)