OpenBSC March 2014

openbsc@lists.osmocom.org

27 participants
71 discussions

Start a nNew thread

OpenBSC unsubscribe notification
by mailman-bounces＠lists.osmocom.org 30 Mar '14

30 Mar '14

jmho(a)jmho.de has been removed from OpenBSC.

1 0

Fwd: OpenBSC and Roaming
by Sahil Gupta 29 Mar '14

29 Mar '14

Hi there, I'm fairly new to the mobile world and am still coming to terms with a whole new world of terminologies. The project is to test out a theory in my lab before wanting to scale this at a larger level for commercial purposes. The intent is to be able to have roaming available with a roaming aggregator in the United States with a small-scale mobile network enabled using OpenSource software. We are probably looking at implementing no more than 15 BTS's nationwide to attract roaming customers at high traffic locations. Our roaming aggregator would like us to send them MAP SS7 Messages from our MSC. My understanding of the requirements so far are: 1 x BTS (this could be a PC with some radio cards or something like a nanoBTS) 1 x MSC/BSC/VLR We won't be issuing any sim cards on our own network in the long run and hence I don't see the point in us having a unique HLR. Are there any gurus here that would be willing to share their intelligence? -- Thanks, Sahil -- Thanks, Sahil

3 5

3 OpenBSC moderator request(s) waiting
by openbsc-bounces＠lists.osmocom.org 29 Mar '14

29 Mar '14

The OpenBSC(a)lists.osmocom.org mailing list has 3 request(s) waiting for your consideration at: https://lists.osmocom.org/mailman/admindb/openbsc Please attend to this at your earliest convenience. This notice of pending requests, if any, will be sent out daily. Pending posts: From: tlab.tester(a)googlemail.com on Mon Mar 3 13:01:09 2014 Subject: Unsubscribe Cause: Message may contain administrivia From: zielonka.markus(a)googlemail.com on Mon Mar 3 15:16:07 2014 Subject: unsubscribe Cause: Message may contain administrivia From: holger(a)freyther.de on Thu Mar 20 21:44:00 2014 Subject: DRAFT for a 30C3 report. Care to review? Cause: Message body is too big: 1033152 bytes with a limit of 400 KB

1 0

Implement gsm340_{gen_,}scts() without using tm_gmtoff
by Daniel Willmann 28 Mar '14

28 Mar '14

Hello, this patch series depends on two patches from Alexander (once they sign handling is fixed): sms: Fix gsm340_scts() to correctly decode absolute valid times. sms: Fix support of negative timezone offsets in gsm340_gen_scts(). The first patch adds a test case to check that gsm340_scts is the inverse of gsm340_gen_scts. The next patches add a helper function to calculate the gmt offset and use those in the *_scts functions. The helper function is somewhat ugly, but it is the only portable way I could find to get the GMT offset. Ideas welcome Regards, Daniel -- - Daniel Willmann <dwillmann(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Schivelbeiner Str. 5 * 10439 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte

3 7

OpenBSC unsubscribe notification
by mailman-bounces＠lists.osmocom.org 28 Mar '14

28 Mar '14

rajeevvats(a)coraltele.com has been removed from OpenBSC.

1 0

3 OpenBSC moderator request(s) waiting
by openbsc-bounces＠lists.osmocom.org 28 Mar '14

28 Mar '14

1 0

3 OpenBSC moderator request(s) waiting
by openbsc-bounces＠lists.osmocom.org 27 Mar '14

27 Mar '14

1 0

[PATCH 6/6] sms: Fix gsm340_scts() to correctly decode absolute valid times.
by Alexander Chemeris 26 Mar '14

26 Mar '14

- Support negative timezone offsets decoding. - Correctly account timezone offset and artificial offset mktime() introduces. -- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. / ООО УмРадио https://fairwaves.co

2 7

[PATCH 5/6] sms: Fix support of negative timezone offsets in gsm340_gen_scts().
by Alexander Chemeris 26 Mar '14

26 Mar '14

-- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. / ООО УмРадио https://fairwaves.co

2 4

[PATCH] sms: Proper decoding and storage of SMS validity period.
by Alexander Chemeris 26 Mar '14

26 Mar '14

- Use time_t instead of abstract minutes to store validity time to make sure we support all possible values. - Return UNIX time from it to support both relative and absolute expire times. - Pass a current time to gsm340_validity_period() to compute the absolute expire time if a relative time is specified. What time is "current" is to b - We also introduce SMS_DEFAULT_VALIDITY_PERIOD macros to reduce number of magic values. PS This is a first patch of a series of patches which fix SMS validity time decoding. I'm cleaning the patch set and want to see if this patch is fine, as other patches rely on it. -- Regards, Alexander Chemeris. CEO, Fairwaves, Inc. / ООО УмРадио https://fairwaves.co

3 13

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC March 2014