June 2024 - OpenBSC - lists.osmocom.org

cmd2 update causing pySim-shell to fail
by bryan coxwell 14 Feb '26

14 Feb '26

Hi all, Just wanted to share an issue and a quick workaround I found for it in case anyone else has the same problem. I believe a cmd2 update is causing pySim-shell to fail. After installing it on a fresh install of Ubuntu Server 20.04 and getting the following error when I run "python3 pySim-shell -p0": >Using PC/SC reader interface >Autodetected card type: sysmoUSIM-SJS1 >AIDs on card: > USIM: a0000000871002ffffffff8907090000 >Traceback (most recent call last): > File "pySim-shell.py", line 512, in <module> > app = PysimApp(card, rs, opts.script) > File "pySim-shell.py", line 59, in __init__ > super().__init__(persistent_history_file='~/.pysim_shell_history', allow_cli_args=False, use_ipython=True, auto_load_commands=False, command_sets=basic_commands, >startup_script=script) >TypeError: __init__() got an unexpected keyword argument 'use_ipython' If you run into this you can fix it by uninstalling cmd2 and reinstalling cmd2 with "pip3 install cmd2==1.5". Best, Bryan

13 15

Video Recordings of OsmoCon 2017
by Harald Welte 09 Feb '26

09 Feb '26

Hi all, the Osmocom Conference 2017 last week was an overwhelming success. We received lots of positive feedback from all sides. Thanks to all the speakers, to the attendees as well as to the anonymous sponsor of the travel grant funds. It is my great pleasure that due to the great support by C3VOC (The CCC Video Operation Center), we have full recordings of all talks given at OsmoCon 2017. You can find the videos on the C3VOC site at https://media.ccc.de/search/?q=osmocon They are also linked individually from the OsmoCon 2017 homepage at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017 I hope the video recordings will be of help for everyone who could not make it to the event in person. We will also be collecting the slides and put them up on the wiki during the next few days. Please don't hesitate to raise any feedback and/or questions. Technical feedback/questions regarding Osmocom software / projects should be addressed to the appropriate mailing lists, such as openbsc(a)lists.osmocom.org. Feedback to the organizers should be sent to osmocon2017(a)sysmocom.de. Looking forward to the next OsmoCon, which we'll expect to be spanning ore than just a single day. Regards, 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 2

GPRS - local and foreign TLLIs
by Luca Melette 04 Feb '26

04 Feb '26

Hello everybody, after setting up a nanoBTS with OpenBSC/SGSN/GGSN, I had some troubles trying to connect my smartphone to the GPRS cell. Investigating the BTS-to-SGSN traffic, I saw that the frames sent by the SGSN were all marked with the same N(U) value (at LLC layer), the value was 0. With some debug, I found that the there was a mismatch in the TLLI storage, used to keep the status of attached terminals. The mentioned code is contained in gprs_llc.c, involving LL Entity functions and gprs_llc_tx_ui(). /* look-up or create the LL Entity for this (TLLI, SAPI) tuple */ lle = lle_by_tlli_sapi(msgb_tlli(msg), sapi); if (!lle) { struct gprs_llc_llme *llme; LOGP(DLLC, LOGL_ERROR, "LLC TX: unknown TLLI 0x%08x, " "creating LLME on the fly\n", msgb_tlli(msg)); llme = llme_alloc(msgb_tlli(msg)); lle = &llme->lle[sapi]; } The TX function uses the previously received TLLI to lookup for the LLE. The lle_by_tlli_sapi() performs the search, but preliminary it applies a foreign2local TLLI conversion to ensure to have a local one. Since no valid entry for the searched TLLI is found, a new one is created. And the problem is here. The new entry has the foreign TLLI. Next time the lookup fails again, and a new entry is created. This way, the counter N(U) is always reset, and the mobile do not recognize the message sequence and no attach is possible. My question is about foreign and local TLLIs. I patched the lookup, avoiding the conversion, so that the LLE is found and everything works fine... but... What is the sense of the conversion? Should the TLLI be always stored as a local one? Can this problem be solved with another foreign2local while allocating new entries? Actually, my problem has been solved with that workaround. But I'm curious to know what is the right way. Hope somebody can answer :) Thanks. Cheers, LM

5 6

OsmoNITB timeslots configuration and UmTRX
by Родион Гадыршин 27 Jan '26

27 Jan '26

