OpenBSC

openbsc@lists.osmocom.org

14 participants
4246 discussions

Questions on OSMOCOM & real nodes integration
by jheyrendt.ext＠orange.com 30 Nov '23

30 Nov '23

Hi We set up a full Osmocom platform, with an Ettus USRP for SDR. All works well. Congratulations to Osmocom developers ! But now we want to use "real" nodes concerning MSC, MGW, HLR, SGSN & GGSN. Do you think it is possible ? Concerning the BSC-MSC association, do we need to use an SG (osmo-stp) ? or could we establish a Point To Point BSC-MSC ? SUA ? Concerning MGW, is there a way to use our MGW ? At this time, with Osmocom corposants, we can see RTP traffic between BTS-TRX and MGW, and some MGCP traffic between (BSC - local MGW) and MGW, and some MGCP traffic between osmo-MGW and osmo-MSC. Is there a way to have a "more standard" architecture: no traffic between BTS and MGW, and MGW controlled by MSC ? Do we have to more study TRAU, AoIP ? Concerning the Gb, do you think that it 'll work if we configure the Gb on a real SGSN connected to the osmo-pcu, hosted on the osmo-bts-trx? Many thanks in advance, Best regards Jean-Marc Orange Restricted

3 6

OsmoMSC: full proper codecs negotiation
by Neels Hofmeyr 20 Nov '23

20 Nov '23

It is my pleasure to inform that I have a WIP patch for OsmoMSC that allows, for the first time, full MO<->MT codecs negotiation to flexibly achieve TFO (Transcoding-Free Operation). It would be great if OsmoMSC users could give the patch a spin (in a setup that is allowed to fail because of the patch) and see if 2G calls now adjust the MO call leg to MT's codecs limitations for you. Looking forward to feedback! This task was idling on my list because I assumed it would be a big effort, but now I realized that it is actually simple, not even a new FSM state required. So I could no longer resist to finally complete this long long quest. The result is this WIP patch: https://gerrit.osmocom.org/c/osmo-msc/+/35051 Related patch series, uncluding ttcn3 test: https://gerrit.osmocom.org/q/topic:reass This patch requires full SDP on MNCC, so if using osmo-sip-connector, it should be current master -- the relevant patch was merged but is not released yet: https://gerrit.osmocom.org/c/osmo-sip-connector/+/16222 Before this patch, MO was eternally stuck on the initially assigned codec. Now we adjust MO's codec if MT needs it. (MT already intelligently chooses codecs before this patch.) For example, if MO is AMR capable and MT is not, - the MO side will start out with assigning an AMR codec (not matching). - Once MT responds (MNCC_ALERT_REQ), the MO side notices that MT does not support the assigned codec. It sends another Assignment Command to the BSC, offering only the codecs that MT supports. - If MO has at least one matching codec (say GSM-FR), the result is a TFO call using a matching codec. We still need to check: - does OsmoBSC play along nicely with the re-assignment (it should AFAICT). - effects on MGCP: there may now be more codecs than just the assigned one in the MGCP towards the MGW. See if that checks out. - effects on 3G: make sure the feature doesn't confuse IuUP handling. The patch passes all MSC_Tests.ttcn for me (but that doesn't necessarily imply proper codecs choices, the tests are not very strict there it seems). ~N -- - Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschäftsführer / Managing Directors: Harald Welte

2 2

OsmoDevCall on Nov 15, 2023: Calypso history: From TI to FreeCalypso to USA PSTN
by Harald Welte 15 Nov '23

15 Nov '23

Dear Osmocom community, we're happy to announce the next incarnation of OsmoDevCall. when: (today) November 15, 2023 at 20:00 CET where: https://osmocom.org/OsmoDevCall (Big Blue Button) This time, @falconia will be presenting on Calypso chipset history and development boards, from TI to FreeCalypso This meeting will have the following schedule: 20:00 meet + greet 20:10 topic 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

Network communication equipments for inquiry <16/10/2023 17:55>
by Yolanda from Longriseequipment 16 Oct '23

16 Oct '23

