OpenBSC August 2022

openbsc@lists.osmocom.org

8 participants
23 discussions

two distinct SCCP sources?
by Neels Hofmeyr 29 Aug '22

29 Aug '22

I'm confused by what is happening in the pcap linked below: According to wireshark, the SCCP message seems to come from *both* PC=4 and PC=185. A column configured as sccp.calling.pc shows Point-Code 4. A column configured as "Source Address" shows Point-Code 185. Is it even possible that the in-band Calling Address differs from whatever wireshark detects as the SCCP Source Addres? Can anyone explain where the 185 is coming from? apparently not from sccp.calling.pc. The pcap and a screenshot showing the two point-codes and the column config are here: http://people.osmocom.org/neels/Eew7we0I/ Context: The original RESET message (not part of the pcap) was sent to called.pc=4, but I have SCCP routing set up to forward PC=4 to the MSC that sees itself as PC=185. I am expecting to see a RESET-ACK sent from PC=185. IIUC The 4 should have evaporated when the MSC parsed the RESET message. But apparently when answering, it takes the "called.pc" and puts it in the response as "calling.pc" (4 is nowhere in the MSC's confguration, it MUST have taken the "4" from the received SCCP message). So what I am seeing in wireshark is eerily correct: it is the MSC that has "185" in its cfg as local address sending the ACK, and it is responding to a request that was originally sent to "4", and which osmo-stp routed to "185". The response shows calling.pc=4. But how can wireshark know that it was really "185" sending, when no such information is in the SCCP layer of that message? What am I missing? if anyone knows, thanks in advance... ~N

2 2

New repository - libosmo-gprs.git
by Vadim Yanitskiy 18 Aug '22

18 Aug '22

Hi all, as some of you may know, I am working on the MS side implementation of GPRS protocol stack. The end goal is to have something similar to srsUE (part of srsRAN, former srsLTE), but for GPRS. In order to reduce code duplication it was decided to move some stuff from both osmo-pcu.git and osmo-sgsn.git into shared libraries, so that we could re-use existing code in the upcoming MS side implementation. == What is already done * Redmine: https://osmocom.org/projects/libosmo-gprs * Gerrit: https://gerrit.osmocom.org/q/libosmo-gprs * Gitea: https://gitea.osmocom.org/osmocom/libosmo-gprs * osmo-ci.git: https://gerrit.osmocom.org/c/osmo-ci/+/29019 == What is missing * GitHub: https://github.com/osmocom/libosmo-gprs * cgit: https://cgit.osmocom.org/libosmo-gprs/ ** Coverity pulls from this mirror ** Jenkins build verification uses this mirror I will need some help with both GitHub and cgit, as I don't have admin permissions. Please also let me know if I missed something. 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

4 8

shadysim STK installation issue
by Karsten Ohme 11 Aug '22

11 Aug '22

I tried to use shadysim (https://gitea.osmocom.org/sim-card/sim-tools) to install a STK / CAT applet on the sysmoISIM. It was not working for me, also it does not support UICC parameters and it seems that still Python 2.7 is needed. As an alternative I have added support for gpshell (https://kaoh.github.io/globalplatform/) to use SCP02 and pass the SIM/UICC parameters. See the new parameters "uiccSystemSpecParam" and "simSpecParam" for the "install" command https://github.com/kaoh/globalplatform/blob/master/gpshell/src/gpshell.1.md and inspect the https://github.com/kaoh/globalplatform/blob/master/gpshell/helloInstallSTK.… example file. If "brew" ins installed then "brew install kaoh/globalplatform/globalplatform" is sufficient for the installation. I also faced the issue that the sysmoISIM cards are only accepting SIM parameters and no UICC parameters, which is strange or even a bug since these cards are newer and are supporting the newer UICC ETSI specifications.

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC August 2022