Hello, list. I have umtrx v2.1 and I have already built GSM and GPRS components. Now I want to know which way of configuring timeslots in osmobsc.cfn is the best. I want GPRS, calls and SMS work. My current configuration is: 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 PDCH hopping enabled 0 timeslot 5 phys_chan_config PDCH hopping enabled 0 timeslot 6 phys_chan_config PDCH hopping enabled 0 timeslot 7 phys_chan_config PDCH hopping enabled 0 Is there a better way to configure? Maybe better use TCH/F_TCH/H_PDCH, but I have heard, that TCH/F is currently not working in dynamic configurations - only TCH/H does. And there is no only TCH/H_PDCH mode. So, could you please give me an advice?

3 2

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

Need nano3G (S8 - Model 237A)
by Akib Sayyed 18 Jan '26

18 Jan '26

Dear List I am extremely sorry for off the topic question. I am willing to buy nano3G Nodeb. Is anyone in list have spare which can be sold. Please let me know. -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

6 6

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

Excel in NURS FPX 4010 Assessments with Our Expert Online Tutoring
by williammores96＠gmail.com 05 Jan '26

05 Jan '26

Excel in NURS FPX 4010 Assessments with Our Expert Online Tutoring Dominate your NURS FPX 4010 assessments with our specialized tutoring services. From Assessment 1 to 4, we provide comprehensive support to complete your nursing program with top grades. Start your success story today! Introduction to NURS FPX 4010 Series Assessments The NURS FPX 4010 series represents a significant milestone in the journey of nursing students. It challenges students to apply their knowledge in real-world scenarios, enhancing their clinical reasoning and decision-making skills. Whether you're just starting with NURS FPX 4010 Assessment 1 or gearing up for <a href=https://www.etutors.us/assessment-4-stakeholder-presentation/> NURS FPX 4010 Assessment 4</a>. , each assessment is a step closer to achieving your academic and professional goals in nursing. Why Our Tutoring Services Are Essential for Your Success Navigating through the NURS FPX 4010 series requires more than just hard work; it demands strategic study plans and insights from experienced professionals. Our tutoring services are designed to guide you through each assessment, including NURS FPX 4010 Assessment 2 and for <a href=https://www.etutors.us/nurs-fpx4010-assessment-3/>NURS FPX 4010 Assessment 3</a>. , ensuring you grasp the core concepts and apply them effectively. Customized Learning for Maximum Impact We believe in a personalized approach to learning, recognizing that each student has unique strengths and challenges. Our tutors tailor their teaching methods to suit your individual needs, focusing on areas that require additional attention, such as NURS FPX 4010 Assessment 4, to maximize your learning outcome. Expert Tutors Ready to Assist You Our team comprises seasoned nursing educators who excel in their respective fields. They bring a wealth of knowledge and practical experience, providing invaluable insights into successfully completing assessments like <a href=https://www.etutors.us/nurs-fpx4010-assessment-1-collaboration/>NURS FPX 4010</a>. . With our experts, you're not just preparing for an exam; you're gearing up for a successful career in nursing. Achieve Excellence in One Billing Cycle Our goal is to help you complete your BSN and MSN programs efficiently, without compromising the depth of learning. By focusing on crucial assessments, including <a href=https://www.etutors.us/nurs-fpx-4010-assessment-2//>NURS FPX 4010 Assessment 2</a>. and NURS FPX 4010 Assessment 3, we streamline your study process to ensure you're exam-ready in the shortest possible time. Comprehensive Support Tailored to Your Needs From "Write my assessment" to "Online assessment help," we offer a range of services to support your academic journey. Our comprehensive tutoring package includes review sessions, practice questions, and personalized feedback, covering every aspect of the NURS FPX 4010 Assessment 4 and beyond. <a href=https://www.etutors.us/nurs-fpx-4010/>Partner in Nursing Education</a>. Choosing our tutoring services for the NURS FPX 4010 series is a step towards academic excellence and professional mastery. With our personalized support, expert guidance, and comprehensive resources, you'll be well-equipped to tackle each assessment with confidence and achieve your goals in the competitive field of nursing. Elevate your nursing education with our expert tutors. Contact us now to learn how we can help you excel in the NURS FPX 4010 series and advance your career with confidence.

4 6

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

Splitting out M3UA and MTP3 out of Open BSC into a separate library
by Arran Cudbard-Bell 15 Dec '25

15 Dec '25

