Hi Ok,let's start with the installation ! setup : Limedsdr mini + ubuntu 18:04 + osmocm cni latest build 1- i used the Ubuntu latest build : - https://download.opensuse.org/repositories/network:/osmocom:/latest/xUbuntu… 2- i just installed all the required Programs using apt-get install command such as osmo-hlr ,osmo,msc etc... 3- i used this script to run the osmocom cni : #!/bin/sh 4- then by running ./osmo-all status i found that all programs work fine without any errors,only for osmo-trx-lms ,i just got this : and for osmo-bts-trx : <0017> control_if.c:911 CTRL at 127.0.0.1 4238 also,by using my phone,i can't find the created network and so the problem is the limesdr mini (osmo-trx-lms) or the osmo-bts-trx . for the confihuration files,i used the default .cfg files for all programs . did i missed any thing ? PS : i just tried the osmocm cni with Raspberry and i got the same problem . Regards. Le lun. 9 déc. 2019 à 21:21, Pau Espin Pedrol &lt;pespin(a)sysmocom.de&gt; a écrit :

Hi Sandi, why do you say the defaults won't work? They should in general. Can you please share what's exactly wrong with default config files? Ahmed: You keep providing the same information with no real detail on what's your setup and what's not working. The log messages you shared seem fine to me. Unless you really investigate yourself a bit what's not working and provide detailed information about it, nobody will be able to support you. Regards, -- - Pau Espin Pedrol &lt;pespin(a)sysmocom.de&gt; 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

HI Thanks for the reply! the problem it's that i can't see the network using my phone,neither on band 1800 or 900 ! osmo-trx-lms[7995]: Sun Dec 8 18:02:05 2019 DTRXCTRL <0001> as you see, for the air interface,the program is sending a 'POWEROFF' command to the limesdrmini ! means that limesdr can't act as a bts correctly!right ? is there any way to dig more into the cause of this behavior ? the only log i can see is from the systemctl ! as i sadi before,i am using all those components for my network : osmo-hlr osmo-msc osmo-mgw osmo-ggsn osmo-sgsn osmo-stp osmo-bsc osmo-hnbgw osmo-bts-trx osmo-trx-lms Thanks. Le mar. 17 déc. 2019 à 15:02, Sandi Suhendro &lt;djks74(a)gmail.com&gt; a écrit : > Hi Pespin, > Im sorry, i might miss things if the default config has been updated? > > Sorry to say in previous email, cause my first experience is not working > with default which is long time ago in some case... When i learning to > build the system. > > At that time might be.. . But thats long time ago. I remember its > though for me to make the system is running for newbie.... > > Once again im so sorry! Hehehe... > > > regards, > Sandi / DUO > > On Tue, Dec 17, 2019, 19:41 Pau Espin Pedrol &lt;pespin(a)sysmocom.de&gt; wrote: > >> Hi Sandi, >> >> why do you say the defaults won't work? They should in general. Can you >> please share what's exactly wrong with default config files? >> >> Ahmed: You keep providing the same information with no real detail on >> what's your setup and what's not working. The log messages you shared >> seem fine to me. Unless you really investigate yourself a bit what's not >> working and provide detailed information about it, nobody will be able >> to support you. >> >> Regards, >> >> -- >> - Pau Espin Pedrol &lt;pespin(a)sysmocom.de&gt; 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 >> >

the problem it's that i can't see the network using my phone,neither on band 1800 or 900 !  osmo-trx-lms[7995]: Sun Dec  8 18:02:05 2019 DTRXCTRL <0001> Transceiver.cpp:773 [tid=140437098583808][chan=0] command is 'POWEROFF'  osmo-trx-lms[7995]: Sun Dec  8 18:02:05 2019 DTRXCTRL <0001> Transceiver.cpp:918 [tid=140437098583808][chan=0] response is 'RSP POWEROFF 0' as you see, for the air interface,the program is sending  a  'POWEROFF' command to the limesdrmini ! means that limesdr can't act as a bts correctly!right ?

is there any way to dig more into the cause of this behavior ? the only log i can see is from the systemctl !

HI all, Just found that theproblem is with the osmo-bts-trx : journalctl -f -u osmo-bts-trx.service <0010> telnet_interface.c:104 Available via telnet 127.0.0.1 4241 the problem is with "Signalling link down" and " osmo-bts-trx[26145]: <0001> bts.c:285 Shutting down BTS 0, Reason Abis close" i tried to verif the unit-id for both osmo-btstrx and osmo-bsc and found that it's the same! still can't figure why the abis close. for the config files : osmo-bts-trx.cfg: https://pastebin.com/wgBxXN6G osmo-bsc.cfg : https://pastebin.com/jh81aKrM Setup : osmocom CNI latest build for ubuntu 18.04 + limesdr mini Thanks! Le mar. 17 déc. 2019 à 22:03, Pau Espin Pedrol &lt;pespin(a)sysmocom.de&gt; a écrit :

