OpenBSC

openbsc@lists.osmocom.org

4317 discussions

Using TCAP/MAP between msc-hlr
by Amir Hossein 21 Apr '22

21 Apr '22

Hi, I'm interested in inspecting TCAP/MAP interactions between hlr-msc, but it seems osmo-msc osmo-hlr are using a custom protocol(GSUP). Are there any options to do so?Any suggestion would be appreciated. I saw some references to RestComm <https://github.com/RestComm/jss7>, moji-mobile <https://github.com/moiji-mobile/tcap> and signerl <https://gitea.osmocom.org/erlang/signerl>(seems abandoned), any of these combinations would work with osmo-msc/hlr? A side question: is GSUP the only custom protocol used in osmocom gsm network?all other interactions are based on 3GPP? Best Regards, amir.

2 1

error in osmo-sim-auth.py
by msfu 20 Apr '22

20 Apr '22

hello, i have this issue with osmo-sim-auth. if i do sudo python osmo-sim-auth.py -r 00000000000000000000000000000000 -a ec9320c2c2000000e1dd22c1ad3e2d3d the cli repeats: Traceback (most recent call last): File "osmo-sim-auth.py", line 27, in <module> from card.USIM import USIM File "/usr/src/osmo-sim-auth/card/USIM.py", line 56 print '[DBG] type definition: %s' % type(self) ^ SyntaxError: invalid syntax maybe it's missing a library for USIM or something else? can you help me get beyond this issue? Thank you

1 0

Inter BSC handover.
by Keith 13 Apr '22

13 Apr '22

I'm still having trouble actually getting an Inter-BSC handover to complete. I'm using two osmo-bts based BTS and all master/nightly etc.. The problem as far as I can see is the the destination BSC complains that: HO-interBSC-In: incoming inter-BSC Handover: HO Request: Invalid or empty Codec List (MSC Preferred) (handover_fsm.c:620) Stopping the MSC at ran_a_make_handover_request() and inspecting the stack and local variables I can see that indeed the member ran_handover_request->codec_list_msc_preferred at that point is NULL. Further up the stack in msc_ho_send_handover_request(), is where this ran_msg of type RAN_MSG_HANDOVER_REQUEST comes into being https://cgit.osmocom.org/osmo-msc/tree/src/libmsc/msc_ho.c#n385 but at no time do we assign anything to codec_list_msc_preferred, therefore, when we get to https://cgit.osmocom.org/libosmocore/tree/src/gsm/gsm0808.c#n995 we are skipping gsm0808_enc_speech_codec_list(msg, params->codec_list_msc_preferred); and therefore not calling msgb_put_u8(msg, GSM0808_IE_SPEECH_CODEC_LIST); I'm not seeing how this is supposed to work. or what am I missing? I do see code that looks like it is setting up the codec_list_msc_preferred, but that seems to relate ONLY to Inter-MSC Handover. Thanks Keith.

2 1

Osmo MGW problem with real Ericsson MGW
by Sjur Thomas Lien 12 Apr '22

12 Apr '22