Hi, Developing a module for FreeRADIUS to support EAP-SIM and EAP-AKA authentication against a HLR. The HLR we were targeting only supported a SCTP/M3UA/SCCP/TCAP/MAP stack, so we couldn't use SUA. Ripping the M3UA/MTP3 code out of OpenBSC worked surprisingly well. We ended up running the event loop in a separate thread to work around the threading issues. Unfortunately the HLR implements the ANSI variant of everything, whereas OpenBSC and supporting libraries seem to have been written to be compatible with the ITU standards. ...but the differences are fairly minor at MTP3 and SCCP layers, and i've started work on a patchset for libosmo-sccp. https://gerrit.osmocom.org/#/c/73/ Anyway, trying to gauge interest in splitting those layers out of Open BSC into a separate library, would be happy to take on M2UA as well for consistency. It would almost certainly get more projects using the code. There's very little out there even in Perl land for working with SS7. Thanks, -Arran Arran Cudbard-Bell <a.cudbardb(a)freeradius.org> FreeRADIUS Development Team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2

8 8

ip.access nano 3G S8 Configuration
by John Thewlis - Meath Broadband 18 Nov '25

18 Nov '25

We are trying to setup this AP as part of the 3.5G Osmocom project. We have the software stack operational and are now preparing the nano for testing. When we try to login via telnet at port 8090 we are getting a constant refusal to connect:- root@osm/openbsc/openbsc/src/ipaccess# telnet 192.168.192.30 8090 Trying 192.168.192.30... telnet: Unable to connect to remote host: Connection refused The device seems to be locked as indicated by the leds on the front panel. We have tried resetting the nano to see if this would help but to no avail. Any ideas as to how to access the device for initial configuration?. Thanks John

4 4

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

pycrate repo update
by benoit michau 22 Jul '25

22 Jul '25

Dear osmocom developpers, This is just to let you know that the Python library pycrate has a new home : https://github.com/pycrate-org/pycrate. The packages on Pypi are now feeded from there. This library can be used in many cases dealing with mobile signalling. I wanted to let you know, as even if I am not aware of any osmocom projects depending on it, some of you may use the library from time to time, or could have local applications depending on it. Best Regards Benoit

2 1

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

08 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

Cell coverage of OsmoBTS B205mini-i
by JPichel 12 Jul '24

12 Jul '24

Hi, I am using osmo-bts-trx with a B205-mini-i, using only CS services. I am currently running the following elements on Ubuntu 22.04, all built from source from the latest version: - osmo-trx-uhd - osmo-bts-trx - osmo-bsc - osmo-msc - osmo-hlr - osmo-mgw - osmo-stp - osmo-sip-connector I have been testing the range of the cell, and I can't seem to get more than around 50 meters, even when I transmit at ~21 dBm using a power amplifier at TX. I find this range too low, since I am used to getting 200-300 meters out of the box when running 4G and 5G networks with the same device, so I suspect I am not configuring the network correctly. I've tried looking at every parameter, so far I've only noticed improvements when setting the min-qual-* to the minimum values and ms_max_power to the maximum. These are my configs for TRX, BTS and BSC: OsmoTRX: ``` log stderr ... ! line vty no login ! cpu-sched policy rr 18 trx bind-ip 127.0.0.1 remote-ip 127.0.0.1 egprs disable tx-sps 4 rx-sps 4 clock-ref gpsdo chan 0 ``` ``` ! ! OsmoBTS () configuration saved from vty !! ! log stderr ... ! line vty no login ! phy 0 instance 0 osmotrx tx-attenuation 0 osmotrx rx-gain 50 osmotrx ip local 127.0.0.1 osmotrx ip remote 127.0.0.1 bts 0 band GSM900 ipa unit-id 1234 0 oml remote-ip 127.0.0.1 gsmtap-remote-host 127.0.0.1 gsmtap-sapi enable-all min-qual-rach -100 min-qual-norm -100 trx 0 phy 0 instance 0 nominal-tx-power 10 ``` ``` ! osmo-bsc default configuration ! (assumes STP to run on 127.0.0.1 and uses default point codes) ! log stderr logging color 1 logging print category-hex 0 logging print category 1 logging timestamp 0 logging print file basename last logging print level 1 e1_input e1_line 0 driver ipa network network country code 1 mobile network code 1 encryption a5 0 neci 1 paging any use tch 0 handover 0 handover algorithm 1 handover1 window rxlev averaging 10 handover1 window rxqual averaging 1 handover1 window rxlev neighbor averaging 10 handover1 power budget interval 6 handover1 power budget hysteresis 3 handover1 maximum distance 9999 ! T3212 is in units of 6min, so below we set 5 * 6 = 30min timer net T3212 5 mgw 0 remote-ip 127.0.0.1 remote-port 2427 local-port 2727 bts 0 type osmo-bts band GSM900 cell_identity 1234 location_area_code 0x0001 base_station_id_code 63 ms max power 40 !default: cell reselection hysteresis 4 cell reselection hysteresis 14 radio-link-timeout 32 channel allocator mode set-all ascending rxlev access min 0 rach tx integer 9 rach max transmission 7 channel-description attach 1 channel-description bs-pa-mfrms 5 channel-description bs-ag-blks-res 1 early-classmark-sending forbidden ipa unit-id 1234 0 oml ipa stream-id 255 line 0 codec-support fr gprs mode none trx 0 rf_locked 0 ! 945M DL/900M UL arfcn 50 nominal power 10 max_power_red 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config TCH/F 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 TCH/F hopping enabled 0 ms-power-control mode dyn-bts rxlev-thresh lower 0 upper 63 msc 0 allow-emergency allow 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 allowed amr-config 5_15k forbidden amr-config 4_75k forbidden bsc mid-call-timeout 0 ``` You might notice I am using the gpsdo as the clock-ref. That's because I've also tried with a B210 with the internal GPSDO, but the results are the same. Thanks in advance, Jonathan Pichel

4 6

E1 to IP with iCE40 E1 USB interface
by Alina Androne 15 Jun '24

15 Jun '24

Hello, How can I utilize the iCE40 E1 USB adapter to transition from E1 to IP in a GSM network, connecting a physical Siemens BSC (which has a BTS connected) to OsmoMSC? Only the BTS and BSC are physical. I already have osmo-e1d installed. Should I use osmo-e1d or dahdi version for this transition? What would be the best approach to begin the process? Regards, Alina

5 10

how do I configure half-rate voice support
by cocfarabicoc＠gmail.com 14 Jun '24

14 Jun '24

I opened this issue for your support and suggestions. I have doing call testing with msisdn(Private network serving the local user). When osmo-bsc-cfg's timeslots are 0->CCCH+SDCCH4, rest 1-7 TCH/F, I can successfully connect 6 phones to each other. When I try to call between 7th and 8th phones, I get an error (from osmo-bts), "Resources unavailable,unspecified"(GSM48_CC_CAUSE_RESOURCE_UNAVAIL). Since each timeslot is allocated to 1 user, I receive an insufficient resource warning. My osmo-bsc-cfg; e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive cs7 instance 0 point-code 1.23.0 asp asp-clnt-msc-0 2905 0 m3ua remote-ip 127.0.0.1 sctp-role client sccp-address msc routing-indicator PC point-code 0.23.1 network network country code 901 mobile network code 75 encryption a5 1 3 neci 1 paging any use tch 0 handover 1 handover algorithm 1 handover1 power budget hysteresis 999 handover1 power budget interval 99 bts 0 type sysmobts band GSM900 cell_identity 0 location_area_code 23 base_station_id_code 63 ms max power 39 cell reselection hysteresis 14 rxlev access min 0 radio-link-timeout 64 penalty time 20 temporary offset 0 cell bar qualify 0 cell reselection offset 31 channel allocator ascending rach tx integer 14 rach max transmission 1 rach emergency call allowed 1 channel-description attach 1 channel-description bs-pa-mfrms 5 channel-description bs-ag-blks-res 2 no access-control-class-ramping access-control-class-ramping-step-interval 5 access-control-class-ramping-step-size 1 access-control-class-ramping-chan-load 71 89 early-classmark-sending allowed early-classmark-sending-3g allowed ipa unit-id 1800 0 oml ipa stream-id 255 line 0 neighbor-list mode manual-si5 codec-support fr hr efr amr amr tch-f modes 0 2 4 7 amr tch-f threshold ms 32 32 32 amr tch-f hysteresis ms 8 8 8 amr tch-f threshold bts 32 32 32 amr tch-f hysteresis bts 8 8 8 amr tch-f start-mode auto amr tch-h modes 0 2 4 amr tch-h threshold ms 32 32 amr tch-h hysteresis ms 8 8 amr tch-h threshold bts 32 32 amr tch-h hysteresis bts 8 8 amr tch-h start-mode auto gprs mode none ms-power-control mode static trx 0 rf_locked 0 arfcn 100 nominal power 23 max_power_red 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config TCH/F 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 TCH/F hopping enabled 0 msc 0 codec-list hr1 fr1 allow-emergency deny 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 allowed amr-config 5_15k forbidden amr-config 4_75k forbidden amr-payload octet-aligned msc-addr msc asp-protocol m3ua lcls-mode disabled lcls-codec-mismatch forbidden mgw remote-ip 127.0.0.1 mgw remote-port 2427 bsc mid-call-timeout 0 cbc no remote-ip no listen-port end I wanted to set half-rate on one trx so that more phones could talk. On my first try, I get this warning("Assignment for this trans already started earlier"- from osmo-msc- function : msc_a_try_call_assignment) and I cannot make any calls. My bsc-cfg for TCH/H; e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive cs7 instance 0 point-code 1.23.0 asp asp-clnt-msc-0 2905 0 m3ua remote-ip 127.0.0.1 sctp-role client sccp-address msc routing-indicator PC point-code 0.23.1 network network country code 901 mobile network code 75 encryption a5 1 3 neci 1 paging any use tch 0 handover 1 handover algorithm 1 handover1 power budget hysteresis 999 handover1 power budget interval 99 bts 0 type sysmobts band GSM900 cell_identity 0 location_area_code 23 base_station_id_code 63 ms max power 39 cell reselection hysteresis 14 rxlev access min 0 radio-link-timeout 64 penalty time 20 temporary offset 0 cell bar qualify 0 cell reselection offset 31 channel allocator ascending rach tx integer 14 rach max transmission 1 rach emergency call allowed 1 channel-description attach 1 channel-description bs-pa-mfrms 5 channel-description bs-ag-blks-res 2 no access-control-class-ramping access-control-class-ramping-step-interval 5 access-control-class-ramping-step-size 1 access-control-class-ramping-chan-load 71 89 early-classmark-sending allowed early-classmark-sending-3g allowed ipa unit-id 1800 0 oml ipa stream-id 255 line 0 neighbor-list mode manual-si5 codec-support fr hr efr amr amr tch-f modes 0 2 4 7 amr tch-f threshold ms 32 32 32 amr tch-f hysteresis ms 8 8 8 amr tch-f threshold bts 32 32 32 amr tch-f hysteresis bts 8 8 8 amr tch-f start-mode auto amr tch-h modes 0 2 4 amr tch-h threshold ms 32 32 amr tch-h hysteresis ms 8 8 amr tch-h threshold bts 32 32 amr tch-h hysteresis bts 8 8 amr tch-h start-mode auto gprs mode none ms-power-control mode static trx 0 rf_locked 0 arfcn 100 nominal power 23 max_power_red 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config TCH/H hopping enabled 0 timeslot 2 phys_chan_config TCH/H hopping enabled 0 timeslot 3 phys_chan_config TCH/H hopping enabled 0 timeslot 4 phys_chan_config TCH/H hopping enabled 0 timeslot 5 phys_chan_config TCH/H hopping enabled 0 timeslot 6 phys_chan_config TCH/H hopping enabled 0 timeslot 7 phys_chan_config TCH/H hopping enabled 0 msc 0 codec-list hr1 fr1 allow-emergency deny 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 allowed amr-config 5_15k forbidden amr-config 4_75k forbidden amr-payload octet-aligned msc-addr msc asp-protocol m3ua lcls-mode disabled lcls-codec-mismatch forbidden mgw remote-ip 127.0.0.1 mgw remote-port 2427 bsc mid-call-timeout 0 cbc no remote-ip no listen-port end What needs to be done to connect more than 6 phones? Am I making a mistake in the config for the half-rate setting? I am waiting for your suggestions and opinions.

2 1

Re: RFC: new type for NAS/EPS in gsmtap.h and question
by md jashin88 14 Jun '24

14 Jun '24

1 0

osmo-smlc / sccp_lb_inst.c
by jheyrendt.ext＠orange.com 05 Jun '24

05 Jun '24

Hi Do you know if the packet osmo-smlc should work with osmo-bsc, osmo-stp last versions? I just tested, saw errors and tried to debug but perhaps I made mistakes (link, as, asp are up between BSC and SMLC via osmo-stp) osmo-smlc 0.2.4 DLSCCP DEBUG <0011> sccp_user.c:176 Delivering N-PCSTATE.indication to SCCP User 'SCCP Management' DLSCCP DEBUG <0011> sccp_scmg.c:298 Ignoring SCCP user primitive N-PCSTATE.indication DLSCCP DEBUG <0011> sccp_user.c:176 Delivering N-PCSTATE.indication to SCCP User 'OsmoSMLC-Lb' DLB ERROR <0002> sccp_lb_inst.c:167 (Lb) sccp_lb_sap_up(N-PCSTATE.indication) unsupported Many thanks in advance Best regards Jean-Marc

2 3

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC June 2024