OpenBSC August 2022

openbsc@lists.osmocom.org

8 participants
23 discussions

On the use of 'decmatch' in TTCN-3
by Harald Welte 27 Jan '26

27 Jan '26

Hi, I know that TTCN-3 is still new to a lot of you, but we are writing tons of integration testing against the various osmocom programs in it. It is quite amazing technology, and I would like to ask you to bear with me reading this mail :) Pau was stating the question earlier today on not finding an example on how to use decmatch. Indeed, it took me some months to find that gem in the TTCN-3 world. It solves the problem that you often have during test of layered protocol stacks: you have separate encoders/decoders for each protocol layer, and now you want to match on some of the *inner* payload. So normally, you have some kind of header definition + a binary (octetstring) payload. This happens in RSL with the L3_INFO IE, and just the same on BSSAP/DTAP where again the L3 message (for example call control) is encapsulated inside one information element. Now you have multiple options of addressing the problem: a) hand-written calls to the decoder function b) write na 'emulation' for the entire protocol layer c) use decmatch. a) would look like this (pseudo-code): var octetstring l3oct; var RSL_Message rsl RSL.receive(tr_RSL_DATA_REQ(g_chan_nr, ?, ?)) -> value rsl { var PDU_ML3_MS_NW l3 := dec_PDU_ML3_MS_NW(rsl.payload); if (match(l3, some_template)) { ... do something } ... } Which uses the built-in pattern-matching on the RSL port to match any message that matches the tr_RSL_DATA_REQ template, and stores the resulting RSL message in a variable. It then uses an explicit call to the decoder function of the L3 message, and then uses regular conditional expressions for further matching on that inner L3 payload. This is more or less how you would write in C, python or any other quite imperative programming languages. It's very verbose, time consuming and un-abstract/elegant. TTCN-3 has many declarative aspects to it. Code like the above is a waste of your time :) b) would mean that you implement some test component that handles the RSL messages on its bottom side test port, and the L3 messages on its top side test port. That is a possible way, and if you need a lot of state/logic of RSL, it maeks sense. But what if you really simply want to have a match? Then it would be a lot of effort and a large detour. c) decmatch to the rescue! You can write RSL.receive(tr_RSL_DATA_REQ(g_chan_nr, ?, decmatch tr_RRM_RR_STATUS)) which means: * do a receive on the RSL test port, and match on an incoming RSL message that matches the tr_RSL_DATA_REQ template, with channel number specified, link_id any (?), *and* if the octetstring payload, if decoded, matches the template tr_RRM_RR_STATUS ! This is *extremely* powerful and expressive. It allows you to condense complex, parametric template matching over multiple proocol layers. It would in the end match RSL DATA REQUEST, only if they contained a [valid] encoded RR STATUS. See https://gerrit.osmocom.org/6229 for the actual test case I used for the above examples. Please also note that I never had to even write the function name of the decoder (dec_PDU_ML3_MS_NW), but TTCN-3 *automatically* figures out which decoder function it must call in order to decode from the binary octetstring. Happy (TTCN-3) hacking + Osmocom bugfixing, 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)

3 3

osmo-gsm-manuals in project repos: I see no .pdf
by Neels Hofmeyr 08 Jan '26

08 Jan '26

Hi Oliver, so I merged the stuff to add the manuals to the individual git repositories, since you said that it works. But when I do --enable-manuals I don't see any PDF files generated. Also a manual 'make pdf' says "nothing to be done". (I probably should have tried it before merging after all) So what am I doing wrong? Alternatively, can you fix it please? ~N

3 3

Some phones cant receive SMS
by Henry Caga 16 Dec '25

16 Dec '25

