August 2021 - baseband-devel - lists.osmocom.org

SMS not received in mobile - Virtual layer1 (osmo-nitb + osmo-bts + osmocom-bb/mobile)
by Sebastian Stumpf 05 Jun '26

05 Jun '26

Hi, Some of my sent SMS are not received by my mobile and I try to figure out if this is a problem with my virtual layer 1, configuration or something in the layers 2+. I use: osmo-nitb: 1 subscriber in hlr (id 1, ext 017519191919) osmo-bts: virt-phy, arfcn 666, TS0=CCCH+SDCCH4, TS1=SDCCH8 MS layer23 app mobile: is the subscriber from osmo-nitb MS layer1 virt-phy: virtual gsmtap layer between bts and mobile I want: Send a sms to subscriber 017519191919. osmo-nitb VTY: OpenBSC# subscriber id 1 sms sender id 1 send Test I have 2 outcomes, first one is the failure. See https://www.dropbox.com/s/eunpfioq518t09a/mobile--ms-virt--bts-virt--bsc-ni… for the pcap. Do not wonder about the duplicated gsmtap messages from mobile, the ones to ip 225.0.0.1 are over virt-phy layer, the ones to localhost from the gsmtap logging option from mobile. Filter them out via "gsmtap && (ip.dst != 127.0.0.1)". 602-613: RR channel establishment with RA and IA as reaction to paging in 590 627,631: SABM from BTS to establish async balanced mode on SAPI3 (SMS) and the ACK from MS 656,684,699: I-Data frames on SAPI3 containing the sms 660,688,703: ReceiveReady's from MS (That ACK all I-frames before N(R)-1 as far as I understood) For me, that looks good and I really do not understand why the MS will not answer with the CP-ACK/RP-ACK after receiving the SMS Data in 699. The LAPDM link will stay up for some more time and be used by the network for retransmission of the sms (1149), but MS will never react to it on the SMS layer (CP-ACK, RP-ACK). Here is the console log for the mobile (https://www.dropbox.com/s/6gug5cd4up5qv7y/mobile--ms-virt--bts-virt--bsc-ni…) The paging is answered in line 378: Fri Mar 10 10:42:06 2017 DLLAPD <0012> lapd_core.c:793 SABM(E) received in state LAPD_STATE_IDLE Second outcome is a successfully sent sms from network to ms. See https://www.dropbox.com/s/ghdn7pc0j4vifbe/mobile--ms-virt--bts-virt--bsc-ni… for the pcap. What is different here? There is no paging, but the sms is sent within the dedicated channel used for the location update initiated by the phone started up. Why there is another outcome, I don't know. 169-181: RR channel establishment with RA and IA as part of mibiles startup routine to make location update 188,416: Location udpdate procedure on SAPI0 230,234: SABM from BTS to establish async balanced mode on SAPI3 (SMS) and the ACK from MS 396,444: I-Data frames on SAPI3 containing the sms 400,449: RR's from MS 450: CP-ACK for BTS 482,499: RP-ACK I-Frames for Network (osmo-nitb) Again, the console log of the mobile (https://www.dropbox.com/s/cujsn40d43g6wxk/mobile--ms-virt--bts-virt--bsc-ni…) The SABM on SAPI3 on downlink is received in line 206: Fri Mar 10 11:06:13 2017 DLLAPD <0012> lapd_core.c:793 SABM(E) received in state LAPD_STATE_IDLE The signaling looks quite similar in both cases, but one time the mobiles sms handler responds to CP-DATA msg containing the SMS, the other time not. Can someone find an error in the signaling I did not see? Is there a known Bug? To be honest, I last merged my branch with master some time ago (~ Jan 18 2017) and thus did not update osmo-nitb and the libraries since then to avoid compatibility problems. Have there been recent changes that could cause that behavior? Thank you and Kind Regards, Sebastian

4 3

Engagetted !
by Sébastien Lorquet 14 Oct '25

14 Oct '25

http://www.engadget.com/2010/12/29/researchers-eavesdrop-on-encrypted-gsm-c… Congrats!

7 7

Phone without a physical sim to connect to network
by Mario Lucas 30 Aug '21

30 Aug '21

Dear All, I have a running BTS (based on SDR) and i can connect my phone to my network… do / learn some operations… I have a couple of sim cards and each time i want to connect to network with different sim i have to switch of mobile remove previous sim put new one etc etc …. Is there an application that will be running on PC and connected to my phone which will a kind of simulate sim and connect my phone to my network ? Avoiding me each time physically remove previous sim put new one etc etc … Would you be so kind and advise me please… Also another question — is there a «search» option in the archives : http://lists.osmocom.org/pipermail/openbsc/ http://lists.osmocom.org/pipermail/baseband-devel/ just not to post questions which already could have been answered…. -- Mario Lucas

