There is an urgent need to migrate our most important public
infrastructure to a new server, and I will be doing that on
*Sunday, July 19 2020*, starting about 9am CEST.
The migration involves redmine (main osmocom.org website), jenkins, gerrit,
git, and cgit.
In theory, the migration should be quick. I would expect (significantly)
less than one hour of downtime. However, we all know Murphys law.
Services not affected are mail (including mailman lists), ftp, dns. So in case
of doubt, we can still use mailing lists to communicate.
In case anyone urgently needs osmocom source code on Sunday morning
during the downtime: There are public mirrors available on github.
Regards,
Harald
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Dear Osmocom community,
the first schedule of the 2018 incarnation of OsmoCon 2018 has been announced,
see http://osmocom.org/news/99 for the announcment and
https://pretalx.sysmocom.de/osmocon2018/schedule/ for the actual schedule.
At OsmoCon, we are not targetting developers, but more the wider community
and Osmocom users. It would be great to meet many of you and hear more
about your relation to Osmocom.
Tickets are available from https://pretix.sysmocom.de/sysmocom/osmocon2018/,
and until August 31st the early bird discount still applies.
For those with a community / "just for fun" background and no employer
that would cover the ticket, we have a number of subsidized community discount
vouchers available. See the OsmoCon 2018 wiki page at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2018
for more information.
Looking forward to meeting as many of you as possible in roughly two
months from now,
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)
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)
== 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)
Dear all,
I've written up a "short" review of what I perceive as the most important
events in the Osmocom Cellular Infrastructure projects in 2017.
See http://osmocom.org/news/84 for all details, or below for a raw copy+paste:
h1. Osmocom Review 2017
This is a review of the most significant changes and events in the Osmocom Cellular Infrastructure projects in 2017
h2. January 2017
* announce of first ever public [[OsmoCon:]] conference in April
* osmo-bts
** Add Abis OML failure event reporting
** fix memory leaks in osmo-bts-{sysmo,lc15} at every channel activation
* openbsc/osmo-bsc
** support multiple UARFCNs in SI2quater
* osmo-hlr
** add test suite for 2G and 3G authentication
** fix UMTS AKA re-sync
h2. February 2017
* weekly manual testing with related weekly test reports to mailing list
* "heads-up about the (lack of a )future of osmo-nitb":http://lists.osmocom.org/pipermail/openbsc/2017-February/010300.html
* "heads-up about libosmo-sccp SIGTRAN work":http://lists.osmocom.org/pipermail/openbsc/2017-February/010274.html
* "sysmo-usim-tool":http://lists.osmocom.org/pipermail/openbsc/2017-February/010317.html
* libosmo-abis
** unix domain socket support (for Ericsson L2TP)
* osmo-bts
** fix AMR HR DTX FSM logic
** fix SACCH sending fo system information with enum value > 7
** osmo-bts-trx: fix RXGAIN and POWER parameters on second TRX
** fix TCH/H interleaving table bit position
** sysmoBTS 1020/1100: slow power ramp-up on TRX enable
* osmo-sgsn
** fix PDP context activation memory allocation bug
** integrate support for UMTS AKA
* openggsn
** fix kernel-gtp tunnel creation/removal for GTPv1
** release 0.93
h3. March 2017
* "cgit improvements":http://lists.osmocom.org/pipermail/openbsc/2017-March/010448.html (about page, change-ID hyperlinks, issue hyperlinks)
* Add README.md files to all our repositories
* libosmocore
** migrate gsm 05.03 coding from OsmoBTS to libosmocore
** fix SQN / SEQ handling in UMTS AKA
** 3GPP AoIP message encoding/decoding
* libosmo-abis
** fix ever-increasing jitter buffer
* libosmo-netif
** handle SCTP in in stream server
** doxygen documentation on stream an datagram modules
* osmo-bts
** octphy: CBCH support
** include MS timing offset in RSL measurements
* osmo-sgsn
** handle IMSIs with leading zeroes
* osmo-bsc
** fix T3186 encoding in SI13
** Improved Ericsson OM2000/RBS2000 support
** new ctrl2soap proxy in python
* osmo-hlr
** add CTRL interface
** fix SQN/SEQ handling in UMTS AKA
h3. April 2017
* "update of coding style for longer line lengths":http://lists.osmocom.org/pipermail/openbsc/2017-April/010502.html
* [[osmo-dev-con:OsmoCon2017]] and [[osmo-dev-con:OsmoDevCon2017]]
* libosmocore
** "control interface for osmo_fsm":http://lists.osmocom.org/pipermail/openbsc/2017-April/010542.html
* libosmo-netif
** fix file descriptor leak in error paths
** work around linux kenrel SCTP bug with sender_dry_events
** RTP marker bit support
* libosmo-sccp
** Add new [[libosmo-sigtran:]] library with SS7 AS/ASP Link/Linkset handling, M3UA support, new FSM based SCCP implementation
** Add [[osmo-stp:]] program
* osmo-bts
** inform BSC of PCU disconnect
** fix measurement reporting period
** exclude idle channels from uplink measurement processing
** octphy: measurement reports
h3. May 2017
* libosmocore
** fix embedded builds
** import and generalise 'sercomm' from osmocom-bb into libosmocore
** SSE optimized convolutional coder
** fix wrong GSM FR codec SID frame generation
** doxygen docs for libosmocoding
* osmo-bsc
** TS 04.14 mobile station side loop control
* osmo-bts
** consistently check all RSL and OML TLVs for minimum length value
** fix bit-order in every HR codec parameter (spec compliance)
** OML get/set attribute handling
** SI2quater support
** bypass radio link timeout for lab testing
* osmo-bsc
** PCU socket support for BSC-colocated PCU for Ericsson RBS2000
** reelase 1.0.1
* "M3UA and SUA testing as part of jenkins":http://lists.osmocom.org/pipermail/openbsc/2017-May/010698.html
* "osmo-gsm-tester produces successful runs with NITB as well as new AoIP":http://lists.osmocom.org/pipermail/openbsc/2017-May/010760.html
h3. June 2017
* libosmocore
** doxygen autobrief
** doxygen documentation for libosmogb
* osmo-bts
** use CLOCK_MONOTONIC timer for GSM frame timer
** PDTCH loopback support
h3. July 2017
* "Plan for openbsc.git split and code review":http://lists.osmocom.org/pipermail/openbsc/2017-July/010914.html
* libosmocore
** PDP charging characteristics in GSUP
** PRBS sequence generators
** multicast IP related helper functions
** 'make release' target
* libosmo-sccp
** SCCP address book
* osmo-bts
** new virtual BTS @osmo-bts-virtual@ for testing without radio hardware
** don't send dummy UI frames on unused BCCH slots on TC=5
** GSMTAP: don't log/send fill frames consisting of only padding
* osmo-hlr
** change to default GSUP port 4222
h3. August 2017
* "Support for SMPP Delivery Receipt / GSM03.40 Status Report":http://lists.osmocom.org/pipermail/openbsc/2017-August/011023.html
* "Jenkins now executing M3UA, SUA and GGSN testsuite":http://lists.osmocom.org/pipermail/openbsc/2017-August/011043.html
* libosmocore
** fix crash in lapd_est_req()
* libosmo-abis
** release 0.4.0
* osmo-bts
** osmo-bts-trx: fix MS power control loop
** release 0.6.0
** support sending/removing SI13 to/from PCU
* osmo-bsc
** indicate R99+ MSC in SI3 to enable UMTS AKA over GERAN
* osmo-sgsn
** properly report GERAN/UTRAN mode in PDP CTX ACT REQ to GGSN
* osmo-msc
** implement IuCS support
** split openbsc.git into osmo-bsc.git, osmo-msc.git and osmo-sgsn.git
* openggsn
** Add IPv6 address pool and IPV6 user (inner) plane support
** release 0.94
h3. September 2017
* libosmocore.git
** "'show talloc-context' VTY introspection":http://lists.osmocom.org/pipermail/openbsc/2017-June/010771.html
** CTRL parsing unit tests
** unification of vty exit/end commands
* osmo-hlr
** CTRL interface tests
--
- 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 all,
starting from today, we're packaging LimeSuite and (as needed) other
dependencies required for using osmo-trx/osmo-bts-trx with LimeSDR in
the network:osmocom:nightly and network:osmocom:latest feeds.
The package versions are fixed and are not tracking "master" of e.g.
limesuite. Only the Osmocom packages are tracking master.
Due to the unfortunate fact that the first LimeSuite with osmo-trx
support (17.09.0) requiring a cmake later than what Debian 8 ships,
LimeSDR support is not working with all of the Distributions/Versions
that the rest of the Osmocom stack supports.
It appears that LimeSuite also has some build issues on ARM
architectures, about which I've submitted an upstream bug report at
https://github.com/myriadrf/LimeSuite/issues/151
But at least for x86_64 and i586 architecture, LimeSDR should be
supported by the Osmocom package feeds , on Debian 9.0, Ubuntu 16.04,
16.10, 17.04 and 17.10.
We will shortly use those packages as part of our osmo-gsm-tester setup
at the sysmocom lab, at which point they should receive extensive
testing.
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)
Dear Osmocom community,
I would like to point out that at sysmocom, we're currently (again)
hiring [1]. If you happen to have an interest in open source cellular
communications and are fluent in C language development, we would
love to hear from you.
sysmocom probably doesn't need any introduction here, but just in case:
The company was founded by Holger Freyther and Harald Welte, two of the
leading OpenBSC and Osmocom developers from the very early days of the
project. Today we are responsible for by far the largest number of commits
to the Osmocom GSM/3G infrastructure related git repositories.
Among our current priorities are automatic testing for the GPRS PCU,
generalization of the OsmoMGW media gateway, support for load-based hand-over,
inter-BSC hand-over as well as various improvements on the lower layers
of the GPRS protocol stack.
We're very dedicated to the cause in furthering the capabilities of
open source cellular infrastructure from 2G to 4G. We believe in
working upstream, no open core or dual licensing.
If you have an interest working with an enthusiastic, strong technical
and dedicated team of Osmocom hackers, please don't hesitate to let me know,
best by e-mail to jobs(a)sysmocom.de
Thanks,
Harald
p.s.: I hope this kind of message is not disturbing to anyone. I think
it is important to the Osmocom project to have more paid people working
on the stack, so it is justified. The positions we are seeking to fill
will work [almost exclusively] on Osmocom, so it's not a random job ad
but in the very interest of Osmocom, and hence on-topic for this list.
[1] https://www.sysmocom.de/jobs/
--
- Harald Welte <hwelte(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
* Geschaeftsfuehrer / Managing Director: Harald Welte
Hi all,
the Osmocom Conference 2017 last week was an overwhelming success. We
received lots of positive feedback from all sides. Thanks to all the
speakers, to the attendees as well as to the anonymous sponsor of the
travel grant funds.
It is my great pleasure that due to the great support by C3VOC (The CCC
Video Operation Center), we have full recordings of all talks given at
OsmoCon 2017.
You can find the videos on the C3VOC site at
https://media.ccc.de/search/?q=osmocon
They are also linked individually from the OsmoCon 2017 homepage at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017
I hope the video recordings will be of help for everyone who could not
make it to the event in person.
We will also be collecting the slides and put them up on the wiki during
the next few days.
Please don't hesitate to raise any feedback and/or questions.
Technical feedback/questions regarding Osmocom software / projects
should be addressed to the appropriate mailing lists, such as
openbsc(a)lists.osmocom.org.
Feedback to the organizers should be sent to osmocon2017(a)sysmocom.de.
Looking forward to the next OsmoCon, which we'll expect to be spanning
ore than just a single day.
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)
OsmoCon 2017 updates
There are some updates related to OsmoCon2017, the first Osmocom
Conference, held on April 21st, 2017 in Berlin, Germany.
See http://osmocom.org/news/68 for the web version of this announcement.
== Summary ==
Summary (for those too busy to read the full post):
* Schedule of talks has been released
http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017#Schedule
* Travel Grants available for participants who are otherwise unable to
travel to Berlin: http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017_TravelGrants
* Social Event details available, including menu:
http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017_SocialEvent
* April 21st is approaching fast, make sure you get your Ticket in time.
Limited number of seats available
http://shop.sysmocom.de/products/ticket-for-osmocon-2017
== Details ==
=== Schedule has been released ===
The list of talks with their abstracts has been on the website for quite
some time, but now we actually have put together a schedule based on
those talks.
Please see
http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017#Schedule
for the schedule.
As you can see, the day is fully packed with talks about Osmocom
cellular infrastructure projects. We had to cut some talk slots short
(30min instead of 45min), but I'm confident that it is good to cover a
wider range of topics, while at the same time avoiding fragmenting the
audience with multiple tracks.
=== Travel Grants ===
We are happy to announce that we have received donations to permit for
providing travel grants!
This means that any attendee who is otherwise not able to cover their
travel to OsmoCon 2017 (e.g. because their interest in Osmocom is not
related to their work, or because their employer doesn't pay the travel
expenses) can now apply for such a travel grant.
For more details see
http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017_TravelGrants
and/or constact osmocon2017(a)sysmocom.de.
=== Social Event ===
Tech Talks are nice and fine, but what many people enjoy even more at
conferences is the informal networking combined with good food. For
this, we have the social event at night, which is open to all attendees.
See more details about it at
http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017_SocialEvent
--
- 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 all,
not everyone might have seen the news item that was posted in late
December on our website at http://osmocom.org/news/62
I'm looking forward to receiving your proposal on how you would
contribute to the Osmocom project if you were to receive one of those
free 3.5G femtocells.
Quote of the news item below:
------
So please excuse me to cross-post this over several Osmocom project
mailing lists. I know that a number of people have either hacked on
femtocells in the past, or at least expressed interest in doing so...
Osmocom's support for 2G/GSM is mature and widespread. Since 2016, we're
taking on the next level: 3G/3.5G. The key to running your own 3G
network is to obtain actual 3G cell hardware -- here is an exciting
opportunity to get started:
No less than 50 femtocells will be given away for free by sysmocom, one
of the main drivers of the Osmocom project. To receive a free 3G
femtocell, tell us how you will help the Osmocom project drive 3.5G
forward if you had one, before the end of January 2017. This marks the
launch of the 3.5G Acceleration Project, backed by the Osmocom
community. Join us!
Find further details on the 3.5G Acceleration Project and receiving your
own 3G femtocell for free at https://sysmocom.de/downloads/accelerate_3g5_cfp.pdf.
------
Best regards and happy hacking,
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)
