OpenBSC November 2021

openbsc@lists.osmocom.org

18 participants
20 discussions

OSMO-MSC External MNCC integration with FeeSwitch
by Justin 07 Dec '21

07 Dec '21

Hi Osmocom, I'm trying to integrate the FreeSwitch as my external MNCC in my test lab using split stack. Currently, I'm getting an error message on FreeSwitch SIP/2.0 400 Missing Contact Header. I'm little bit confused with the error and I don't know where to troubleshoot this. I've attached my osmo configurations and pcap trace for your reference. Hoping for your reply. Thank you. Regards, Justin Mark Repollo

5 16

AGCH Channel via virtual Um
by Ivan Babanov 27 Nov '21

27 Nov '21

Hello all! I'm sorry for a stupid question, but I can't find an answer by myself. We are using Osmocom solution in University to demonstrate to students how GSM works. We have and fully virtualized workplaces with osm-bts-virtual and osmocom-bb UE via virtual Um. We are making an IMSI Attach procedure and capturing traces with wireshark. Virtual Um messages are visible in wireshark traces with "gsmtap" filter. According standart description, after RACH request UE should receive channel assignment via AGCH channel. But AGCH is not visible in traces. Am I wrong in my expectations somewhere? I tried to filter out messages, tried to filter gsmtap.chan_type == 4 but still no luck. Thank you Vania

1 0

"OsmoDevCall" on Nov 25, 2021: Control/User Plane Separation (CUPS) + PFCP
by Harald Welte 24 Nov '21

24 Nov '21

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at November 25, 2021 at 20:00 CET (yes, Thursday instead of Friday this time!) at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:10 presentation "Control/User Plane Separation (CUPS) + PFCP" by laforge 21:00 unstructured supplementary social event [*] Attendance is free of charge and open to anyone with an interest in Osmocom or open source cellular technologies. More information about OsmoDevCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall Looking forward to meeting you on Friday. Best regards, Harald [*] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - 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)

2 1

Osmocom CNI release 202111
by Pau Espin Pedrol 19 Nov '21

19 Nov '21

Dear all, I am pleased to announce new tagged releases for Osmocom Cellular Network Infrastructure components. Find more information about the release here [1]. Osmocom "Latest" repositories in OBS [2] should already contain packages for the new versions. OpenEmbedded related meta-layers such as meta-telephony usual stable/testing branch "201705" [3] have also been updated to build recipes for new versions. Regards, Pau [1] https://osmocom.org/news/152 [2] https://osmocom.org/projects/cellular-infrastructure/wiki/Latest_Builds [3] https://git.osmocom.org/meta-telephony/log/?h=201705 -- - Pau Espin Pedrol <pespin(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

2 1

"OsmoDevCall" on Nov 12, 2021: icE1usb in practice
by Harald Welte 11 Nov '21

11 Nov '21

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at November 12, 2021 at 20:00 CET at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:10 presentation "E1 / TDM / PDH / SDH basics" by laforge 20:30 presentation "icE1usb in practice" by tnt later USSE: unstructured supplementary social event [*] Attendance is free of charge and open to anyone with an interest in Osmocom. More information about OsmoDevCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall Looking forward to meeting you on Friday. Best regards, Harald [*] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - 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)

1 0

Anyone still using mISDN for OpenBSC / OsmoBSC / OsmoMGW ?
by Harald Welte 10 Nov '21

10 Nov '21

Dear Osmocom users, the Linux kernel developers are considering to remove mISDN from the kernel, as can be seen in posts like https://marc.info/?l=linux-netdev&m=163636911918302&w=2 They are aware that Osmocom still supports mISDN, but it would of course be interesting if anyone is actually still using this approach. I've switched to DAHDI a long time ago (4- and 8-port cards for PCIe available) and only used mISDN very early on with the HFC-E1 in the 2008-2011 timeframe. These days, I'm using both DAHDI and icE1usb. IMHO, mISDN based interface cards are becomming less and less attractive, as the chips only support parallel PCI bus and I've never seen cards with more than two ports. So the point of this post is to find out if anyone still is using [or planning to use] mISDN. If so, please let me, netdev + Anrd Bergmann know about it. Basically it is kind of a "speak now or forever hold your peace" kind of moment, as mISDN would then likely be phased out from mainline Linux. Even in that case I think libosmo-abis should keep mISDN support, as there will be Linux systems on older kernels for many years to come, and the mISDN support doesn't hurt the rest of our code base in any way. 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)

