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
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
I'm confused by what is happening in the pcap linked below:
According to wireshark, the SCCP message seems to come from *both* PC=4 and PC=185.
A column configured as sccp.calling.pc shows Point-Code 4.
A column configured as "Source Address" shows Point-Code 185.
Is it even possible that the in-band Calling Address differs from whatever
wireshark detects as the SCCP Source Addres? Can anyone explain where the 185
is coming from? apparently not from sccp.calling.pc.
The pcap and a screenshot showing the two point-codes and the column config are
here: http://people.osmocom.org/neels/Eew7we0I/
Context:
The original RESET message (not part of the pcap) was sent to called.pc=4, but
I have SCCP routing set up to forward PC=4 to the MSC that sees itself as
PC=185.
I am expecting to see a RESET-ACK sent from PC=185.
IIUC The 4 should have evaporated when the MSC parsed the RESET message. But
apparently when answering, it takes the "called.pc" and puts it in the response
as "calling.pc" (4 is nowhere in the MSC's confguration, it MUST have taken the
"4" from the received SCCP message).
So what I am seeing in wireshark is eerily correct: it is the MSC that has
"185" in its cfg as local address sending the ACK, and it is responding to a
request that was originally sent to "4", and which osmo-stp routed to "185".
The response shows calling.pc=4. But how can wireshark know that it was really
"185" sending, when no such information is in the SCCP layer of that message?
What am I missing?
if anyone knows, thanks in advance...
~N
Hi all,
as some of you may know, I am working on the MS side implementation of
GPRS protocol stack. The end goal is to have something similar to srsUE
(part of srsRAN, former srsLTE), but for GPRS.
In order to reduce code duplication it was decided to move some stuff
from both osmo-pcu.git and osmo-sgsn.git into shared libraries, so that
we could re-use existing code in the upcoming MS side implementation.
== What is already done
* Redmine: https://osmocom.org/projects/libosmo-gprs
* Gerrit: https://gerrit.osmocom.org/q/libosmo-gprs
* Gitea: https://gitea.osmocom.org/osmocom/libosmo-gprs
* osmo-ci.git: https://gerrit.osmocom.org/c/osmo-ci/+/29019
== What is missing
* GitHub: https://github.com/osmocom/libosmo-gprs
* cgit: https://cgit.osmocom.org/libosmo-gprs/
** Coverity pulls from this mirror
** Jenkins build verification uses this mirror
I will need some help with both GitHub and cgit, as I don't have admin
permissions. Please also let me know if I missed something.
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
I tried to use shadysim (https://gitea.osmocom.org/sim-card/sim-tools)
to install a STK / CAT applet on the sysmoISIM. It was not working for
me, also it does not support UICC parameters and it seems that still
Python 2.7 is needed.
As an alternative I have added support for gpshell
(https://kaoh.github.io/globalplatform/) to use SCP02 and pass the
SIM/UICC parameters.
See the new parameters "uiccSystemSpecParam" and "simSpecParam" for the
"install" command
https://github.com/kaoh/globalplatform/blob/master/gpshell/src/gpshell.1.md
and inspect the
https://github.com/kaoh/globalplatform/blob/master/gpshell/helloInstallSTK.…
example file. If "brew" ins installed then "brew install
kaoh/globalplatform/globalplatform" is sufficient for the installation.
I also faced the issue that the sysmoISIM cards are only accepting SIM
parameters and no UICC parameters, which is strange or even a bug since
these cards are newer and are supporting the newer UICC ETSI specifications.
