simtrace

simtrace@lists.osmocom.org

346 discussions

"OsmoDevCall" on Nov 12, 2021: icE1usb in practice
by Harald Welte 11 Nov '21

11 Nov '21

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at November 12, 2021 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 "E1 / TDM / PDH / SDH basics" by laforge 20:30 presentation "icE1usb in practice" by tnt later USSE: unstructured supplementary social event [*] Attendance is free of charge and open to anyone with an interest in Osmocom. 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)

1 0

Questions about the SIM card for VoWiFi
by Hyunwoo Lee 06 Nov '21

06 Nov '21

Dear, I am Hyunwoo Lee. I am a newbie to configure the custom SIM card. I have one question in configuring sysmoISIM-SJA2 to enable VoWiFi on COTS UEs. The UEs that I am working on are Samsung Galaxy A21, OnePlus 7T, and Motorola G Power. I tried to make the UEs discover the ePDG by sending the DNS query and establish the IPsec channel with my IPsec server. I ran my own DNS server to reply with the IP address of my IPsec server on the DNS query. I tried to make it similar to the T-mobile setting since all of the UEs work well with the T-mobile SIM card. Unfortunately, I could not succeed in enabling VoWiFi on the UEs and I do not know why they do not work and what I can do further. I would appreciate it if someone could help me with this. I described what I did in detail below the line. Thank you in advance for your help! Sincerely, Hyunwoo Lee. ------------------------------ What I did is as follows: 1) Equipments - Two sysmoISIM-SJA2 - PC/SC CCID ISO7816 USB Smart Card Reader - UEs: Samsung Galaxy A21, OnePlus 7T, and Motorola G Power (all of them work well with the T-mobile SIM card) 2) Environment - Ubuntu 18.04 LTS - python 3.6.9 - pySim 1.0 3) Configuration of the SIM cards with pysim - The command that I used to configure the SIM cards (to T-mobile) was: : python3 pySim-prog.py -p 0 -a <adm value> -n name -x 310 -y 260 --imsi=3102601234567890 --msisdn=<telephone number> --epdgid= epdg.epc.mnc260.mcc310.pub.3gppnetwork.org --epdgSelection=310260 --ims-hdomain=ims.mnc260.mcc310.3gppnetwork.org --impi= sip:3102601234567890@ims.mnc260.mcc310.3gppnetwork.org --impu= sip:3102601234567890@ims.mnc260.mcc310.3gppnetwork.org --iccid=<ICCID value> - The mnclen value is set to 3 4) UE behavior with the SIM card - Samsung Galaxy A21 : It sends the DNS query for the ePDG, but does not execute the IKE protocol to establish the IPsec channel with the T-mobile core network. - OnePlus 7T and Motorola G Power : It does not send the DNS query for the ePDG. 5) Configuration result - The command that I used to read the SIM card : python3 pySim-read.py -p 0 - The result of the command Using PC/SC reader interface Reading ... Autodetected card type: sysmoISIM-SJA2 ICCID: 8988211000000459514 IMSI: None GID1: ffffffffffffffffffff GID2: ffffffffffffffffffff SMSP: ffffffffffffffffffffffffffffffffffffffffffffffffe1ffffffffffffffffffffffff0581005155f5ffffffffffff000000 SPN: name Show in HPLMN: True Hide in OPLMN: True PLMNsel: 130062ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PLMNwAcT: 130062ffff # MCC: 310 MNC: 260 AcT: UTRAN, E-UTRAN WB-S1, E-UTRAN NB-S1, GSM, GSM COMPACT, cdma2000 HRPD, cdma2000 1xRTT ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused OPLMNwAcT: 130062ffff # MCC: 310 MNC: 260 AcT: UTRAN, E-UTRAN WB-S1, E-UTRAN NB-S1, GSM, GSM COMPACT, cdma2000 HRPD, cdma2000 1xRTT ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused HPLMNAcT: 130062ffff # MCC: 310 MNC: 260 AcT: UTRAN, E-UTRAN WB-S1, E-UTRAN NB-S1, GSM, GSM COMPACT, cdma2000 HRPD, cdma2000 1xRTT ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ffffff0000 # unused ACC: 0002 MSISDN (NPI=1 ToN=3): 17657759216 Administrative data: 00000003 MS operation mode: normal Ciphering Indicator: disabled SIM Service Table: ff33ffff3f003f0f300cf0c3f00000 Service 1 - CHV1 disable function Service 2 - Abbreviated Dialling Numbers (ADN) Service 3 - Fixed Dialling Numbers (FDN) Service 4 - Short Message Storage (SMS) Service 5 - Advice of Charge (AoC) Service 6 - Capability Configuration Parameters (CCP) Service 7 - PLMN selector Service 8 - RFU Service 9 - MSISDN Service 10 - Extension1 Service 13 - Last Number Dialled (LND) Service 14 - Cell Broadcast Message Identifier Service 17 - Service Provider Name Service 18 - Service Dialling Numbers (SDN) Service 19 - Extension3 Service 20 - RFU Service 21 - VGCS Group Identifier List (EFVGCS and EFVGCSS) Service 22 - VBS Group Identifier List (EFVBS and EFVBSS) Service 23 - enhanced Multi-Level Precedence and Pre-emption Service Service 24 - Automatic Answer for eMLPP Service 25 - Data download via SMS-CB Service 26 - Data download via SMS-PP Service 27 - Menu selection Service 28 - Call control Service 29 - Proactive SIM Service 30 - Cell Broadcast Message Identifier Ranges Service 31 - Barred Dialling Numbers (BDN) Service 32 - Extension4 Service 33 - De-personalization Control Keys Service 34 - Co-operative Network List Service 35 - Short Message Status Reports Service 36 - Network's indication of alerting in the MS Service 37 - Mobile Originated Short Message control by SIM Service 38 - GPRS Service 49 - MExE Service 50 - Reserved and shall be ignored Service 51 - PLMN Network Name Service 52 - Operator PLMN List Service 53 - Mailbox Dialling Numbers Service 54 - Message Waiting Indication Status Service 57 - Multimedia Messaging Service (MMS) Service 58 - Extension 8 Service 59 - MMS User Connectivity Parameters EHPLMN: 130062 # MCC: 310 MNC: 260 ffffff # unused ffffff # unused ffffff # unused USIM Service Table: beff9f9de73e0408400170330006002e00000000 Service 2 - Fixed Dialling Numbers (FDN) Service 3 - Extension 2 Service 4 - Service Dialling Numbers (SDN) Service 5 - Extension3 Service 6 - Barred Dialling Numbers (BDN) Service 8 - Outgoing Call Information (OCI and OCT) Service 9 - Incoming Call Information (ICI and ICT) Service 10 - Short Message Storage (SMS) Service 11 - Short Message Status Reports (SMSR) Service 12 - Short Message Service Parameters (SMSP) Service 13 - Advice of Charge (AoC) Service 14 - Capability Configuration Parameters 2 (CCP2) Service 15 - Cell Broadcast Message Identifier Service 16 - Cell Broadcast Message Identifier Ranges Service 17 - Group Identifier Level 1 Service 18 - Group Identifier Level 2 Service 19 - Service Provider Name Service 20 - User controlled PLMN selector with Access Technology Service 21 - MSISDN Service 24 - Enhanced Multi-Level Precedence and Pre-emption Service Service 25 - Automatic Answer for eMLPP Service 27 - GSM Access Service 28 - Data download via SMS-PP Service 29 - Data download via SMS-CB Service 32 - RUN AT COMMAND command Service 33 - shall be set to 1 Service 34 - Enabled Services Table Service 35 - APN Control List (ACL) Service 38 - GSM security context Service 39 - CPBCCH Information Service 40 - Investigation Scan Service 42 - Operator controlled PLMN selector with Access Technology Service 43 - HPLMN selector with Access Technology Service 44 - Extension 5 Service 45 - PLMN Network Name Service 46 - Operator PLMN List Service 51 - Service Provider Display Information Service 60 - User Controlled PLMN selector for I-WLAN access Service 71 - Equivalent HPLMN Service 73 - Equivalent HPLMN Presentation Indication Service 85 - EPS Mobility Management Information Service 86 - Allowed CSG Lists and corresponding indications Service 87 - Call control on EPS PDN connection by USIM Service 89 - eCall Data Service 90 - Operator CSG Lists and corresponding indications Service 93 - Communication Control for IMS by USIM Service 94 - Extended Terminal Applications Service 106 - ePDG configuration Information support Service 107 - ePDG configuration Information configured Service 122 - 5GS Mobility Management Information Service 123 - 5G Security Parameters Service 124 - Subscription identifier privacy support Service 126 - UAC Access Identities support ePDGId: 657064672e6570632e6d6e633236302e6d63633331302e7075622e336770706e6574776f726b2e6f7267 # epdg.epc.mnc260.mcc310.pub.3gppnetwork.org ePDGSelection: 130062000100 # MCC: 310 MNC: 260 ePDG Priority: 0001 ePDG FQDN format: Operator Identifier FQDN ffffffffffff # unused ffffffffffff # unused ffffffffffff # unused P-CSCF: Not available Not available Not available Not available Not available Not available Not available Not available Home Network Domain Name: ims.mnc260.mcc310.3gppnetwork.org IMS private user identity: sip:3102601234567890@ims.mnc260.mcc310.3gppnetwork.org IMS public user identity: sip:3102601234567890@ims.mnc260.mcc310.3gppnetwork.org Not available Not available Not available Not available Not available Not available Not available UICC IARI: Not available Not available Not available Not available Not available Not available Not available Not available ISIM Service Table: 190200 Service 1 - P-CSCF address Service 4 - GBA-based Local Key Establishment Mechanism Service 5 - Support of P-CSCF discovery for IMS Local Break Out Service 10 - Support of UICC access to IMS Done ! Hyunwoo Lee, Ph. D. Network Security Researcher E-mail: hw5773(a)gmail.com Homepage: https://hw5773.github.io

