diff options
| author | Jacob Erlbeck <jerlbeck@sysmocom.de> | 2015-01-27 12:41:19 +0100 |
|---|---|---|
| committer | Holger Hans Peter Freyther <holger@moiji-mobile.com> | 2015-01-28 20:42:58 +0100 |
| commit | e988ae471d8e699a4045d77048986570349203fa (patch) | |
| tree | 7f3dba3295e0b7d2123ea315cb4b76cc3473df54 /openbsc/tests/vty_test_runner.py | |
| parent | e671d254cbc294f87620c2938eb6fa2883253fcb (diff) | |
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
Diffstat (limited to 'openbsc/tests/vty_test_runner.py')
| -rw-r--r-- | openbsc/tests/vty_test_runner.py | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/openbsc/tests/vty_test_runner.py b/openbsc/tests/vty_test_runner.py index 31fadf1f8..de6a708c3 100644 --- a/openbsc/tests/vty_test_runner.py +++ b/openbsc/tests/vty_test_runner.py @@ -770,6 +770,9 @@ class TestVTYSGSN(TestVTYGenericBSC): self.assert_(res.find('Authorized: 1') >= 0) self.assertTrue(self.vty.verify('update-subscriber imsi 1234567890 cancel', [''])) res = self.vty.command('show subscriber cache') + self.assert_(res.find('1234567890') >= 0) + self.assertTrue(self.vty.verify('update-subscriber imsi 1234567890 destroy', [''])) + res = self.vty.command('show subscriber cache') self.assert_(res.find('1234567890') < 0) def add_nat_test(suite, workdir): |