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
//
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.
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
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.
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
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
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)
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~
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
