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,
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 there,
i have an issue with sysmo-usim-tool. If i do
sudo ./sysmo-usim-tool.sjs1.py -a 4051049678932293688 -o
my cli returns with
sysmoUSIM-SJS1 parameterization tool
Copyright (c)2017-2019 Sysmocom s.f.m.c. GmbH
Initializing smartcard terminal...
Traceback (most recent call last):
File "./sysmo-usim-tool.sjs1.py", line 97, in <module>
main(sys.argv[1:])
File "./sysmo-usim-tool.sjs1.py", line 94, in main
Application(argv, "ucmI:", ["usim", "classic", "mode", "set-iccid="])
File "/usr/src/sysmo-usim-tool/common.py", line 125, in __init__
self._init()
File "./sysmo-usim-tool.sjs1.py", line 76, in _init
self.sim = Sysmo_usim_sjs1()
File "/usr/src/sysmo-usim-tool/sysmo_usim_sjs1.py", line 240, in __init__
Sysmo_usim.__init__(self, "3B 9F 96 80 1F C7 80 31 A0 73 BE 21 13
67 43 20 07 18 00 00 01 A5")
File "/usr/src/sysmo-usim-tool/sysmo_usim.py", line 40, in __init__
self.sim = Simcard(GSM_USIM, toBytes(atr))
File "/usr/src/sysmo-usim-tool/simcard.py", line 88, in __init__
self.card = USIM(atr)
File "/usr/src/sysmo-usim-tool/card/USIM.py", line 188, in __init__
ISO7816.__init__(self, atr, CLA=0x00)
File "/usr/src/sysmo-usim-tool/card/ICC.py", line 158, in __init__
self.cardservice = cardrequest.waitforcard()
File
"/usr/local/lib/python3.8/dist-packages/pyscard-1.9.5-py3.8-linux-aarch64.egg/smartcard/CardRequest.py",
line 68, in waitforcard
return self.pcsccardrequest.waitforcard()
File
"/usr/local/lib/python3.8/dist-packages/pyscard-1.9.5-py3.8-linux-aarch64.egg/smartcard/pcsc/PCSCCardRequest.py",
line 208, in waitforcard
raise CardRequestTimeoutException()
smartcard.Exceptions.CardRequestTimeoutException: Time-out during card
request
maybe i spelled the adm wrong. but it is calculated from hex
3838383838383838.
can you help me?
Thanks
msfu
Hello Osmocom community,
In my previous reply to Anonymous Internet User msfu666, I mentioned
that I sometimes give out FCSIM1 cards free of cost to certain
recipients, but I did not elaborate on the conditions. I did not
spell out the conditions because I hadn't actually given much thought
to what they should be - but thinking about it now, I realize that
only one condition would actually make sense. My FCSIM1 cards are
good for one and only one purpose: operating your own GSM network
(presumably with Osmocom CNI software, no idea if OpenBTS/YateBTS
would work or not) *for the purpose of* providing service specifically
to vintage handsets. Therefore, the condition becomes quite simple:
if there is anyone here besides just me who operates their own
Osmocom-based GSM network _specifically for the purpose_ of providing
service specifically to _vintage_ GSM handsets and you would like some
of my FCSIM1 cards, please let me know and I'll send you a few.
What are vintage GSM handsets? For the present purpose, we can define
a vintage GSM handset as being one that:
a) has a 2FF SIM socket, as opposed to 3FF or 4FF or eSIM;
b) has a 2G-only radio;
c) does not speak UICC/USIM protocol, only GSM 11.11 SIM.
If anyone besides me operates their own GSM network specifically for
the purpose of providing service to (or just playing with) such vintage
handsets, then FCSIM1 cards would be a good choice for such operation:
hence if you would like some, you can have them for the cost of
shipping. OTOH, if you operate your own network, even if it's a 2G
network radio-wise, for some purpose other than exclusively serving or
playing with vintage handsets, then my FCSIM1 cards will NOT be a good
choice for your applications. Specifically, if you are going to
connect any kind of "modern" phones to your network, even if it's 2G
RAN, those "modern" phones will want 3FF or 4FF SIMs - but my FCSIM1
cards are 2FF only, and thus a poor choice for such usage.
Sincerely,
Lady Mychaela Nadezhda Falconia,
Mother of FreeCalypso,
Dame of the Order of 2G,
Champion of Published Source Code
Hello Osmocom CNI folks,
I got my first GSM network up and running, using nanoBTS hardware and
Osmocom CNI sw stack. I compiled everything from source (to my
knowledge, no one makes binary packages for Slackware), but rather
than grabbing the state of git master on some random day, I checked
out tagged versions corresponding to the latest official 2021-11 CNI
release. My configuration is 2G-only, CS-only, minimal split-NITB,
thus the 5 processes I am running are OsmoSTP, OsmoHLR, OsmoMGW,
OsmoMSC and OsmoBSC. I'm using the same OsmoMGW instance for both MSC
and BSC.
The functional state is: phones with FCSIM1 cards in them whose
programming matches the data I entered into HLR are able to connect
(location update succeeds), SMS from one phone to another works, and
USSD requests *#100# and *#101# also work. However, voice calls don't
work. The user-visible symptoms are:
1) When I dial a call from one connected phone to another, the
destination phone starts ringing, and it shows the calling number on
the display - thus CC signaling works correctly at least in the
initial phases.
2) However, a short time (I measured a little under 20 s) after the
start of the process, the destination phone stops ringing and shows a
missed call indication. However, the origin phone continues playing
its NOIBT ringing tone as if it is still waiting for the call to be
answered, and it keeps going for another 15-20 s or so, before it
gives up.
3) Trying to press the answer button on the destination phone before
it stops ringing and goes into the "missed call" state does NOT
produce a connected call state either.
To see what's going on, I turned on maximum verbosity logging in all
OsmoCNI components and plowed through the resulting massive log.
(I am logging via syslog - the whole point of running Slackware is
principled opposition to systemd.) And I see what appears to be the
culprit - see lines 7558 and 7559 in the attached log, UTC timestamp
02:48:54, 11 seconds after I initiated the test call from the origin
phone. It appears that the BTS is telling the BSC that this error
occurred: "Timer T200 expired (N200+1) times", and based on the
lchan(0-0-2-TCH_F-0) annotation, this error is happening on the origin
leg of the call, rather than the destination leg.
I looked up what T200 is:
https://www.rfwireless-world.com/Terminology/GSM-timers.html
T200: "It is used as retransmission on data link layer. Value varies
depending on different messages (for FACCH it is set to 155ms)"
Why in the world are FACCH (or is it SACCH?) data link transmissions
suddenly failing on the origin leg of the call, some 11 to 13 seconds
in? I have tried 4 different phones in the call-origin role (Motorola
C139 running its original fw, Pirelli DP-L10 likewise, Nokia C3-00 and
my own FreeCalypso fw), and the behaviour is always the same.
Has anyone seen this problem before? Is it perhaps a known issue with
nanoBTS that requires some special workaround? This tarball:
https://www.freecalypso.org/members/falcon/osmo-cni/t200-fail-config+log.ta…
contains my configuration files for all 5 OsmoCNI components and an
excerpt from syslog. The syslog excerpt begins with all 5 OsmoCNI
components booting up, followed by two phones connecting, and finally
the test call.
I would really appreciate it if someone could give me some pointers
for debugging this voice call show-stopper.
TIA,
Mychaela
hello,
i ran into an issue with osmo-sim-auth.
if i try ./osmo-sim-auth.py -r 00000000000000000000000000000000 -s
it says
Traceback (most recent call last):
File "./osmo-sim-auth.py", line 27, in <module>
from card.USIM import USIM
File "/usr/src/osmo-sim-auth/card/USIM.py", line 56
print '[DBG] type definition: %s' % type(self)
^
SyntaxError: invalid syntax
do you know what the problem is? i think i installed pcsc-lite, pcscd
and pyscard and dependencies.
thank you
Dear Osmocom community,
It's my pleasure to announce the next OsmoDevCall (delayed by one
week from our usual spot) on
April 29, 2022 at 20:00 CEST
at
https://meeting5.franken.de/b/har-xbc-bsx-wvs
In this edition, I will be presenting on the state of the OCTOI
(Osmocom TDMoIP) Retronetworking activities
(see https://osmocom.org/projects/octoi/wiki)
This meeting will have the following schedule:
20:00 meet + greet
20:10 presentation 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)
Hi,
The script seems to be python2 and you are running it with python3.
Either the script has to be ported or yust try to use legacy python2.
Björn
Am 21.04.2022 14:13 schrieb msfu <msfu666(a)gmail.com>:
hello,
i have this issue with osmo-sim-auth.
if i do
sudo python osmo-sim-auth.py -r 00000000000000000000000000000000 -a
ec9320c2c2000000e1dd22c1ad3e2d3d
the cli repeats:
Traceback (most recent call last):
File "osmo-sim-auth.py", line 27, in <module>
from card.USIM import USIM
File "/usr/src/osmo-sim-auth/card/USIM.py", line 56
print '[DBG] type definition: %s' % type(self)
^
SyntaxError: invalid syntax
maybe it's missing a library for USIM or something else?
can you help me get beyond this issue?
Thank you
Configuration is Network In The Box with everything running on a LimeNET
Micro (RPi CM3+), using Raspbian 10 and osmocom:latest packages via OBS.
UEs can register fine and send/receive SMS, but when I attempt to make a
call I see the Rx RR Assignment Failure error from osmo-bsc.
The same hardware and CNI configuration works fine when used with an old
RPi image that has packages from late 2019.
Configs and error log attached. Would appreciate any suggestions for
things to try.
Regards,
Andrew
//
Hi,
I'm interested in inspecting TCAP/MAP interactions between hlr-msc, but it
seems osmo-msc osmo-hlr are using a custom protocol(GSUP).
Are there any options to do so?Any suggestion would be appreciated.
I saw some references to RestComm <https://github.com/RestComm/jss7>,
moji-mobile <https://github.com/moiji-mobile/tcap> and signerl
<https://gitea.osmocom.org/erlang/signerl>(seems abandoned), any of these
combinations would work with osmo-msc/hlr?
A side question: is GSUP the only custom protocol used in osmocom gsm
network?all other interactions are based on 3GPP?
Best Regards,
amir.
hello,
i have this issue with osmo-sim-auth.
if i do
sudo python osmo-sim-auth.py -r 00000000000000000000000000000000 -a
ec9320c2c2000000e1dd22c1ad3e2d3d
the cli repeats:
Traceback (most recent call last):
File "osmo-sim-auth.py", line 27, in <module>
from card.USIM import USIM
File "/usr/src/osmo-sim-auth/card/USIM.py", line 56
print '[DBG] type definition: %s' % type(self)
^
SyntaxError: invalid syntax
maybe it's missing a library for USIM or something else?
can you help me get beyond this issue?
Thank you
I'm still having trouble actually getting an Inter-BSC handover to
complete.
I'm using two osmo-bts based BTS and all master/nightly etc..
The problem as far as I can see is the the destination BSC complains that:
HO-interBSC-In: incoming inter-BSC Handover: HO Request: Invalid or
empty Codec List (MSC Preferred) (handover_fsm.c:620)
Stopping the MSC at ran_a_make_handover_request() and inspecting the
stack and local variables I can see that indeed the member
ran_handover_request->codec_list_msc_preferred
at that point is NULL.
Further up the stack in msc_ho_send_handover_request(), is where this
ran_msg of type RAN_MSG_HANDOVER_REQUEST comes into being
https://cgit.osmocom.org/osmo-msc/tree/src/libmsc/msc_ho.c#n385
but at no time do we assign anything to codec_list_msc_preferred,
therefore, when we get to
https://cgit.osmocom.org/libosmocore/tree/src/gsm/gsm0808.c#n995
we are skipping
gsm0808_enc_speech_codec_list(msg, params->codec_list_msc_preferred);
and therefore not calling
msgb_put_u8(msg, GSM0808_IE_SPEECH_CODEC_LIST);
I'm not seeing how this is supposed to work. or what am I missing?
I do see code that looks like it is setting up the
codec_list_msc_preferred, but that seems to relate ONLY to Inter-MSC
Handover.
Thanks
Keith.
Hi,
I'm running OsmoHNBGW version 1.2.1.13.be9e.202204110026 and OsmoSTP version 1.5.0.15.64dd.202204110026.
When a mobile is @ home, and then roams to our network, a "Routing area update request" (SCCP connection request ) is sent by osm-hnbgw to our SGSN.
But the message is ignored by our SGSN, we need to study this further, but we do see some errors related to SCCP in the hnbgw log:
20220411100428998 DMAIN INFO 002448ffff0d2770.servicesnode.spidercloud.com Creating new Mapping RUA CTX 0x558d149bba80/30 <-> SCU Conn ID 0x558d149779a0/1529 (context_map.c:94)
20220411100444098 DLSCCP ERROR SCCP-SCOC(1529)[0x558d14ad2230]{CONN_PEND_OUT}: Event N-DATA.req not permitted (sccp_scoc.c:1772)
20220411100448629 DLSCCP ERROR SCCP-SCOC(1529)[0x558d14ad2230]{CONN_PEND_OUT}: Event N-DATA.req not permitted (sccp_scoc.c:1772)
20220411100453031 DLSCCP ERROR SCCP-SCOC(1528)[0x558d14acb9d0]{WAIT_CONN_CONF}: transition to state IDLE not permitted! (sccp_scoc.c:1031)
20220411100529016 DLSCCP ERROR SCCP-SCOC(1529)[0x558d14ad2230]{WAIT_CONN_CONF}: transition to state IDLE not permitted! (sccp_scoc.c:1031)
20220411100550019 DMAIN INFO 002448ffff0d2770.servicesnode.spidercloud.com Creating new Mapping RUA CTX 0x558d149bba80/30 <-> SCU Conn ID 0x558d149779a0/1530 (context_map.c:94)
20220411100605018 DLSCCP ERROR SCCP-SCOC(1530)[0x558d14ad82b0]{CONN_PEND_OUT}: Event N-DATA.req not permitted (sccp_scoc.c:1772)
20220411100609648 DLSCCP ERROR SCCP-SCOC(1530)[0x558d14ad82b0]{CONN_PEND_OUT}: Event N-DATA.req not permitted (sccp_scoc.c:1772)
20220411100626108 DMAIN INFO 002448ffff0d2770.servicesnode.spidercloud.com Creating new Mapping RUA CTX 0x558d149bba80/30 <-> SCU Conn ID 0x558d149779a0/1531 (context_map.c:94)
20220411100641058 DLSCCP ERROR SCCP-SCOC(1531)[0x558d14ad1c50]{CONN_PEND_OUT}: Event N-DATA.req not permitted (sccp_scoc.c:1772)
20220411100645648 DLSCCP ERROR SCCP-SCOC(1531)[0x558d14ad1c50]{CONN_PEND_OUT}: Event N-DATA.req not permitted (sccp_scoc.c:1772)
20220411100650021 DLSCCP ERROR SCCP-SCOC(1530)[0x558d14ad82b0]{WAIT_CONN_CONF}: transition to state IDLE not permitted! (sccp_scoc.c:1031)
So we think this might be related. The bottom line is that mobile does not attempt a PS attach.
When checking logs for successful RA updates, we see that SGSN receives a standalone SCCP Connection request, this is answered with connection confirmed, and the RA update req comes in with SCCP message type DT1 instead of connection request.
Hope someone can help.
Best Regards
Sjur Thomas Lien
Systems engineer Roaming & Network access
Telenor Maritime
+47 91602376
Kystveien 2D
N-4841 Arendal, Norway
www.telenormaritime.com<http://www.telenormaritime.com/>
LinkedIn<https://www.linkedin.com/company/telenor-maritime/>
[/Users/rinomartinsen/Dropbox (ANTI)/Telenor/2_Projects/TNO036_digitizing and renewal of the telenor identity/FINAL/Toolkit/Logo/Symbol/RGB/pdf/telenor_symbol_blue.pdf]
Internal
Configuration is Network In The Box with everything running on a LimeNET
Micro (RPi CM3+), using Raspbian 10 and osmocom:latest packages via OBS.
UEs can register fine and send/receive SMS, but when I attempt to make a
call I see the Rx RR Assignment Failure error from osmo-bsc.
I have a suspicion it's a configuration error and would appreciate any
suggestions. Attached config and log output.
Regards,
Andrew
Dear Osmocom community,
It's my pleasure to announce the next OsmoDevCall on
April 8, 2022 at 20:00 CEST
at
https://meeting5.franken.de/b/har-xbc-bsx-wvs
In this edition, we will not have a presentation / speaker but just
informal chat / conversation.
Attendance is free of charge and open to anyone with an interest
in Osmocom or open source cellular technologies.
NOTE: There will be no recording of this talk, so if interested,
please make sure you don't miss it!
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
--
- 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)
Hello Osmocom CNI folks,
I am getting ready to set up my own GSM network using nanoBTS hardware
(currently going through the incredible pain of satisfying all
dependencies to get Osmocom CNI software running on Slackware - because
no one makes binary packages for Slackware to my knowledge, I have to
compile from source), and I found this note in this wiki page:
https://osmocom.org/projects/osmobsc/wiki/NanoBTS_Getting_Started
"Do not power up the device without a TX antenna"
Can someone please educate me (and possibly other wondering souls)
*why* one must not power up a nanoBTS with no Tx antenna connected?
I understand how it can be a bad idea to actually turn on Tx output
with an open antenna connector, as the lack of 50 ohm termination
would case Tx energy to reflect back to the PA or whatever internal
components this unit has, but it is also my understanding that these
units turn on their Tx only after they establish a good link with a
BSC, with the BSC then telling the nanoBTS what ARFCN it should
transmit on, and at what power level. Therefore, if I am powering up
a nanoBTS for the purpose of getting its DHCP to work and doing
abisip-find and ipaccess-config steps on it, then during this phase
prior to osmo-bsc configuration, the unit's Tx output should be fully
off - so what would be the problem with having no Tx antenna?
For context, once I get past initial DHCP etc configuration, before I
deploy my nanoBTS on live air, I intend to check its Tx output first:
instead of an antenna, connect an RF measuring instrument (I'll use my
CMU200 in the non-GSM-specific "generic RF analyzer" mode) to the Tx
output port, verify that the frequency it transmits on matches the
ARFCN I configure in osmo-bsc, and verify that Tx power control is
working - and only then put the real antenna on. But it would be
cumbersome to bring the unit into the lab with the CMU200 while I am
sorting out DHCP etc, hence I wonder if it would be OK to have nothing
at all connected to the Tx port while I work on those preliminary
steps.
M~
Hi Harald,
I just stumbled upon your GTP load gen code on the Osmocom git.
My question is: can I use this tool to "act" as an enodeb and test
GTP-U performance? The issue is my S/PGW is a combo one, so if this
GTP load gen tool acts as an SGSN/SGW, I cannot attach it to the
network, as there is no externally accessible S5 interface, just the
2152 GTP-U port used by S1-U.
Thanks!
Csaba