summaryrefslogtreecommitdiffstats
path: root/tests/gb/gprs_bssgp_test.ok
diff options
context:
space:
mode:
authorJacob Erlbeck <jerlbeck@sysmocom.de>2014-09-10 12:43:28 +0200
committerHolger Hans Peter Freyther <holger@moiji-mobile.com>2014-10-23 18:53:02 +0200
commitb43baf20c571925cca16266482c4b5c325f41700 (patch)
tree87205c1a860b3ff8bf11701bfaa0da3322c590ee /tests/gb/gprs_bssgp_test.ok
parentcdebf7484a72c6a8221d68d7f360aee58d21ea83 (diff)
gprs: Don't discard SUSPEND/RESUME in bssgp_rcvmsg
Currently sending SUSPEND/RESUME messages to this function (like it is done in the osmo-sgsn) results in STATUS messages complaining about an unknown BVCI. The reason is, that these messages rely on a TLLI/RAI pair to identify the context and do not contain an explicit BVCI. This patch modifies bssgp_rcvmsg() to only complain about and unknown BVCI if one is given but a matching context is not found (except for RESET messages). The ctx argument is removed from the functions handling SUSPEND and RESUME since it will always be NULL then. Sponsored-by: On-Waves ehf
Diffstat (limited to 'tests/gb/gprs_bssgp_test.ok')
-rw-r--r--tests/gb/gprs_bssgp_test.ok2
1 files changed, 2 insertions, 0 deletions
diff --git a/tests/gb/gprs_bssgp_test.ok b/tests/gb/gprs_bssgp_test.ok
index 9c7b4c07..c9ec83d7 100644
--- a/tests/gb/gprs_bssgp_test.ok
+++ b/tests/gb/gprs_bssgp_test.ok
@@ -1,5 +1,7 @@
===== BSSGP test START
----- test_bssgp_suspend_resume START
+BSSGP primitive, SAP 16777219, prim = 3, op = 0, msg = 0b 1f 84 f0 12 34 56 1b 86 0f f1 80 20 37 00
+BSSGP primitive, SAP 16777219, prim = 4, op = 0, msg = 0e 1f 84 f0 12 34 56 1b 86 0f f1 80 20 37 00 1d 81 01
----- test_bssgp_suspend_resume END
===== BSSGP test END