Hi, I would like to ask for help regarding my osmo-bsc setup. I have 2 problems as of now. 1) My setup is working fine on my phones, i can send and receive sms. However, on some phones, i can only send sms or call. But i cannot receive sms. I attached the sample logs from the phone that can receive sms and phone that cannot receive sms. I also included my config files. 2) i have a GPSDO TCXO and i wanted to use the maximum setting like setting up the 10mhz reference. what should i set or configure at the config files in order to set it? 3) Is there a way to improve my setup? Im using 50w PA and are there any settings that i have missed? Thank you Henry Phone that can receive sms ========= 20220226175408907 DRLL <0000> chan_alloc.c:240 (bts=0) channel load average is 0.00% 20220226175408907 DRLL <0000> chan_alloc.c:253 (bts=0) T3122 wait indicator set to 10 seconds 20220226175409767 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226175414767 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226175415439 DLSCCP <0020> sccp_user.c:175 Delivering N-UNITDATA.indication to SCCP User 'msc-0' 20220226175415439 DMSC <0007> osmo_bsc_sigtran.c:231 N-UNITDATA.ind(00 16 52 08 08 59 51 20 20 02 00 04 21 09 04 23 1d 63 44 1a 03 05 03 f4 ) 20220226175415439 DMSC <0007> osmo_bsc_bssap.c:1259 Rx MSC UDT: 00 16 52 08 08 59 51 20 20 02 00 04 21 09 04 23 1d 63 44 1a 03 05 03 f4 20220226175415439 DMSC <0007> osmo_bsc_bssap.c:1116 Rx MSC UDT BSSMAP PAGING 20220226175415439 DMSC <0007> osmo_bsc_bssap.c:131 Paging request from MSC BTS: 0 IMSI: '515020220004012' TMSI: '0x231d6344/589128516' LAC: 0x3f4 20220226175416335 DRSL <0003> abis_rsl.c:1383 (bts=0) CHAN RQD: reason: answer to paging (ra=0x9e, neci=0x01, chreq_reason=0x01) 20220226175416335 DRLL <0000> lchan_select.c:173 (bts=0) lchan_select_by_type(SDCCH) 20220226175416335 DRLL <0000> lchan_select.c:87 looking for lchan CCCH+SDCCH4: (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4,state=UNUSED) ss=0 is available 20220226175416335 DRSL <0003> abis_rsl.c:476 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4,state=IN_USE) Tx RSL Channel Activate with act_type=INITIAL 20220226175416662 DMSC <0007> fsm.c:461 SUBSCR_CONN[0x558560323460]{INIT}: Allocated 20220226175416662 DMSC <0007> gsm_08_08.c:489 Tx MSC COMPL L3 20220226175416662 DRSL <0003> gsm_08_08.c:232 RR GSM48_MT_RR_PAG_RESP: TMSI-0x231D6344 matches earlier Paging from msc 0 20220226175416662 DMSC <0007> osmo_bsc_sigtran.c:308 Initializing resources for new SCCP connection to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP... 20220226175416663 DMSC <0007> gsm_08_08.c:532 SUBSCR_CONN(msc0-conn4294967295_IMSI515020220004012)[0x558560323460]{INIT}: Received Event MO-CONNECT.req 20220226175416663 DMSC <0007> osmo_bsc_sigtran.c:350 Allocated new connection id: 7 20220226175416663 DMSC <0007> osmo_bsc_sigtran.c:354 Opening new SCCP connection (id=7) to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP 20220226175416663 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-CONNECT.request) 20220226175416663 DLSCCP <0020> fsm.c:461 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: Allocated 20220226175416663 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: Received Event N-CONNECT.req 20220226175416663 DLSCCP <0020> sccp_scoc.c:830 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: state_chg to CONN_PEND_OUT 20220226175416663 DMSC <0007> bsc_subscr_conn_fsm.c:286 SUBSCR_CONN(msc0-conn4294967295_IMSI515020220004012)[0x558560323460]{INIT}: state_chg to WAIT_CC 20220226175416664 DLSCCP <0020> sccp_scoc.c:1662 Received CO:COAK for local reference 7 20220226175416664 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{CONN_PEND_OUT}: Received Event RCOC-CONNECT_CONFIRM.ind 20220226175416664 DLSCCP <0020> sccp_scoc.c:981 SCCP-SCOC(7)[0x55856030ca50]{CONN_PEND_OUT}: state_chg to ACTIVE 20220226175416664 DLSCCP <0020> sccp_user.c:175 Delivering N-CONNECT.confirm to SCCP User 'msc-0' 20220226175416664 DMSC <0007> osmo_bsc_sigtran.c:244 N-CONNECT.cnf(7, ) 20220226175416664 DMSC <0007> osmo_bsc_sigtran.c:247 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{WAIT_CC}: Received Event MO-CONNECT.cfm 20220226175416664 DMSC <0007> bsc_subscr_conn_fsm.c:354 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{WAIT_CC}: state_chg to ACTIVE 20220226175416664 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 7 20220226175416664 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event RCOC-DT1.ind 20220226175416664 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226175416664 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(7, 00 0b 2f 08 08 59 51 20 20 02 00 04 21 ) 20220226175416664 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x55856030c700]{CONN}: Received Event EV_N_CONNECT 20220226175416664 DMSC <0007> osmo_bsc_bssap.c:1153 Rx MSC DT1 BSSMAP COMMON ID 20220226175416664 DMSC <0007> osmo_bsc_bssap.c:1099 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event COMMON_ID.ind 20220226175416664 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 7 20220226175416664 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event RCOC-DT1.ind 20220226175416664 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226175416664 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(7, 01 03 26 09 01 23 01 00 07 91 44 77 58 10 06 50 00 17 20 06 d1 32 99 0c 00 00 22 20 62 71 45 51 23 07 f4 f2 9c 9e 76 9f 01 ) 20220226175416664 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x55856030c700]{CONN}: Received Event EV_N_CONNECT 20220226175416664 DMSC <0007> osmo_bsc_bssap.c:1208 Rx MSC DTAP: 01 03 26 09 01 23 01 00 07 91 44 77 58 10 06 50 00 17 20 06 d1 32 99 0c 00 00 22 20 62 71 45 51 23 07 f4 f2 9c 9e 76 9f 01 20220226175416664 DMSC <0007> osmo_bsc_bssap.c:1232 Rx MSC DTAP, SAPI: 3 CHAN: 0 20220226175416664 DMSC <0007> osmo_bsc_bssap.c:1249 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event MT_DTAP 20220226175416664 DRLL <0000> abis_rsl.c:833 (bts=0,trx=0,ts=0,ss=0) RSL RLL ESTABLISH REQ (link_id=0x03) 20220226175416757 DRSL <0003> abis_rsl.c:1082 (bts=0,trx=0,ts=0,ss=0): meas_rep_count++=1 meas_rep_last_seen_nr=0 20220226175416907 DRLL <0000> chan_alloc.c:240 (bts=0) channel load average is 0.20% 20220226175416907 DRLL <0000> chan_alloc.c:253 (bts=0) T3122 wait indicator set to 10 seconds 20220226175417227 DRSL <0003> abis_rsl.c:1082 (bts=0,trx=0,ts=0,ss=0): meas_rep_count++=2 meas_rep_last_seen_nr=1 20220226175417839 DMSC <0007> gsm_08_08.c:548 Tx MSC DTAP LINK_ID=0x03 20220226175417839 DMSC <0007> gsm_08_08.c:554 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event MO_DTAP 20220226175417839 DMSC <0007> osmo_bsc_sigtran.c:394 Tx MSC: DTAP 20220226175417839 DMSC <0007> osmo_bsc_sigtran.c:418 Sending connection (id=7) oriented data to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP (01 03 02 89 04 ) 20220226175417839 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-DATA.request) 20220226175417839 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event N-DATA.req 20220226175418075 DMSC <0007> gsm_08_08.c:548 Tx MSC DTAP LINK_ID=0x03 20220226175418075 DMSC <0007> gsm_08_08.c:554 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event MO_DTAP 20220226175418075 DMSC <0007> osmo_bsc_sigtran.c:394 Tx MSC: DTAP 20220226175418076 DMSC <0007> osmo_bsc_sigtran.c:418 Sending connection (id=7) oriented data to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP (01 03 09 89 01 06 02 00 41 02 00 00 ) 20220226175418076 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-DATA.request) 20220226175418076 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event N-DATA.req 20220226175418085 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 7 20220226175418085 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event RCOC-DT1.ind 20220226175418085 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(7, 01 03 02 09 04 ) 20220226175418085 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x55856030c700]{CONN}: Received Event EV_N_CONNECT 20220226175418085 DMSC <0007> osmo_bsc_bssap.c:1208 Rx MSC DTAP: 01 03 02 09 04 20220226175418085 DMSC <0007> osmo_bsc_bssap.c:1232 Rx MSC DTAP, SAPI: 3 CHAN: 0 20220226175418085 DMSC <0007> osmo_bsc_bssap.c:1249 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event MT_DTAP 20220226175418085 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 7 20220226175418085 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event RCOC-DT1.ind 20220226175418085 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(7, 00 04 20 04 01 09 ) 20220226175418085 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x55856030c700]{CONN}: Received Event EV_N_CONNECT 20220226175418085 DMSC <0007> osmo_bsc_bssap.c:1153 Rx MSC DT1 BSSMAP CLEAR COMMAND 20220226175418085 DMSC <0007> osmo_bsc_bssap.c:473 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: Received Event CLEAR_CMD 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:774 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{ACTIVE}: state_chg to CLEARING 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:775 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Releasing all lchans (if any) after BSSMAP Clear Command 20220226175418085 DMSC <0007> lchan_fsm.c:1458 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: lchan lchan(0-0-0-CCCH_SDCCH4-0)[0x55856030cee0] detaches from conn 20220226175418085 DRR <0002> gsm_04_08_rr.c:323 Sending Channel Release: Chan: Number: 0 Type: 1 RR-Cause: 0x0 'Normal event' 20220226175418085 DRSL <0003> abis_rsl.c:644 (bts=0,trx=0,ts=0,ss=0) DEACTivate SACCH CMD 20220226175418085 DRLL <0000> abis_rsl.c:857 (bts=0,trx=0,ts=0,ss=0) RSL RLL RELEASE REQ (link_id=0x03, reason=1) 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:390 Tx MSC: BSSMAP: CLEAR COMPLETE 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:418 Sending connection (id=7) oriented data to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP (00 01 21 ) 20220226175418085 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-DATA.request) 20220226175418085 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event N-DATA.req 20220226175418085 DLSCCP <0020> sccp_scoc.c:1662 Received CO:RELRE for local reference 7 20220226175418085 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: Received Event RCOC-RELEASED.ind 20220226175418085 DLSCCP <0020> sccp_user.c:175 Delivering N-DISCONNECT.indication to SCCP User 'msc-0' 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:274 N-DISCONNECT.ind(7, , cause=768) 20220226175418085 DMSC <0007> osmo_bsc_sigtran.c:281 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Received Event DISCONNET.ind 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:791 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Terminating (cause = OSMO_FSM_TERM_REGULAR) 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:862 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: FSM instance already terminating, not dispatching event LCLS_FAIL 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:866 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Releasing all lchans (if any) because this conn is terminating 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:845 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Putting bsc_subscr 20220226175418085 DMSC <0007> bsc_subscr_conn_fsm.c:791 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Freeing instance 20220226175418085 DMSC <0007> fsm.c:573 SUBSCR_CONN(msc0-conn7_IMSI515020220004012)[0x558560323460]{CLEARING}: Deallocated 20220226175418085 DLSCCP <0020> sccp_scoc.c:1070 SCCP-SCOC(7)[0x55856030ca50]{ACTIVE}: state_chg to IDLE 20220226175418085 DLSCCP <0020> sccp_scoc.c:517 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: Terminating (cause = OSMO_FSM_TERM_REQUEST) 20220226175418085 DLSCCP <0020> sccp_scoc.c:517 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: Freeing instance 20220226175418085 DLSCCP <0020> fsm.c:573 SCCP-SCOC(7)[0x55856030ca50]{IDLE}: Deallocated 20220226175419767 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226175424767 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226175424910 DRLL <0000> chan_alloc.c:240 (bts=0) channel load average is 3.03% 20220226175424910 DRLL <0000> chan_alloc.c:253 (bts=0) T3122 wait indicator set to 10 seconds ========= Phone that doesnt receive sms ========== 20220226173512464 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226173514434 DRLL <0000> chan_alloc.c:240 (bts=0) channel load average is 0.00% 20220226173514434 DRLL <0000> chan_alloc.c:253 (bts=0) T3122 wait indicator set to 10 seconds 20220226173517464 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226173519748 DLSCCP <0020> sccp_user.c:175 Delivering N-UNITDATA.indication to SCCP User 'msc-0' 20220226173519748 DMSC <0007> osmo_bsc_sigtran.c:231 N-UNITDATA.ind(00 16 52 08 08 59 51 20 11 27 23 70 04 09 04 38 2a bc 18 1a 03 05 03 f4 ) 20220226173519748 DMSC <0007> osmo_bsc_bssap.c:1259 Rx MSC UDT: 00 16 52 08 08 59 51 20 11 27 23 70 04 09 04 38 2a bc 18 1a 03 05 03 f4 20220226173519748 DMSC <0007> osmo_bsc_bssap.c:1116 Rx MSC UDT BSSMAP PAGING 20220226173519748 DMSC <0007> osmo_bsc_bssap.c:131 Paging request from MSC BTS: 0 IMSI: '515021172320740' TMSI: '0x382abc18/942324760' LAC: 0x3f4 20220226173522006 DRSL <0003> abis_rsl.c:1383 (bts=0) CHAN RQD: reason: answer to paging (ra=0x87, neci=0x01, chreq_reason=0x01) 20220226173522006 DRLL <0000> lchan_select.c:173 (bts=0) lchan_select_by_type(SDCCH) 20220226173522006 DRLL <0000> lchan_select.c:87 looking for lchan CCCH+SDCCH4: (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4,state=UNUSED) ss=0 is available 20220226173522006 DRSL <0003> abis_rsl.c:476 (bts=0,trx=0,ts=0,pchan=CCCH+SDCCH4,state=IN_USE) Tx RSL Channel Activate with act_type=INITIAL 20220226173522295 DMSC <0007> fsm.c:461 SUBSCR_CONN[0x56450d5e3f80]{INIT}: Allocated 20220226173522295 DMSC <0007> gsm_08_08.c:489 Tx MSC COMPL L3 20220226173522295 DRSL <0003> gsm_08_08.c:232 RR GSM48_MT_RR_PAG_RESP: TMSI-0x382ABC18 matches earlier Paging from msc 0 20220226173522295 DMSC <0007> osmo_bsc_sigtran.c:308 Initializing resources for new SCCP connection to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP... 20220226173522295 DMSC <0007> gsm_08_08.c:532 SUBSCR_CONN(msc0-conn4294967295_IMSI515021172320740)[0x56450d5e3f80]{INIT}: Received Event MO-CONNECT.req 20220226173522295 DMSC <0007> osmo_bsc_sigtran.c:350 Allocated new connection id: 5 20220226173522295 DMSC <0007> osmo_bsc_sigtran.c:354 Opening new SCCP connection (id=5) to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP 20220226173522295 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-CONNECT.request) 20220226173522295 DLSCCP <0020> fsm.c:461 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: Allocated 20220226173522295 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: Received Event N-CONNECT.req 20220226173522295 DLSCCP <0020> sccp_scoc.c:830 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: state_chg to CONN_PEND_OUT 20220226173522295 DMSC <0007> bsc_subscr_conn_fsm.c:286 SUBSCR_CONN(msc0-conn4294967295_IMSI515021172320740)[0x56450d5e3f80]{INIT}: state_chg to WAIT_CC 20220226173522296 DLSCCP <0020> sccp_scoc.c:1662 Received CO:COAK for local reference 5 20220226173522296 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(5)[0x56450d5e2160]{CONN_PEND_OUT}: Received Event RCOC-CONNECT_CONFIRM.ind 20220226173522296 DLSCCP <0020> sccp_scoc.c:981 SCCP-SCOC(5)[0x56450d5e2160]{CONN_PEND_OUT}: state_chg to ACTIVE 20220226173522296 DLSCCP <0020> sccp_user.c:175 Delivering N-CONNECT.confirm to SCCP User 'msc-0' 20220226173522296 DMSC <0007> osmo_bsc_sigtran.c:244 N-CONNECT.cnf(5, ) 20220226173522296 DMSC <0007> osmo_bsc_sigtran.c:247 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{WAIT_CC}: Received Event MO-CONNECT.cfm 20220226173522296 DMSC <0007> bsc_subscr_conn_fsm.c:354 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{WAIT_CC}: state_chg to ACTIVE 20220226173522296 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 5 20220226173522296 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event RCOC-DT1.ind 20220226173522296 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226173522296 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(5, 00 0b 2f 08 08 59 51 20 11 27 23 70 04 ) 20220226173522296 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x56450d5d3700]{CONN}: Received Event EV_N_CONNECT 20220226173522296 DMSC <0007> osmo_bsc_bssap.c:1153 Rx MSC DT1 BSSMAP COMMON ID 20220226173522296 DMSC <0007> osmo_bsc_bssap.c:1099 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{ACTIVE}: Received Event COMMON_ID.ind 20220226173522296 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 5 20220226173522296 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event RCOC-DT1.ind 20220226173522296 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226173522296 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(5, 01 03 28 09 01 25 01 00 07 91 44 77 58 10 06 50 00 19 20 0c 91 36 39 71 82 34 93 00 00 22 20 62 71 53 91 23 06 f4 f2 9c 0e 92 01 ) 20220226173522296 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x56450d5d3700]{CONN}: Received Event EV_N_CONNECT 20220226173522296 DMSC <0007> osmo_bsc_bssap.c:1208 Rx MSC DTAP: 01 03 28 09 01 25 01 00 07 91 44 77 58 10 06 50 00 19 20 0c 91 36 39 71 82 34 93 00 00 22 20 62 71 53 91 23 06 f4 f2 9c 0e 92 01 20220226173522296 DMSC <0007> osmo_bsc_bssap.c:1232 Rx MSC DTAP, SAPI: 3 CHAN: 0 20220226173522296 DMSC <0007> osmo_bsc_bssap.c:1249 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{ACTIVE}: Received Event MT_DTAP 20220226173522296 DRLL <0000> abis_rsl.c:833 (bts=0,trx=0,ts=0,ss=0) RSL RLL ESTABLISH REQ (link_id=0x03) 20220226173522439 DRLL <0000> chan_alloc.c:240 (bts=0) channel load average is 0.20% 20220226173522439 DRLL <0000> chan_alloc.c:253 (bts=0) T3122 wait indicator set to 10 seconds 20220226173522464 DNM <0004> abis_nm.c:345 BTS 0 reported connected PCU version 0.8.0.178-b75c2 20220226173522766 DMSC <0007> gsm_08_08.c:71 Tx MSC SAPI N REJECT DLCI=0x03 20220226173522766 DMSC <0007> gsm_08_08.c:74 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{ACTIVE}: Received Event TX_SCCP 20220226173522766 DMSC <0007> osmo_bsc_sigtran.c:390 Tx MSC: BSSMAP: SAPI N REJECT 20220226173522766 DMSC <0007> osmo_bsc_sigtran.c:418 Sending connection (id=5) oriented data to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP (00 06 25 18 03 04 01 25 ) 20220226173522766 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-DATA.request) 20220226173522766 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event N-DATA.req 20220226173522768 DLSCCP <0020> sccp_scoc.c:1662 Received CO:CODT for local reference 5 20220226173522768 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event RCOC-DT1.ind 20220226173522768 DLSCCP <0020> sccp_user.c:175 Delivering N-DATA.indication to SCCP User 'msc-0' 20220226173522768 DMSC <0007> osmo_bsc_sigtran.c:261 N-DATA.ind(5, 00 04 20 04 01 09 ) 20220226173522768 DMSC <0007> a_reset.c:227 A-RESET(msc-0)[0x56450d5d3700]{CONN}: Received Event EV_N_CONNECT 20220226173522768 DMSC <0007> osmo_bsc_bssap.c:1153 Rx MSC DT1 BSSMAP CLEAR COMMAND 20220226173522768 DMSC <0007> osmo_bsc_bssap.c:473 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{ACTIVE}: Received Event CLEAR_CMD 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:774 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{ACTIVE}: state_chg to CLEARING 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:775 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Releasing all lchans (if any) after BSSMAP Clear Command 20220226173522768 DMSC <0007> lchan_fsm.c:1458 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: lchan lchan(0-0-0-CCCH_SDCCH4-0)[0x56450d5e4240] detaches from conn 20220226173522768 DRR <0002> gsm_04_08_rr.c:323 Sending Channel Release: Chan: Number: 0 Type: 1 RR-Cause: 0x0 'Normal event' 20220226173522768 DRSL <0003> abis_rsl.c:644 (bts=0,trx=0,ts=0,ss=0) DEACTivate SACCH CMD 20220226173522768 DMSC <0007> osmo_bsc_sigtran.c:390 Tx MSC: BSSMAP: CLEAR COMPLETE 20220226173522768 DMSC <0007> osmo_bsc_sigtran.c:418 Sending connection (id=5) oriented data to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP (00 01 21 ) 20220226173522768 DLSCCP <0020> sccp_scoc.c:1729 Received SCCP User Primitive (N-DATA.request) 20220226173522768 DLSCCP <0020> sccp_scoc.c:1769 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event N-DATA.req 20220226173522768 DLSCCP <0020> sccp_scoc.c:1662 Received CO:RELRE for local reference 5 20220226173522768 DLSCCP <0020> sccp_scoc.c:1695 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: Received Event RCOC-RELEASED.ind 20220226173522768 DLSCCP <0020> sccp_user.c:175 Delivering N-DISCONNECT.indication to SCCP User 'msc-0' 20220226173522768 DMSC <0007> osmo_bsc_sigtran.c:274 N-DISCONNECT.ind(5, , cause=768) 20220226173522768 DMSC <0007> osmo_bsc_sigtran.c:281 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Received Event DISCONNET.ind 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:791 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Terminating (cause = OSMO_FSM_TERM_REGULAR) 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:862 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: FSM instance already terminating, not dispatching event LCLS_FAIL 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:866 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Releasing all lchans (if any) because this conn is terminating 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:845 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Putting bsc_subscr 20220226173522768 DMSC <0007> bsc_subscr_conn_fsm.c:791 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Freeing instance 20220226173522768 DMSC <0007> fsm.c:573 SUBSCR_CONN(msc0-conn5_IMSI515021172320740)[0x56450d5e3f80]{CLEARING}: Deallocated 20220226173522768 DLSCCP <0020> sccp_scoc.c:1070 SCCP-SCOC(5)[0x56450d5e2160]{ACTIVE}: state_chg to IDLE 20220226173522768 DLSCCP <0020> sccp_scoc.c:517 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: Terminating (cause = OSMO_FSM_TERM_REQUEST) 20220226173522768 DLSCCP <0020> sccp_scoc.c:517 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: Freeing instance 20220226173522768 DLSCCP <0020> fsm.c:573 SCCP-SCOC(5)[0x56450d5e2160]{IDLE}: Deallocated ======== Osmo-bts-trx config ! ! OsmoBTS () configuration saved from vty !! ! log stderr logging color 1 logging timestamp 0 logging level rsl notice logging level oml notice logging level rll notice logging level rr notice logging level meas error logging level pag error logging level l1c error logging level l1p error logging level dsp error logging level abis error logging level loop debug ! line vty no login ! phy 0 instance 0 !COMMENT HERE FOR DEFAULT JOJO osmotrx rx-gain 50 osmotrx tx-attenuation 0 !osmotrx rx-gain 10 !osmotrx tx-attenuation oml !osmotrx maxdly 20 osmotrx ip local 127.0.0.1 osmotrx ip remote 127.0.0.1 bts 0 band 900 ipa unit-id 1012 0 oml remote-ip 127.0.0.1 gsmtap-sapi ccch gsmtap-sapi pdtch !ADDED FOR TEST JOJO gsmtap-sapi bcch gsmtap-sapi rach gsmtap-sapi agch gsmtap-sapi sdcch gsmtap-sapi sacch uplink-power-target -110 trx 0 !ms-power-control osmo !power-ramp max-initial 0 dBm !power-ramp step-size 2000 dB !power-ramp step-interval 10 phy 0 instance 0 ========= Osmo-bsc config ========= ! Configuration rendered by osmo-gsm-tester log stderr logging filter all 1 logging color 1 logging print category 1 logging print extended-timestamp 1 logging level all debug line vty no login bind 127.0.0.1 ctrl bind 127.0.0.1 e1_input e1_line 0 driver ipa ipa bind 127.0.0.1 network network country code 515 mobile network code 02 encryption a5 0 neci 1 handover 0 handover window rxlev averaging 10 handover window rxqual averaging 1 handover window rxlev neighbor averaging 10 handover power budget interval 6 handover power budget hysteresis 4 handover maximum distance 9999 allow-unusable-timeslots bts 0 type sysmobts band 900 cell_identity 1012 location_area_code 1012 training_sequence_code 1 base_station_id_code 1 channel-description attach 0 !ms max power 40 cell reselection hysteresis 4 rxlev access min 0 channel allocator ascending rach tx integer 9 rach max transmission 7 ip.access unit_id 1012 0 oml ip.access stream_id 255 line 0 gprs mode none no force-combined-si trx 0 rf_locked 0 arfcn 27 !nominal power 40 nominal power 80 ! to use full TRX power, set max_power_red 0 max_power_red 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config SDCCH8 hopping enabled 0 timeslot 2 phys_chan_config TCH/F hopping enabled 0 timeslot 3 phys_chan_config TCH/F hopping enabled 0 timeslot 4 phys_chan_config TCH/F hopping enabled 0 timeslot 5 phys_chan_config TCH/F hopping enabled 0 timeslot 6 phys_chan_config TCH/F hopping enabled 0 timeslot 7 phys_chan_config PDCH hopping enabled 0 msc 0 !ip.access rtp-base 25000 no bsc-welcome-text no bsc-msc-lost-text no bsc-grace-text type normal allow-emergency allow !codec-list fr1 !amr-config 12_2k forbidden !amr-config 10_2k forbidden !amr-config 7_95k forbidden !amr-config 7_40k forbidden !amr-config 6_70k forbidden !amr-config 5_90k forbidden !amr-config 5_15k forbidden !amr-config 4_75k forbidden mgw remote-ip 127.0.0.1 mgw remote-port 2427 !mgw endpoint-range 1 31 mgw local-ip 127.0.0.1 bsc mid-call-timeout 0 ========== Osmo-msc config ========== ! ! OsmoMSC configuration saved from vty ! log stderr logging filter all 1 logging color 0 logging print category 1 logging timestamp 1 logging level all everything logging level rll notice logging level cc notice logging level mm notice logging level mm debug logging level rr notice logging level pag notice logging level msc notice logging level mgcp notice logging level ho notice logging level ref notice logging level ctrl notice logging level lglobal notice logging level llapd notice logging level linp notice logging level lmux notice logging level lmi notice logging level lmib notice logging level lsms notice logging level lctrl notice logging level lgtp notice logging level lstats notice logging level lgsup notice logging level loap notice logging level lss7 notice logging level lsccp notice logging level lsua notice logging level lm3ua notice logging level lmgcp notice logging level all debug line vty no login bind 127.0.0.1 ! network network country code 515 mobile network code 02 short name GLOBE long name GLOBE encryption a5 0 rrlp mode none mm info 1 timezone 8 0 msc mgw remote-ip 127.0.0.1 mgw remote-port 2427 mgw local-ip 127.0.0.1 !mgw endpoint-range 1 31 !mgw bts-base 8000 assign-tmsi cs7-instance-a 0 check-imei-rqd early !timer vlr T3212 1 ctrl bind 127.0.0.1 mncc-int default-codec tch-f fr default-codec tch-h hr hlr remote-ip 127.0.0.1 smpp local-tcp-port 2775 policy accept-all smpp-first esme bhat password bhat default-route

3 2

Pysim error: SW match failed
by Martin Nagy 16 Aug '25

16 Aug '25

Hi all, After buying a super Sim Kit (16 in 1) from China, I tried the reader (green PCB inside a blue transparent plastic case with a blue LED) and SIM (identified as a fakesupersim) with pysim tool. However i am getting the following error: /pySim-prog.py -n 26C3 -c 49 -x 262 -y 42 -z 1234 -j 1 -t auto Insert card now (or CTRL-C to cancel) Autodetected card type fakemagicsim Generated card parameters : > Name : 26C3 > SMSP : e1ffffffffffffffffffffffff058100945555ffffffffffff000000 > ICCID : 8949262427518313026 > MCC/MNC : 262/42 > IMSI : 262422461512085 > Ki : 7b74741a1ee14337ec23f9ab92a13648 > OPC : ccd867d60797d8d45354a51b3ef568ff Programming ... Traceback (most recent call last): File "./pySim-prog.py", line 530, in <module> card.program(cp) File "/home/nadicek/pysim/pysim/pySim/cards.py", line 231, in program self._scc.update_binary('6f30', hplmn + 'ff' * (tl-3)) File "/home/nadicek/pysim/pysim/pySim/commands.py", line 53, in update_binary return self._tp.send_apdu_checksw(pdu) File "/home/nadicek/pysim/pysim/pySim/transport/__init__.py", line 87, in send_apdu_checksw raise RuntimeError("SW match failed ! Expected %s and got %s." % (sw.lower(), rv[1])) RuntimeError: SW match failed ! Expected 9000 and got 9804. I checked mailing lists and haven’t found anybody who had similar problem with pysim. Also I have tried forcing different models of SIM, but nothing is working. Obviously I can remove this check from the script file (__init__.py in /pySim/transport), however somebody had a reason to put such condition there. I would like to ask if it is safe to remove that line of code and the purpose of that line of code. Thanks a lot and best regards Martin