3 2

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

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

Leaks simcom ?
by Bastien 09 Aug '21

09 Aug '21

https://github.com/bbaranoff/simcom https://pl4y.store https://simcom.ee/documents

2 1

CalypsoBTS with recent OsmoBTS in 2021?
by . 06 Aug '21

06 Aug '21

Hello, I'm trying to run CalypsoBTS as described here: https://osmocom.org/projects/baseband/wiki/CalypsoBTS I'm using a single Motorola C123 phone and in my openbsc.conf, i have only one CCCH+SDCCH4 channel on timeslot 0: timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 I'm using the fixeria/trx branch with recent OsmoBTS. First, i load the trx firmware on the phone, and then i start the transceiver host app to sync with a known ARFCN. The syncing goes without any issues. Then, i start OpenBSC through OsmoNITB like that: osmo-nitb -c ~/.osmocom/openbsc.cfg -l ~/.osmocom/hlr.sqlite3 -P -C --debug=DRLL:DCC:DMM:DRR:DRSL:DNM --yes-i-really-want-to-run-prehistoric-software And OsmoBTS: osmo-bts-trx -c ~/.osmocom/osmo-bts.cfg OsmoBTS fails almost instantly with: <0012> input/ipaccess.c:898 received ID_GET for unit ID 1801/0/0 <000b> trx_if.c:701 phy0.0: Response message 'RSP ERR 1 ' does not match command message 'CMD RFMUTE 1' <000b> trx_if.c:645 phy0.0: transceiver rejected TRX command with response: 'ERR 1' <0001> oml.c:221 (bts=0,trx=0): O&M Get Attributes [0], Manufacturer Dependent State is unsupported by TRX. <000b> trx_if.c:134 phy0.0: Ignoring CLOCK IND 2061832, TRX not yet powered on The last message repeats until i terminate the application. On the OsmoNITB side, i get: <0005> abis_nm.c:550 OC=BTS(01) INST=(00,ff,ff) Get Attributes Response for BTS0 <0005> abis_nm.c:463 BTS0 Get Attributes Response Info: 72 bytes total with 0 unreported attributes <0005> abis_nm.c:497 BTS0 Get Attributes Response: reported unexpectedly long (3 bytes) feature vector - most likely it was compiled against newer BSC headers. Consider upgrading your BSC to later version. <0005> abis_nm.c:507 BTS0 feature 'Frequency Hopping' reported via OML does not match statically set feature: 1 != 0. Please fix. <0005> abis_nm.c:507 BTS0 feature 'Multi-TSC' reported via OML does not match statically set feature: 1 != 0. Please fix. <0005> abis_nm.c:507 BTS0 feature 'OML Alerts' reported via OML does not match statically set feature: 1 != 0. Please fix. <0005> abis_nm.c:507 BTS0 feature 'CBCH' reported via OML does not match statically set feature: 1 != 0. Please fix. <0005> abis_nm.c:577 BTS0: failed to parse SW-Config part of Get Attribute Response Info: Invalid argument <0005> abis_nm.c:550 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) Get Attributes Response for BTS0 <0005> abis_nm.c:463 BTS0 Get Attributes Response Info: 34 bytes total with 1 unreported attributes <0005> abis_nm.c:468 BTS0 Attribute Manufacturer Dependent State is unreported <0005> abis_nm.c:577 BTS0: failed to parse SW-Config part of Get Attribute Response Info: Invalid argument <0005> abis_nm.c:771 OC=SITE-MANAGER(00) INST=(ff,ff,ff) Opstart ACK <0005> abis_nm.c:381 OC=SITE-MANAGER(00) INST=(ff,ff,ff) STATE CHG: OP_STATE=Enabled AVAIL=OK(ff) ADM=Locked <0005> abis_nm.c:1938 OC=SITE-MANAGER(00) INST=(ff,ff,ff) Sending OPSTART <0005> abis_nm.c:771 OC=SITE-MANAGER(00) INST=(ff,ff,ff) Opstart ACK And on the transceiver side, between the successful CLK Indication messages, i get: <0011> trx.c:509 [!] No handlers found for command 'RFMUTE'. Empty response <0011> trx.c:226 TRX Control send: |RSP ERR 1 | Is this issue due to the unimplemented in the transceiver command "RFMUTE" or what really fails is: <0005> abis_nm.c:577 BTS0: failed to parse SW-Config part of Get Attribute Response Info: Invalid argument ? I also tried using components from their circa-2017-2018 revisions but there are so many changes in core Osmocom libraries that they always fail to compile and fixing them is hardly worth it, given the amount of work it is. I know OsmoNITB is abandoned since 2017, but currently this is the only way for a beginner to experiment with BTS based on cheap Calypso phones, as it is not implemented in the new Oscomcom stack.

1 0