Dear attendees of OsmoDevCon 2016,
below are some updates regarding OsmoDevCon 2016
= Lunch Catering =
OsmoDevCon lunch catering has been finalized by now. I wanted to
try some change by having (authentic) thai food, but unfortunately that
didn't work out and we're back to our trusted old suppliers for all of
the lunches. More details are available on
http://projects.osmocom.org/projects/openbsc/wiki/OsmoDevCon2016
= Dinner Catering =
In terms of dinner catering, we didn't plan/schedule anything yet. I
know it was a request to have it and we introduced it (last year?) but
I didn't have time to actively look for a sponsor for this in 2016,
sorry.
If you think it's important, I can try to get something organized for
dinner too, but there's not much time left. It might be easier to
simply go out in 2-3 groups, order pizza from the place down the road or
even place a larger 'a la carte' order from another place.
= Schedule / Talks =
Thre's already a list of topics listed at the wiki, specifically:
http://projects.osmocom.org/projects/openbsc/wiki/OsmoDevCon2016#TalksDiscu…
I think we still have plenty of slots for talks, presentations,
discussions, workshops, you name it.
Each of you: Please take some time to think about
a) topics that you would be able to contribute to the event by
giving a talk or leading a discussion or workshop
b) topics that you would like to hear about from somebody else
Even if we do the actual scheduling ad-hoc at the event itself, it still
is useful to have some advance notice about the topics, as the
speaker(s) will need to prepare accordingly.
= Attendance =
If you have registered but will not attend, please let us know as we can
still adjust the amount of food we get delivered, and we might offer
your seat to somebody else.
If you did not register but are an active contributor to the project(s)
and would like to attend, let me know, too. I will let you know if
somebody cancels their attendance.
Looking forward to meeting all of you in Berlin soon.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
I've just pushed a fix of the BCD decoding for the MNC part of the RANAP
PLMN-Id to master: osmo-iuh.git d8013d1f8caf1c38c9b4191f0bbb411f6a4ff9d6
(along with a few other commits)
BTW, my apologies for the unrelated and unnecessary cosmetic change in
@@ -93,7 +98,8 @@ void test_asn1_helpers(void).
I've recently been pushing to osmo-iuh without posting for reviews, since the
code is in flux and not in production use yet. Let me know if I should post
patches instead.
~Neels
--
- Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Holger Freyther, Harald Welte
Hey,
Was scrolling across some of your code and saw some syntactical touching up
and optimizations that could be made. They're attached, if you'd like to
commit them.
Best,
Matthew Daiter
From: Holger Hans Peter Freyther <holger(a)moiji-mobile.com>
Add testcase to issue the subscriber create twice. db_create_subscriber
in db.c will first try to find the subscriber and if it exists, it will
update the "updated" column in the database.
Related: OS Issue #1657
---
openbsc/tests/vty_test_runner.py | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/openbsc/tests/vty_test_runner.py b/openbsc/tests/vty_test_runner.py
index 8db0825..620254e 100644
--- a/openbsc/tests/vty_test_runner.py
+++ b/openbsc/tests/vty_test_runner.py
@@ -307,6 +307,34 @@ class TestVTYNITB(TestVTYGenericBSC):
if classNum != 10:
self.assertEquals(res.find("rach access-control-class " + str(classNum) + " barred"), -1)
+ def testSubscriberCreateDeleteTwice(self):
+ self.vty.enable()
+
+ imsi = "204300854013739"
+
+ # Initially we don't have this subscriber
+ self.vty.verify('show subscriber imsi '+imsi, ['% No subscriber found for imsi '+imsi])
+
+ # Lets create one
+ res = self.vty.command('subscriber create imsi '+imsi)
+ self.assert_(res.find(" IMSI: "+imsi) > 0)
+ res2 = self.vty.command('subscriber create imsi '+imsi)
+ self.assert_(res2.find(" IMSI: "+imsi) > 0)
+ self.assertEqual(res, res2)
+
+ # Now we have it
+ res = self.vty.command('show subscriber imsi '+imsi)
+ self.assert_(res.find(" IMSI: "+imsi) > 0)
+
+ # Delete it
+ res = self.vty.command('subscriber delete imsi '+imsi)
+ self.assert_(res != "")
+
+ # Now it should not be there anymore
+ res = self.vty.command('show subscriber imsi '+imsi)
+ self.assert_(res != '% No subscriber found for imsi '+imsi)
+
+
def testSubscriberCreateDelete(self):
self.vty.enable()
--
2.6.3
Hello everyone,
a student college and me are using the osmo-sim-auth tool for a student
project. We have valid data for our SIM card since it's a special
ordered test SIM card. In 2G mode we get the correct RES value, but in
3G mode we always get only an AUTS value. We calculated the SQN value
from the AUTS to verify that we have the correct SQN value, but still we
only get AUTS as return.
I would be grateful to hear if any of you have an idea why this is
happening.
Best regards
Marco