path: root/openbsc/tests/sgsn/sgsn_test.ok
diff options
authorJacob Erlbeck <jerlbeck@sysmocom.de>2014-11-06 15:43:10 +0100
committerHolger Hans Peter Freyther <holger@moiji-mobile.com>2014-11-14 10:19:29 +0100
commitf6e7d99d54cc75fdc19433011afb5eaaa8a2a002 (patch)
tree370d0bed4efcab87e3bb7ce734c5518f297e4487 /openbsc/tests/sgsn/sgsn_test.ok
parentc4f9bf3142f54b63174f653b07103dd6ab36b1ae (diff)
sgsn: Don't assign a new P-TMSI if one is pending
Currently every time an RA Update Req or an Attach Req is processed, a new P-TMSI is allocated. When an MS issues another of these messages before it has completed the first procedure, old_ptmsi is replaced by ptmsi (and thus lost) and ptmsi is replaced by the newly allocated P-TMSI. This can confuse the gbproxy, which can loose track of the logical link then. At least a Blackberry emits a double set of RA Upd Req messages from time to time which may be just 20ms apart. This patch adds a check whether mm->ptmsi or mm->old_ptmsi are set. If both are set, the P-TMSI is not re-allocated. This is only the case, when the Complete message has not been received yet, since that message will reset old_ptmsi. Sponsored-by: On-Waves ehf
Diffstat (limited to 'openbsc/tests/sgsn/sgsn_test.ok')
1 files changed, 4 insertions, 0 deletions
diff --git a/openbsc/tests/sgsn/sgsn_test.ok b/openbsc/tests/sgsn/sgsn_test.ok
index d3b333f8a..6f6204ff5 100644
--- a/openbsc/tests/sgsn/sgsn_test.ok
+++ b/openbsc/tests/sgsn/sgsn_test.ok
@@ -10,4 +10,8 @@ Testing GMM reject
- Routing Area Update Request (valid)
- Routing Area Update Request (invalid type)
- Routing Area Update Request (invalid CAP length)
+Testing P-TMSI allocation
+ - sgsn_alloc_ptmsi
+ - Repeated Attach Request
+ - Repeated RA Update Request