== OsmoCon 2018 ==
OsmoCon (Osmocom Conference) 2018 is the technical conference for
Osmocom users, operators and developers!
We are happy to announce the date of OsmoCon 2018. It has been scheduled
on October 18 + 19, 2018 and will happen in Berlin, Germany.
For the second time, the Osmocom Conference brings together users,
operators and developers of the Osmocom Open Source cellular
infrastructure projects, such as OsmoBTS, OsmoBSC, OsmoSGSN, OpenGGSN
and others.
Join us for two days of presentations and discussions with the main
developers behind Open Source Mobile Communications, as well as
commercial and non-profit users of the Osmocom cellular infrastructure
software.
You can find some initial information in our wiki at
http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2018
which will be updated as more information becomes available.
== Call for Participation ==
We're also at the same time announcing the Call for Participation and
call on everyone with experiences to share around the Osmocom member
projects to submit talks, workshops, discussions or other proposals.
You can find the CfP at https://pretalx.sysmocom.de/osmocon2018/cfp
We are particularly looking for contributions about:
* updates on features/functionality/status of individual Osmocom projects
* success stories on how Osmocom projects are deployed in practice
* migration from OsmoNITB to the post-NITB architecture
* tutorials / workshops on how to setup / analyze Osmocom projects
* statistics, reporting, operations aspects of Osmocom projects
* third-party open source utilities to be used with Osmocom projects
Looking forward to meeting many existing and new Osmocom users at OsmCon
this October!
Regards,
Harald Welte
--
- 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)
Hi,
I'm wondering where I can source the Siemens BS11 firmware. It looks
like OpenBSC is not providing any firmware images.
# bs11_config -p /dev/ttyUSB0
bs11_config (C) 2009-2010 by Harald Welte and Dieter Spaar
This is FREE SOFTWARE with ABSOLUTELY NO WARRANTY
LMT LOGON: ACK
PHASE: 1 Software required Abis-link: Down
No valid Safety Load file "BTSBMC76.SWI"
Thanks,
Andrew
Recently, dexter has added this commit:
http://git.osmocom.org/osmo-bsc/commit/?id=b9d3c71af347906cef2bb54be57418a9…
Our osmo-gsm-tester tests fail to pass since this commit thwarts all L3
Complete.
The commit refuses to compose a Layer-3-Complete message if the speech codecs
supported by the BSS cannot be included, either because none are configured, or
because none remain after all the criteria of finding codecs permitted.
It may be mandatory to include the speech codecs or not, what bugs me is that
we even refuse a mere attach to the network just because speech codecs are not
available. Those only become interesting much much later, only for voice.
The backwards-compatibility consideration: configurations that have always
worked well are suddenly likely to fail. Users will wonder what happened, and
we need to avoid that.
I think instead of thwarting L3 Complete entirely, we should loudly error-log,
but still send out an L3 Complete while simply omitting the speech codec list.
It might be a spec violation for AoIP, but practically works fine, AFAICT.
Again, the way to handle this spec violation should be to log an error, not to
break all access.
The alternative would be, IMHO, to abort osmo-bsc startup right away,
complaining about misconfiguration, if that is possible at all. But no.
Let's allow L3 Complete even in the absence of speech codecs that all
participants support. There are USSD and SMS and GPRS that are all going to be
broken just because codecs don't match.
The commit right after sets, apparently, the full list of codecs as supported
by default. Is that not working? Do we override that in the osmo-gsm-tester
config? Either way, even if the allowed codecs are all configured properly, but
there is simply no match between MS,BTS,BSC,MSC, we would still refuse LU,
right?
Hence I would like to revert above commit / replace with error logging.
@dexter, what do you think? Am I making sense, or am I missing something?
Thanks!
~N
P.S.: in that commit log, it would have been nice to mention the config items
that would help solve the situation. It's not entirely clear to me yet what the
misconfigured items are on the osmo-gsm-tester setup.
Hi All.
This is very brief, but something that's been on my mind to make a
ticket about.
I realise maybe it's better to ask first if there is a plan.
The issue is about restarting MSC or BSC (or both).
I still really haven't looked at the split setup enough yet, in terms of
getting familiar with all the info available from logging in both
programs, so I don't have a good analysis of what's going on. Sorry.
But my point here is not to describe a bug to be fixed but just asking
in general what is the strategy to deal with daemon restarts,
intentional or not. Is there a plan to implement some kind of
non-volatile state?
The problem in terms of usability, from simple observation:
In the case of restarting the MSC with two phones connected, of course
the phones don't notice anything. One now needs to attempt a call setup
at least 3 times, including a call setup attempt from the "callee" phone
before we can even call it.
I tried restarting both BSC and MSC, in various orders, and I did not
get a satisfactory result. Of course, restarting the BSC restarts
osmo-bts which causes (some) phones to notice the temporary loss of
BCCH, but of course no LUR or anything as LAC doesn't change, so there's
some state that is not getting set right someplace on restart, as I
said. both phones need to interact before one of them can be called.
Yeah, so, sorry for the lame analysis, but I think this should be pretty
easy to reproduce, and at this time there are people who are MUCH more
familiar with osmo-msc and osmo-bsc than me, who probably know what I'm
talking about and can comment.
Thanks!
k/
Hi all
Another one not quite ready for a ticket, but maybe worth mentioning here.
A while back I noticed a phone of mine was holding channels open all the
time. Turns out in does checks for call forwarding status and such on
camping.
This got fixed in Legacy OpenBSC:
https://gerrit.osmocom.org/#/c/openbsc/+/503/
I noticed this, or something similar is back with the split setup.
Try dialing *#21# for example. or pick a code from here:
http://www.geckobeach.com/cellular/secrets/gsmcodes.php
Then make a call. On some phones you can't, but if it does proceed, then
hangup. On all the phones I tried you now have not only a lingering
SDCCH, but also a TCH/F and on one phone, it doesn't ever go away, until
you turn off the phone, or drop the BCCH.
sorry again for the lame bug report. I don't want to forget it and I
can't pay it due attention in the coming days.
k/
[private hacking hat on]
Thinking ahead to the 35C3, I have tinkered with IuUP a bit.
I'm at the point where I have an IuUP core net node in the osmo-mgw, which
auto-detects IuUP peers and removes IuUP headers coming from a 3G RNC, and
inserts IuUP headers in RTP going to a 3G RNC. So far we were merely hacking
over the IuUP header to mimick an Initialization ACK, and were otherwise just
handing the IuUP headers through from one 3G peer to the other. I realized now
that hacking up an Initialization ACK like we currently do on osmo-mgw master
produces a header CRC error, which the femto cells we currently tested
completely don't care about, thankfully.
Ok, so now I am de/encapsulating the IuUP from/to RTP, so that IuUP is present
only on the last leg to/from an RNC. 3G to 3G calls still work well with that,
now also having correct IuUP header CRCs.
And, the naive idea was that now the 2G would simply understand the RTP from
the 3G and vice versa. But that's not the case, apparently. The phones at best
crackle some random artifacts.
I picked a codec-list of fr3 hr3 in osmo-bsc, and tried a few AMR rates (12.2k,
5.9k, 5.2k).
So I think there's still some fundamental concept that I'm lacking. Is there
anyone more familiar with AMR and/or the way 3G encodes audio, and whether
there's a simple way to make them match? Where should I read on?
Would a call router like we use in the C3 POC be able to transcode when the
IuUP is stripped? (I'm not even sure what the POC side is doing to connect SIP
with GSM.)
I've noticed the laforge/iu_up branch in libosmocore only later, which includes
an FSM that apparently does only state transitions so far. My patch has no FSM
yet, since all I see on the wire is Init->InitAck, then Data PDUs, and maybe an
occasional error report. Do those FSM states convey a secret of making 3G
encoding readable by 2G?
Various pcaps of the status quo are here:
http://kleinekatze.de/eeD0ouCo/
My IuUP branch: osmo-mgw neels/iuup
http://git.osmocom.org/osmo-mgw/log/?h=neels/iuup
IuUP protocol spec: 3GPP TS 25.415 (I've so far ignored most of it)
~N
Hi all.
Was just thinking today about if it was ever considered to write the VTY
history out to a file on exiting (and load it on startup)
I'm quite the fan of the up arrow and it's been something that sometimes
annoys that I have no history after leaving the VTY.
It would seem reasonably trivial to implement, and I suppose you could
write out to files in $HOME/.osmo-bsc_history or $HOME/.config or somesuch.
Just wondering if this was ever discussed before, if there's any
unforseen problem with it on my part + if it would be a desirable
feature for anybody else?
k/
Dear all,
In this mail I would like to negotiate and discuss some details
about further development of the Osmocom CNI, in particular the
way of handling of SMS messages.
At this time, all SMS messages within the Osmocom CNI are terminated
at OsmoMSC. There we have some basic routing configuration, either
internal, or SMPP. This approach has some disadvantages, at least:
- MSC is not a proper place for terminating SMS messages,
in commercial networks it's usually done by SMS Center;
- in case if a network based on the Osmocom CNI does contain
multiple MSCs, one has to configure / update the SMS routing
configuration for each MSC individually;
- one would have to use SMPP in order to deliver SMS messages
to / from commercial networks, which in most cases "speak"
either MAP, or DIAMETER, or even both, but not SMPP;
- using SMPP (as it's the only external interface available)
involves the need to encode and decode complex SMS protocol,
what is not desired in some situations.
This is why it was decided to rip the SMS routing out of OsmoMSC,
and use generic (for Osmocom CNI) GSUP protocol as the transport.
Please see OS#3587 for more details about "SMS over GSUP".
So, we actually need a separate process, let's call it "OsmoSMSC"
in quotes for now, as I am not sure about the proper name. It
should implement at least basic functionality of the SMS Center.
Since we are using OsmoHLR as the main / central gateway in the
Osmocom CNI for all GSUP communications, this to be discussed
"OsmoSMSC" should basically be connected to OsmoHLR.
What I would like to discuss is how should we implement "OsmoSMSC"?
I think there are two possible ways: either write it from scratch,
or fork some existing project. Implementing from scratch would
require much more efforts and time than forking an existing
SMSC implementation, for sure.
I've recently discovered a project called Kannel - an Open Source
WAP and SMS gateway written in C and distributed under the Kannel
Software License, please see: https://www.kannel.org/index.shtml
What do I personally like:
- helpers for OTA configuration (e.g. WAP, MMS settings) messages;
- written in C and using automake as the build system;
- high performance (hundreds of messages per second);
- 7-bit, 8-bit and Unicode message coding.
So we could fork this project as "OsmoSMSC",
and extend in the following way:
- integrate generic Osmocom logging;
- integrate VTY interface and generic configuration;
- implement GSUP client from OsmoHLR.
I already started to read the source code and documentation.
If anyone has any experience with Kannel, please share!
And finally, how should we name "OsmoSMSC"? :)
With best regards,
Vadim Yanitskiy.
Thinking ahead to the 35C3, I have tinkered with IuUP a bit.
I'm at the point where I have an IuUP FSM which auto-detects IuUP peers and
removes IuUP headers coming from a 3G RNC, and inserts IuUP headers in RTP
going to a 3G RNC. So far we were merely hacking over the IuUP header to mimick
an Initialization ACK, and were otherwise just handing the IuUP headers through
from one 3G peer to the other. I realized now that hacking up an Initialization
ACK like we currently do on osmo-mgw master produces a header CRC error, which
the femto cells we currently tested completely don't care about, thankfully.
Ok, so now I am de/encapsulating the IuUP from/to RTP, so that IuUP is present
only on the last leg to/from an RNC. 3G to 3G calls still work well with that,
now also having correct IuUP header CRCs.
And, the naive idea was that now the 2G would simply understand the RTP from
the 3G and vice versa. But that's not the case, apparently. The phones at best
crackle some random artifacts.
I picked a codec-list of fr3 hr3 in osmo-bsc, and tried a few AMR rates (12.2k,
5.9k, 5.2k).
So I think there's still some fundamental concept that I'm lacking. Is there
anyone more familiar with AMR and/or the way 3G encodes audio, and whether
there's a simple way to make them match? Where should I read on?
Would a call router like we use in the C3 POC be able to transcode when the
IuUP is stripped? (I'm not even sure what the POC side is doing to connect SIP
with GSM.)
Various pcaps of the status quo are here:
http://kleinekatze.de/eeD0ouCo/
My IuUP branch: osmo-mgw neels/iuup
http://git.osmocom.org/osmo-mgw/log/?h=neels/iuup
IuUP protocol spec: 3GPP TS 25.415 (I've so far ignored most of it)
~N
Hi Community,
Is the auto provisioning (subscriber-create-on-demand) of OSMO-NITB is still present or available in OSMO-BSC/OSMO-MSC/OSMO-HLR version?
We tried to use the “authentication optional” under OSMO-MSC configuration but still, it checks if the subscriber is provisioned in OSMO-HLR.
Best Regard,
Ron Menez
ron.menez(a)entropysolution.com<mailto:ron.menez@entropysolution.com>