It's working. now i can see the network after changing the remote ip from 192.168.122.1 to localhost ! just missed to change it as you said! i will try to provide a working config for other users ASAP ! thanks! Le mar. 24 déc. 2019 à 19:03, Sandi Suhendro &lt;djks74(a)gmail.com&gt; a écrit : > Signaling link down appear because OML not connecting, > have you try use oml remote-ip 127.0.0.1 ? > > You running on the same computer for the CNI right? > > On Wed, Dec 25, 2019 at 12:33 AM ah med &lt;grgrehreher(a)gmail.com&gt; wrote: > >> HI all, >> >> Just found that theproblem is with the osmo-bts-trx : >> >> journalctl -f -u osmo-bts-trx.service >> >> <0010> telnet_interface.c:104 Available via telnet 127.0.0.1 4241 >>> osmo-bts-trx[26145]: <0012> input/ipaccess.c:897 enabling ipaccess BTS >>> mode, OML connecting to 192.168.122.1:3002 >>> osmo-bts-trx[26145]: <000b> trx_if.c:1155 phy0.0: Open transceiver >>> osmo-bts-trx[26145]: <000b> trx_if.c:173 phy0.0: No satisfactory >>> response from transceiver(CMD POWEROFF) >>> osmo-bts-trx[26145]: <0009> pcu_sock.c:929 PCU socket connected to >>> external PCU >>> osmo-bts-trx[26145]: <0001> oml.c:91 OC=GPRS-CELL INST=(00,ff,ff): >>> Sending PCU version report to BSC: 0.7.0 >>> osmo-bts-trx[26145]: <0001> oml.c:91 OC=GPRS-CELL INST=(00,ff,ff): >>> Sending PCU version report to BSC: 0.7.0 >>> osmo-bts-trx[26145]: <0001> oml.c:91 OC=GPRS-CELL INST=(00,ff,ff): >>> Sending PCU version report to BSC: 0.7.0 >>> osmo-bts-trx[26145]: <0001> oml.c:91 OC=GPRS-CELL INST=(00,ff,ff): >>> Sending PCU version report to BSC: 0.7.0 >>> osmo-bts-trx[26145]: <0001> oml.c:91 OC=GPRS-CELL INST=(00,ff,ff): >>> Sending PCU version report to BSC: 0.7.0 >>> osmo-bts-trx[26145]: <0001> oml.c:91 OC=GPRS-CELL INST=(00,ff,ff): >>> Sending PCU version report to BSC: 0.7.0 >>> osmo-bts-trx[26145]: <000d> abis.c:144 Signalling link down >>> osmo-bts-trx[26145]: <0001> bts.c:285 Shutting down BTS 0, Reason Abis >>> close >>> osmo-bts-trx[26145]: Shutdown timer expired >>> osmo-bts-trx[26145]: ((*)) >>> osmo-bts-trx[26145]: | >>> osmo-bts-trx[26145]: / \ OsmoBTS >>> systemd[1]: osmo-bts-trx.service: Main process exited, code=exited, >>> status=42/n/a >>> systemd[1]: osmo-bts-trx.service: Failed with result 'exit-code'. >>> systemd[1]: osmo-bts-trx.service: Service hold-off time over, >>> scheduling restart. >>> systemd[1]: osmo-bts-trx.service: Scheduled restart job, restart >>> counter is at 1. >>> >> >> the problem is with "Signalling link down" and " osmo-bts-trx[26145]: >> <0001> bts.c:285 Shutting down BTS 0, Reason Abis close" >> >> i tried to verif the unit-id for both osmo-btstrx and osmo-bsc and found >> that it's the same! >> still can't figure why the abis close. >> >> for the config files : >> >> osmo-bts-trx.cfg: >> https://pastebin.com/wgBxXN6G >> >> osmo-bsc.cfg : >> https://pastebin.com/jh81aKrM >> >> Setup : >> osmocom CNI latest build for ubuntu 18.04 + limesdr mini >> >> Thanks! >> >> >> >> Le mar. 17 déc. 2019 à 22:03, Pau Espin Pedrol &lt;pespin(a)sysmocom.de&gt; a >> écrit : >> >>> >>> >>> On 12/17/19 8:55 PM, ah med wrote: >>> > the problem it's that i can't see the network using my phone,neither >>> on >>> > band 1800 or 900 ! >>> > >>> > osmo-trx-lms[7995]: Sun Dec 8 18:02:05 2019 DTRXCTRL <0001> >>> > Transceiver.cpp:773 [tid=140437098583808][chan=0] command is >>> 'POWEROFF' >>> > osmo-trx-lms[7995]: Sun Dec 8 18:02:05 2019 DTRXCTRL <0001> >>> > Transceiver.cpp:918 [tid=140437098583808][chan=0] response is 'RSP >>> > POWEROFF 0' >>> > >>> > >>> > as you see, for the air interface,the program is sending a >>> 'POWEROFF' >>> > command to the limesdrmini ! means that limesdr can't act as a bts >>> > correctly!right ? >>> >>> As I said, it's expected that the BTS upon connecting to osmo-trx first >>> sends a POWEROFF command to make sure the TRX is stopped, in a "known" >>> state. Once there, it configures it and finally turns it on with >>> "POWERON". >>> >>> > is there any way to dig more into the cause of this behavior ? the >>> only >>> > log i can see is from the systemctl ! >>> >>> Please read the wiki and the user manuals to learn the basics on how to >>> operate the osmocom software. Specially how to access the VTY and >>> configure it as well as get logging information. >>> https://ftp.osmocom.org/docs/latest/ >>> >>> -- >>> - Pau Espin Pedrol &lt;pespin(a)sysmocom.de&gt; 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 >>> >> > > -- > Best Regards, > Sandi > >