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
Hi Osmocom Community,
May I ask your help on this. We have a test setup with UmTrx 2.3.2 SDR. We
are trying to set the tx-attenuation and measure the power output but it
seems it doesn't reflect based on the defined configurations. We tried to
set 0, 5, 10 as values and below are the results.
[image:
0-02-03-588e9973ceef2e018e29c0b2eb576f5b7d26972bbb779b44f79c97408d360299_1c6daee34bf8ee.jpg]
[image:
0-02-06-99d6d7ce8551b10be62ea130c638b19c5475b5b4140bf2843b92a5b55d36c67c_1c6daee34bfeec.jpg]
Please see attached files for osmo configurations and logs. Thanks!
Regards,
Justin
Hi all,
We're trying to setup osmo-gsm-tester on bare metal and are currently experiencing issues with the Jenkins job 'osmo-gsm-tester-runner'. All of our test machines are running Ubuntu Server 20.04 and have been setup following the latest available manual from https://downloads.osmocom.org/docs/latest/osmo-gsm-tester-manual.pdf.
We've trying to use the '4g_srsLTE' example from https://github.com/osmocom/osmo-gsm-tester/tree/master/doc/examples/4g_srsL… but when trying to run the 'ping' test the following error is returned in the Jenkins console output:
" 14:07:52.867022 run mk-remote-dir(pid=2480): ERR: Terminated: ERROR {rc=1} [trial-21↪4g:srsenb-rftype@soapy↪ping.py:9↪ping.py↪srsepc_10.100.100.113↪host-jenkins@10.100.100.113↪mk-remote-dir(pid=2480)]
14:07:53.015620 run mk-remote-dir(pid=2480): stdout:
| (launched: 2022-09-23_14:07:51.598612)
| mkdir: cannot create directory ‘/osmo-gsm-tester-srsepc’: Permission denied "
It appears that osmo-gsm-tester is trying to create the directory 'osmo-gsm-tester-srsepc' under root, which is not permitted as the Jenkins user the script runs has does not have permissions. Additionally, it looks like this path is hard-coded in the Python module https://github.com/osmocom/osmo-gsm-tester/blob/master/src/osmo_gsm_tester/… and also the same applies for srsENB https://github.com/osmocom/osmo-gsm-tester/blob/master/src/osmo_gsm_tester/…
Is this the intended behaviour? Or have we missed out steps during our bare-metal setup process? I've double-checked that the main unit can SSH into the slave unit without a password so that's not the issue causing "permission denied".
Best regards,
Callum.
Hi all,
We're trying to setup osmo-gsm-tester on bare metal and are currently experiencing issues with the Jenkins job 'osmo-gsm-tester-runner'. All of our test machines are running Ubuntu Server 20.04 and have been setup following the latest available manual from https://downloads.osmocom.org/docs/latest/osmo-gsm-tester-manual.pdf.
We've trying to use the '4g_srsLTE' example from https://github.com/osmocom/osmo-gsm-tester/tree/master/doc/examples/4g_srsL… but when trying to run the 'ping' test the following error is returned in the Jenkins console output:
" 14:07:52.867022 run mk-remote-dir(pid=2480): ERR: Terminated: ERROR {rc=1} [trial-21↪4g:srsenb-rftype@soapy↪ping.py:9↪ping.py↪srsepc_10.100.100.113↪host-jenkins@10.100.100.113↪mk-remote-dir(pid=2480)]
14:07:53.015620 run mk-remote-dir(pid=2480): stdout:
| (launched: 2022-09-23_14:07:51.598612)
| mkdir: cannot create directory ‘/osmo-gsm-tester-srsepc’: Permission denied "
It appears that osmo-gsm-tester is trying to create the directory 'osmo-gsm-tester-srsepc' under root, which is not permitted as the Jenkins user the script runs has does not have permissions. Additionally, it looks like this path is hard-coded in the Python module https://github.com/osmocom/osmo-gsm-tester/blob/master/src/osmo_gsm_tester/… and also the same applies for srsENB https://github.com/osmocom/osmo-gsm-tester/blob/master/src/osmo_gsm_tester/…
Is this the intended behaviour? Or have we missed out steps during our bare-metal setup process? I've double-checked that the main unit can SSH into the slave unit without a password so that's not the issue causing "permission denied".
Best regards,
Callum.
Hi all,
We're trying to setup osmo-gsm-tester on bare metal and are currently experiencing issues with the Jenkins job 'osmo-gsm-tester-runner'. All of our test machines are running Ubuntu Server 20.04 and have been setup following the latest available manual from https://downloads.osmocom.org/docs/latest/osmo-gsm-tester-manual.pdf.
We've trying to use the '4g_srsLTE' example from https://github.com/osmocom/osmo-gsm-tester/tree/master/doc/examples/4g_srsL… but when trying to run the 'ping' test the following error is returned in the Jenkins console output:
" 14:07:52.867022 run mk-remote-dir(pid=2480): ERR: Terminated: ERROR {rc=1} [trial-21↪4g:srsenb-rftype@soapy↪ping.py:9↪ping.py↪srsepc_10.100.100.113↪host-jenkins@10.100.100.113↪mk-remote-dir(pid=2480)]
14:07:53.015620 run mk-remote-dir(pid=2480): stdout:
| (launched: 2022-09-23_14:07:51.598612)
| mkdir: cannot create directory ‘/osmo-gsm-tester-srsepc’: Permission denied "
It appears that osmo-gsm-tester is trying to create the directory 'osmo-gsm-tester-srsepc' under root, which is not permitted as the Jenkins user the script runs has does not have permissions. Additionally, it looks like this path is hard-coded in the Python module https://github.com/osmocom/osmo-gsm-tester/blob/master/src/osmo_gsm_tester/… and also the same applies for srsENB https://github.com/osmocom/osmo-gsm-tester/blob/master/src/osmo_gsm_tester/…
Is this the intended behaviour? Or have we missed out steps during our bare-metal setup process? I've double-checked that the main unit can SSH into the slave unit without a password so that's not the issue causing "permission denied".
Best regards,
Callum.
hi there,
i ran into an error with ./transceiver in osmocom-bb
if i write
osmocom/osmocom-bb/src/host/layer23/src/transceiver # sudo ./transceiver
-a 47 -2 -r 99
the cli returns with
47
41
1
Aborted
what am i doing wrong? i hope you can help me out.
have a nice day
msfu
Dear Osmocom community,
during the past years, we've been applying for (and often receiving) grants
for the development of certain parts of the Osmocom project.
There are two organizations (NLnet foundation and the German prototype fund) where the
next call for proposals ends in 10 days from now.
So if any of you has some ideas about Osmocom related work that you would want
to see implemented and for which you can argue that it fits the scope of the
related funds, please feel free to bring them up here.
For NLnet, the scope should fit either
* https://nlnet.nl/entrust/
* https://nlnet.nl/useroperated/
For prototype fund, the scope should fit
https://prototypefund.de/jetzt-bewerben-fuer-runde-13/ - specifically I think
it is likely that we could fit a number of "our" topics in
https://prototypefund.de/softwareinfrastruktur/ which explicitly lists
implementation of communication protocols.
Given that I have plenty of experience with both funds, I'd be willing
to work on a concrete proposal and submit it before the deadline on Sept
30 / Oct 1.
In terms of "who would do the actual work": With NLnet projects we can
involve freelancers across Europe, with prototype fund probably only
in Germany. In the worst case, if you propose some idea but have no
time to work on such a project yourself, or you are not eligible due
to the restriction to EU/DE, sysmocom could carry out the
implementation.
Let me know if anyone of you has some ideas as to what kind of osmocom
related topics might be suitable candidates.
Thanks,
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)
RFC about mscgen
mscgen is our tool of choice to generate ladder diagrams from the "msc" text
input format. We use it in user manuals and on our redmine wiki, and there are
also various .msc files in doc/ subdirs, as assistance for development.
I've written a lot of ladder diagrams, for documentation as well as figuring
out how to implement things. I've developed a love/hate relationship, and
recently I found a bug in mscgen.
Things have come up that I'd like your opinion on:
* ladder_to_msc.py
Writing .msc files by hand quickly started to annoy me:
- Having to write '[label="..."]' all the time.
- Multiline labels (e.g. '(note)' block) require "foo\nbar\nbaz"
- input symbols for arrows are weird / non-intuitive
- cannot use 'msc' as entity, weirdly conflicts with the outer 'msc { ... }',
which is annoying for GSM diagrams featuring an MSC.
So quite some while ago I wrote a python script that reads my personal favorite
format in which i enjoy writing ladder diagrams, and outputs plain .msc file
format. I put it in libosmocore/contrib/ on a branch, have been using it ever
since, but i never submitted it for merging, because it seemed like a personal
preference thing, not worth complicating the doc tool chain for.
So far I was, if at all, committing only the resulting .msc to git. But that
creates a situation where only I have the *original* source in .ladder format,
so (hypothetically) collaborating on ladder diagrams becomes convoluted.
Here is an example of my favorite ".ladder" format:
------
{hscale=1}
upf = User Plane function
cpf = Control Plane function
upf <- cpf PFCP Association Setup Request
CP function Node Id, features
upf -> cpf PFCP Association Setup Response
UP function Node Id, features
upf <> cpf associated
upf () cpf start Heartbeat checking
...
------
The equivalent .msc produced by ladder_to_msc.py:
------
msc {
hscale="1";
upf[label="User Plane function"],cpf[label="Control Plane function"];
upf <= cpf [label="PFCP Association Setup Request\nCP function Node Id, features"];
upf => cpf [label="PFCP Association Setup Response\nUP function Node Id, features"];
upf abox cpf [label="associated"];
upf rbox cpf [label="start Heartbeat checking"];
...;
------
I'd like to hear some opinions, if you have any, on whether anyone else likes
my new ladder format, and how to deal with .ladder source files.
Would it make sense to merge ladder_to_msc.py to libosmocore, install it via
'make install', and add the original .ladder files as well as Makefile rules to
convert .ladder to .msc to .png where ever i wrote .ladder diagrams?
* mscgen bitrot is likely
Recently I've found a segfault in mscgen. I found a fix and tried to submit it.
That's when I discovered that:
- the original project on code.google.com is dead and gone
- the mail addresses of the original author result in bounces
- random people put mscgen's trunk on github, exported from google code, no
activity is apparent
I did reach the Debian maintainer of mscgen by mail. He doesn't have any way to
contact the original author, either. It seems there could be a patch in the
Debian package, at best.
I wonder if it would make sense to officially create an mscgen "fork" on
Osmocom, in an effort to save the tool from bitrot and extinction, and offer
our mscgen as the new upstream for debian's mscgen packaging.
I do have a number of things i'd like mscgen to be able to do, like left-adjust
text in "note" blocks or improve the resolution of produced PNG images;
I might also implement support for my .ladder format directly in mscgen.
I am vague on what my opinion is between the advantages and disadvantages, and
it's all only semi important. I just know that I always end up writing .ladder
instead of .msc, and that we will always need ladder diagrams.
Do you have any opinions on these things?
Thanks!
pointers:
ladder_to_msc.py: libosmocore branch neels/ladder
https://cgit.osmocom.org/libosmocore/commit/?h=neels/ladder&id=073ad74435ec…
My most recent ladder chart:
https://cgit.osmocom.org/osmo-bsc/commit/?h=neels/codec&id=01f370c1b365305f…
--
- Neels Hofmeyr <nhofmeyr(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
* Geschäftsführer / Managing Directors: Harald Welte
Dear OpenBSC team,
I am Ahnaf Tahmid Chowdhury, currently building Osmocom graphical user
interface. I have created a subscriber page where one can add/remove/update
subscriber. The repo is available at:
https://github.com/ahnaf-tahmid-chowdhury/osmo-gui
Please let me know your thoughts about the application.
Thank you