3 2

pysim-shell: export is missing some files
by Riemer, Björn 10 Nov '21

10 Nov '21

Hi, i recently noticed that the `export` command from pysim-shell is failing on some basic files like EF.ICCID. However if i manually select the file it can be read. This happens on a generic USIM and on the orange sysmousim-SJS1. see the logs below to illustrate. Cheers Bjoern sysmo usim: <..snip..> ################################################################################ # Export summary # ################################################################################ # total files visited: 165 # bad files: 75 # MF/EF.DIR, string indices must be integers # MF/EF.ICCID, string indices must be integers <...snip...> pySIM-shell (MF)> select EF.ICCID "621e8202412183022fe2a506c00100ca01808a01058b032f06048002000a8800" pySIM-shell (MF/EF.ICCID)> read_binary_decoded { "iccid": "8988211000000169394" } ------- KDDI USIM: Using PC/SC reader interface Waiting for card... ATR: [59, 157, 149, 128, 63, 199, 160, 128, 49, 160, 115, 190, 33, 83, 81, 6, 131, 5, 144, 0, 63] Autodetected card type: Generic-UISIM AIDs on card: USIM: a0000000871002ff81ff108904150001 Welcome to pySim-shell! pySIM-shell (MF)> select EF.ICCID "0000000a2fe204000fffff01020000" pySIM-shell (MF/EF.ICCID)> read_binary_decoded { "iccid": "8981100055906574179" } pySIM-shell (MF/EF.ICCID)> select MF "0000ffff3f0001000000000011b304110400838a838a0000000000000000" pySIM-shell (MF)> export ################################################################################ # MF/EF.DIR # ################################################################################ # directory: MF (3f00) # file: EF.DIR (2f00) # bad file: MF/EF.DIR, string indices must be integers # ################################################################################ # MF/EF.ICCID # ################################################################################ # directory: MF (3f00) # file: EF.ICCID (2fe2) # bad file: MF/EF.ICCID, string indices must be integers #

1 0

enabling ssh on nano3g s8
by Erich Dachleger 05 Nov '21

05 Nov '21

Hi all,Is there some special routine for enabling ssh on nano 3gs8 device?Or is the unit "useless" if the ssh-daemon is not running?(I have no way of seeing whether or not it is running) I can access by telnet to dmi interface, the telnet commands from the wiki are present and have read the docs from accelerate 3g but I think there might be some subtle info I miss regarding starting ssh. Port 22 is blocked is the errror message I get and i also tested the aes-method suggested in the wiki, same error, port 22 blocked also in that case. Could this be the situation where one has to try setting up a tr069 server? Regards /erich

1 0

USA or Mexico alternative to OsmoDevCon?
by Mychaela Falconia 04 Nov '21

04 Nov '21

Hello fellow telecom hackers, Seeing that OsmoDevCon 2022 is being discussed, I would like to propose a more inclusive alternative, to be held in either USA or Mexico. There are two severe lack-of-inclusion problems with OsmoDevCon: 1) Since its very beginning, ODC has been exclusionary, limited only to Osmocom developers specifically, excluding those developers and tinkerers who work on non-Osmocom projects in the "indie" telecom space, "indie" being defined as independent of major commercial vendors and industry. I hold the opinion that all monocultures are bad in principle, and an Osmocom monoculture is no better than, say, a Microsoft monoculture. Osmocom is currently in the dominant position, outweighing all others by some orders of magnitude, but might does not make right, and we need more diversity. We need more players in this niche space than just Osmocom! 2) The recent decision to limit OsmoDevCon only to those who have agreed to put a certain class of pharmaceutical into their bodies, *on top* of the Osmocom-only restriction of the previous paragraph, makes the proposed conference even more exclusionary and therefore of no service to the wider telecom hacker community. Of course it is not my place as a Russian-American to try to tell EU countries whom to allow or not allow within their borders, nor is it my place to tell private individuals like our Fearless Leader Harald whom to allow or not allow in their private spaces. But what I *can* do instead is to step forward and offer to organize and host a more inclusive alternative, and that is what I am doing with this post. Specifically I am offering to organize and host a physical in-person gathering of telecom (all telecom, not just wireless) hackers, enthusiasts and tinkerers, very similar in spirit to OsmoDevCon, but more inclusive: 1) Welcoming everyone who has devoted a major portion of his or her life to *any* project in the indie telecom space, regardless of which domain that project is hosted under, and regardless of whether that project is FOSS or merely PSS. (PSS = Published Source Software, a superset of FOSS.) 2) Welcoming everyone regardless of personal medical choices - what you do with your body is your business, not mine - you don't tell me what I should or shouldn't put in my body, and I won't tell you what you should or shouldn't put into yours. Also no forced testing: if you wish to get yourself tested for this or that before attending, it is your sovereign choice to do so, but no one will *ever* be turned away from an event which I organize and host, neither for refusing to test nor for any other reason. If there is anyone interested in such an inclusive in-person gathering of telecom hackers, I am offering to host one in my part of the world. Where is it geographically? I live in USA, near San Diego, and right next to the border between USA and Mexico. Depending on who is interested in joining and where they will come from, I can host our InclusiveDevCon on either side of the border, i.e., either in USA or in Mexico. It is my understanding that gaining entry into Mexico is much easier than gaining entry into USA, hence for that reason I suggest that we hold our get-together on the Mexican side of the border. If we do choose Mexico as our host country, the specific location will need to be in the northern part of that country, specifically in the Mexican state of Baja California; the candidate cities would be Tijuana or Ensenada, somewhere close to the border with USA. However, if the only people who are interested in joining either already live in USA or can easily enter this lovely country, then holding our Inclusive- DevCon in USA would make more sense - in that case it will be somewhere in San Diego area. Alternatively, if there is anyone in the community who shares my stated values of wider inclusion but cannot or does not wish to travel to USA or Mexico, if you would be willing to host an inclusive event in your part of the world, then I will consider traveling to attend your event - but *only* if your event is open to non-Osmocom PSS developers *and* open to those who refuse injections. Please note, however, that I cannot enter Russia - other parts of the former USSR including Transnistria are potentially accessible to me, but not Russia - I was born there, but I permanently lost the ability to visit my birthplace as a result of having done my gender transition while living in USA, with all steps for legal name and gender change done under the American system, as opposed to Russian. In hacking solidarity, Mother Mychaela of FreeCalypso

3 3

Catching missing #include of <endian.h>
by Vadim Yanitskiy 01 Nov '21

01 Nov '21

Hi list, today I fixed a header file in libosmocore: https://gerrit.osmocom.org/c/libosmocore/+/26044 TL;DR, using OSMO_IS_{LITTLE,BIG}_ENDIAN macros without including the <osmocom/core/endian.h> header leads to empty struct definitions, and thus weird compiler warnings like 'struct `foo` has no member `bar`'. We may want to catch missing #include of the <endian.h> automatically, so I wrote a simple script to check whether it is absent: https://gerrit.osmocom.org/c/osmo-ci/+/26045 Below is an example of using it: $ cd libosmocore/ $ verify_endian_header.sh $(find . -name "*.[hc]") File './include/osmocom/gsm/protocol/gsm_44_004.h' does not #include <osmocom/core/endian.h> What's still missing is the actual integration into the build verification process. I guess there is currently no easy way other than calling this script from 'contrib/jenkins.sh' of each project? P.S. I found out that we also have 'scripts/verify_log_statements.py' in osmo-ci.git, but we don't seem to call it anywhere? Best regards, Vadim. -- - Vadim Yanitskiy <vyanitskiy at 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

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC November 2021