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 13713264aa539ce1343ad6c7dd0f8308b242a892 (commit)
discards f30d7455f17f8488b03d8727f33dfaa39e812107 (commit)
discards 917d8e33aa0f6f14d459124ab63961a1876b7379 (commit)
discards b0f9aae0e08b65ce2636218379853f88f33134fa (commit)
discards 033dacd0be40045485ce85fe6d736dad56277b97 (commit)
discards df41492476d1134f907c9eeaa8da592223012e30 (commit)
discards d255302af01073748213504bd65692941b30c01c (commit)
discards 9230f1a7537821dff9b5cd6f65fd77cf5a0a16f8 (commit)
via a43e25b50c1ad30a597e336c8f47e274a9911186 (commit)
via 6a3dab12333b610ca35622d943647b17585f8871 (commit)
via f2cde608fc40b767e540073c575fbd0479c1c0a7 (commit)
via 156c91bc2e564894aa09b5ebe7f2ff13923cd8da (commit)
via 1e3bc33ed38ed2f9fca27f19e4197abb559b1cf8 (commit)
via 76a917b02cff735d1bf7eaa4685462ab631dce76 (commit)
via 93d39583080a58fb16597ecc341a1ce32ad38d7a (commit)
via f8f8fba629ed6b861dacb1f997c9f28d83a162e0 (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 (13713264aa539ce1343ad6c7dd0f8308b242a892)
\
N -- N -- N (a43e25b50c1ad30a597e336c8f47e274a9911186)
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=a43e25b50c1ad30a597e336c8f47e274…
commit a43e25b50c1ad30a597e336c8f47e274a9911186
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=6a3dab12333b610ca35622d943647b17…
commit 6a3dab12333b610ca35622d943647b17585f8871
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=f2cde608fc40b767e540073c575fbd04…
commit f2cde608fc40b767e540073c575fbd0479c1c0a7
Author: Jacob Erlbeck <jerlbeck(a)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=156c91bc2e564894aa09b5ebe7f2ff13…
commit 156c91bc2e564894aa09b5ebe7f2ff13923cd8da
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
http://cgit.osmocom.org/openbsc/commit/?id=1e3bc33ed38ed2f9fca27f19e4197abb…
commit 1e3bc33ed38ed2f9fca27f19e4197abb559b1cf8
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Mon Jan 5 16:20:47 2015 +0100
gprs: Pass GMM causes related to the MSC connection
Currently the error causes MSC_TEMP_NOTREACH, NET_FAIL, and
CONGESTION are silently dropped to force the MS to continue. On the
other hand, GSM 04.08/24.008, 4.7.3.1.4 in combination with 4.7.3.1.5,
require the MS to retry the attachment procedure for cause codes
above 15 instead of disabling GPRS. All of the mentioned GMM causes
have codes above 15, so using a REJECT message including the cause
code is a better choice. This way, the retry algorithm based on T3311
(15s, 5 times) and T3302 (default 12min) could be used.
This patch modifies gprs_subscr_handle_gsup_auth_err and
gprs_subscr_handle_gsup_upd_loc_err to proceed like when the access
has beed denied, except that the corresponding subscriber's
information fields are not cleared.
This has been successfully tested which an iphone which enters a
retry loop as it is being described in the specification.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=76a917b02cff735d1bf7eaa4685462ab…
commit 76a917b02cff735d1bf7eaa4685462ab631dce76
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Tue Dec 23 14:24:16 2014 +0100
gprs: Use LOGMMCTX for logging in gprs_susbcriber.c
To unify the layout of the logging messages, this patch replaces some
calls to LOGP by calls to LOGMMCTXP.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=93d39583080a58fb16597ecc341a1ce3…
commit 93d39583080a58fb16597ecc341a1ce32ad38d7a
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Mon Jan 5 18:57:32 2015 +0100
gprs: Let GSUP parser functions return GMM causes on errors
Currently the GSUP message handling function in gprs_subscriber.c and
the functions in gprs_gsup_messages.c are not consistent with respect
to the return codes if an error happens. Albeit all error return
codes are negative, the semantics of the absolute value are not
clearly defined. In addition, some return codes are not passed to the
calling function.
This path changes these functions to always return a negated GMM
cause value in case of errors. Return values of called parser
functions are not longer ignored.
Sponsored-by: On-Waves ehf
http://cgit.osmocom.org/openbsc/commit/?id=f8f8fba629ed6b861dacb1f997c9f28d…
commit f8f8fba629ed6b861dacb1f997c9f28d83a162e0
Author: Jacob Erlbeck <jerlbeck(a)sysmocom.de>
Date: Mon Jan 5 18:38:41 2015 +0100
gprs: Use the cause value in GSUP error messages
Currently always a cause with the meaning of 'access denied' is
assumed. gprs_subscr_handle_gsup_auth_err just clears the auth
triplets and the authorized flag before calling the update function.
gprs_subscr_handle_gsup_upd_loc_err only clears the authorized flag
and calls the update function. This means, that an MS will not retry
to attach even on temporary network errors.
This patch changes these functions to use the GSUP error cause value
to decide, whether to clear the corresponding subscriber fields, to
just continue with the corresponding update function, or to log,
ignore and not pass the cause to the MS in case the error is directly
related to the GSUP protocol. The subscriber's error_cause field is
updated, if the update function is going to be called. The
error_cause fielt is reset on non-error GSUP messages.
Sponsored-by: On-Waves ehf
-----------------------------------------------------------------------
Summary of changes:
openbsc/src/gprs/gprs_subscriber.c | 30 ++++++++++++++++++++----------
1 file changed, 20 insertions(+), 10 deletions(-)
hooks/post-receive
--
The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)