2 1

Osmocom redmine upgrade / Let me know if something broke
by Harald Welte 27 Oct '21

27 Oct '21

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)

1 0

Simtrace2 tools question
by Paul Cevoli 06 Oct '21

06 Oct '21

Good morning, Working with the simtrace2 code cross compiled for an a53 processor and am running into a few issues. This email summarizes the issues and am wondering if anybody has either resolved these or has any suggestions. The issues are * Cross compiling errors with the simtrace2 host tools * simtrace2-tool run time logging errors Issue #1 simtrace2-cardem-pcsc.c app Simtrace2 requires libosmocore. When trying to build the simtrace2 host tools neither tagged versions of libosmcore 1.5.1 or 1.5.2 will compile correctly. The only way to get the simtrace2 host tools to compile is to use commit cfea39ba. Otherwise the following syntax errors occur in the simtrace2-cardem-pcsc.c app. Is there some magic required to have the simtrace2 host tools compile with a tagged version of libosmocore? CC simtrace2-cardem-pcsc.o simtrace2-cardem-pcsc.c: In function ‘update_flags’: simtrace2-cardem-pcsc.c:94:4: warning: implicit declaration of function ‘osim_card_reset’; did you mean ‘osim_card_open’? [-Wimplicit-function-declaration] 94 | osim_card_reset(card, cold_reset); | ^~~~~~~~~~~~~~~ | osim_card_open simtrace2-cardem-pcsc.c: In function ‘main’: simtrace2-cardem-pcsc.c:441:23: error: ‘OSIM_MAX_ATR_LEN’ undeclared (first use in this function); did you mean ‘USB_MAX_PATH_LEN’? 441 | uint8_t override_atr[OSIM_MAX_ATR_LEN]; | ^~~~~~~~~~~~~~~~ | USB_MAX_PATH_LEN simtrace2-cardem-pcsc.c:441:23: note: each undeclared identifier is reported only once for each function it appears in simtrace2-cardem-pcsc.c:611:45: error: ‘struct osim_card_hdl’ has no member named ‘atr’ 611 | osmo_st2_cardem_request_set_atr(ci, card->atr, card->atr_len); | ^~ simtrace2-cardem-pcsc.c:611:56: error: ‘struct osim_card_hdl’ has no member named ‘atr_len’ 611 | osmo_st2_cardem_request_set_atr(ci, card->atr, card->atr_len); | ^~ simtrace2-cardem-pcsc.c:441:10: warning: unused variable ‘override_atr’ [-Wunused-variable] 441 | uint8_t override_atr[OSIM_MAX_ATR_LEN]; | ^~~~~~~~~~~~ make: *** [Makefile:465: simtrace2-cardem-pcsc.o] Error 1 Issue #2 simtrace2-tool Simtrace2-tool has an assertion error in the osmo logging system, perhaps this is related to the question above about using tagged versions of libosmocore. When trying to use the built version of simtrace2-tool the following stack track occurs: $ simtrace2-tool -V 1d50 -P 60e3 -C 2 -I 0 -S 0 -A 10 modem sim-switch local (C) 2019 Harald Welte <laforge(a)gnumonks.org<mailto:laforge@gnumonks.org>> Setting SIM=LOCAL; Modem reset recommended ERROR: osmo_log_info == NULL! You must call log_init() before using logging in log_check_level()!<webextlink://You%20must%20call%20log_init()%20before%20using%20logging%20in%20log_check_level()!> Assert failed osmo_log_info ../../git/src/logging.c:299 backtrace() returned 8 addresses /usr/lib/libosmocore.so.17(osmo_panic+0xd8) [0xffffbc03abb8] /usr/lib/libosmocore.so.17(log_parse_level+0) [0xffffbc037c00] /usr/lib/libosmocore.so.17(log_check_level+0x30) [0xffffbc039120] /usr/lib/libosmo-simtrace2.so.0(+0x1c50) [0xffffbc077c50] simtrace2-tool(+0x13fc) [0xaaaac79f13fc] /lib/libc.so.6(__libc_start_main+0xe8) [0xffffbbea7878] simtrace2-tool(+0x15b8) [0xaaaac79f15b8] Aborted Adding the osmo logging initialization (listed below) does not, at first glance, appear to help static struct log_info log_info = {}; rc = osmo_libusb_init(NULL); if (rc < 0) { fprintf(stderr, "libusb initialization failed\n"); return rc; } Thank you,

