Hello.
I have installed open5gs v2.6.6 on ubuntu 22.04 (192.168.75.181) with
kamailio and volte config as in
https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/. It work well. I
have installed osmo on 192.168.75.185 and also it work well and call
establised. but when I add sgs config in mme, It show this info:
[mme] INFO: sgsap client() [192.168.75.185]:29118
(../src/mme/sgsap-sctp.c:55)
[mme] INFO: VLR-SGs[192.168.75.185] connection refused!!!
(../src/mme/mme-sm.c:717)
In osmo-msc.cfg i add:
sgs
local-port 29118
local-ip 192.168.75.185
vlr-name vlr.msc001.mnc001.mcc001.3gppnetwork.org
end
and in mme.yaml:
sgsap:
addr: 192.168.75.185
map:
tai:
plmn_id:
mcc: 001
mnc: 01
tac: 1
lai:
plmn_id:
mcc: 001
mnc: 01
lac: 1
@
mme.txt <https://github.com/user-attachments/files/17811895/mme.txt>
This is the log when run osmomsc
smo-msc -c /etc/osmocom/osmo-msc.cfg
DMNCC NOTICE MNCC socket at /tmp/msc_mncc (mncc_sock.c:300)
DLGLOBAL NOTICE Available via telnet 127.0.0.1 4254 (telnet_interface.c:88)
DSMPP NOTICE SMPP at 0.0.0.0 2775 (smpp_smsc.c:989)
DLCTRL NOTICE CTRL at 127.0.0.1 4255 (control_if.c:1024)
DLGSUP NOTICE GSUP connecting to 127.0.0.1:4222 (gsup_client.c:74)
DDB NOTICE Init database connection to 'sms.db' using SQLite3 lib version
3.37.2 (db.c:521)
DLMGCP NOTICE MGW(mgw) MGCP client: using endpoint domain '@mgw
<https://github.com/mgw>' (mgcp_client.c:932)
DMSC NOTICE MGW pool with 1 pool members configured, (ignoring MGW
configuration in VTY node 'msc'). (msc_main.c:596)
DLSCCP NOTICE OsmoMSC-A-Iu: Using SS7 instance 0, pc:0.23.1
(sccp_user.c:566)
DLSCCP NOTICE OsmoMSC-A-Iu: Creating AS instance (sccp_user.c:573)
DLSCCP NOTICE OsmoMSC-A-Iu: Using AS instance as-clnt-OsmoMSC-A-Iu
(sccp_user.c:584)
DLSCCP NOTICE OsmoMSC-A-Iu: Creating default route (sccp_user.c:590)
DLSCCP NOTICE OsmoMSC-A-Iu: No unassociated ASP for m3ua, creating new ASP
asp-clnt-OsmoMSC-A-Iu (sccp_user.c:629)
DLGLOBAL ERROR Trying to dispatch event 17 to non-existent FSM instance!
(osmo_ss7_as.c:118)
DLGLOBAL ERROR backtrace() returned 9 addresses (backtrace.c:42)
DLGLOBAL ERROR
/lib/x86_64-linux-gnu/libosmocore.so.22(_osmo_fsm_inst_dispatch+0x486)
[0x7f4b057e68d6] (backtrace.c:53)
DLGLOBAL ERROR
/lib/x86_64-linux-gnu/libosmo-sigtran.so.10(osmo_ss7_as_add_asp+0x15b)
[0x7f4b055596ab] (backtrace.c:53)
DLGLOBAL ERROR
/lib/x86_64-linux-gnu/libosmo-sigtran.so.10(osmo_sccp_simple_client_on_ss7_id+0x97b)
[0x7f4b0557381b] (backtrace.c:53)
DLGLOBAL ERROR osmo-msc(+0x185ca) [0x55b74b7575ca] (backtrace.c:53)
DLGLOBAL ERROR osmo-msc(+0x1780a) [0x55b74b75680a] (backtrace.c:53)
DLGLOBAL ERROR /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7f4b05167d90]
(backtrace.c:53)
DLGLOBAL ERROR /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80)
[0x7f4b05167e40] (backtrace.c:53)
DLGLOBAL ERROR osmo-msc(+0x181c5) [0x55b74b7571c5] (backtrace.c:53)
DLSCCP NOTICE OsmoMSC-A-Iu: Using ASP instance asp-clnt-OsmoMSC-A-Iu
(sccp_user.c:699)
DLSS7 NOTICE 0: Creating SCCP instance (osmo_ss7.c:408)
DSGS NOTICE SGs socket bound to r=NULL<->l=192.168.75.185:29118
(sgs_server.c:186)
DMSC NOTICE A-interface: SCCP user OsmoMSC-A:RI=SSN_PC,PC=(no
PC),SSN=BSSAP, cs7-instance 0 ((null)) (msc_main.c:806)
DMSC NOTICE Iu-interface: SCCP user OsmoMSC-IuCS:RI=SSN_PC,PC=(no
PC),SSN=RANAP, cs7-instance 0 ((null)) (msc_main.c:826)
DLINP NOTICE 127.0.0.1:4222 connection done (ipa.c:143)
DLINP NOTICE received ID_GET for unit ID 0/0/0 (ipaccess.c:897)
DLM3UA NOTICE 0: asp-asp-clnt-OsmoMSC-A-Iu: Received NOTIFY Type State
Change:AS Inactive () (m3ua.c:622)
DLSS7 NOTICE xua_default_lm(asp-clnt-OsmoMSC-A-Iu)[0x55b74ca95a20]{ACTIVE}:
Ignoring primitive M-ASP_ACTIVE.confirm (xua_default_lm_fsm.c:400)
DLM3UA NOTICE 0: asp-asp-clnt-OsmoMSC-A-Iu: Received NOTIFY Type State
Change:AS Active () (m3ua.c:622)
DSGS NOTICE r=192.168.75.181:51999<->l=192.168.75.185:29118: Connection
lost (sgs_server.c:101)
DSGS NOTICE r=192.168.75.181:37170<->l=192.168.75.185:29118: Connection
lost (sgs_server.c:101)
DSGS NOTICE r=192.168.75.181:42624<->l=192.168.75.185:29118: Connection
lost (sgs_server.c:101)
DSGS NOTICE r=192.168.75.181:40043<->l=192.168.75.185:29118: Connection
lost (sgs_server.c:101)
DSGS NOTICE r=192.168.75.181:51479<->l=192.168.75.185:29118: Connection
lost (sgs_server.c:101)
Dear Harald,
I watched your excellent presentation on eSIMs and I have two
questions just to make sure I understand the situation correctly.
1. Both the eSIM profile and the SM-DP+ server's certificate has to be
signed by the GSMA in order to be able to provide eSIM services to
commercial handsets?
2. If the above is the case, that means we effectively lost control of
the SIM infra, as we always have to rely on 3rd party SM-DP+ and eSIM
profile providers who can provide the necessary signing for both the
eSIM profiles and the SM-DP+ server certs signed by GSMA?
Based on what you implied during the OsmoDevCall call about getting
certified, I am under the impression that Sysmocom will not be able to
provide nor eSIM profiles nor SM-DP+ services that can be used for
commercial handsets? If this is the case, can you kindly redirect me
to a vendor/provider who you have good experience with in this regard?
Much appreciate your help!
Regards,
Csaba
It refers to professional assistance provided to students who are struggling with statistical concepts, data analysis, or complex calculations. Whether it’s understanding probability theory, regression analysis, or hypothesis testing, expert tutors offer tailored support to help students complete their assignments accurately and on time. With help with Statistics assignment, students can gain a better grasp of difficult concepts, improve their grades, and enhance their problem-solving skills. This support is especially valuable for those in fields like economics, engineering, or social sciences, where statistical knowledge is crucial. With expert guidance, students can overcome academic challenges and achieve success in their coursework. https://theassignmentshelp.com/statistics-assignment-help
It refers to professional assistance provided to students who are struggling with statistical concepts, data analysis, or complex calculations. Whether it’s understanding probability theory, regression analysis, or hypothesis testing, expert tutors offer tailored support to help students complete their assignments accurately and on time. With help with Statistics assignment, students can gain a better grasp of difficult concepts, improve their grades, and enhance their problem-solving skills. This support is especially valuable for those in fields like economics, engineering, or social sciences, where statistical knowledge is crucial. With expert guidance, students can overcome academic challenges and achieve success in their coursework. https://theassignmentshelp.com/statistics-assignment-help
Hello Osmocom community,
(Cc'ing Eric per instructions from Harald)
I am looking to acquire an SDR device for the purpose of running
osmo-bts-trx. My initial goal is to get to the bottom of some
mysteries observed in OS#6579; because it is CSD, getting a
non-virtual test setup requires an SDR-based BTS rather than the
otherwise wonderful sysmoBTS. And of course there will likely be
other fixes and improvements that can be made in osmo-bts-trx. :)
Harald recommended that I get a BladeRF 2.0 xA4 for this purpose,
plus a Leo Bodnar GPSDO. However, before I commit to buying that hw
with an aggregate cost of around $800, I wanted to get some community
input to make sure it is the right choice for the job at hand.
(There is also the possibility that Sysmocom will sponsor this hw for
me, which is wonderful - but still, I don't want to waste money even
if it's someone else's!)
Harald told me that Eric has worked on BladeRF, and instructed me to
ask both Eric and the wider community. My basic question is: how
stable and reliable is this BladeRF 2.0 in the BTS application? I
presume I will need to run osmo-trx-bladerf, but I find it alarming
that there is absolutely no documentation for this variant: the wiki
and the user manual cover osmo-trx-uhd and osmo-trx-lms, but not one
mention of BladeRF.
It is my understanding that BladeRF always runs on 38.4 MHz clock; if
the external clock frequency is some other, the PLL inside BladeRF
will discipline the local 38.4 MHz VCXO to "follow" the external
reference, but the SDR will still run at 38.4 MHz. Thus I see no way
to avoid fractional resampling, i.e., configuring the external GPSDO
to put out 26 MHz or 52 MHz won't do anything to eliminate that
fractional resampling need. Hence the question: does this fractional
resampling constitute a real problem, or is it a sufficiently minor
defect such that one can live with it in a lab environment? Will
there be any gotchas to be aware of, such as MS struggling to connect
to the test network?
Finally, how does this BladeRF compare to various LimeSDR options? It
seems like LimeSDR has always been the popular choice in the "cheap"
department, whereas for BladeRF I see not one mention anywhere as I
already noted. How do these two options compare? I recall hearing
that while LimeSDR was once very popular, people were also having
problems with it. Is BladeRF now better in terms of stability, or not
really? And if BladeRF really is a better choice than LimeSDR for the
purpose of running an SDR BTS on something cheaper than Ettus hw, then
how did we get into the peculiar situation of having documentation
that covers LimeSDR but not BladeRF?
Please help this SDR-ignorant gal figure out which hardware I should
buy. Whether I cover the cost on my own or take up Harald's offer of
cost reimbursement, either way I need to be sure I buy the right thing...
Oh, one more detail: whichever USB-interfaced SDR I get, I plan on
using a Raspberry Pi 5 to drive it, running stock Raspbian. Does
anyone have any experience with using RPi devices to drive SDRs for
use as BTS? Is RPi5 powerful enough to run all of the computationally
demanding parts, including that fractional resampling? Is stock
Raspbian good enough in terms of sw dependencies?
TIA,
Mychaela
Hello fellow Osmocomers,
I just recently came across and watched Harald's ODC 2018 presentation
about Ericsson RBS 6000. The part that intrigued me: Harald said in
that year that this hardware was available quite inexpensively and
plentifully; he said that a DUG10+RUG pair could be had for around
300 EUR in that year.
My question to the community: what is the current situation 6 y later?
Is there still any above-zero supply of either DUG10+RUG or DUG20+RUS
surplus hardware? If a nonzero supply does exist, what is the typical
price these days?
In that 2018 presentation Harald also mentioned that the successor to
DUG20 was DUS31/DUS41, and that those DUS units (which support GSM,
WCDMA and LTE all in one box) have integrated SIU02 equivalent instead
of native E1 interfaces. Hence question: has anyone in Osmocom cracked
the E1-over-IP protocol spoken by SIU02 and its later incarnations,
allowing Osmocom CNI to drive the GSM part of DUS31 etc, or is such
operation beyond our current community capabilities?
There are rumors going around that T-Mobile USA may be shutting down
some Ericsson 2G equipment (though I still never got any clear answers
as to what equipment it might be, if any), hence I am trying to brush
up on my knowledge of this platform.
M~
Hello, I tried using the osmocom stack with the usrp1 and I
encountered this error :
DMAIN NOTICE Starting the transceiver (Transceiver.cpp:287)
DDEV NOTICE Setting TX gain to 0 dB. (USRPDevice.cpp:265)
DDEV NOTICE Setting RX gain to 20 dB. (USRPDevice.cpp:292)
DDEV NOTICE Setting TX gain to 0 dB. (USRPDevice.cpp:265)
DDEV NOTICE Setting TX gain to 0 dB. (USRPDevice.cpp:265)
DDEV NOTICE Setting TX gain to 0 dB. (USRPDevice.cpp:265)
DMAIN NOTICE Stopping the transceiver (Transceiver.cpp:345)
after that the osmo-trx-usrp1 seems to crash.
I know it is not supported anymore but any possible fix would be appreciated.
here is my system and log files together with a pcap :
System : Debian 12 amd64
using osmocom-nightly repo (the stable repo still gives the same error)
I've raised this some years ago, then had gotten the response that our .ttcn
files should grow to any size, and we should fix the tooling instead or buy a
faster computer.
But I'm still having the annoyance when working with our ttcn that even
changing a tiny constant will trigger a longish recompilation. It looks like it
is dividing a .ttcn into parts, and keeps recompiling *all* of the parts.
(not always all of the parts, but usually it is clumsy about compiling more
than would be logically required from my POV.)
It looks like this:
+ make -j 5
Creating dependency file for HNBGW_Tests_part_6.cc
Creating dependency file for HNBGW_Tests_part_5.cc
Creating dependency file for HNBGW_Tests_part_4.cc
Creating dependency file for HNBGW_Tests_part_3.cc
Creating dependency file for HNBGW_Tests_part_2.cc
Creating dependency file for HNBGW_Tests_part_1.cc
Creating dependency file for HNBGW_Tests.cc
env CCACHE_SLOPPINESS=time_macros ccache g++ -c -DLINUX -DMAKEDEPEND_RUN -DUSE_SCTP -DLKSCTP_MULTIHOMING_ENABLED -DAS_USE_SSL -I/usr/include/titan -fPIC -o HNBGW_Tests.o HNBGW_Tests.cc
env CCACHE_SLOPPINESS=time_macros ccache g++ -c -DLINUX -DMAKEDEPEND_RUN -DUSE_SCTP -DLKSCTP_MULTIHOMING_ENABLED -DAS_USE_SSL -I/usr/include/titan -fPIC -o HNBGW_Tests_part_1.o HNBGW_Tests_part_1.cc
env CCACHE_SLOPPINESS=time_macros ccache g++ -c -DLINUX -DMAKEDEPEND_RUN -DUSE_SCTP -DLKSCTP_MULTIHOMING_ENABLED -DAS_USE_SSL -I/usr/include/titan -fPIC -o HNBGW_Tests_part_2.o HNBGW_Tests_part_2.cc
env CCACHE_SLOPPINESS=time_macros ccache g++ -c -DLINUX -DMAKEDEPEND_RUN -DUSE_SCTP -DLKSCTP_MULTIHOMING_ENABLED -DAS_USE_SSL -I/usr/include/titan -fPIC -o HNBGW_Tests_part_3.o HNBGW_Tests_part_3.cc
env CCACHE_SLOPPINESS=time_macros ccache g++ -c -DLINUX -DMAKEDEPEND_RUN -DUSE_SCTP -DLKSCTP_MULTIHOMING_ENABLED -DAS_USE_SSL -I/usr/include/titan -fPIC -o HNBGW_Tests_part_4.o HNBGW_Tests_part_4.cc
env CCACHE_SLOPPINESS=time_macros ccache g++ -c -DLINUX -DMAKEDEPEND_RUN -DUSE_SCTP -DLKSCTP_MULTIHOMING_ENABLED -DAS_USE_SSL -I/usr/include/titan -fPIC -o HNBGW_Tests_part_5.o HNBGW_Tests_part_5.cc
env CCACHE_SLOPPINESS=time_macros ccache g++ -c -DLINUX -DMAKEDEPEND_RUN -DUSE_SCTP -DLKSCTP_MULTIHOMING_ENABLED -DAS_USE_SSL -I/usr/include/titan -fPIC -o HNBGW_Tests_part_6.o HNBGW_Tests_part_6.cc
env CCACHE_SLOPPINESS=time_macros ccache g++ -shared -o HNBGW_Tests.so HNBGW_Tests.o
env CCACHE_SLOPPINESS=time_macros ccache g++ -shared -o HNBGW_Tests_part_3.so HNBGW_Tests_part_3.o
env CCACHE_SLOPPINESS=time_macros ccache g++ -shared -o HNBGW_Tests_part_4.so HNBGW_Tests_part_4.o
env CCACHE_SLOPPINESS=time_macros ccache g++ -shared -o HNBGW_Tests_part_2.so HNBGW_Tests_part_2.o
env CCACHE_SLOPPINESS=time_macros ccache g++ -shared -o HNBGW_Tests_part_1.so HNBGW_Tests_part_1.o
HNBGW_Tests_part_5.cc: In function ‘OCTETSTRING HNBGW__Tests::f__gen__one__compl__l3(const Compl3Type&, const MobileL3__CommonIE__Types::MobileIdentityLV_template&, const INTEGER&)’:
HNBGW_Tests_part_5.cc:2130:1: warning: control reaches end of non-void function [-Wreturn-type]
2130 | }
| ^
env CCACHE_SLOPPINESS=time_macros ccache g++ -shared -o HNBGW_Tests_part_5.so HNBGW_Tests_part_5.o
env CCACHE_SLOPPINESS=time_macros ccache g++ -shared -o HNBGW_Tests_part_6.so HNBGW_Tests_part_6.o
I want a fast dev cycle, and the ttcn dev cycle is slow: after a tiny edit,
the CPU spools up and the fan goes for a whole while, and I get bored and
irritated. When I'm on a train ttcn compilation drains the battery...
My local workaround was to create a second file, like BSC_Tests_2.ttcn, with
only my new test in it. Then compilation cycles are rapid.
But that requires modifying all sorts of s/private/friend and even only moving
the code is another annoyance. If I want to apply CR, I won't move it back and
forth, so usually I end up with two copies and get confused.
So my local workaround isn't working out very well.
Why am I writing this here? Because I would like to request that we start
subdividing our ttcn into smaller compilation units, not as my local workaround
but permanently in our upstream.
Please?
~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