Hi all,
After buying a super Sim Kit (16 in 1) from China, I tried the reader (green PCB inside a blue transparent plastic case with a blue LED) and SIM (identified as a fakesupersim) with pysim tool. However i am getting the following error:
/pySim-prog.py -n 26C3 -c 49 -x 262 -y 42 -z 1234 -j 1 -t auto
Insert card now (or CTRL-C to cancel)
Autodetected card type fakemagicsim
Generated card parameters :
> Name : 26C3
> SMSP : e1ffffffffffffffffffffffff058100945555ffffffffffff000000
> ICCID : 8949262427518313026
> MCC/MNC : 262/42
> IMSI : 262422461512085
> Ki : 7b74741a1ee14337ec23f9ab92a13648
> OPC : ccd867d60797d8d45354a51b3ef568ff
Programming ...
Traceback (most recent call last):
File "./pySim-prog.py", line 530, in <module>
card.program(cp)
File "/home/nadicek/pysim/pysim/pySim/cards.py", line 231, in program
self._scc.update_binary('6f30', hplmn + 'ff' * (tl-3))
File "/home/nadicek/pysim/pysim/pySim/commands.py", line 53, in update_binary
return self._tp.send_apdu_checksw(pdu)
File "/home/nadicek/pysim/pysim/pySim/transport/__init__.py", line 87, in send_apdu_checksw
raise RuntimeError("SW match failed ! Expected %s and got %s." % (sw.lower(), rv[1]))
RuntimeError: SW match failed ! Expected 9000 and got 9804.
I checked mailing lists and haven’t found anybody who had similar problem with pysim. Also I have tried forcing different models of SIM, but nothing is working. Obviously I can remove this check from the script file (__init__.py in /pySim/transport), however somebody had a reason to put such condition there. I would like to ask if it is safe to remove that line of code and the purpose of that line of code.
Thanks a lot and best regards
Martin
> I don't understand. This callback will be called with data you need to
write
> to the network. In case of MTP Level3 you will need to wrap that around
the
> msgb you got.
I means: is the interaction with mtp3 layer implemented (is sending sccp
data by mtp3 implemented by the library?)?
Also, what about the reception of data from mtp3 layer. is that implemented
in the sccp lib.
I am asking these questions because I see the code of mtp3 in the lib but no
significant call is present in the sccp part of the lib.
Thank you for your help.
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
On Tue, Jun 28, 2016 at 10:05:28AM +0200, Harald Welte wrote:
> [translated from german]
> is it certain that we switch a channel to PDCH only when
> gprs mode != none?
A TS can be GSM_PCHAN_TCH_F_PDCH; those are the only ones for which we
send a PDCH ACT message.
We send a PDCH ACT message
- during init (CHANNEL OML's state changed to enabled -> send PDCH ACT),
- and upon channel release ack when pchan == GSM_PCHAN_TCH_F_PDCH.
So the question is, when we receive a channel release ack, could that be
the PDCH release and we switch PDCH right back on by accident? No, because
we only receive a chan rel ack when the *TCH/F* is being released.
That is because the PDCH release is initiated "internally" from the PDCH
DEACT, and thus this condition in common/rsl.c rsl_tx_rf_rel_ack() catches
on, which existed before dyn PDCH:
if (lchan->rel_act_kind != LCHAN_REL_ACT_RSL) {
LOGP(DRSL, LOGL_NOTICE, "%s not sending REL ACK\n",
gsm_lchan_name(lchan));
return 0;
}
In rsl_rx_rf_chan_rel() the rel_act_kind is set to LCHAN_REL_ACT_RSL, but
not in the rsl_rx_dyn_pdch().
This is analogous to the ip.access way -- the ip.access nanobts replies to
a PDCH DEACT with a PDCH DEACT ACK and doesn't send a separate channel
release ack.
Maybe we could set rel_act_kind to some new LCHAN_REL_ACT_IPAC_DYN_PDCH
for clarity? (But we shouldn't actually send a release ack, to stay
compatible.)
Even though it works as-is, we should indeed add another flag check:
- We do check the flags that no ACT/DEACT is already pending;
- And we do send a PDCH DEACT only if ts->flags & TS_F_PDCH_ACTIVE;
- But we would send a PDCH ACT despite ts->flags & TS_F_PDCH_ACTIVE.
This should never happen, but it would make sense to ensure that.
~Neels
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,
I'm trying to integrate the FreeSwitch as my external MNCC in my test lab using split stack. Currently, I'm getting an error message on FreeSwitch SIP/2.0 400 Missing Contact Header. I'm little bit confused with the error and I don't know where to troubleshoot this.
I've attached my osmo configurations and pcap trace for your reference. Hoping for your reply. Thank you.
Regards,
Justin Mark Repollo
Hi list,
today I fixed a header file in libosmocore:
https://gerrit.osmocom.org/c/libosmocore/+/26044
TL;DR, using OSMO_IS_{LITTLE,BIG}_ENDIAN macros without including the
<osmocom/core/endian.h> header leads to empty struct definitions, and
thus weird compiler warnings like 'struct `foo` has no member `bar`'.
We may want to catch missing #include of the <endian.h> automatically,
so I wrote a simple script to check whether it is absent:
https://gerrit.osmocom.org/c/osmo-ci/+/26045
Below is an example of using it:
$ cd libosmocore/
$ verify_endian_header.sh $(find . -name "*.[hc]")
File './include/osmocom/gsm/protocol/gsm_44_004.h'
does not #include <osmocom/core/endian.h>
What's still missing is the actual integration into the build
verification process. I guess there is currently no easy way other than
calling this script from 'contrib/jenkins.sh' of each project?
P.S. I found out that we also have 'scripts/verify_log_statements.py' in
osmo-ci.git, but we don't seem to call it anywhere?
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
Dear All,
I am running a GSM stack:
osmo-stp
smo-msc
osmo-hlr
osmo-bsc
osmo-bts-trx
osmo-trx-lms
It seems that my transmitter is emitting radio-waves into air (osmo-bts-trx and osmo-trx-lms communicate with each other through ports 5702 / 5802 — pls see attached printscreen), however i could not make GSMTAP tracing. Osmo-bts-trx does not send GSMTAP messages to port 4729.
In most recent version of osmo-bts, GSMTAP tracing is arranged through config file:
bts 0
gsmtap-remote-host 127.0.0.1
gsmtap-sapi ccch
I could not run the GSMTAP tracing even in previous verions of osmo-bts where you have to specify in synopsis when you call a program:
/usr/bin/osmo-bts-trx -s -c /etc/osmocom/osmo-bts-trx.cfg --gsmtap-ip 127.0.0.1
I thought may be i am having some issues in stack components behind osmo-bts for example in osmo-bsc or behind and i tried to run virtual bts.
When i tried to run osmo-bts-virtual GSMTAP messages were visible in wireshark (please see attached file osmo-bts-virtual), therefore bts-bsc communication is good.
However I still could not figure out why my osmo-bts-trx does not send GSMTAP messages.
Or would you advise what log might be helpful to see what i am doing wrong ….
Thank you for your always helpful assistance
--
Mario Lucas
----------------------------------------------------------------------
--
Mario Lucas
Dear Osmocom community,
today we finally upgraded our redmine installation from the unmaintained
3.4.x to the latest 4.2.3. The upgrade had been overdue for years,
but today we (actually, Kevin) finally managed to find out how to make
the openid_provider plugin to work with modern rails 5.x.
In any case, I'm just informing you in case there is some unexpected fallout.
I've verified that at least the following appears working:
* logging into redmine
* openid authentication from gerrit.osmocom.org (also after logout/relogin)
* graphviz rendering
* mscgen rendering
There could however still be unexpected problems, particularly in features
such as
* e-mail notifications from redmine
* updating redmine issues via e-mail
* git integration ("Closes: OS#xxxx")
If you run into any troubles, pleas report to https://osmocom.org/projects/osmocom-servers
or if that also fails, feel free to send e-mails.
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)
Not sure if this is a repost, i just joined the list and i don't think i
had confirmed my account when i sent it (the confirmation was in my spam).
Anyways, not trying to be a bad list member.
I just picked up this IPAccess model which supports band 2/5 and has the
same housing as the other units on the accelerate3g5 project docs. I've
been pouring over docs and trying a lot of network configurations in my
home lab. I have the login information for the factory reset and can access
the web gui on port 8089 during the reset process, but ssh and telnet DMI
seem to be disabled. I've been fuzzing ports and i've tried static as well
as DHCP for IP addresses.
My thought was that if i point the nano3G to the IP of my osmo-hNodeB
machine that it would at least stimulate the device and maybe i'd see some
log messages in the HNodeB gateway, but so far i haven't seen anything in
the logs. i've also tried abisip-find and that doesn't find anything.
Wireshark shows basic 'who has' Layer 2 messages and also DHCP requests
sent to 0.0.0.0, both from the nano3g. The nano3g does get an ip from my
lab router and i can ping it. The LAN behind that router can also access
the 0.ipaccess ntp server, but again no telnet DMI or ssh so i'm unsure
where to go from here.
Layer 1 seems to show nothing on the uarfcn in the web gui, so it seems
that its not crossing all the right bridges.
I will admit, i haven't run any other osmo network components for the
network, but as far as i was reading the home nodeb gateway and ntp should
be the only things necessary to at least start the process.
Any insight on what to try next would be very helpful. Does anyone have
experience with this model?
thanks
