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 List,
I tried to set up Osmo-CBC with a Nokia MetroSite BTS according to the
wiki. But every time the CBSP clinet of the BSC connects to the CBC
server, the BSC log indicates:
DCBS cbsp_link.c:150 CBSP Client connected to CBC:
(r=127.0.0.1:48049<->l=127.0.0.1:46133)
DCBS smscb.c:805 (bts=0) Rx CBSP RESET: clearing all state; disabling broadcast
Same time on the CBC:
<0002> cbsp_link.c:265 New CBSP link connection from 127.0.0.1:46133
<0002> cbsp_link_fsm.c:181 local-bsc: RESTART (CBS) but re-sending not
implemented yet
The BTS is configured with CCCH+SDCCH4+CBCH, and these are the
relevant sections:
osmo-cbc.cfg:
cbc
unknown-peers reject
ecbe
local-ip 127.0.0.1
local-port 12345
cbsp
local-ip 127.0.0.1
local-port 48049
sbcap
local-ip 127.0.0.1
local-port 29168
peer cbsp local-bsc
mode server
remote-port 46133
remote-ip 127.0.0.1
osmo-bsc.cfg:
cbc
mode client
client
remote-ip 127.0.0.1
local-ip 127.0.0.1
local-port 46133
Every other CS service is working fine on the BTS.
Is there anything else I might have missed?
Regards,
Csaba
Dear Osmocom community,
we're happy to announce the next incarnation of OsmoDevCall.
when:
September 20, 2023 at 20:00 CEST
where:
https://osmocom.org/OsmoDevCall (Big Blue Button)
This time, @falconia will be presenting on
Themyscira Wireless: a case study in interconnecting an Osmocom GSM network to USA PSTN
This meeting will have the following schedule:
20:00 meet + greet
20:10 topic as outlined above
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 soon!
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)
I just noticed that a release was made,
ignoring this remark in osmo-msc's TODO-RELEASE:
MNCC osmo-sip-connector should do full SDP via MNCC and be released at the same time as the next osmo-msc, ask neels, thanks
https://gerrit.osmocom.org/c/osmo-msc/+/34386
There is no full SDP support in current osmo-sip-connector.
In fact the patch for that is just now becoming ready for merge:
https://gerrit.osmocom.org/c/osmo-sip-connector/+/16222
I guess we should get the sipcon patch merged, and follow up with another
sipcon release.
~N
Dear list,
I built an icE1USB device so I can provide stable clock to my legacy Nokia BTS.
I have not found any information about how to bring up a completely
empty device, so I just took the icE1usb-202210-5890f3e4.bin file and
flashed it to the SPI flash, yet the device is not booting. Maybe
something else is missing (like a boot block), or the binary has to be
flashed with an offset? The device takes 80mA in this state, USB
device is not recognized on the host.
Thanks!
Hi all,
I am happy to announce that a new version 202309 of the Osmocom CNI
(Cellular Network Infrastructure) software has been released this week.
For further information, please visit: https://osmocom.org/news/220
Regards,
Pau
--
- 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
Hi Vadim,
You are probably correct, in the mean time I recompiled everything, so
it works now, but most likely the *-dev packages were missing. Thanks
for pointing that out!
Another question I have is about displaying the Osmo-BSC logs:
I am working on a museum setup and would be nice to show the BSC log
output on the screen when there is activity. I wonder if there is a
practical way to do that without altering the systemd part.
Regards,
Csaba
Dear List,
I face the problem that when I am in general using the nightly builds
on Ubuntu 20.04, but I want to compile a specific project (Osmo-BSC in
this case), the configure script is not able to find the Osmocom
libraries which are already installed and available.
Output of the configure script:
configure: error: Package requirements (libosmocore >= 1.8.0) were not met:
Package 'libosmocore', required by 'virtual:world', not found
Libosmocore is available on the system:
root@openbsc:~/osmo-bsc_bootstrap_mod/osmo-bsc# ldconfig -v|grep libosmocore
/sbin/ldconfig.real: Can't stat /usr/local/lib/i386-linux-gnu: No such
file or directory
/sbin/ldconfig.real: Path `/usr/lib/i386-linux-gnu' given more than once
/sbin/ldconfig.real: Can't stat /usr/local/lib/i686-linux-gnu: No such
file or directory
/sbin/ldconfig.real: Can't stat /lib/i686-linux-gnu: No such file or directory
/sbin/ldconfig.real: Can't stat /usr/lib/i686-linux-gnu: No such file
or directory
/sbin/ldconfig.real: Can't stat /usr/local/lib/x86_64-linux-gnu: No
such file or directory
/sbin/ldconfig.real: Path `/usr/lib/x86_64-linux-gnu' given more than once
/sbin/ldconfig.real: Path `/lib/x86_64-linux-gnu' given more than once
/sbin/ldconfig.real: Path `/usr/lib/x86_64-linux-gnu' given more than once
/sbin/ldconfig.real: Path `/usr/lib' given more than once
/sbin/ldconfig.real: /lib/i386-linux-gnu/ld-2.31.so is the dynamic
linker, ignoring
/sbin/ldconfig.real: /lib/x86_64-linux-gnu/ld-2.31.so is the dynamic
linker, ignoring
libosmocore.so.20 -> libosmocore.so.20.0.0
Can someone help me with what kind of flags do I need to provide to
the configure script and how?
Much appreciate the help!
Regards,
Csaba