Hi, I'm using OsmoMGW version 1.9.0.20.069dd.202204110026 and OsmoHNBGW version 1.2.1.13.be9e.202204110026. Call is established, but is silent. The connection is up,but only data flowing one way: OsmoMGW# show mgcp endpoint rtpbridge/1@mgw Virtual trunk 0 endpoint rtpbridge/1@mgw: Availability: available CONN: (1701/rtp, id:0x49AD9023, ip:10.40.16.36, rtp:19856 rtcp:19857) Packets Sent: 0 (0 bytes total) Packets Received: 0 (0 bytes total) Timestamp Errs: 0->0 Dropped Packets: 0 Payload Type: 96 Rate: 16000 Channels: 1 Frame Duration: 20 Frame Denominator: 1000 FPP: 0 Packet Duration: 20 FMTP-Extra: (null) Audio-Name: VND.3GPP.IUFP/16000 Sub-Type: VND.3GPP.IUFP Output-Enabled: 1 Force-PTIME: 0 CONN: (1701/rtp, id:0x5AFEDEF8, ip:10.103.36.93, rtp:55078 rtcp:55079) Packets Sent: 918 (15606 bytes total) Packets Received: 1118 (34350 bytes total) Timestamp Errs: 0->0 Dropped Packets: 0 Payload Type: 96 Rate: 16000 Channels: 1 Frame Duration: 20 Frame Denominator: 1000 FPP: 0 Packet Duration: 20 FMTP-Extra: (null) Audio-Name: VND.3GPP.IUFP/16000 Sub-Type: VND.3GPP.IUFP Output-Enabled: 1 Force-PTIME: 0 OsmoMGW# And I can ping 10.40.16.36 with source 10.40.50.67. But there seems to be aproblem with RTP initialization on link towards core ( Ericsson MGW ) <0012> mgcp_protocol.c:855 endpoint:rtpbridge/1@mgw CRCX: creating new connection ... <0012> mgcp_protocol.c:165 endpoint:rtpbridge/1@mgw RTP-setup: Endpoint is in loopback mode, stopping here! <0012> mgcp_protocol.c:1091 endpoint:rtpbridge/1@mgw CI:C6A09234 CRCX: connection successfully created <0012> mgcp_protocol.c:1124 endpoint:rtpbridge/1@mgw MDCX: modifying existing connection ... <0012> mgcp_sdp.c:436 endpoint:rtpbridge/1@mgw CI:C6A09234 Got media info via SDP: port:55076, addr:10.103.36.93, duration:20, payload-types:96=VND.3GPP.IUFP <0000> mgcp_iuup.c:705 (rtpbridge/1@mgw I:C6A09234) No RFCI NO_DATA found, unable to send dummy packet <0012> mgcp_protocol.c:1312 endpoint:rtpbridge/1@mgw CI:C6A09234 MDCX: connection successfully modified <0012> mgcp_protocol.c:855 endpoint:rtpbridge/1@mgw CRCX: creating new connection ... <0012> mgcp_sdp.c:436 endpoint:rtpbridge/1@mgw CI:E7B356C6 Got media info via SDP: port:19008, addr:10.40.16.36, duration:20, payload-types:96=VND.3GPP.IUFP <0000> mgcp_iuup.c:705 (rtpbridge/1@mgw I:E7B356C6) No RFCI NO_DATA found, unable to send dummy packet <0012> mgcp_protocol.c:1091 endpoint:rtpbridge/1@mgw CI:E7B356C6 CRCX: connection successfully created <0019> iuup.c:537 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Initialization: Unexpected RFCI 1 at position 0 received <0019> iuup.c:612 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Tx Initialization NACK cause=19 orig_message=e0 00 dd b4 06 01 51 67 3c 86 27 00 00 00 01 00 <0019> iuup.c:537 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Initialization: Unexpected RFCI 1 at position 0 received <0019> iuup.c:612 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Tx Initialization NACK cause=19 orig_message=e0 00 dd b4 06 01 51 67 3c 86 27 00 00 00 01 00 <0019> iuup.c:537 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Initialization: Unexpected RFCI 1 at position 0 received < . . . <0019> iuup.c:537 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Initialization: Unexpected RFCI 1 at position 0 received <0019> iuup.c:612 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Tx Initialization NACK cause=19 orig_message=e0 00 dd b4 06 01 51 67 3c 86 27 00 00 00 01 00 <0019> iuup.c:537 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Initialization: Unexpected RFCI 1 at position 0 received <0019> iuup.c:612 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Tx Initialization NACK cause=19 orig_message=e0 00 dd b4 06 01 51 67 3c 86 27 00 00 00 01 00 <0019> iuup.c:537 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Initialization: Unexpected RFCI 1 at position 0 received <0019> iuup.c:612 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Tx Initialization NACK cause=19 orig_message=e0 00 dd b4 06 01 51 67 3c 86 27 00 00 00 01 00 <0019> iuup.c:537 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Initialization: Unexpected RFCI 1 at position 0 received <0019> iuup.c:612 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Tx Initialization NACK cause=19 orig_message=e0 00 dd b4 06 01 51 67 3c 86 27 00 00 00 01 00 <0019> iuup.c:895 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Event IuUP-DATA-ind not permitted <0000> mgcp_iuup.c:189 (rtpbridge/1@mgw I:C6A09234) Failed passing IuUP-Init to IuUP layer <0019> iuup.c:537 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Initialization: Unexpected RFCI 1 at position 0 received <0019> iuup.c:612 IuUP(C6A09234)[0x562a59d9c600]{Initialisation}: Tx Initialization NACK cause=19 orig_message=e0 00 dd b4 06 01 51 67 3c 86 27 00 00 00 01 00 <00 Configs: ! MGW mgcp domain mgw local ip 10.40.50.67 bind ip 10.40.50.67 bind port 2427 rtp port-range 4002 16001 no rtp ip-probing rtp ip-dscp 0 rtp keep-alive once no rtcp-omit no rtp-patch sdp audio-payload send-ptime sdp audio-payload send-name number endpoints 15 allow-transcoding osmux off end !HnbGW cs7 instance 0 network-indicator national point-code 0.69.4 sccp-address msc routing-indicator PC point-code 0.27.4 sccp-address sgsn routing-indicator PC point-code 0.113.6 hnbgw log-prefix hnb-id iuh local-ip 10.40.50.69 iucs remote-addr msc iups remote-addr sgsn mgcp mgw remote-ip 10.40.50.67 mgw remote-port 2427 mgw reset-endpoint rtpbridge/* end Best Regards Sjur Thomas Lien Systems engineer Roaming & Network access Telenor Maritime +47 91602376 Kystveien 2D N-4841 Arendal, Norway www.telenormaritime.com<http://www.telenormaritime.com/> LinkedIn<https://www.linkedin.com/company/telenor-maritime/> [/Users/rinomartinsen/Dropbox (ANTI)/Telenor/2_Projects/TNO036_digitizing and renewal of the telenor identity/FINAL/Toolkit/Logo/Symbol/RGB/pdf/telenor_symbol_blue.pdf] Internal

