OpenBSC

openbsc@lists.osmocom.org

14 participants
4246 discussions

no calls in 2G network
by CRX 22 Oct '22

22 Oct '22

Hey, i am trying to build a 2G network with an ip.access BTS (Model 165G DCS1800). So far I can see the network on the RF spectrum and SMS delivery is working fine. Unfortunately I cant send calls to other phones. The open-bsc sends a lot of error messages to the log when the BTS is booting, I am not sure if my configuration is ok. As attachments there are my configs and the logs of open-bsc and osmo-msc. Thanks for your Help! regards crx

2 1

OsmoDevCall on Oct 19, 2022: SIMtrace2 Tutorial
by Harald Welte 17 Oct '22

17 Oct '22

Dear Osmocom community, after a rather extended 2022 summer break, we're happy to announce the next incarnation of OsmoDevCall. Based on the recent polls, the timing has shifted to *every 3rd wednesday of the month*! when: October 19, 2022 at 20:00 CEST where: https://meeting5.franken.de/b/har-xbc-bsx-wvs In this edition, I will be presenting a SIMtrace2 tutorial, showing SIM card protocol tracing, decoding with the new pySim-trace as well as the card emulation firmware. This meeting will have the following schedule: 20:00 meet + greet 20:10 presentation as outlined above 21:00 unstructured supplementary social event [*] Attendance is free of charge and open to anyone with an interest in Osmocom or open source cellular technologies. More information about OsmoDevCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall Looking forward to meeting you soon! Best regards, Harald [*] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

RFC: OsmoDevCall restart: Your input required
by Harald Welte 16 Oct '22

16 Oct '22

Dear Osmocom community, your input is required in order to tune the re-launch of the OsmoDevCall talk series. One of the complaints before the suspension in Summer this year was that the "Friday night 8pm CEST" timeslot was not exactly ideal for several people. Finding a common denominator might be difficult, given that Osmocom is a dayjob for some, a hobby for most, and we're of course not all in the same time zone or even continent. So let's try to run a couple of polls to figure out: * What is the best day of the week for OsmoDevCall? https://bitpoll.de/poll/CEQnaQKEvO/ * What is the best time of day for OsmoDevCall? https://bitpoll.de/poll/59dgmzOocT/ * What is the best frequency of OsmoDevCall https://bitpoll.de/poll/8jyuRJB6Hb/ The polls are open until October 21st, 2021. I would appreciate a high turn-out so we have a good representation across our community to make an educated decision about the schedule of futur events. Can't wait to re-start OsmoDevCall! 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)

1 1

Osmocom Software
by Neil John Reponcion 15 Oct '22

15 Oct '22

We would like to ask how to use counters in Osmocom to compute KPI's such as 1) CSSR (Call Setup Success Rate). 2) CDR (Call Drop Rate). 3) HSR (Handover Success Rate). 4) TCH (Traffic Channel) Congestion Rate Please assist us how to get the counters in Osmocom if there are such counters Thanks and regards, Neil John Reponcion Systems Engineer Entropy Solutions

2 1

Call waiting and MNCC_RTP_CREATE
by Mychaela Falconia 14 Oct '22

14 Oct '22

Hello Osmocom CNI community, I am writing my own software that talks MNCC to OsmoMSC instead of using osmo-sip-connector, and I am seeing perplexing behaviour with call waiting. Normally when I send an MT call toward GSM with MNCC_SETUP_REQ, the response from OsmoMSC consists of MNCC_CALL_CONF_IND (when the called phone confirms the call), followed by MNCC_RTP_CREATE (when OsmoMSC assigns the call), and finally followed by MNCC_ALERT_IND when the called phone starts alerting. Likewise on MO calls I get an MNCC_RTP_CREATE message on the MNCC interface when the call is assigned, typically in response to MNCC_CALL_PROC_REQ. But now consider a call waiting scenario: call 1 is already in progress (fully connected, parties talking), and there is a second incoming call. I send a new MNCC_SETUP_REQ to OpenMSC for call 2, with a new callref, the phone receives it and starts making call-waiting beeps. The response on the MNCC socket for call 2 is that I get MNCC_CALL_CONF_IND followed by MNCC_ALERT_IND (and then MNCC_SETUP_CNF if the target phone puts call 1 on hold and answers call 2) - but there is no MNCC_RTP_CREATE! I can see how MNCC_RTP_CREATE is sent by OsmoMSC when the call has been assigned and there is a TCH cross-connected through OsmoMGW, and I can see how the call assignment step will naturally be omitted in the call waiting scenario when TCH is already there for call 1. But the call gateway (be it osmo-sip-connector or an independent reimplementation) feeding MT call 2 to MNCC has to have some way of obtaining RTP connection information for this call without having to know how to associate it with another previous call, and if it doesn't get MNCC_RTP_CREATE, how would it get this vital info? This is one of those "how does it work for everyone else?" moments - while I am certainly unique in writing my own MNCC software instead of running osmo-sip-connector, surely o-s-c also needs to receive MNCC_RTP_CREATE with RTP info from OsmoMSC in order to successfully connect call 2... And given that someone implemented call hold and retrieve operations in o-s-c, I reason that someone must be using the call waiting feature and it must be working for them - but how? One thing which o-s-c does differently from my sw is that o-s-c sends an empty MNCC_RTP_CREATE (the "command" version of this packet) to OsmoMSC in response to MNCC_CALL_CONF_IND, which my sw doesn't do at the moment. But I looked in the OsmoMSC code, and I don't see any difference: the function that handles MNCC_RTP_CREATE command (tch_rtp_create()) simply calls msc_a_try_call_assignment(trans), and the exact same call is made in the gsm48_cc_rx_call_conf() function that sends MNCC_CALL_CONF_IND. So I don't see any code path that can result in call 2 receiving MNCC_RTP_CREATE from OsmoMSC in the call waiting scenario when TCH is already there from call 1. So, how does the call waiting feature work for others in the community, and what am I missing? I am running the tagged release from 2021-11. M~

3 10

osmo-gsm-tester: Issue with osmo-gsm-tester-runner Jenkins job
by Callum Snowden 11 Oct '22

11 Oct '22

Hi all, We're trying to setup osmo-gsm-tester on bare metal and are currently experiencing issues with the Jenkins job 'osmo-gsm-tester-runner'. All of our test machines are running Ubuntu Server 20.04 and have been setup following the latest available manual from https://downloads.osmocom.org/docs/latest/osmo-gsm-tester-manual.pdf. We've trying to use the '4g_srsLTE' example from https://github.com/osmocom/osmo-gsm-tester/tree/master/doc/examples/4g_srsL… but when trying to run the 'ping' test the following error is returned in the Jenkins console output: " 14:07:52.867022 run mk-remote-dir(pid=2480): ERR: Terminated: ERROR {rc=1} [trial-21↪4g:srsenb-rftype@soapy↪ping.py:9↪ping.py↪srsepc_10.100.100.113↪host-jenkins@10.100.100.113↪mk-remote-dir(pid=2480)] 14:07:53.015620 run mk-remote-dir(pid=2480): stdout: | (launched: 2022-09-23_14:07:51.598612) | mkdir: cannot create directory ‘/osmo-gsm-tester-srsepc’: Permission denied " It appears that osmo-gsm-tester is trying to create the directory 'osmo-gsm-tester-srsepc' under root, which is not permitted as the Jenkins user the script runs has does not have permissions. Additionally, it looks like this path is hard-coded in the Python module https://github.com/osmocom/osmo-gsm-tester/blob/master/src/osmo_gsm_tester/… and also the same applies for srsENB https://github.com/osmocom/osmo-gsm-tester/blob/master/src/osmo_gsm_tester/… Is this the intended behaviour? Or have we missed out steps during our bare-metal setup process? I've double-checked that the main unit can SSH into the slave unit without a password so that's not the issue causing "permission denied". Best regards, Callum.

3 11

osmo-gsm-tester: Issue with osmo-gsm-tester-runner Jenkins job
by Callum Snowden 26 Sep '22

26 Sep '22

1 0

osmo-gsm-tester: Issue with osmo-gsm-tester-runner Jenkins job
by Callum Snowden 26 Sep '22

26 Sep '22

1 0

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

transceiver aborted
by msfu 24 Sep '22

24 Sep '22

hi there, i ran into an error with ./transceiver in osmocom-bb if i write osmocom/osmocom-bb/src/host/layer23/src/transceiver # sudo ./transceiver -a 47 -2 -r 99 the cli returns with 47 41 1 Aborted what am i doing wrong? i hope you can help me out. have a nice day msfu

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC