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)
those harmonics) must be above:
-30 dBm @ 30 kHz span above 1 GHz
-36 dBm @ 30 kHz span below 1 GHz
In case of UmTRX without an amplifier it's enough to use a ceramic or
SAW duplexer to bring harmonics below those levels.
For those buying UmTRX's as a lab package of universal UmDESKs, we
offer to buy an external ceramic duplexers. These improves coverage
and solves the out of band noise issues.
For those buying band-specific UmDESK's, we use SAW duplexers, which
are even more efficient in reducing out of band noise.
>> A calibrated USRP N200 running osmo-trx passes RF spectrum and
>> modulation accuracy requirements of 3GPP 05.05 by very large margins
>> and is competitive with commercial GSM equipment in this regard. Other
>> SDR devices are also capable to varying degrees.
>
> The policy of FCC vs. European Union is quite different. There are more
> norms that apply in Europe.
You're obviously more proficient in European norms. Could you point me
to a link where we could find these differences between the ETSI
published GSM Standard and European harmonized norms?
It would be a very good addition to the OpenBSC wiki's "Standards" page.
--=20
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / =D0=9E=D0=9E=D0=9E =D0=A3=D0=BC=D0=A0=D0=B0=D0=B4=D0=
=B8=D0=BE
http://fairwaves.ru
