Hello Osmocom community,
A question: is it possible to configure OsmoMSC+OsmoHLR such that
authentication is required for those IMSIs for which key material
records are present in HLR subscriber db, yet allow unauthenticated
access for certain other IMSIs (specific ones, *not* accept-all) that
are entered into HLR subscriber db without keys?
My use case: I generally operate my network with SIMs of my own issue,
and I wish to continue enforcing authentication (and using ciphering)
for all Themyscira SIMs. However, I would like to play with some old
phone models which cannot be found unlocked - only operator-locked
units can be found on ebay - and some of those historical operator-
locked phones come with SIM cards in them, issued by historical
operators who have bit the dust ages ago. It would be really nice if
I could add the IMSIs of those defunct-operator SIMs to my HLR
subscriber db and allow them to connect - which would have to be
unauthenticated, as I don't know their Ki or even their A38 algorithm
version - but do so _without_ dropping the authentication requirement
for my own Themyscira IMSIs. Is what I seek possible with current
OsmoMSC and OsmoHLR? And if it isn't possible with current code, any
ideas as to what would be the right way to implement such a feature?
TIA,
Mychaela
[please follow-up-to openbsc(a)lists.osmocom.org so we don't cross-post
all related mails]
Dear Osmocom community,
OsmoDevCall used to be rather successful for quite some time in recent years,
but recently has been suffering quite a bit due to insufficient people
volunteering to present. Big thanks to all who did! Interestingly,
there's no shortage of ideas of topics at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall - but then
many of the potential speakers did not have the interest or time to
follow-up.
Most recently, the last few instances have not been taking place due to a lack
of volunteers during my holidays.
Last, but not least, while during COVID lockdown winter "friday night
8pm" was a good idea, this of course is more difficult during the
summer, when people are more likely want to go out the weekend.
So, to summarize, let me ask some questions:
* would you be interested in OsmoDevCall continuing?
* which day/time/timezone would you prefer ?
* would you be able and willing to volunteer to give at talk within the
next 3 or so months?
Any other suggestions for or around OsmoDevCall are of course also welcome.
Thanks in advance,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Often I struggle to understand memory allocations and the "weird" things
of C, so please point out to me what I'm missing here (I must be wrong,
because you guys would not miss this, right?
cleared_ci = (struct osmo_mgcpc_ep_ci){
.ep = ep,
.mgcp_client_fi = ci->mgcp_client_fi,
.got_port_info = ci->got_port_info,
.rtp_info = ci->rtp_info,
.occupied = true,
/* .pending = true follows below */
.verb = verb,
.notify = {
.fi = notify,
.success = event_success,
.failure = event_failure,
.data = notify_data,
}
};
osmo_strlcpy(cleared_ci.label, ci->label, sizeof(cleared_ci.label));
osmo_strlcpy(cleared_ci.mgcp_ci_str, ci->mgcp_ci_str,
sizeof(cleared_ci.mgcp_ci_str));
*ci = cleared_ci;
LOG_CI_VERB(ci, LOGL_DEBUG, "notify=%s\n",
osmo_fsm_inst_name(ci->notify.fi));
#define LOG_CI_VERB(ci, level, fmt, args...) do { \
if (ci->verb_info.addr[0]) \
LOG_CI(ci, level, "%s %s:%u: " fmt, \
osmo_mgcp_verb_name(ci->verb), ci->verb_info.addr,
ci->verb_info.port, \
## args); \
else \
LOG_CI(ci, level, "%s: " fmt, \
osmo_mgcp_verb_name(ci->verb), \
## args); \
} while(0)
How is ci->verb_info not being using uninitialized here?
Would that explain random crashes with this code?
https://osmocom.org/issues/5572
Hi,
I am looking for contracted support on a osmocom based project, for a
few days of configuration/setup assistance on a 2G / GPRS
configuration. There are a lot of moving parts in the osmocom projects
and versions of individual projects. Best to grab an expert on the
subject than for us to dive in quite so deep just to work through some
configurations. Please email me with contact details and will reach
out immediately!
Jeffery Palmer
GSE
Hi
I'm going to establish a call between two MSes on two different MSCs . Is This Scenario possible without an external application (for MNCC interface)?
Are there any options other than LCR(Linux Call Router)?
Best Regards
Hi Osmocom Team,
Long time listener, first time writer.
Short Version: Would it be possible to get the source for your USIM/ISIM
JavaCard applets that are installed on the sysmoISIM-SJA2, please?
The Alternative: I've been researching a method to give my JavaCard applet
default installation, and if my applet doesn't support the ADPU command,
then it will revert back to your USIM/ISIM applet. Unfortunately, I have
not found a solution. If you know of one, this would solve my ADPU update
problem.
Long Version: I've been looking into how SmartCards work and got interested
in SIM card pertaining to JavaCard applets. I am interested in creating my
own ADPU commands while still supporting all other ADPU commands that
USIM/ISIM provide. Given the awesomeness of your products and dedication to
open source research, I was hoping you can help me by providing the source.
This way, I can overwrite the USIM/ISIM applets on the sysmoISIM-SJA2, and
support my new ADPU updates. BTW, I looked/searched for these in your
github repos and could not find these applets.
Let me know if this is possible. Thanks for being awesome!
--
Jeremy S.
Hello Osmocom community,
Is there anyone here who uses Osmocom CNI software to operate a "real"
cellular phone network (2G or 3G or both) anywhere in USA, or am I
going to be the first? By "real", I mean operating a cellular phone
network that strives to provide a user experience to its subscribers
that is as close as possible to what one would get from a "regular"
operator like AT&T or T-Mobile, aside from much much smaller coverage
area, perhaps as small as the operator's house and its immediate
surroundings. But aside from the tiny coverage area, all other
aspects of user experience need to be fully "real": each subscriber
gets a real 10-digit phone number in the North American Numbering Plan,
can receive calls and SMS at this number, and can place calls and send
SMS to the outside world, with the user's real NANP number appearing
as the source. The principal difference from a self-contained classic
NITB setup is that subscribers' MSISDNs are real NANP, rather than
made-up "extension" numbers, plus a PSTN gateway implementation for
outside connectivity.
Is there anyone in USA (or anywhere else in the world, substituting
your country's "real" numbering plan for NANP) who operates an Osmocom
CNI network in this manner? If there isn't, I will be happy to be the
first, and I will also be quite happy to publish the source for all of
the custom sw components I'm going to develop for this task - which I
plan to implement as add-ons to Osmocom CNI, connecting via MNCC, SMPP
and GSUP interfaces, rather than patches to Osmocom sw components
themselves. However, if I am not the first to embark on such a
venture, it would be nice to know how others have done it before me,
so I can make a more informed decision as to what I can reuse vs which
wheels I would rather reinvent per my own taste.
Someone please correct me if I'm wrong, but it is my understanding
that Rhizomatica (the most "real" and "production" user of Osmocom CNI
I know of) does things differently from what I envision: aside from
being in Mexico rather than USA (hence no NANP), it is my understanding
(again, someone please correct me if I'm wrong) that they don't give
their individual subscribers (end users) direct phone numbers in the
Mexican numbering plan, directly reachable from anywhere in the world
as +52-xxxxx, instead subscribers get "extension" numbers that are
meaningful only inside those special village networks. In other words,
a PBX-style network like the inside of a company with phone extensions,
rather than direct PSTN phone numbers.
I currently plan on using bulkvs.com as my North American PSTN
connectivity back-end provider with real NANP phone numbers, at least
for voice - I haven't found a solution for P2P SMS connectivity yet,
but because of the complexity of the task, I decided to break it into
pieces and focus on just voice at first. However, if someone else has
already done something similar, operating your own cellular network
where your subscribers get real 10-digit NANP phone numbers instead of
just internal extensions, I would be interested in knowing whom you
use (or used) as your back-end provider for PSTN connectivity and
source of phone numbers, and if anyone was able to get P2P SMS
included in the deal.
M~
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
Hi all!
[please follow-up-to the openbsc(a)lists.osmocom.org mailing list, if
there is any discussion, we don't want to drag it over tons of mailing
lists in parallel]
Some weeks ago, I created https://osmocom.org/issues/5397 but it seems nobody
noticed the ticket or had any comments to it.
So let me post this as RFC here on the mailing list:
In the past, we had a gitolite/gitosis setup, which was fine in the
early days of git, but it means that people cannot easily create new
repositories, see who has permissions, and we cannot delegate ownership.
Even updating SSH keys requires manual interaction of a sysadmin like
me.
I would therefore suggest to migrate git.osmocom.org to gitea[1]
This would allow the following features:
* users can self-create any number of personal repositories (like gitlab/github)
* we can create 'organizations' along the line of reasonably independent
osmocom member projects like op25, who can then manage their own
repos/permissions/...
* gitea can link to redmine wiki and redmine issue trackers (rather than
using its own built-in)
For those repositories hosted in gerrit (mainly CNI), we would still
keep git.osmocom.org a read-only mirror, like we do it right now.
For those repositories not hosted in gerrit, users/projects could then
accept merge requests in gitea. Coupling this with 3rd party
authentication via github/gitlab/etc should make it easier for the
occasional contributor to submit changes.
There is a downside, of course; A lot of repo URLs have to change. Most
of our current repositories are at git.osmocom.org/project.git while
gitea follows a git.osmocom.org/organization/project.git scheme. I'm not
sure there is any way to help to mitigate this...
Any thoughts, comments?
[1] https://gitea.io/
--
- 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 Osmocom,
I'm setting up osmo-hnbgw and osm-stp ( on centos 8 ) to work with Spidercloud Hnb, and Ericsson MSC/SGSN.
Today I had a major breakthrough. I've done my first PS and CS attach, even got voice call up. But it's silent. I see in hnbgw manual that I should configure a co-located MGW instance.
I've installed the osmo-mgw, but my problem is the osmo-hnbgw config.
There is no option "mgcp" under node hnbgw, so I'm not able to do the config.
From my osmo-mgw:
OsmoHNBGW(config-hnbgw)#
OsmoHNBGW(config-hnbgw)#
OsmoHNBGW(config-hnbgw)# list
help
list [with-flags]
show vty-attributes
show vty-attributes (application|library|global)
write terminal
write file [PATH]
write memory
write
show running-config
exit
end
rnc-id <0-65535>
log-prefix (hnb-id|umts-cell-id)
iuh
iucs
iups
OsmoHNBGW(config-hnbgw)#
OsmoHNBGW(config-hnbgw)#
OsmoHNBGW(config-hnbgw)# mgcp
% Unknown command.
OsmoHNBGW(config-hnbgw)#
OsmoHNBGW(config-hnbgw)#
OsmoHNBGW(config-hnbgw)#
I'm using version
[root@tmaeurosmohnbgw osmo_hngw_rpms]# osmo-hnbgw -V
OsmoHNBGW version 1.2.1
OsmoHNBGW - Osmocom Home Node B Gateway implementation
Copyright (C) 2016 by sysmocom s.f.m.c. GmbH <info(a)sysmocom.de>
Contributions by Daniel Willmann, Harald Welte, Neels Hofmeyr
License AGPLv3+: GNU AGPL version 3 or later <http://gnu.org/licenses/agpl-3.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
[root@tmaeurosmohnbgw osmo_hngw_rpms]#
All help highly appreciated.
Best regards,
/Sjur
Internal
Hi,
I'm getting closer. But SCTP does not come up, both my real MSC and SGSN sends SCTP ABORT:
283 2022-03-25 08:14:08.200734109 10.30.50.124 -> 10.40.33.6 SCTP 86 INIT
284 2022-03-25 08:14:08.201189770 10.40.33.6 -> 10.30.50.124 SCTP 298 INIT_ACK
285 2022-03-25 08:14:08.201286756 10.30.50.100 -> 10.40.2.66 SCTP 86 INIT
286 2022-03-25 08:14:08.201405921 10.40.2.66 -> 10.30.50.100 SCTP 60 ABORT
287 2022-03-25 08:14:08.204033135 10.30.50.124 -> 10.40.33.6 SCTP 254 COOKIE_ECHO
288 2022-03-25 08:14:08.204405432 10.40.33.7 -> 10.30.50.124 SCTP 130 HEARTBEAT
289 2022-03-25 08:14:08.204423695 10.40.33.6 -> 10.30.50.124 SCTP 64 COOKIE_ACK
290 2022-03-25 08:14:08.204595511 10.40.33.6 -> 10.30.50.124 SCTP 64 ABORT
291 2022-03-25 08:14:08.207135400 10.30.50.124 -> 10.40.33.7 SCTP 60 ABORT
SCTP endpoints:
SGSN HnbGw MSC
-------------------------------------------------------------------------------
10.40.33.6| <---------> 10.30.40.124 |10.40.2.66
10.40.33.7| 10.30.40.100 <---------> |10.40.2.74
I suspect the source port on HnbGw:
Source: 10.30.50.100
Destination: 10.40.2.66
Stream Control Transmission Protocol, Src Port: 38989 (38989), Dst Port: 2905 (2905)
Source port: 38989
Destination port: 2905
The MSC sends ABORT as answer to SCTP-INIT. But our SGSN seems to accept INIT and COOKIE, but eventually sends ABORT.
OsmoHNBGW> show version
OsmoHNBGW 1.2.1 (OsmoHNBGW).
So a few questions:
- I tried to set local port to 2905 under asp in config file, but was rejected ( no such command ). So is there a way to set source port ?
- In MSC and SGSN we must give local and remote port for the SCTP link. Have you tested HnbGW with real Ericsson MSC and SGSN ?
- There are many parameters and timers connected to SCTP protocol:
HBInterval 3;
MaxAssociationRetransmits 10;
MaxInitRetransmits 3;
MaxPathRetransmits 5;
RTOInitial 3000;
RTOMax 6000;
RTOMin 1000;
ValCookieLife 60000;
Are these hardcoded, or could they be configured ?
Thanks,
/Sjur
Internal
Dear Osmocom community,
It's my pleasure to announce the next OsmoDevCall on
March 25, 2022 at 20:00 CET
at
https://meeting5.franken.de/b/har-xbc-bsx-wvs
In this edition, Sec and schneider will present an
"Iridium reverse engineering update".
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.
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 on Friday.
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,
I've managed to install HnbGW on a Centos 8 machine.
But at startup I get many errors of type
socket.c:658 Unable to create socket: Protocol not supported
[root@tmaeurosmohnbgw osmo_hngw_rpms]# osmo-hnbgw
<0004> socket.c:658 Unable to create socket: Protocol not supported
<0010> osmo_ss7.c:1629 0: asp-asp-clnt-OsmoHNBGW: Unable to open stream client for ASP asp-clnt-OsmoHNBGW, 0.0.0.0:0 ==> 10.40.2.66:2905
<0004> socket.c:658 Unable to create socket: Protocol not supported
<0010> osmo_ss7.c:1629 0: asp-asp-clnt-OsmoHNBGW2: Unable to open stream client for ASP asp-clnt-OsmoHNBGW2, 0.0.0.0:0 ==> 10.40.33.6:2905
20220324104532635 DLGLOBAL NOTICE Available via telnet 127.0.0.1 4261 (telnet_interface.c:104)
20220324104532635 DLCTRL NOTICE CTRL at 127.0.0.1 4262 (control_if.c:1017)
20220324104532635 DRANAP NOTICE Remote IuCS SCCP addr: RI=SSN_PC,PC=0.27.4,SSN=RANAP (hnbgw_cn.c:488)
20220324104532636 DRANAP NOTICE Remote IuPS SCCP addr: RI=SSN_PC,PC=0.113.6,SSN=RANAP (hnbgw_cn.c:488)
20220324104532636 DRANAP NOTICE Local SCCP addr: RI=SSN_PC,PC=0.69.3,SSN=RANAP (hnbgw_cn.c:524)
20220324104532636 DLSCCP NOTICE OsmoHNBGW: Using SS7 instance 0, pc:0.69.3 (sccp_user.c:549)
20220324104532636 DLSCCP NOTICE OsmoHNBGW: Using AS instance msc-as (sccp_user.c:567)
20220324104532636 DLSCCP NOTICE OsmoHNBGW: Creating default route (sccp_user.c:572)
20220324104532636 DLSS7 INFO 0: Creating route: pc=0=0.0.0 mask=0x0 via AS 'msc-as' (osmo_ss7.c:830)
20220324104532636 DLSS7 INFO 0: asp-asp-clnt-OsmoHNBGW: Restarting ASP asp-clnt-OsmoHNBGW, r=10.40.2.66:2905<->l=0.0.0.0:0 (osmo_ss7.c:1596)
20220324104532638 DLGLOBAL ERROR Unable to create socket: Protocol not supported (socket.c:658)
20220324104532638 DLINP INFO [WAIT_RECONNECT] osmo_stream_cli_reconnect(): retrying in 5 seconds... (stream.c:286)
20220324104532638 DLSS7 ERROR 0: asp-asp-clnt-OsmoHNBGW: Unable to open stream client for ASP asp-clnt-OsmoHNBGW, 0.0.0.0:0 ==> 10.40.2.66:2905 (osmo_ss7.c:1629)
20220324104532638 DLSCCP NOTICE OsmoHNBGW: Using ASP instance asp-clnt-OsmoHNBGW (sccp_user.c:643)
20220324104532638 DLSS7 NOTICE 0: Creating SCCP instance (osmo_ss7.c:457)
20220324104532638 DLSCCP INFO Binding user 'SCCP Maangement' to SSN=1 PC=(no PC) (sccp_user.c:108)
20220324104532638 DLSCCP INFO Binding user 'OsmoHNBGW' to SSN=142 PC=0.69.3 (sccp_user.c:108)
20220324104532638 DRANAP NOTICE Remote SCCP addr: IuCS: RI=SSN_PC,PC=0.27.4,SSN=RANAP (hnbgw_cn.c:549)
20220324104532638 DRANAP NOTICE Remote SCCP addr: IuPS: RI=SSN_PC,PC=0.113.6,SSN=RANAP (hnbgw_cn.c:551)
20220324104532638 DHNBAP NOTICE Using RNC-Id 23 (hnbgw.c:660)
20220324104532638 DMAIN NOTICE Listening for Iuh at 10.30.50.69 29169 (hnbgw.c:665)
20220324104532640 DLGLOBAL ERROR Unable to create socket: Protocol not supported (socket.c:658)
Cannot open server: Protocol not supported
[root@tmaeurosmohnbgw osmo_hngw_rpms]#
So, does anyone know why I get this socket error ?
I use real MSC and SGSN, here's my config file:
hnbgw
iuh
local-ip 10.30.50.69
local-port 29169
iucs
remote-addr msc
iups
remote-addr sgsn
cs7 instance 0
point-code 0.69.3
asp asp-clnt-OsmoHNBGW 2905 0 m3ua
remote-ip 10.40.2.66
sctp-role client
as msc-as m3ua
asp asp-clnt-OsmoHNBGW
routing-key 2 0.69.3
sccp-address msc
routing-indicator PC
point-code 0.27.4
asp asp-clnt-OsmoHNBGW2 2905 0 m3ua
remote-ip 10.40.33.6
sctp-role client
as sgsn-as m3ua
asp asp-clnt-OsmoHNBGW2
routing-key 2 0.113.6
sccp-address sgsn
routing-indicator PC
point-code 0.113.6
log stderr
logging filter all 1
logging print extended-timestamp 1
logging print category 1
logging print category-hex 0
logging print level 1
logging print file basename last
logging level set-all info
And since I use real MSC and SGSN, I don't need to use osmo-stp, right? As the real nodes act as SCTP servers?
Internal
Hi Osmocom,
Do we have feature/functionality in OSMO-BSC similar to authorized-regex of OSMO-NITB where a IMSI prefix or regex is used to determine if the subscriber is permitted to register to the network or not. I've tried to looked at the osmo-bsc manual but I haven't seen any configurations related to the said feature/functionality. I've tried also the access-list configuration but I think it's no longer supported in latest version.
Regards,
Justin
Hi,
please reply to the ML, not only to me.
according to [1] osmo-hnbw is available in CentOS_8, but I think you are
using CentOS_7. Maybe try using the package from CentOS_8.
[1] https://build.opensuse.org/project/monitor/network:osmocom:nightly
On 3/18/22 08:46, Sjur Thomas Lien wrote:
> Hi,
>
> Thanks for quick feedback.
> First of all, I can't find OsmoHNBGW executable, so that at least needs to be compiled. And I totally agree, I'll use prebuilt packages if I can find them. I did find prebuilt libosmocore, but did not find prebuilt osmo-mgw.
> So when running 'make ' on osmo-mgw, I see that file osmocom/netif/osmux.h is missing. Netif was not available, so I did a git clone of netif, and tried a ./configure.
>
> That's when I got this fault:
>
> checking for osmo_sock_init2_multiaddr in -losmocore... no
> configure: error: libosmocore built without libsctp support
> [root@tmaeurcellmngr libosmo-netif]#
>
> So my conclusion was that the prebuilt libosmocore could not be used in my case. That's why I tried to compile libosmocore from scratch.
>
> But thanks for advice, I'll give it another go.
>
> BR,
> /Sjur
>
--
- 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,
Did a git clone of libosmocore.
./configure gives a few faults when checking the log, but seems to finish OK.
From config.log:
.
.
.
configure:12134: $? = 0
configure:12134: gcc -c -std=gnu11 conftest.c >&5
conftest.c: In function 'main':
conftest.c:71:21: error: expected expression before ')' token
if (sizeof ((size_t)))
^
configure:12134: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "libosmocore"
| #define PACKAGE_TARNAME "libosmocore"
| #define PACKAGE_VERSION "1.6.0.77-381dc"
.
.
.
configure:12379: result: -ldl
configure:12388: checking for library containing dlsym
configure:12419: gcc -o conftest -std=gnu11 conftest.c >&5
/tmp/ccp0wxaN.o: In function `main':
conftest.c:(.text+0xa): undefined reference to `dlsym'
collect2: error: ld returned 1 exit status
configure:12419: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "libosmocore"
| #define PACKAGE_TARNAME "libosmocore"
|
.
.
.
There are more "conftest.c" errors, but not sure if these are very serious.
Anyway, ./configure finishes off without errors when done executing.
So next thing is "make".
And here I encounter a problem that stops the process:
[root@tmaeurcellmngr libosmocore]# make
make all-recursive
make[1]: Entering directory `/root/hnbgw/osmo-hnbgw/libosmocore'
Making all in include
make[2]: Entering directory `/root/hnbgw/osmo-hnbgw/libosmocore/include'
make all-am
make[3]: Entering directory `/root/hnbgw/osmo-hnbgw/libosmocore/include'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/root/hnbgw/osmo-hnbgw/libosmocore/include'
make[2]: Leaving directory `/root/hnbgw/osmo-hnbgw/libosmocore/include'
Making all in src
make[2]: Entering directory `/root/hnbgw/osmo-hnbgw/libosmocore/src'
make all-am
make[3]: Entering directory `/root/hnbgw/osmo-hnbgw/libosmocore/src'
CC context.lo
gcc: error: /usr/local/lib:/lib:/usr/lib64: No such file or directory
make[3]: *** [context.lo] Error 1
make[3]: Leaving directory `/root/hnbgw/osmo-hnbgw/libosmocore/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/root/hnbgw/osmo-hnbgw/libosmocore/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/hnbgw/osmo-hnbgw/libosmocore'
make: *** [all] Error 2
[root@tmaeurcellmngr libosmocore]#
So this my "real" problem.
I did find a compiled version of libosmocore and thought this would help me to compile osmoHNBGW.
But , as OsmoHNBGW need a MGW client I ran into another problem. During "make" of osm-mgw:
.
.
CC mgcp_protocol.o
In file included from mgcp_protocol.c:39:0:
../../include/osmocom/mgcp/osmux.h:5:33: fatal error: osmocom/netif/osmux.h: No such file or directory
#include <osmocom/netif/osmux.h>
.
.
And I saw that "netif" was not there at all. Did a git clone of netif.
Then I did a "netif" ./configure. But then I see a new problem, probably caused by the use of the already-compiled libmocore:
.
.
checking netinet/sctp.h usability... yes
checking netinet/sctp.h presence... yes
checking for netinet/sctp.h... yes
checking for osmo_sock_init2_multiaddr in -losmocore... no
configure: error: libosmocore built without libsctp support
[root@tmaeurcellmngr libosmo-netif]#
So , I've hit the wall here.
Best Regards,
Sjur
Internal
Hi,
maybe you remember me: I am a TTCN-3 tool developer and fan of your TTCN-3 test suite. :)
Therefore I'd like to shamelessly promote a test oriented conference by ETSI, which I think some of you could be interested in.
The User Conference on Advanced Automated Testing is calling for submissions, deadline is 2 May 2022. Topics of interest include:
* Open-source projects, testing solutions and automated test frameworks.
* Lessons learnt from advanced test automation techniques (CI, AI, Cloud, ...)
* Good practices for automated testing (TDD, BDD, MBT, ...)
* Advances in test specification languages and methodologies
* ...
See you in Munich maybe?
Cheers,
Matthias
PS: Forgive me, if this mail was inappropriate for this channel.
Hey Neels,
and potentially other users of osmo-dev.git reading the ML,
since I'm using osmo-dev's net scripts to test OsmoBSCNAT while
developing it, I submitted patches with significant changes that make
testing easier/possible:
* config_mine is now a diff to config_2g3g
* optionally build mobile + virtphy from osmocom-bb.git
* optionally start BSC2, virtual BTS, virtual MS
* all cmds can be overwritten in config_mine now, without modifying
run.sh (e.g. to use valgrind, CMD_BSCNAT="valgrind osmo-bsc-nat")
Patches were submitted for review here:
https://gerrit.osmocom.org/c/osmo-dev/+/27432/1
Related osmo-bsc-nat patches:
https://gerrit.osmocom.org/c/osmo-bsc-nat/+/27461
Best,
Oliver
--
- Oliver Smith <osmith(a)sysmocom.de> https://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 Osmocom community,
It's my pleasure to announce the next OsmoDevCall on
March 11, 2022 at 20:00 CET
at
https://meeting5.franken.de/b/har-xbc-bsx-wvs (URL has changed!)
In this edition, Kevin "tsaitgaist" Redon will present on
"USB-C - the connector and USB-PD (Power Delivery)".
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 on Friday.
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)
Dear fellow Osmocom developers,
as you all know, we've sadly had to skip OsmoDevCon 2020 and 2021,
trying to compensate it at least to some extent with our OsmoDevCall
every two weeks.
The COVID-19 pandemic is far from over, and we don't know what the
upcoming winter season will bring.
Nevertheless, I think it would be a good idea to start a discussion of
whether we should plan for an OsmoDevCon in 2022.
I personally would say let's plan for the usual late April 2022 time frame,
and if the pandemic situation deteriorates, we can still cancel it with
something like one month lead time.
I would also personally suggest to limit attendance to people who are fully
vaccinated, and in addition do a self-test for all participants every
morning.
In terms of venue, we might also consider to move to a venue that allows better
ventilation. Irrespective of the above we can also bring the air filters from
the sysmocom office.
So with that as an input statement, I would like to hear your opinion
on the above proposals. Who would want to attend? Any complaints against
the "vaccinated only plus daily self-tests in the morning" approach?
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)
Just now I looked at the failures in ttcn3-bsc-test-latest.
https://jenkins.osmocom.org/jenkins/job/ttcn3-bsc-test-latest/
TL;DR: we should roll a release.
Two real failures happen that are actual bugs in the latest release,
and the rest of the failures are due to the lingering subscriber leak.
BSC_Tests.TC_ho_into_this_bsc
fails because osmo-bsc-latest omits the 'Codec List (BSS Supported)' in the
Handover Request Acknowledge message, which is mandatory on AoIP. This error is
fixed on osmo-bsc master. It makes no sense to me to punch a hole in the tests
for latest -- this failure shows a real failure of the current osmo-bsc
release.
BSC_Tests.TC_cm_service_during_lcs_loc_req
shows a subscriber leak, where a bsc_subscr is not cleaned up. This bsc_subscr
lingers all the way to the end of the BSC_Tests run, and all other current
failures of ttcn3-bsc-test-latest are due to that. (The only one not failing is
TC_refuse_chan_act_to_vamos(), because it is the only one not verifying that no
bsc_subscr stay behind.)
So this also shows a real error in the current osmo-bsc release.
There is nothing I would do at this point to make bsc-test-latest appear to be
passing, because the errors shown are errors.
The conclusion is that it might be time to roll another release one of these
days.
Related: important fixes I recently submitted are all merged to master, so from
my side it would be a good time.
~N
--
- 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 Osmocom community,
It's my pleasure to announce the next OsmoDevCall on
February 25, 2022 at 20:00 CET
at
https://meeting5.franken.de/b/har-xbc-bsx-wvs (URL has changed!)
In this edition, I will present about a number of "advanced" SIM card topics,
such as GlobalPlatform SCP02, OTA, ARA-M and the ISIM applet.
This meeting will have the following schedule:
20:00 meet + greet
20:10 talk on advanced SIM topics by @laforge
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 on Friday.
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)
Dear Osmocom community,
It's my pleasure to announce the next OsmoDevCall on
February 11, 2022 at 20:00 CET
at
https://meeting5.franken.de/b/har-xbc-bsx-wvs (URL has changed!)
In this edition, we will not have a presentation, as unfortunately nobody
has volunteered to present this time. Nevertheless, we will still have
the call in case anyone wants to chat about random stuff.
This meeting will have the following schedule:
20:00 meet + greet
20:10 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 on Friday.
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)
Hello Harald & Co.
This sounds like a positive development. If there is any resulting trouble(s) we'll deal with it if / as nec.
Let me take this opportunity to thank you and Osmocom for hosting OP25.
Best Regards
Max
Hello,
I need help to understand my problem installing a simple HelloWorld applet
on USIM card.
There is already a USIM applet (AID: a0000000871002ffXXffXX89) running
there, so perhaps that's the issue.
1. Should I remove it?
Here is my code to INSTALL (for load), LOAD, INSTALL (for install):
https://gist.github.com/Novitoll/2d8146b85f4384eb4dd039eb8116d1ed
2. All of them returns 9000, which is OK, I'm using a simple CardReader,
but when I insert the SIM to a phone, no applet comes up.
Initially, I thought that the AID for instance is the reason. So when I do
https://gist.github.com/Novitoll/2d8146b85f4384eb4dd039eb8116d1ed#file-appl…
... module_aid="d07002CA44900101", app_aid="d07002CA44900101"
I'm getting 6A88 (Referenced data not found). I changed it to
A0000000871002FFffFFff8900000101
A000000087 - RID for 3GPP
1002 - USIM
FFff - country code
FFff - card issuer code
89 - Telecom
00000101 - App version? Havent figured out this yet
the answer is 9000. But no app pops up on the phone once I insert SIM card
back.
3. Also I'm checking if any load file actually ends up by taking some
non-volatile space in SIM -- no difference.
4. After Install for install, there is nothing to be done, rght? Like
updating EF_DIR is not required, where USIM is the only applet.
Could you please assist? My twitter is twitter.com/novitoll
Thanks,
--
Sabr
Dear Osmocom community,
It's my pleasure to announce the next OsmoDevCall on
January 28, 2022 at 20:00 CET
at
https://meeting4.franken.de/b/har-xbc-bsx-wvs
In this edition, laforge will present a number of brief (lightning)
talks about a number of projects he's currently been thinking about or
working on, including
* efficient TDMoIP protocol
* TDMoIP community network
* hardware design of ISDN BRI interface for TDMoIP community network
* continuous testing setup for simtrace2 "cardem" firmware
* non-transparent ISA-over-USB bridge attached to qemu
The idea is to ping-pong some ideas wit others and maybe find somebody interested in helping out.
This meeting will have the following schedule:
20:00 meet + greet
20:10 various brief talks (see 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 on Friday.
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)
Hello,
Sorry, for the late reply. (replying again in new thread as prev mails failed).
Quoted prev mails in quotes below.
>> Which is "your test sim". Can you share the make and model?
It's a sysmoUSIM-SJS1, I believe.
I'm receiving 9000 for INSTALL for load, and for consequent LOAD
commands 9000 as well. Only for the last INSTALL for install, I'm
getting 6A88 (reference data not found). I think, the issue is in
AIDs. I'm trying to figure out if I should use arbitrary bytes for AID
or construct AID (which includes RID + RIX) the same way as
existing Load Files, Applets' AID are on the SIM card?
I'm using d07002CA44 from this https://github.com/mrlnc/HelloSTK2,
I believe that should be reason for the 6A88 error code.
Could you please assist?
Here is my Install for Install Python3 code:
--
def install_install_make_selectable(self, exe_rid="d07002CA44",
module_aid="d07002CA44900101",
app_aid="d07002CA44900101"):
apdu = "".join([
"80", # CLS
"e6", # INSTR
"0c", # p1 ; for install (b3=1) ; for make selectable (b4=1)
"00", # p2
"%02x", # p3 ; Lc
])
# 11.5.2.3.2, page 170
data = "".join([
"%02x" % int(len(exe_rid)/2),
exe_rid, # V, executable Load file AID / load file AID
"%02x" % int(len(module_aid)/2),
module_aid, # V, executable Module AID / class file AID
"%02x" % int(len(app_aid)/2),
app_aid, # V, Application AID / instance AID
"0100", # L privileges ; V=00, 11.1.2 Privileges
Coding, page 146
"%02x", # L Install Parameters field
])
system_params_v = "".join([
"c802", # TL - non-volatile memory quota
"00ff", # V
"c702", # TL - volatile memory quota
"00ff",
])
install_params_tl = "".join([
"EF", # T - System Specific Parameters
"%02x"
])
install_params_v = ""
install_params_v += system_params_v
install_params_v += "".join([
# ETSI 102 226, page 23
# 8.2.1.3.2.1 Coding of the SIM File Access and Toolkit
Application Specific Parameters
"ca",
"%02x", # TL
])
toolkit_app_params = "".join([
"01", # L of access domain
##
## Access Domain
## 00 - full access
## 01 - APDU access (reserved for 2G; see 3GPP TS 31 116)
## 02 - UICC access (reserved for 3G)
## ff - no access
##
"ff", # V access domain
"01", # V priority
"00", # V max timers
"0f", # V max menu text
"02", # V max menu entries
"0000" * int("02"),
"00", # max number of channels for this application instance
"00", # length of MSL
])
install_params_v = install_params_v %
int(len(toolkit_app_params)/2) + toolkit_app_params
### C9 - Application Specific Parameters (none?)
applet_specific_params_v = "".join([
""
])
applet_specific_params_tlv = "".join([
"c9",
"%02x" % int(len(applet_specific_params_v)/2),
applet_specific_params_v
])
install_params_v += applet_specific_params_tlv
install_params = install_params_tl %
int(len(install_params_v)/2) + install_params_v
data = data % int(len(install_params)/2) + install_params
data += "00" # load token
apdu = apdu % int(len(data)/2) + data
apdu += "00c0000000" # C-MAC
return apdu
--
> On Dec 24, 2021, 2:51 AM, Sabyrzhan Tasbolatov wrote:
> Hello,
>
> I need help with installing the HelloWorld.cap applet in my test SIM.
> I know how to construct APDUs and osmocom's shadysim.py,
> does not work properly for me. So I've written the script myself.
>
> https://gist.github.com/Novitoll/2d8146b85f4384eb4dd039eb8116d1ed
>
> GP "Card Specification – Public Release v2.3.1".
>
> 1. Install for LOAD, Data = 00, SW = 9000
> 2. LOAD 0, SW = 9000
> 3. LOAD 1, SW = 9000
> 4. LOAD 2, SW = 9000
> 5. LOAD 3, SW = 9000, final
> 6. Install for install and make selectable, SW = 6988 (Reference data not found)
>
> Trying to figure out where the issue is.
> I've tried to re-use `install_app` function from shadysim.py - same result.
>
> I'm using this https://github.com/mrlnc/HelloSTK2/blob/main/HelloSTK2.cap
>
> Could anyone assist?
--
>> On Tue, Jan 4, 6:30 PM, Harald Welte wrote:
>> Hi Sabr,
>> On Mon, Jan 03, 2022 at 03:51:54PM +0600, Sabyrzhan Tasbolatov wrote:
>>> Following up
>>
>>I didn't see your original mail, sorry.
>>
>>> > I need help with installing the HelloWorld.cap applet in my test SIM.
>>
>>Which is "your test sim". Can you share the make and model?
>>
>>> > I know how to construct APDUs and osmocom's shadysim.py
>>> > <https://git.osmocom.org/sim/sim-tools/tree/shadysim/shadysim.py>,
>>> > does not work properly for me.
>>
>>please note that different cards have different expectations (and bugs) on the exact
>>parameters to load applets. Also, shadysim is a "early proof of concept"
>>and not something that intended to be a full implementation and/or
>>support a wide variety of cards with related workarounds, etc.
Hello all,
I'm looking for some guidance on adding an ADF which I will then be able to
select by AID to a SysmoISIM-SJA2. Primarily I'm curious if there's any
reason this WOULDN'T be doable before I continue down the rabbit hole of
figuring it out.
What I've tried so far is:
1) Pushing the applet to the SIM using shadysim_isim.py. It loads fine, and
when I enable SIM toolkit it appears properly on my Android device. When I
try to SELECT the AID however I get an error saying the AID doesn't exist.
2) I figure the above error is because EF.DIR doesn't include the AID, so
I update the first empty record in EF.DIR to include the AID of my applet.
When I try to SELECT the AID now I get the same error however.
I'm not sure how to proceed but I figure now is a good time to see if it is
in fact possible before spinning my wheels further. If anyone can point me
in the right direction or even just a yes/no about whether it can be done
that would be greatly appreciated.
Best,
Bryan
Following up
On Fri, Dec 24, 2021 at 2:51 AM Sabyrzhan Tasbolatov <snovitoll(a)gmail.com>
wrote:
> Hello,
>
> I need help with installing the HelloWorld.cap applet in my test SIM.
> I know how to construct APDUs and osmocom's shadysim.py
> <https://git.osmocom.org/sim/sim-tools/tree/shadysim/shadysim.py>,
> does not work properly for me. So I've written the script myself.
>
> https://gist.github.com/Novitoll/2d8146b85f4384eb4dd039eb8116d1ed
>
> GP "Card Specification – Public Release v2.3.1".
>
> 1. Install for LOAD, Data = 00, SW = 9000
> 2. LOAD 0, SW = 9000
> 3. LOAD 1, SW = 9000
> 4. LOAD 2, SW = 9000
> 5. LOAD 3, SW = 9000, final
> 6. Install for install and make selectable, SW = 6988 (Reference data not
> found)
>
> Trying to figure out where the issue is.
> I've tried to re-use `install_app` function from shadysim.py - same result.
>
> I'm using this https://github.com/mrlnc/HelloSTK2/blob/main/HelloSTK2.cap
>
> Could anyone assist?
>
> --
> Sabr
>
--
Sabr
Hi all,
I'd like to draw attention again to the state of codecs handling in OsmoMSC master.
The reason being that the recent IuUP changes create conflicts with the
neels/mncc_codecs3 branch.
I fear that we are currently doing the same thing that we discourage everyone
else from doing: keeping an important branch on the side and not upstreaming it.
There is recurrent overhead on rebasing the branch.
Facts about OsmoMSC: master neels/codecs_mncc*
heeds MS Bearer Cap from ComplL3 NO YES
logically combines codec constraints NO YES
communicates available codecs to/via SIP NO YES
worked at last congress NO YES
has the last IuUP patches YES NO
I think the reasoning for completing that codecs work and merging the branch is
compelling. Can we somehow achieve that before OsmoMSC diverges further?
I could start maybe by holding a talk on it in an OsmoDevCall? That way I've
read all of the code again and can explain what the patch does why, to ease
review. Or maybe spend that time on merging the code instead? Or both? :)
~N
Dear Osmocom community,
It's my pleasure to announce the next OsmoDevCall on
January 14, 2022 at 20:00 CET
at
https://meeting4.franken.de/b/har-xbc-bsx-wvs
This meeting will have the following schedule:
20:00 meet + greet
20:10 presentation "Codesc in OsmoMSC, MNCC and SIP" by neels
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 on Friday.
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 all,
I have a SysmoISIM-SJA2 which I believe doesn't have a CAT application and
doesn't support the SUSPEND APDU (per the manual). Given that, is there any
way to reset/refresh the card through APDU commands (or through any other
means)? Would something along the lines of deactivating and then
reactivating the USIM application work?
Thanks,
Bryan
Dear Osmocom community,
today our mailing list server lists.osmocom.org has finally been migrated
from mailman2-on-freebsd to mailman3-on-linux. This also included a variety
of changes to DNS. I'll spare you the details, but everything _should_ be up
and running now.
* The List-Id headers should not have changed.
* all list subscriptions + user accounts have been converted.
* old 'static html' archives are still available (read only) at URLs like
https://lists.osmocom.org/pipermail/baseband-devel/
* old List URLs like https://lists.osmocom.org/mailman/listinfo/baseband-devel
are redirected to their respective modern counterparts
In case you notice any mailing list related problem, please don't hesitate to
contact me.
Happy hacking,
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)