OpenBSC April 2022

openbsc@lists.osmocom.org

17 participants
26 discussions

FCSIM1 cards availability and applications
by Mychaela Falconia 28 Apr '22

28 Apr '22

Hello Osmocom community, In my previous reply to Anonymous Internet User msfu666, I mentioned that I sometimes give out FCSIM1 cards free of cost to certain recipients, but I did not elaborate on the conditions. I did not spell out the conditions because I hadn't actually given much thought to what they should be - but thinking about it now, I realize that only one condition would actually make sense. My FCSIM1 cards are good for one and only one purpose: operating your own GSM network (presumably with Osmocom CNI software, no idea if OpenBTS/YateBTS would work or not) *for the purpose of* providing service specifically to vintage handsets. Therefore, the condition becomes quite simple: if there is anyone here besides just me who operates their own Osmocom-based GSM network _specifically for the purpose_ of providing service specifically to _vintage_ GSM handsets and you would like some of my FCSIM1 cards, please let me know and I'll send you a few. What are vintage GSM handsets? For the present purpose, we can define a vintage GSM handset as being one that: a) has a 2FF SIM socket, as opposed to 3FF or 4FF or eSIM; b) has a 2G-only radio; c) does not speak UICC/USIM protocol, only GSM 11.11 SIM. If anyone besides me operates their own GSM network specifically for the purpose of providing service to (or just playing with) such vintage handsets, then FCSIM1 cards would be a good choice for such operation: hence if you would like some, you can have them for the cost of shipping. OTOH, if you operate your own network, even if it's a 2G network radio-wise, for some purpose other than exclusively serving or playing with vintage handsets, then my FCSIM1 cards will NOT be a good choice for your applications. Specifically, if you are going to connect any kind of "modern" phones to your network, even if it's 2G RAN, those "modern" phones will want 3FF or 4FF SIMs - but my FCSIM1 cards are 2FF only, and thus a poor choice for such usage. Sincerely, Lady Mychaela Nadezhda Falconia, Mother of FreeCalypso, Dame of the Order of 2G, Champion of Published Source Code

1 0

T200 expiring with nanoBTS, breaking voice calls
by Mychaela Falconia 22 Apr '22

22 Apr '22

Hello Osmocom CNI folks, I got my first GSM network up and running, using nanoBTS hardware and Osmocom CNI sw stack. I compiled everything from source (to my knowledge, no one makes binary packages for Slackware), but rather than grabbing the state of git master on some random day, I checked out tagged versions corresponding to the latest official 2021-11 CNI release. My configuration is 2G-only, CS-only, minimal split-NITB, thus the 5 processes I am running are OsmoSTP, OsmoHLR, OsmoMGW, OsmoMSC and OsmoBSC. I'm using the same OsmoMGW instance for both MSC and BSC. The functional state is: phones with FCSIM1 cards in them whose programming matches the data I entered into HLR are able to connect (location update succeeds), SMS from one phone to another works, and USSD requests *#100# and *#101# also work. However, voice calls don't work. The user-visible symptoms are: 1) When I dial a call from one connected phone to another, the destination phone starts ringing, and it shows the calling number on the display - thus CC signaling works correctly at least in the initial phases. 2) However, a short time (I measured a little under 20 s) after the start of the process, the destination phone stops ringing and shows a missed call indication. However, the origin phone continues playing its NOIBT ringing tone as if it is still waiting for the call to be answered, and it keeps going for another 15-20 s or so, before it gives up. 3) Trying to press the answer button on the destination phone before it stops ringing and goes into the "missed call" state does NOT produce a connected call state either. To see what's going on, I turned on maximum verbosity logging in all OsmoCNI components and plowed through the resulting massive log. (I am logging via syslog - the whole point of running Slackware is principled opposition to systemd.) And I see what appears to be the culprit - see lines 7558 and 7559 in the attached log, UTC timestamp 02:48:54, 11 seconds after I initiated the test call from the origin phone. It appears that the BTS is telling the BSC that this error occurred: "Timer T200 expired (N200+1) times", and based on the lchan(0-0-2-TCH_F-0) annotation, this error is happening on the origin leg of the call, rather than the destination leg. I looked up what T200 is: https://www.rfwireless-world.com/Terminology/GSM-timers.html T200: "It is used as retransmission on data link layer. Value varies depending on different messages (for FACCH it is set to 155ms)" Why in the world are FACCH (or is it SACCH?) data link transmissions suddenly failing on the origin leg of the call, some 11 to 13 seconds in? I have tried 4 different phones in the call-origin role (Motorola C139 running its original fw, Pirelli DP-L10 likewise, Nokia C3-00 and my own FreeCalypso fw), and the behaviour is always the same. Has anyone seen this problem before? Is it perhaps a known issue with nanoBTS that requires some special workaround? This tarball: https://www.freecalypso.org/members/falcon/osmo-cni/t200-fail-config+log.ta… contains my configuration files for all 5 OsmoCNI components and an excerpt from syslog. The syslog excerpt begins with all 5 OsmoCNI components booting up, followed by two phones connecting, and finally the test call. I would really appreciate it if someone could give me some pointers for debugging this voice call show-stopper. TIA, Mychaela

3 6

issue with osmo-sim-auth
by msfu 22 Apr '22

22 Apr '22

hello, i ran into an issue with osmo-sim-auth. if i try ./osmo-sim-auth.py -r 00000000000000000000000000000000 -s it says 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 do you know what the problem is? i think i installed pcsc-lite, pcscd and pyscard and dependencies. thank you

5 5

OsmoDevCall on Apr 29, 2022: Osmocom Community TDMoIP (OCTOI)
by Harald Welte 22 Apr '22

22 Apr '22

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall (delayed by one week from our usual spot) on April 29, 2022 at 20:00 CEST at https://meeting5.franken.de/b/har-xbc-bsx-wvs In this edition, I will be presenting on the state of the OCTOI (Osmocom TDMoIP) Retronetworking activities (see https://osmocom.org/projects/octoi/wiki) 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

Re: error in osmo-sim-auth.py
by Riemer, Björn 21 Apr '22

21 Apr '22

Hi, The script seems to be python2 and you are running it with python3. Either the script has to be ported or yust try to use legacy python2. Björn Am 21.04.2022 14:13 schrieb msfu <msfu666(a)gmail.com>: 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

2 2

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

21 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. The same hardware and CNI configuration works fine when used with an old RPi image that has packages from late 2019. Configs and error log attached. Would appreciate any suggestions for things to try. Regards, Andrew //

3 3

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC April 2022