== 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, sorry for my English. I installed osmocombb on Kali rolling. When i'm
trying to start my own bts, it works for 4 seconds, then i can see message
"Shutdown timer expired". Bellow you can see my config files. 1 screenshot
- 2 trx firmware on motorola c115. 2 screenshot, left - follow the
commercial BTS timer, right - starting MSC, SMS, HLR. 3 screenshot -
starting osmo-bts. 4 screen - my problem. I can connect with telnet to BSC
and BTS, but BTS - only for this 4 seconds, when it's up. I didn't replaced
filters on motorola, is it my problem? Or i just need to install smth more?
Also, if i write to the wrong mail list, tell me please where should i
write with my problem?
Hello all,
I have recently tried migrating an OsmoNITB setup to the new standard using mostly this guide right here: https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_I… <https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_I…>
However, while my nanoBTS works perfectly fine in the old setup, it just doesn not work at all in the new one. When I start osmo-bsc the LED on the BTS starts flashing green after a few seconds and then stops flashing and just stays green all the time, which is the expected behaviour. Unfortunately though, after another couple of seconds, the LED starts flashing green again and then turns red.
This is what the log shows:
BTS 0: Failure Event Report: Type=processing failure, Severity=critical failure, Probable cause=Manufacturer specific values: Fatal software error, Additional Text=l2_bch.c:1154
****
** l2_bch.c#1154:BCHbcchSItypeValid( prim_p->infoType )
** IPA_SW_FATAL_ERROR
** In task "TRX Proc:L2_BCH" @ (1063).
****
.
BTS 0: Failure Event Report: Type=processing failure, Severity=critical failure, Probable cause=Manufacturer specific values: Fatal software error, Additional Text=TRX Proc:L2_BCH:l2_bch.c#1154 (1063).
BTS 0: Failure Event Report: Type=processing failure, Severity=warning level failure, Probable cause=Manufacturer specific values: Software warning, Additional Text=31385:WARN:OAM_RES:trx_fatal_error_log.c#255:TRX has logged the error:
.
BTS 0: Failure Event Report: Type=processing failure, Severity=warning level failure, Probable cause=Manufacturer specific values: Software warning, Additional Text=31385:WARN:OAM_RES:trx_fatal_error_log.c#256:TRX Proc:L2_BCH:l2_bch.c#1154 (1063)
.
BTS 0: Failure Event Report: Type=processing failure, Severity=critical failure, Probable cause=Manufacturer specific values: Fatal software error, Additional Text=BCHbcchSItypeValid( prim_p->infoType ).
BTS 0: Failure Event Report: Type=processing failure, Severity=warning level failure, Probable cause=Manufacturer specific values: Software warning, Additional Text=31385:WARN:OAM_RES:trx_fatal_error_log.c#260:BCHbcchSItypeValid( prim_p->infoType )
20180328072641280 DLINP <0013> input/ipaccess.c:247 Sign link vanished, dead socket
20180328072641281 DLINP <0013> input/ipaccess.c:71 Forcing socket shutdown with no signal link set
20180328072641282 DCTRL <000e> osmo_bsc_ctrl.c:160 No more BTS connected, sending TRAP.
Now I'm not claiming that my config is already 100% correct but I feel like this isn't a configuration issue. I'm using the most recent nightly builds of the entire osmocom library.
Does anyone know what could be at fault here?
Kind regards,
Michael Spahn
Hi All,
I have a use case where I'd like to react to MS connecting to the
network, that is on initial IMSI ATTACH.
We already have the SMPP alert notification mechanism which can be used,
but unfortunately in SMPP the ms_availability_status only has 3 posible
values in the spec:
0: Available
1: Denied
2: Unavailable.
So currently if I react to status 0, this would also happen on periodic LURs
I could keep state separately but that sounds prone to errors.
The external process reacting to the alert notification could try
somehow to get the previous status from HLR or database, but that sounds
like a race condition.
One possibility might be to extend this with a further custom value 3:
Available (Initial Attach) or some such?
Any thoughts?
Hello All,
Sorry if this is an off-topic question, but I was wondering: does anyone know of any carrier that actually uses a UICC ('SIM card') with the ISIM application installed? So far all cards I saw have only USIM, maybe CSIM on them. I'd like to extend Benoit's card library with ISIM support, but there is no way to test my code right now, so I'm thinking about buying maybe a card.
Thanks.
Domi
Hi all
Somebody mentioned recently (at osmodevcon was it?) about writing to the
FPLMNS list to avoid service loss due to
LUR reject cause 11 (I think?)
I notice we don't seem to have this an a option in pySim-prog.py, so I
am wondering what tool was used?
Thanks!
(I noted the commented FIXME section for HPLMN in pySim.read.py and from
there was able to modify read address and read and decipher the FPLMN
list, although i did not get a nice readable output format yet.)
I received following error while compling osmo-trx on rasbian, i have already build libosmocore-0-11-0 from source and installed but despite this still unable to compile osmo-trx, any one can help to resolve the issue!
configure: error: Package requirements (libosmocore >= 0.11.0) were not met:
Requested ‘libosmocore >= 0.11.0’ but version of Osmocom Core Library is UNKNOWN
Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix.”
I have already build following components on Rasbian from source successfully
LimeSuite SoapySDR SoapyUHD libosmocore-0.11.0/ libosmocore-0.96.0
RegardsBabar
Dear list,
I have question about osmo-trx config with osmo-bts-trx.
if in osmo-bts-trx
osmotrx ip local 192.168.100.73
osmotrx ip remote 192.168.100.100
then what ip address fill on osmo-trx for limesdr.cfg?
bind-ip 192.168.100.73
remote-ip 192.168.100.100
Please correct me, cause I confuse osmo-trx won't running if not using same
ip as 127.0.0.1
well,
Does 127.0.0.1 is fine for only sms/call network in new split?
please advise. Thanks.
--
Best Regards,
DUO
Dear Osmocom community,
one of the main difficulty with OsmoCon 2017 last year was that nobody
submitted talks / discussions within the deadline, early enough to allow
for proper planning.
This lead to the situation where the sysmocom team had to come up with
a schedule/agenda on their own. Later on *much after the CfP deadline*,
people then squeezed in talks, making the overall schedule too full.
It is up to you to avoid this situation again in 2018 by submitting your
talk *RIGHT NOW*. We will be very strict regarding late submissions. So
if you would like to shape the Agenda of OsmoCon 2018, this is your
chance. Please use it.
We will have to create a schedule soon, as [almost] nobody will register
to a conference unless the schedule is known. If there's not sufficient
contribution in terms of CfP response from the wider community, don't
complain later that 90% of the talks are from sysmocom team members and
only about the Cellular Network Infrastructure topics.
You have been warned. Please make your CfP submission in time at
https://pretalx.sysmocom.de/osmocon2018/cfp
before the CfP deadline on
*2018-05-30 23:59 (Europe/Berlin)*
Thanks for your kind attention. Looking forward to meet with the
community at OsmoCon 2018 in October.
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)
Hello All
I wanted to ask your about something regarding user privacy leakage in the
broadcast channels. As i have been sniffing and testing myself and i found
that on the paging requests type 1 IMSI along with TMSI is sent.
I have came to understand that first sending two identifications is the
norm, but what i dont understand the high rate of sending IMSI as mobile
identification, and as per specification its noted that either TMSI OR IMSI
are sent, so does that by any mean could be a configuration issues from
the MSC/VLR side that should be changed, is this the norm? if its the norm,
then why using TMSI.
>From your experience what are the countermeasures you think that should be
taken from the operator side to protect against such information leaks, or
there is nothing that an operator can do much for this ?What could be the
different cases where the IMSI could be sent ?
Thanks
Dear All,
I was wondering whether anyone could please provide me a set of fully
working configuration files for a network-in-the-box setup with msc,
bsc, stp, hlr, mgw parts (not osmo-nitb). I have successfully compiled
all the required software from source, however, the migration guide is
incomplete and I cannot seem to find a simple tutorial for building an
osmo network from scratch using all the new components. I want to set up
a 2g network for calls/sms, i don't need gprs though.
Thanks!
Sincerely,
Toby M.
Hi all,
In libsmpp34 git there are examples on how to send an SMS (esme in
test_app directory, for example), but none to receive on SMS (from
osmo-nitb / osmo-msc tcp smpp port). In case anyone has some sample C
code to receive SMS using libsmpp34... it will help me.
; )
Thanks,
Rafael Diniz
Hi,
I stumbled upon LIBVERSION in src/Makefile.am of libsmpp34.
Is there a reason why it changed from 0:1:0 to 1:0:0? At least the names
of all exported symbols did not change!?
Thorsten
Good day, ladies and gentlemen
that's a great community you have. Mobile communications programming is a
demanding field requiring best developers.
I would be extremely grateful if you find time to answer a couple of my
simple questions.
I found myself reading the code of OsmoHLR project in order to understand
how it works and how the GSUP protocol works (it seems that the only
example of the GSUP-server is OsmoHLR).
How do you understand the code when you need to modify it or accomplish
other things that programmers usually do? It seems to not be documented
much.
Though I feel fluent in C, I find it hard to understand what is going on
there.
I've come up with an idea of running the OsmoHLR with a debugger. But in
order to see what actually happens in the code when the location update is
being performed (for example) I need to have the real phone and the real
BTS, don't I? How do you check that the code is working as intended?
Thank you very much!
Kind regards,
Mykola Shchetinin
Hi Shingy,
On Mon, May 14, 2018 at 07:51:28PM +0200, Shingirai Simba wrote:
> My name is shingy and like Nico it's my first post on mailing list.
welcome!
> I have access to both the Huawei BBU3900 and Old ZTE BTS at my
> university.(Not sure of model as yet). Would love to do that on my
> masters degree.
We would be more than happy to integrate any code for supporting more vendors
in OsmoBSC.
> Does anyone have an idea how we can get our hands on protocol traces.
I would expect your university has some BSC/network simulator or a core network+BSC
to get those BTSs up and running? How were they used so far?
If you have some kind of environment where the BTSs can be brought up, and you
have some additional E1 interface cards so you can trace the interface between
BSC and BTS, a significant step forward is made.
However, if you don't have protocol-level documentation from Huawei or ZTE,
and you cannot get any Abis protocol traces of BTS bring-up, it is almost
impossible to get them ever supported from Osmocom, sorry.
--
- 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)
Dear Osmocom community,
this sunday (May 13), I'm planning to do some of the pending migration of
osmocom.org services from our old server to a new machine.
This will cause some downtime. Hopefully it will be minimal, but I'm sure
there will be unexpected events that will mean some of the osmocom.org services
will be unavailable at some point during Sunday.
In terms of priorities, gerrit is high up on the list, so this will be my primary
focus. If that goes well, redmine is the next on the list.
In case you're interested in the gory details, https://osmocom.org/issues/3076
is the overview ticket.
--
- 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)
Hello everybody,
My name is Niko, and it's my first post on mailing list.
Is it possible to use OpenBSC together with Huawei BBU3900, or Ericsson
RBS6601?
Thanks in advice
Niko
Hi,
I am new to this list.
I use ubuntu 14.04.02. I am trying to configure/compile osmocom-bb.
I have a few questions and problems:
According to the src/README.building file, I should get the arm toolchain
from gnuarm.com
This should be updated, gnuarm.com doesn't have any downloads any more.
Instead I installed gcc-arm-linux-gnueabi from ubuntu reps
1) normal gcc seems to support x-compiling for arm CPUs. Why not use that?
2) Your stock Makefile tests for CROSS_HOST against arm-elf-gcc. This
should be updated to test also against arm-linux-gnueabi-gcc from
gcc-arm-linux-gnueabi package
3) configure warnings:
configure: WARNING: unrecognized options: --disable-tests, --disable-tests.
Should be disabled if not supported any more
checking for arm-linux-gnueabi-mt... no
checking for mt... mt
configure: WARNING: using cross tools not prefixed with host triplet
Is this a problem?
4) configure asks for libosmovty. Despite listed, couldn't find it under
osmocom libraries any more:(
Where can i download it from?
TIA,
Nikos
Hello everyone
Can anyone help me to connect two nanobts via Linux call router.I have tested with multitrx mode .but my problem is to connect two nanobts in different locations
Thanks
Regards
Rajitha
Sent from my iPhone