3 3

Re: Help with sccp library
by mosbah abdelkader 07 Jul '25

07 Jul '25

> I don't understand. This callback will be called with data you need to write > to the network. In case of MTP Level3 you will need to wrap that around the > msgb you got. I means: is the interaction with mtp3 layer implemented (is sending sccp data by mtp3 implemented by the library?)? Also, what about the reception of data from mtp3 layer. is that implemented in the sccp lib. I am asking these questions because I see the code of mtp3 in the lib but no significant call is present in the sccp part of the lib. Thank you for your help.

4 3

dynamic traffic channels
by Neels Hofmeyr 20 May '25

20 May '25

On Tue, Jun 28, 2016 at 10:05:28AM +0200, Harald Welte wrote: > [translated from german] > is it certain that we switch a channel to PDCH only when > gprs mode != none? A TS can be GSM_PCHAN_TCH_F_PDCH; those are the only ones for which we send a PDCH ACT message. We send a PDCH ACT message - during init (CHANNEL OML's state changed to enabled -> send PDCH ACT), - and upon channel release ack when pchan == GSM_PCHAN_TCH_F_PDCH. So the question is, when we receive a channel release ack, could that be the PDCH release and we switch PDCH right back on by accident? No, because we only receive a chan rel ack when the *TCH/F* is being released. That is because the PDCH release is initiated "internally" from the PDCH DEACT, and thus this condition in common/rsl.c rsl_tx_rf_rel_ack() catches on, which existed before dyn PDCH: if (lchan->rel_act_kind != LCHAN_REL_ACT_RSL) { LOGP(DRSL, LOGL_NOTICE, "%s not sending REL ACK\n", gsm_lchan_name(lchan)); return 0; } In rsl_rx_rf_chan_rel() the rel_act_kind is set to LCHAN_REL_ACT_RSL, but not in the rsl_rx_dyn_pdch(). This is analogous to the ip.access way -- the ip.access nanobts replies to a PDCH DEACT with a PDCH DEACT ACK and doesn't send a separate channel release ack. Maybe we could set rel_act_kind to some new LCHAN_REL_ACT_IPAC_DYN_PDCH for clarity? (But we shouldn't actually send a release ack, to stay compatible.) Even though it works as-is, we should indeed add another flag check: - We do check the flags that no ACT/DEACT is already pending; - And we do send a PDCH DEACT only if ts->flags & TS_F_PDCH_ACTIVE; - But we would send a PDCH ACT despite ts->flags & TS_F_PDCH_ACTIVE. This should never happen, but it would make sense to ensure that. ~Neels

3 5

libosmocore/BSC/MSC: MO voice calls rejected from Siemens S11E (patch included)
by Lennart Müller 31 Jan '24

31 Jan '24

Hi, I had a problem placing MO GSM calls from a Siemens S11E: The calls were dropped immediately; Osmo-MSC reports "Cannot compose Channel Type from bearer capabilities" After investigating the SETUP request from the S11E, the phone does not use octet 3a (no extension bit set in IE 3). Wireshark decodes the radio channel requirement as "Full rate support only MS/fullrate speech version 1 supported", so I added a condition to the gsm48_ie.c function of libosmocore to include at least GSM FR in the list of available speech_ver in case octet 3 has no extension. Attached to this message are the Abis-IP PCAP traces of MO calls, and the patch for gsm48_ie.c. Regards, Lennart

6 6

Problem while running NIB on Open Cellular Base sation
by Brackley Casinga 31 Jan '24

31 Jan '24

Hi, My name is Brackley Cassinga Form DRC, we run a community network called pamoja net where we offer gsm services using osmocom open source software and OC Base station. Recently I have tried to install another base station as the same installed but I could not find any resource guiding through all the steps to take to run NIB on a base station. I'm currently running Ubuntu and I will appreciate if you could guide me on the installation of BSC,hlr,MSC , in order to run a basic gsm network. Thank you. Regards -- *Ir Brackley heshima Casinga **Pacifique* *CEO and Founder of kwanzatechnologie* KwanzaTechnologies ,GlobalElectronics +243977265291 | +243977265291 | Pcassinga(a)gmail.com/ brackley(a)ensemblepourladifference.org www.kwantechnologies.jimdosite.com <http://www.kwantechnologies.com/> | Skype: Brackley cassinga <https://webapp.wisestamp.com/#> Av Semliki N 43

2 1

git infrastructure
by Neels Hofmeyr 26 Sep '22

26 Sep '22

I guess it's a bit late, but do we really need categories on gitea? The simple world I would have expected: git clone https://gitea.osmocom.org/libosmo-pfcp git clone https://gitea.osmocom.org/osmo-upf The world we live in: git clone https://gitea.osmocom.org/celullar_infarsturcure/libosmo-pfcp git clone https://gitea.osmocom.org/osmocom/osmo-upf git clone https://gerrit.osmocom.org/libosmo-dsp and works: git clone git://git.osmocom.org/osmo-upf fails: git clone https://git.osmocom.org/osmo-upf works: git clone https://git.osmocom.org/libosmo-pfcp While I'm at it: do we have a designated primary git place for Osmocom? De facto the answer seems to be: gerrit, except when it's not on gerrit. Because of the above issues, currently there is a wave of patches rolling out which edit build scripts and READMEs to change git URLs -- it feels wrong that this is necessary. It seems the topic needs some clarification, and maybe it is still possible to simplify the git structures? - remove the layer of categories from gitea? - move gitea/cellular-infrastraucute/* to gitea/osmocom/* ? - point git.osmocom.org at gitea.osmocom.org/osmocom/ ? (cgit.osmocom.org still works) - keep cgit as the primary git place, gitea as users' playgrounds? (not sure if possible or good ideas) ~N

3 5

Osmocom GUI support
by Ahnaf Tahmid 02 Sep '22

02 Sep '22

Dear OpenBSC team, I am Ahnaf Tahmid Chowdhury, currently building Osmocom graphical user interface. I have created a subscriber page where one can add/remove/update subscriber. The repo is available at: https://github.com/ahnaf-tahmid-chowdhury/osmo-gui Please let me know your thoughts about the application. Thank you

4 6

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC August 2022