1 1

Announcement of "OsmoDevCall" on September 24, 2021
by Harald Welte 23 Sep '21

23 Sep '21

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at September 24, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation on "ISO 7816 smart card interface FPGA softcore" by tnt 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. 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)

1 0

Announcement of "OsmoDevCall" on August 27, 2021
by Harald Welte 24 Aug '21

24 Aug '21

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at August 27, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation on "osmo-remsim in practice" 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. 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)

1 0

Using simtrace with gps
by Yazid Yemmi 22 Aug '21

22 Aug '21

Hello, I'am currently using simtrace and it works perfectly with my mobile phone, it was for me a training before using it for my main objectif the GPS. i tried to use it and on a a gps it not working , i attached the wireshark file so you can see what i had when i plugged the gps thank you for your help,

1 0

Announcement of "OsmoDevCall" on August 13, 2021
by Harald Welte 12 Aug '21

12 Aug '21

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at August 13, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation on "GSM-R and its differences to GSM" 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. 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)

1 0

Announcement of "OsmoDevCall" on July 23, 2021
by Harald Welte 22 Jul '21

22 Jul '21

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at July 23, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation on "high-level overview on IMS, VoLTE, VoWiFi" 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. 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)

1 0

Announcement of "OsmoDevCall" on July 9, 2021
by Harald Welte 09 Jul '21

09 Jul '21

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at July 9, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 hands-on tutorial by miaoski: Setting up open5gs 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Attendance is free of charge and open to anyone with an interest in Osmocom. 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)

1 0

← Newer
1
...
6
7
8
9
10
11
12
...
35
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

simtrace