2 3

OSMO HnbGW - issue with real Ericsson SGSN
by Sjur Thomas Lien 11 Apr '22

11 Apr '22

Hi, I'm running OsmoHNBGW version 1.2.1.13.be9e.202204110026 and OsmoSTP version 1.5.0.15.64dd.202204110026. When a mobile is @ home, and then roams to our network, a "Routing area update request" (SCCP connection request ) is sent by osm-hnbgw to our SGSN. But the message is ignored by our SGSN, we need to study this further, but we do see some errors related to SCCP in the hnbgw log: 20220411100428998 DMAIN INFO 002448ffff0d2770.servicesnode.spidercloud.com Creating new Mapping RUA CTX 0x558d149bba80/30 <-> SCU Conn ID 0x558d149779a0/1529 (context_map.c:94) 20220411100444098 DLSCCP ERROR SCCP-SCOC(1529)[0x558d14ad2230]{CONN_PEND_OUT}: Event N-DATA.req not permitted (sccp_scoc.c:1772) 20220411100448629 DLSCCP ERROR SCCP-SCOC(1529)[0x558d14ad2230]{CONN_PEND_OUT}: Event N-DATA.req not permitted (sccp_scoc.c:1772) 20220411100453031 DLSCCP ERROR SCCP-SCOC(1528)[0x558d14acb9d0]{WAIT_CONN_CONF}: transition to state IDLE not permitted! (sccp_scoc.c:1031) 20220411100529016 DLSCCP ERROR SCCP-SCOC(1529)[0x558d14ad2230]{WAIT_CONN_CONF}: transition to state IDLE not permitted! (sccp_scoc.c:1031) 20220411100550019 DMAIN INFO 002448ffff0d2770.servicesnode.spidercloud.com Creating new Mapping RUA CTX 0x558d149bba80/30 <-> SCU Conn ID 0x558d149779a0/1530 (context_map.c:94) 20220411100605018 DLSCCP ERROR SCCP-SCOC(1530)[0x558d14ad82b0]{CONN_PEND_OUT}: Event N-DATA.req not permitted (sccp_scoc.c:1772) 20220411100609648 DLSCCP ERROR SCCP-SCOC(1530)[0x558d14ad82b0]{CONN_PEND_OUT}: Event N-DATA.req not permitted (sccp_scoc.c:1772) 20220411100626108 DMAIN INFO 002448ffff0d2770.servicesnode.spidercloud.com Creating new Mapping RUA CTX 0x558d149bba80/30 <-> SCU Conn ID 0x558d149779a0/1531 (context_map.c:94) 20220411100641058 DLSCCP ERROR SCCP-SCOC(1531)[0x558d14ad1c50]{CONN_PEND_OUT}: Event N-DATA.req not permitted (sccp_scoc.c:1772) 20220411100645648 DLSCCP ERROR SCCP-SCOC(1531)[0x558d14ad1c50]{CONN_PEND_OUT}: Event N-DATA.req not permitted (sccp_scoc.c:1772) 20220411100650021 DLSCCP ERROR SCCP-SCOC(1530)[0x558d14ad82b0]{WAIT_CONN_CONF}: transition to state IDLE not permitted! (sccp_scoc.c:1031) So we think this might be related. The bottom line is that mobile does not attempt a PS attach. When checking logs for successful RA updates, we see that SGSN receives a standalone SCCP Connection request, this is answered with connection confirmed, and the RA update req comes in with SCCP message type DT1 instead of connection request. Hope someone can help. Best Regards Sjur Thomas Lien Systems engineer Roaming & Network access Telenor Maritime +47 91602376 Kystveien 2D N-4841 Arendal, Norway www.telenormaritime.com<http://www.telenormaritime.com/> LinkedIn<https://www.linkedin.com/company/telenor-maritime/> [/Users/rinomartinsen/Dropbox (ANTI)/Telenor/2_Projects/TNO036_digitizing and renewal of the telenor identity/FINAL/Toolkit/Logo/Symbol/RGB/pdf/telenor_symbol_blue.pdf] Internal

1 0

osmo-bsc Rx RR Assignment Failure.
by Andrew Back 09 Apr '22

09 Apr '22