1 0

Osmo-CBC: (bts=0) Rx CBSP RESET: clearing all state; disabling broadcast
by Sipos Csaba 26 Sep '23

26 Sep '23

Dear List, I tried to set up Osmo-CBC with a Nokia MetroSite BTS according to the wiki. But every time the CBSP clinet of the BSC connects to the CBC server, the BSC log indicates: DCBS cbsp_link.c:150 CBSP Client connected to CBC: (r=127.0.0.1:48049<->l=127.0.0.1:46133) DCBS smscb.c:805 (bts=0) Rx CBSP RESET: clearing all state; disabling broadcast Same time on the CBC: <0002> cbsp_link.c:265 New CBSP link connection from 127.0.0.1:46133 <0002> cbsp_link_fsm.c:181 local-bsc: RESTART (CBS) but re-sending not implemented yet The BTS is configured with CCCH+SDCCH4+CBCH, and these are the relevant sections: osmo-cbc.cfg: cbc unknown-peers reject ecbe local-ip 127.0.0.1 local-port 12345 cbsp local-ip 127.0.0.1 local-port 48049 sbcap local-ip 127.0.0.1 local-port 29168 peer cbsp local-bsc mode server remote-port 46133 remote-ip 127.0.0.1 osmo-bsc.cfg: cbc mode client client remote-ip 127.0.0.1 local-ip 127.0.0.1 local-port 46133 Every other CS service is working fine on the BTS. Is there anything else I might have missed? Regards, Csaba

3 5

OsmoDevCall on Sept 20, 2023: Interconnecting an Osmocom GSM network to USA PSTN
by Harald Welte 18 Sep '23

18 Sep '23

Dear Osmocom community, we're happy to announce the next incarnation of OsmoDevCall. when: September 20, 2023 at 20:00 CEST where: https://osmocom.org/OsmoDevCall (Big Blue Button) This time, @falconia will be presenting on Themyscira Wireless: a case study in interconnecting an Osmocom GSM network to USA PSTN This meeting will have the following schedule: 20:00 meet + greet 20:10 topic 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

osmo-msc release?
by Neels Hofmeyr 16 Sep '23

16 Sep '23

I just noticed that a release was made, ignoring this remark in osmo-msc's TODO-RELEASE: MNCC osmo-sip-connector should do full SDP via MNCC and be released at the same time as the next osmo-msc, ask neels, thanks https://gerrit.osmocom.org/c/osmo-msc/+/34386 There is no full SDP support in current osmo-sip-connector. In fact the patch for that is just now becoming ready for merge: https://gerrit.osmocom.org/c/osmo-sip-connector/+/16222 I guess we should get the sipcon patch merged, and follow up with another sipcon release. ~N

5 9

icE1USB gateware
by Sipos Csaba 16 Sep '23

16 Sep '23

Dear list, I built an icE1USB device so I can provide stable clock to my legacy Nokia BTS. I have not found any information about how to bring up a completely empty device, so I just took the icE1usb-202210-5890f3e4.bin file and flashed it to the SPI flash, yet the device is not booting. Maybe something else is missing (like a boot block), or the binary has to be flashed with an offset? The device takes 80mA in this state, USB device is not recognized on the host. Thanks!

2 9

September 2023 Osmocom CNI releases (202302)
by Pau Espin Pedrol 14 Sep '23

14 Sep '23

Hi all, I am happy to announce that a new version 202309 of the Osmocom CNI (Cellular Network Infrastructure) software has been released this week. For further information, please visit: https://osmocom.org/news/220 Regards, Pau -- - Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

1 0

Re: Libraries not found when using nightly
by Sipos Csaba 11 Sep '23

11 Sep '23

Hi Vadim, You are probably correct, in the mean time I recompiled everything, so it works now, but most likely the *-dev packages were missing. Thanks for pointing that out! Another question I have is about displaying the Osmo-BSC logs: I am working on a museum setup and would be nice to show the BSC log output on the screen when there is activity. I wonder if there is a practical way to do that without altering the systemd part. Regards, Csaba

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC