This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
ah med grgrehreher at gmail.comHI 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 <pespin at sysmocom.de> 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 <pespin at sysmocom.de> 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20191224/5b869f23/attachment.htm>