Configuration is Network In The Box with everything running on a LimeNET Micro (RPi CM3+), using Raspbian 10 and osmocom:latest packages via OBS. UEs can register fine and send/receive SMS, but when I attempt to make a call I see the Rx RR Assignment Failure error from osmo-bsc. I have a suspicion it's a configuration error and would appreciate any suggestions. Attached config and log output. Regards, Andrew

1 0

OsmoDevCall on Apr 8, 2022: No presentation, just random chat
by Harald Welte 08 Apr '22

08 Apr '22

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall on April 8, 2022 at 20:00 CEST at https://meeting5.franken.de/b/har-xbc-bsx-wvs In this edition, we will not have a presentation / speaker but just informal chat / conversation. Attendance is free of charge and open to anyone with an interest in Osmocom or open source cellular technologies. NOTE: There will be no recording of this talk, so if interested, please make sure you don't miss it! 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 -- - 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

Powering up nanoBTS with no Tx antenna connected
by Mychaela Falconia 07 Apr '22

07 Apr '22

Hello Osmocom CNI folks, I am getting ready to set up my own GSM network using nanoBTS hardware (currently going through the incredible pain of satisfying all dependencies to get Osmocom CNI software running on Slackware - because no one makes binary packages for Slackware to my knowledge, I have to compile from source), and I found this note in this wiki page: https://osmocom.org/projects/osmobsc/wiki/NanoBTS_Getting_Started "Do not power up the device without a TX antenna" Can someone please educate me (and possibly other wondering souls) *why* one must not power up a nanoBTS with no Tx antenna connected? I understand how it can be a bad idea to actually turn on Tx output with an open antenna connector, as the lack of 50 ohm termination would case Tx energy to reflect back to the PA or whatever internal components this unit has, but it is also my understanding that these units turn on their Tx only after they establish a good link with a BSC, with the BSC then telling the nanoBTS what ARFCN it should transmit on, and at what power level. Therefore, if I am powering up a nanoBTS for the purpose of getting its DHCP to work and doing abisip-find and ipaccess-config steps on it, then during this phase prior to osmo-bsc configuration, the unit's Tx output should be fully off - so what would be the problem with having no Tx antenna? For context, once I get past initial DHCP etc configuration, before I deploy my nanoBTS on live air, I intend to check its Tx output first: instead of an antenna, connect an RF measuring instrument (I'll use my CMU200 in the non-GSM-specific "generic RF analyzer" mode) to the Tx output port, verify that the frequency it transmits on matches the ARFCN I configure in osmo-bsc, and verify that Tx power control is working - and only then put the real antenna on. But it would be cumbersome to bring the unit into the lab with the CMU200 while I am sorting out DHCP etc, hence I wonder if it would be OK to have nothing at all connected to the Tx port while I work on those preliminary steps. M~

2 1

GTP load generator
by Sipos Csaba 05 Apr '22

05 Apr '22

Hi Harald, I just stumbled upon your GTP load gen code on the Osmocom git. My question is: can I use this tool to "act" as an enodeb and test GTP-U performance? The issue is my S/PGW is a combo one, so if this GTP load gen tool acts as an SGSN/SGW, I cannot attach it to the network, as there is no externally accessible S5 interface, just the 2152 GTP-U port used by S1-U. Thanks! Csaba

3 4

RFC: migrating git.osmocom.org to gitea?
by Harald Welte 31 Mar '22

31 Mar '22

Hi all! [please follow-up-to the openbsc(a)lists.osmocom.org mailing list, if there is any discussion, we don't want to drag it over tons of mailing lists in parallel] Some weeks ago, I created https://osmocom.org/issues/5397 but it seems nobody noticed the ticket or had any comments to it. So let me post this as RFC here on the mailing list: In the past, we had a gitolite/gitosis setup, which was fine in the early days of git, but it means that people cannot easily create new repositories, see who has permissions, and we cannot delegate ownership. Even updating SSH keys requires manual interaction of a sysadmin like me. I would therefore suggest to migrate git.osmocom.org to gitea[1] This would allow the following features: * users can self-create any number of personal repositories (like gitlab/github) * we can create 'organizations' along the line of reasonably independent osmocom member projects like op25, who can then manage their own repos/permissions/... * gitea can link to redmine wiki and redmine issue trackers (rather than using its own built-in) For those repositories hosted in gerrit (mainly CNI), we would still keep git.osmocom.org a read-only mirror, like we do it right now. For those repositories not hosted in gerrit, users/projects could then accept merge requests in gitea. Coupling this with 3rd party authentication via github/gitlab/etc should make it easier for the occasional contributor to submit changes. There is a downside, of course; A lot of repo URLs have to change. Most of our current repositories are at git.osmocom.org/project.git while gitea follows a git.osmocom.org/organization/project.git scheme. I'm not sure there is any way to help to mitigate this... Any thoughts, comments? [1] https://gitea.io/ -- - 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)

5 5

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC