OpenBSC

openbsc@lists.osmocom.org

4315 discussions

Annoucement of first tagged release of osmo-epdg
by Harald Welte 15 Jul '24

15 Jul '24

I'm happy to announce that [finally], the osmo-epdg development has reached its first release: 0.1.0. [Link to news item: https://osmocom.org/news/262] osmo-epdg[1] is combined ePDG and AAA to support Voice over Wifi (VoWiFi) calls. An ePDG allows a UE to connect over regular wireless networks to an IMS (untrusted non-3GPP network access). The combined ePDG/AAA is using a modified strongSwan[2] together with osmo-epdg[3], a daemon written in erlang/OTP. The osmo-epdg has been tested with open5gs as EPC and kamailio as IMS. To allow an easy setup of a fully working ePDG/epc/IMS there are ansible playbooks[4] which has been used to create our Hosted ePDG playground Thanks a lot to NLNet[5] for funding development of this project. Thanks also to the main developers of this project: Alexander "lynxis" Couzens and Pau "pespin" Espin Pedrol. Best regards, Harald [1] https://osmocom.org/projects/osmo-epdg/wiki [2] https://gitea.osmocom.org/ims-volte-vowifi/strongswan-epdg [3] https://gitea.osmocom.org/Erlang/osmo-epdg [4] https://gitea.osmocom.org/ims-volte-vowifi/ansible-prototype [5] https://nlnet.nl/project/Osmocom-ePDG/ -- - Harald Welte <laforge(a)osmocom.org> https://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

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

11 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

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 13 Jun '24

13 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

Re: New Defects reported by Coverity Scan for Osmocom
by Neels Hofmeyr 29 May '24

29 May '24

For the record, below DEADCODE warnings are "false" positives -- technically correct, but due to the VTY_NEWLINE macro: #define VTY_NEWLINE ((vty->type == VTY_TERM) ? "\r\n" : "\n") > 906 if (vty->type == VTY_TERM) > >>> CID 368762: Control flow issues (DEADCODE) > >>> Execution cannot reach the expression ""\n"" inside this statement: "vty_out(vty, "%% WARNING: n...". > 907 vty_out(vty, "%% WARNING: nft configuration changes need a restart of osmo-hnbgw%s", VTY_NEWLINE); On Tue, May 28, 2024 at 11:00:54PM +0000, scan-admin(a)coverity.com wrote: > Hi, > > Please find the latest report on new defect(s) introduced to Osmocom found with Coverity Scan. > > 2 new defect(s) introduced to Osmocom found with Coverity Scan. > > > New defect(s) Reported-by: Coverity Scan > Showing 2 of 2 defect(s) > > > ** CID 368762: Control flow issues (DEADCODE) > /source-Osmocom/osmo-hnbgw/src/osmo-hnbgw/hnbgw_vty.c: 907 in cfg_hnbgw_no_nft_kpi() > > > ________________________________________________________________________________________________________ > *** CID 368762: Control flow issues (DEADCODE) > /source-Osmocom/osmo-hnbgw/src/osmo-hnbgw/hnbgw_vty.c: 907 in cfg_hnbgw_no_nft_kpi() > 901 > 902 DEFUN(cfg_hnbgw_no_nft_kpi, cfg_hnbgw_no_nft_kpi_cmd, > 903 "no nft-kpi", > 904 NO_STR NFT_KPI_STR) > 905 { > 906 if (vty->type == VTY_TERM) > >>> CID 368762: Control flow issues (DEADCODE) > >>> Execution cannot reach the expression ""\n"" inside this statement: "vty_out(vty, "%% WARNING: n...". > 907 vty_out(vty, "%% WARNING: nft configuration changes need a restart of osmo-hnbgw%s", VTY_NEWLINE); > 908 g_hnbgw->config.nft_kpi.enable = false; > 909 return CMD_SUCCESS; > 910 } > 911 > 912 #if ENABLE_PFCP > > ** CID 368761: Control flow issues (DEADCODE) > /source-Osmocom/osmo-hnbgw/src/osmo-hnbgw/hnbgw_vty.c: 894 in cfg_hnbgw_nft_kpi() > > > ________________________________________________________________________________________________________ > *** CID 368761: Control flow issues (DEADCODE) > /source-Osmocom/osmo-hnbgw/src/osmo-hnbgw/hnbgw_vty.c: 894 in cfg_hnbgw_nft_kpi() > 888 { > 889 const char *set_table_name = NULL; > 890 if (argc > 0) > 891 set_table_name = argv[0]; > 892 > 893 if (vty->type == VTY_TERM) > >>> CID 368761: Control flow issues (DEADCODE) > >>> Execution cannot reach the expression ""\n"" inside this statement: "vty_out(vty, "%% WARNING: n...". > 894 vty_out(vty, "%% WARNING: nft configuration changes need a restart of osmo-hnbgw%s", VTY_NEWLINE); > 895 > 896 g_hnbgw->config.nft_kpi.enable = true; > 897 osmo_talloc_replace_string(g_hnbgw, &g_hnbgw->config.nft_kpi.table_name, set_table_name); > 898 > 899 return CMD_SUCCESS; > > > ________________________________________________________________________________________________________ > To view the defects in Coverity Scan visit, https://u15810271.ct.sendgrid.net/ls/click?upn=u001.AxU2LYlgjL6eX23u9ErQy-2… > > To manage Coverity Scan email notifications for "nhofmeyr(a)sysmocom.de", click https://u15810271.ct.sendgrid.net/ls/click?upn=u001.AxU2LYlgjL6eX23u9ErQy-2… > -- - Neels Hofmeyr <nhofmeyr(a)sysmocom.de> https://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Siemensstr. 26a * 10551 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

1 0

Developing GSMTAP version 3
by Shinjo Park 20 May '24

20 May '24

Hi all, After the OsmoDevCon 2024, I have set up a repository containing the GSMTAPv3 WIP version: https://gitea.osmocom.org/peremen/gsmtapv3 There is a Redmine ticket for GSMTAPv3: https://osmocom.org/issues/6445 Currently only the global header structure and types/subtypes are defined, and detailed explanation of what each data type stands for is still WIP. Also, GSMTAPv3 will use T16L16V dynamic metadata instead of fixed metadata structure, and the metadata definition is still in early stage. Having a structure definition is the very begging, which will be followed by additional works to actually use the new GSMTAPv3 format (APIs, Wireshark dissector, ...). Any form of help will be much appreciated. Best, Shinjo

4 7

Question about connecting OSMO-MSC to MME from Open5Gs
by Hennig, Lilly 18 May '24

18 May '24

Hello everybody, I was trying to setup an OSMO-MSC with an Open5Gs-Corenetwork, so I can send SMS to different UEs. Unfortunately the OSMO-MSC does not connect to the MME of the Open5Gs-Core and I do not find any installation guide for this specific setup. For your information: The Open5Gs-Core runs on a Laptop and I build the Software from source (4G and 5G components). The MSC should run on the same Laptop. Therefore I would like to ask you, if you can tell me, which other components besides of the OSMO-MSC I possibly have to install and how I should configure this components and the components of the core. Many thanks in advance! Best regards Lilly Hennig

2 1

hnbgw counter thread: another complication [solved]
by Neels Hofmeyr 15 May '24

15 May '24

So, we've been discussing IRL about the osmo-hnbgw implementation of interacting with nftables from a separate thread. The idea now is that a separate thread gets the results from nftables, caches them and enqueues them, so that the main thread can update the hnbgw counters in-sync. A second separate thread does nft add/del rule maintenance. There is another complication, and I want to make sure we agree on the solution: Problem: to delete a rule, I need to retrieve its 'handle' first. With the amount of threading we want, this becomes a bit complex. So. We 'add rule' and 'delete rule', as hNodeB attach and detach. But, to be able to 'delete rule', we need to retrieve an id that nftables assigned to this rule when it was added, the 'handle': add rule inet osmo-hnbgw gtpu-ul ip saddr 1.2.3.4 counter comment "ul:1-2-3-4"; ... list table inet osmo-hnbgw --> table inet osmo-hnbgw { chain gtpu-ul { ip saddr 1.2.3.4 counter packets 5 bytes 100 comment "ul:1-2-3-4" # handle 23; } ^^^^^^^^^ } ... delete rule inet osmo-hnbgw gtpu-ul handle 23; ^^^^^^^^^ AFAICT I cannot set a handle right from the start. I can also not delete a rule by just stating it again as it is, nor by using the 'comment' as a handle. nft wants a 'handle', period. Does anyone know better? Every time we read counters, osmo-hnbgw also retrieves the handles for each rule, and correlates via the 'comment'. Similarly to counters, we can only get all handles at once, via a complete table dump (possibly inefficient). It works out fine in most practical cases. But the complex corner case is when an hNodeB detaches quickly, before the counters had a chance to run and update the hNodeB's state, including the handle. In the current agreement on our implementation with two threads for nft, with queues back to the main thread, it would go something like this, to avoid races: main() nft_maintenance_thread() nft_read_counters_thread() | | | |---add hNodeB-------->| | |<--ok-----------------| | X | | |---del hNodeB-------->| | | [rule handle unknown!] | ..|<--EAGAIN-------------| | . | | | . |---do counters--------------------------------->| . | | [work] . | | [work] . | | [work] . |<--update-counters-and-handles------------------| . | | | ..|---del hNodeB-------->| | | [delete rule] | |<--done---------------| | Simplifying a bit... main() nft_maintenance_thread() nft_read_counters_thread() | | | |---add hNodeB-------->| | |<--ok-----------------| | X | | [want: del hNodeB] | | [rule handle unknown!] | | [set some "del" flag] | | . | | | . |---do counters--------------------------------->| . | | [work] . | | [work] . | | [work] . |<--update-counters-and-handles------------------| . | | | [del flag!] | | |---del hNodeB-------->| | | [delete rule] | |<--done---------------| | I'm not liking very much the amount of complexity spawning here, but this last approach is ok I guess, do you agree? i.e. when the handle is not set yet, set a flag on the hNodeB, and trigger the 'delete' the next time the counter thread reports back a handle for the hNodeB. ~N -- - Neels Hofmeyr <nhofmeyr(a)sysmocom.de> https://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Siemensstr. 26a * 10551 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

2 5

Is anyone using the official Osmocom rpm repositories?
by Oliver Smith 10 May '24

10 May '24

Dear mailing list, as announced in https://osmocom.org/news/246, the rpm packages for CentOS 8 / AlmaLinux 8 are unmaintained. sysmocom is currently still ensuring that the rpm binary packages build from the rpm spec files we have in our git repositories. But this is also significant effort that we would rather spend elsewhere, and so we are considering to stop providing rpm builds altogether and possibly removing these spec files from our git repositories. This affects the official Osmocom binary package repositories (nightly and latest) for CentOS 8/AlmaLinux 8 and openSUSE Tumbleweed. Stable versions of Osmocom programs are also in openSUSE's official repositories and can be installed from there. So, is anyone using the official Osmocom rpm repositories? As OsmoDevCon is coming up this weekend, we can also discuss it there, feel free to talk to me about it. Best regards, Oliver -- - Oliver Smith <osmith(a)sysmocom.de> https://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Siemensstr. 26a * 10551 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC