Dear Osmocom developers,
In our project we have been using the gsmtap pseudo-header to store UMTS and LTE signalling traces in pcapng format. This is very efficient compared to our previous implementation based on DLT_USER, and thanks to the gsmtap dissector, it allows any *shark app to read our output file.
When looking for the proper type and sub_type for NR signalling traces, I discovered they are not yet part of the standard. I found several threads of discussion about this, from about 2017 onwards, and I understand it is a matter of time and resources if the version 3 of GSMTAP has not been released.
The most interesting feature I have read about is the ability to extend the header with a TLV approach. EARFCN, eNodeB-ID, PCI, are useful metadata we would like to add to our traces.
In an ideal world, I would like things to be put in motion so that a new version of GSMTAP could see the light. More humbly, I ask you what kind of help is needed. Are you waiting for a draft specification? Are all requirements well known?
I suppose that LTE and NR are not the main focus today for liboscmocore development, but there are many projects out there waiting for the GSMTAP format to be updated.
Thanks!
Mauro
Hi all,
Just wanted to share an issue and a quick workaround I found for it in case
anyone else has the same problem. I believe a cmd2 update is causing
pySim-shell to fail. After installing it on a fresh install of Ubuntu
Server 20.04 and getting the following error when I run "python3
pySim-shell -p0":
>Using PC/SC reader interface
>Autodetected card type: sysmoUSIM-SJS1
>AIDs on card:
> USIM: a0000000871002ffffffff8907090000
>Traceback (most recent call last):
> File "pySim-shell.py", line 512, in <module>
> app = PysimApp(card, rs, opts.script)
> File "pySim-shell.py", line 59, in __init__
> super().__init__(persistent_history_file='~/.pysim_shell_history',
allow_cli_args=False, use_ipython=True, auto_load_commands=False,
command_sets=basic_commands, >startup_script=script)
>TypeError: __init__() got an unexpected keyword argument 'use_ipython'
If you run into this you can fix it by uninstalling cmd2 and reinstalling
cmd2 with "pip3 install cmd2==1.5".
Best,
Bryan
Hi,
I had a problem placing MO GSM calls from a Siemens S11E: The calls
were dropped immediately; Osmo-MSC reports "Cannot compose Channel
Type from bearer capabilities"
After investigating the SETUP request from the S11E, the phone does
not use octet 3a (no extension bit set in IE 3). Wireshark decodes the
radio channel requirement as "Full rate support only MS/fullrate
speech version 1 supported", so I added a condition to the gsm48_ie.c
function of libosmocore to include at least GSM FR in the list of
available speech_ver in case octet 3 has no extension.
Attached to this message are the Abis-IP PCAP traces of MO calls, and
the patch for gsm48_ie.c.
Regards,
Lennart
Hi,
My name is Brackley Cassinga Form DRC, we run a community network called
pamoja net where we offer gsm services using osmocom open source software
and OC Base station.
Recently I have tried to install another base station as the same installed
but I could not find any resource guiding through all the steps to take to
run NIB on a base station.
I'm currently running Ubuntu and I will appreciate if you could guide me on
the installation of BSC,hlr,MSC , in order to run a basic gsm network.
Thank you. Regards
--
*Ir Brackley heshima Casinga **Pacifique*
*CEO and Founder of kwanzatechnologie*
KwanzaTechnologies ,GlobalElectronics
+243977265291 | +243977265291 | Pcassinga(a)gmail.com/
brackley(a)ensemblepourladifference.org
www.kwantechnologies.jimdosite.com <http://www.kwantechnologies.com/> |
Skype: Brackley cassinga <https://webapp.wisestamp.com/#>
Av Semliki N 43
Hello Osmocom community,
I have a contact in Australia who reached out to me with a desire to
set up his own personal GSM/2G network. Australia is a nasty anti-
retrotechnology country, even worse than USA, where all official 2G
networks were shut down back in 2018. As most of you know, I run my
own pirate-radio GSM cell in USA, and I tried reaching out to other
Vintage Mobile Phone communities, promoting the idea that people can
run their own networks using Osmocom CNI plus suitable hw plus my
ThemWi add-ons for outside PSTN interconnection, and offering to teach
others how to copy what I am doing. When I made the latter offer to
the community, I was expecting people from other parts of USA - but
right now the only person with an active interest is in Australia.
I am currently teaching my Australian contact the "pure physics"
aspects of running your own GSM network: what frequencies are usable
for GSM, dB and dBm units of measurements, how to use a handheld
spectrum analyzer etc. These are all "physics" topics that are
independent of where one happens to be geopolitically. But there is
another key aspect which I feel he needs to know, but which I won't be
able to teach him: country-specific spectrum-political aspects.
I know the spectrum-political landscape in USA: how FCC has divvied up
PCS1900 and GSM850 bands (or B2 & B5 in modern parlance) between
carriers, which spots in these bands are completely unused and thus
reasonably safe to squat in, and how one can exploit the overlap
between EGSM900 DL and USA ISM band to run a BTS with low probability
of getting into trouble. But I have absolutely no such knowledge for
any other country in the world, let alone one as remote and foreign to
me as Australia.
Is there anyone in this community who is based in Australia and knows
this topic? I would greatly appreciate any advice from an AU-knowing
person that I could pass to my GSM-enthusiast contact: out of the 4
frequency bands that are in-principle suitable for GSM, which is the
safest one to squat in for a pirate operator, and which ARFCN range(s)?
Obviously I will teach my contact that he needs to pick a spot where
the spectrum analyzer shows nothing but noise floor, but just because
a spot "looks blank" on an SA doesn't mean that the spot is safe to
squat on, without knowing anything at all about the country's
spectrum-political landscape...
TIA,
Mychaela
Dear all
We have a questions for you, experts.
Has anyone managed to get Osmocom with limesdr Mini 2.0 ? (USB)
We have stability issues, so if someone has tried and can share configuration for osmocom-bsc and osmocom-trx-lms, it woud be great !
Many thanks in advance,
Best regards
Good Morning,
My name is Tanya and was referred to this email regarding open source
involvement. I am genuinely interested in sysmocom and am open to exploring
various ways I can support your team. If there are any upcoming
opportunities or specific areas where my skills could be of value in a
volunteer capacity, I would be grateful for the chance to discuss them
further.
Please take a look at my GitHub profile: https://github.com/wonntann
Thank you again for your consideration. I look forward to the possibility
of contributing to sysmocom and will continue to follow your updates.
Best,
Tanya
Hello Osmocom community,
I have a question about TCP port number assignment for programs using
libosmovty. Every Osmo-official server program gets official port
number assignments listed in the wiki, in PDF manuals etc - so far, so
good. But what about non-Osmo-official 3rd-party programs that wish
to use common Osmocom libraries, including the vty facility? Suppose
that an operator of an Osmocom-based cellular network needs to develop
some additional programs to satisfy some operational need, and some of
these additional programs are long-lived server processes for which an
Osmocom-style vty interface would be very useful. But implementing
such a telnet vty i/f requires a TCP port number...
Has anyone thought about designating an official range of TCP port
numbers which would be recommended for vty/ctrl/etc ports of processes
that use Osmocom libraries and extend Osmocom CNI in various ways, but
aren't official Osmocom projects?
M~
