From domi at tomcsanyi.net  Thu Jul  1 19:22:22 2021
From: domi at tomcsanyi.net (Tomcsanyi, Domonkos)
Date: Thu, 1 Jul 2021 21:22:22 +0200
Subject: People.osmocom.org seems to be down
Message-ID: <8239C154-0473-43A6-96F5-507A5704263C@tomcsanyi.net>

Hello All,

Sorry about creating noise on this list, but I could not find the correct place to raise this: people.osmocom.org seems to be down. I have checked it from multiple internet connections and also with DownDetector and the result was always the same.
I noticed this when I tried to watch a recording of the OsmoDevCall about SS7 and SIGTRAN - the link to the video timed out.

Apologies again for asking for a sysadmin task on this list. In case there is anything I could help with or there is a mirror of these videos I don?t know of (yet) feel free to tell me about it.

Thank you!

Domi



From laforge at osmocom.org  Thu Jul  1 19:55:29 2021
From: laforge at osmocom.org (Harald Welte)
Date: Thu, 1 Jul 2021 21:55:29 +0200
Subject: People.osmocom.org seems to be down
In-Reply-To: <8239C154-0473-43A6-96F5-507A5704263C@tomcsanyi.net>
References: <8239C154-0473-43A6-96F5-507A5704263C@tomcsanyi.net>
Message-ID: <YN4dsc75obN5rdrR@nataraja>

Hi Domi,

thanks for Reaching out.  We do have a 'sysadmin' category in our redmine
where you can report such issues without involving everyone on the mailing
list here.  I'll investigate.

Regards,
	Harald

On Thu, Jul 01, 2021 at 09:22:22PM +0200, Tomcsanyi, Domonkos wrote:
> Hello All,
> 
> Sorry about creating noise on this list, but I could not find the correct place to raise this: people.osmocom.org seems to be down. I have checked it from multiple internet connections and also with DownDetector and the result was always the same.
> I noticed this when I tried to watch a recording of the OsmoDevCall about SS7 and SIGTRAN - the link to the video timed out.
> 
> Apologies again for asking for a sysadmin task on this list. In case there is anything I could help with or there is a mirror of these videos I don?t know of (yet) feel free to tell me about it.
> 
> Thank you!
> 
> Domi
> 

-- 
- Harald Welte <laforge at osmocom.org>            http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)


From keith at rhizomatica.org  Fri Jul  2 00:32:09 2021
From: keith at rhizomatica.org (Keith)
Date: Thu, 1 Jul 2021 19:32:09 -0500
Subject: inter-BSC handover
Message-ID: <8307bc1a-e868-db7d-d8fc-542ef73cc739@rhizomatica.org>

Hi all.

I'm testing to see if inter-BSC handover will work between RBS and
osmo-bts, given that support for handover from an E1 to RTP call is not
yet supported.

Among all kinds of other things going on, I'm not finding it easy to
understand how to configure everything for inter bsc handover.

I know there are two videos (at least) from Neels at OsmoDevCon, on the
subject of handover and then inter-MSC handover.

I have one DUG/RUS configurarion with the e1d, bsc/msc/mgw/hlr running
on the associated PC and one remote SysmoBTS, which is running osmo-bsc
and it's associated MGW locally. All that is fine, I can call between
the two BTSs successfully.

I'm guessing I should add the neighbours manually in each bsc but I'm
not sure what to configure in the MSC.

Maybe I'll figure it out this evening, but I thought it best to also
write most given the time zones and most of you guys will see this
before I get back to work tomorrow.

Thanks!

k




From nhofmeyr at sysmocom.de  Fri Jul  2 16:50:47 2021
From: nhofmeyr at sysmocom.de (Neels Hofmeyr)
Date: Fri, 2 Jul 2021 18:50:47 +0200
Subject: inter-BSC handover
In-Reply-To: <8307bc1a-e868-db7d-d8fc-542ef73cc739@rhizomatica.org>
References: <8307bc1a-e868-db7d-d8fc-542ef73cc739@rhizomatica.org>
Message-ID: <20210702165047.GA30924@my.box>




On Thu, Jul 01, 2021 at 07:32:09PM -0500, Keith wrote:
> I'm not finding it easy to understand how to configure everything for inter
> bsc handover.

Hm, it appears we are lacking documentation on inter-BSC and inter-MSC handover
in the osmo-msc manual.

In each BSC, you add a mapping of ARFCN-BSIC to Cell Identifiers.
(In osmo-bsc.cfg, remote-BSS neighbors have to be full Cell Id + ARFCN-BSIC.)
I recommend to use CGI identifiers only.

In the MSC, you add a mapping of Cell Identifiers to Point-Codes.

In osmo-bsc.cfg:

 # this is the ARFCN+BSIC of the remote-BSS cell,
 # and the LAC+CI of the remote-BSS cell.
 neighbor cgi 262 42 23 42 arfcn 123 bsic 4

In osmo-msc.cfg:

 neighbor a cgi 262 42 23 42 ran-pc 0.24.1

 serving BSC --Cell-Id--> MSC --Point-Code--> target BSC serving given cgi, at given PC

The BSC gets reports about a specific ARFCN and BSIC showing up strongly.
It needs to translate that to a Cell Identifier.
Only the Cell Identifier is sent to MSC in Handover Required.
Then the MSC needs to know which of its BSCs serves that Cell Id.
That's why you add to osmo-msc.cfg a mapping of cgi to point-code.
Hence MSC will send the Handover Request to the BSC with that point-code
matching the cgi.

And to support handover back to the first BSC, do the same thing vice versa.
So in a scenario with two BSCs with one BTS each, each BSC has one entry for the other BSC's BTS,
and the MSC has two entries, one for each BSC's BTS.

HTH
~N


From keith at rhizomatica.org  Fri Jul  2 20:21:28 2021
From: keith at rhizomatica.org (Keith)
Date: Fri, 2 Jul 2021 15:21:28 -0500
Subject: inter-BSC handover
In-Reply-To: <20210702165047.GA30924@my.box>
References: <8307bc1a-e868-db7d-d8fc-542ef73cc739@rhizomatica.org>
 <20210702165047.GA30924@my.box>
Message-ID: <5b1b26de-dfcc-ec39-4053-07772c5befd7@rhizomatica.org>


On 02/07/2021 11:50, Neels Hofmeyr wrote:
>
>
> Hm, it appears we are lacking documentation on inter-BSC and inter-MSC handover
> in the osmo-msc manual.
>
> [...]
> HTH
> ~N

Many thanks for that explanation, Neels!

I've applied that configuration and I'm testing it out now, although not
having so much success as yet. I am not seeing the neighbours in the vty
log.

One weird thing, which I will try to diagnose further, is some really
strange meas reports on the meas-feed from osmo-bsc running the the bts.
i get reports with 100 or more neighbours. and the RX levels are not
what the vty log says Could that be something to do with the arm arch?





From laforge at osmocom.org  Sat Jul  3 09:05:00 2021
From: laforge at osmocom.org (Harald Welte)
Date: Sat, 3 Jul 2021 11:05:00 +0200
Subject: inter-BSC handover
In-Reply-To: <5b1b26de-dfcc-ec39-4053-07772c5befd7@rhizomatica.org>
References: <8307bc1a-e868-db7d-d8fc-542ef73cc739@rhizomatica.org>
 <20210702165047.GA30924@my.box>
 <5b1b26de-dfcc-ec39-4053-07772c5befd7@rhizomatica.org>
Message-ID: <YOAoPMGwtRhWnac+@nataraja>

On Fri, Jul 02, 2021 at 03:21:28PM -0500, Keith wrote:
 
> One weird thing, which I will try to diagnose further, is some really
> strange meas reports on the meas-feed from osmo-bsc running the the bts.
> i get reports with 100 or more neighbours. and the RX levels are not
> what the vty log says Could that be something to do with the arm arch?

meas_feed doesn't use portable data structures, AFAIR.  You ahve to run
both sender and recipient on the same architecture / ABI.

-- 
- Harald Welte <laforge at osmocom.org>            http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)


From nhofmeyr at sysmocom.de  Mon Jul  5 10:47:15 2021
From: nhofmeyr at sysmocom.de (Neels Hofmeyr)
Date: Mon, 5 Jul 2021 12:47:15 +0200
Subject: inter-BSC handover
In-Reply-To: <5b1b26de-dfcc-ec39-4053-07772c5befd7@rhizomatica.org>
References: <8307bc1a-e868-db7d-d8fc-542ef73cc739@rhizomatica.org>
 <20210702165047.GA30924@my.box>
 <5b1b26de-dfcc-ec39-4053-07772c5befd7@rhizomatica.org>
Message-ID: <20210705104715.GA2239@my.box>

Feel free to paste config files... bsc and msc

~N


From keith at rhizomatica.org  Mon Jul  5 23:32:27 2021
From: keith at rhizomatica.org (Keith)
Date: Mon, 5 Jul 2021 18:32:27 -0500
Subject: inter-BSC handover
In-Reply-To: <20210705104715.GA2239@my.box>
References: <8307bc1a-e868-db7d-d8fc-542ef73cc739@rhizomatica.org>
 <20210702165047.GA30924@my.box>
 <5b1b26de-dfcc-ec39-4053-07772c5befd7@rhizomatica.org>
 <20210705104715.GA2239@my.box>
Message-ID: <656c0191-b6f8-d385-bec5-d9076ecb42ba@rhizomatica.org>


On 05/07/2021 05:47, Neels Hofmeyr wrote:
> Feel free to paste config files... bsc and msc
>
> ~N

Thanks Neels, I will test it again first.. I swap the lacs to force LURs
on each MSC restart and I think that might have got in the way in this
case... Off site now, but I will set up two BSC/BTS locally and check it
again.

Posting here again really to ask, should one also use:

? neighbor-list mode manual
? neighbor-list add arfcn 246

or just the :

? neighbor cgi 334 07 274 102 arfcn 246 bsic 62




From nhofmeyr at sysmocom.de  Thu Jul  8 05:25:55 2021
From: nhofmeyr at sysmocom.de (Neels Hofmeyr)
Date: Thu, 8 Jul 2021 07:25:55 +0200
Subject: inter-BSC handover
In-Reply-To: <656c0191-b6f8-d385-bec5-d9076ecb42ba@rhizomatica.org>
References: <8307bc1a-e868-db7d-d8fc-542ef73cc739@rhizomatica.org>
 <20210702165047.GA30924@my.box>
 <5b1b26de-dfcc-ec39-4053-07772c5befd7@rhizomatica.org>
 <20210705104715.GA2239@my.box>
 <656c0191-b6f8-d385-bec5-d9076ecb42ba@rhizomatica.org>
Message-ID: <20210708052555.GB4611@my.box>

On Mon, Jul 05, 2021 at 06:32:27PM -0500, Keith wrote:
> Posting here again really to ask, should one also use:
> 
> ? neighbor-list mode manual
> ? neighbor-list add arfcn 246

Those are legacy config items, or may be used in special cases.
You should normally omit all neighbor-list commands completely and only
configure neighbors as:

   # remote-BSS always of the form:
 ? neighbor cgi 334 07 274 102 arfcn 246 bsic 62

   # local-BSS may come in different sizes:
 ? neighbor bts 23
 ? neighbor cgi 334 07 274 102
 ? neighbor cgi 334 07 274 102 arfcn 246 bsic 62

Note that it has to go both ways:

  bts 23
   neighbor bts 42
  bts 42
   neighbor bts 23

meaning it is not implicitly reciprocal, each cell's neighbor config starts
with a clean slate, no matter what the other cells configured.


From laforge at osmocom.org  Fri Jul  9 14:52:57 2021
From: laforge at osmocom.org (Harald Welte)
Date: Fri, 9 Jul 2021 16:52:57 +0200
Subject: Announcement of "OsmoDevCall" on July 9, 2021
Message-ID: <YOhiyVs/8ocZsJkj@nataraja>

Dear Osmocom community,

It's my pleasure to announce the next OsmoDevCall at

	July 9, 2021 at 20:00 CEST
at
	https://meeting4.franken.de/b/har-xbc-bsx-wvs

This meeting will have the following schedule:

20:00 meet + greet
20:15 hands-on tutorial by miaoski: Setting up open5gs
21:00 USSE: unstructured supplementary social event [*]
22:00 close of call

Attendance is free of charge and open to anyone with an interest
in Osmocom.

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 on Friday.

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 at osmocom.org>            http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)


From andreas at eversberg.eu  Sat Jul 10 15:03:43 2021
From: andreas at eversberg.eu (Andreas Eversberg)
Date: Sat, 10 Jul 2021 17:03:43 +0200
Subject: Nanobts will not correctly attach to osmo-bsc.
Message-ID: <24d8f22c-ffb3-6730-d105-ad0a575294e5@eversberg.eu>

Hi,

after long time (may years), I do a "compileathlon"/"configathlon" with 
a osmo-bsc/osmo-stp/osmo-msc/osmo-sip-connector setup. If I interpret 
this the shown osmo-bsc output correctly, it attaches successfully 
through the osmo-stp with the osmo-msc. Then I start an ipaccess 
nanobts. It connects via OML, comes to a point where provisioning stops 
or times out.

I use a fresh debian installation with am64 and todays master branches 
from git.osmocom.org repository.

A pcap file of the OML connection is attached to this message. (The 
order of packets in the trace is messed up, due to my switch's port 
mirroring.) Also attached is the osmo-bsc.cfg.

Any idea?


Thank you,

Andreas


<0004> fsm.c:461 NM_BTS_SM_OP[0x558f2b1d17e0]{DISABLED_NOTINSTALLED}: 
Allocated
<0004> fsm.c:461 NM_BTS_OP[0x558f2b1d5120]{DISABLED_NOTINSTALLED}: Allocated
<0004> fsm.c:461 NM_GPRS_CELL_OP[0x558f2b1d5250]{DISABLED_NOTINSTALLED}: 
Allocated
<0004> fsm.c:461 NM_RCARRIER_OP[0x558f2b1da770]{DISABLED_NOTINSTALLED}: 
Allocated
<0004> fsm.c:461 NM_BB_TRANSC_OP[0x558f2b1da940]{DISABLED_NOTINSTALLED}: 
Allocated
<0004> fsm.c:461 NM_CHAN_OP[0x558f2b1dac40]{DISABLED_NOTINSTALLED}: 
Allocated
<0004> fsm.c:461 NM_CHAN_OP[0x558f2b1db340]{DISABLED_NOTINSTALLED}: 
Allocated
<0004> fsm.c:461 NM_CHAN_OP[0x558f2b1dbb40]{DISABLED_NOTINSTALLED}: 
Allocated
<0004> fsm.c:461 NM_CHAN_OP[0x558f2b1dc340]{DISABLED_NOTINSTALLED}: 
Allocated
<0004> fsm.c:461 NM_CHAN_OP[0x558f2b1dcb40]{DISABLED_NOTINSTALLED}: 
Allocated
<0004> fsm.c:461 NM_CHAN_OP[0x558f2b1dd3d0]{DISABLED_NOTINSTALLED}: 
Allocated
<0004> fsm.c:461 NM_CHAN_OP[0x558f2b1ddc60]{DISABLED_NOTINSTALLED}: 
Allocated
<0004> fsm.c:461 NM_CHAN_OP[0x558f2b1de4f0]{DISABLED_NOTINSTALLED}: 
Allocated
<0004> fsm.c:461 NM_GPRS_NSE_OP[0x558f2b1debd0]{DISABLED_NOTINSTALLED}: 
Allocated
<0004> fsm.c:461 NM_GPRS_NSVC_OP[0x558f2b1ded90]{DISABLED_NOTINSTALLED}: 
Allocated
<0004> fsm.c:461 NM_GPRS_NSVC_OP[0x558f2b1defc0]{DISABLED_NOTINSTALLED}: 
Allocated
<0015> telnet_interface.c:104 Available via telnet 127.0.0.1 4242
<0017> input/ipaccess.c:1035 enabling ipaccess BSC mode on 0.0.0.0 with 
OML 3002 and RSL 3003 TCP ports
<001c> control_if.c:922 CTRL at 127.0.0.1 4249
<0025> mgcp_client.c:782 MGCP client: using endpoint domain '@mgw'
<0007> osmo_bsc_sigtran.c:548 Initializing SCCP connection for A/m3ua on 
cs7 instance 0
<0022> sccp_user.c:548 A-0-m3ua: Using SS7 instance 0, pc:1.23.3
<0022> sccp_user.c:555 A-0-m3ua: Creating AS instance
<0022> sccp_user.c:566 A-0-m3ua: Using AS instance as-clnt-A-0-m3ua
<0022> sccp_user.c:571 A-0-m3ua: Creating default route
<0022> sccp_user.c:605 A-0-m3ua: ASP my-asp for m3ua is not associated 
with any AS, using it
<0022> sccp_user.c:638 A-0-m3ua: Using ASP instance my-asp
<0021> osmo_ss7.c:456 0: Creating SCCP instance
<0007> osmo_bsc_sigtran.c:600 A-0-m3ua msc-0: local (BSC) SCCP address: 
RI=SSN_PC,PC=1.23.3,SSN=BSSAP
<0007> osmo_bsc_sigtran.c:602 A-0-m3ua msc-0: remote (MSC) SCCP address: 
RI=SSN_PC,PC=0.23.1,SSN=BSSAP
<0007> osmo_bsc_sigtran.c:607 A-0-m3ua msc-0: binding SCCP user
<0021> m3ua.c:507 XUA_AS(as-clnt-A-0-m3ua)[0x558f2b1e2c10]{AS_DOWN}: 
Event AS-TRANSFER.req not permitted
<0024> m3ua.c:622 0: asp-my-asp: Received NOTIFY Type State Change:AS 
Inactive ()
<0021> xua_default_lm_fsm.c:361 
xua_default_lm(my-asp)[0x558f2b1e2f40]{ACTIVE}: Ignoring primitive 
M-ASP_ACTIVE.confirm
<0024> m3ua.c:622 0: asp-my-asp: Received NOTIFY Type State Change:AS 
Active ()
<0007> osmo_bsc_bssap.c:81 RESET ACK from MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP
<0014> bssmap_reset.c:83 bssmap_reset(msc-0)[0x558f2b1e3d50]{CONN}: link up
<0007> a_reset.c:44 (msc0) BSSMAP assocation is up
<0017> input/ipa.c:284 0.0.0.0:3002 accept()ed new link from 10.0.0.96:48280
<0004> abis_nm.c:258 OC=SITE-MANAGER(00) INST=(ff,ff,ff): STATE CHG: 
OP_STATE=Disabled AVAIL=Not installed(07)
<0004> bts_ipaccess_nanobts.c:156 
NM_BTS_SM_OP(bts_sm)[0x558f2b1d17e0]{DISABLED_NOTINSTALLED}: Received 
Event STATE_CHG_REP
<0004> abis_nm.c:258 OC=BTS(01) INST=(00,ff,ff): STATE CHG: 
OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked
<0004> bts_ipaccess_nanobts.c:160 
NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_NOTINSTALLED}: Received Event 
STATE_CHG_REP
<0004> abis_nm.c:258 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): STATE 
CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked
<0004> bts_ipaccess_nanobts.c:164 
NM_BB_TRANSC_OP(bts0-trx0)[0x558f2b1da940]{DISABLED_NOTINSTALLED}: 
Received Event STATE_CHG_REP
<0004> abis_nm.c:258 OC=CHANNEL(03) INST=(00,00,00): STATE CHG: 
OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked
<0004> bts_ipaccess_nanobts.c:169 
NM_CHAN_OP(bts0-trx0-ts0)[0x558f2b1dac40]{DISABLED_NOTINSTALLED}: 
Received Event STATE_CHG_REP
<0004> abis_nm.c:258 OC=CHANNEL(03) INST=(00,00,01): STATE CHG: 
OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked
<0004> bts_ipaccess_nanobts.c:169 
NM_CHAN_OP(bts0-trx0-ts1)[0x558f2b1db340]{DISABLED_NOTINSTALLED}: 
Received Event STATE_CHG_REP
<0004> abis_nm.c:258 OC=CHANNEL(03) INST=(00,00,02): STATE CHG: 
OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked
<0004> bts_ipaccess_nanobts.c:169 
NM_CHAN_OP(bts0-trx0-ts2)[0x558f2b1dbb40]{DISABLED_NOTINSTALLED}: 
Received Event STATE_CHG_REP
<0004> abis_nm.c:258 OC=CHANNEL(03) INST=(00,00,03): STATE CHG: 
OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked
<0004> bts_ipaccess_nanobts.c:169 
NM_CHAN_OP(bts0-trx0-ts3)[0x558f2b1dc340]{DISABLED_NOTINSTALLED}: 
Received Event STATE_CHG_REP
<0004> abis_nm.c:258 OC=CHANNEL(03) INST=(00,00,04): STATE CHG: 
OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked
<0004> bts_ipaccess_nanobts.c:169 
NM_CHAN_OP(bts0-trx0-ts4)[0x558f2b1dcb40]{DISABLED_NOTINSTALLED}: 
Received Event STATE_CHG_REP
<0004> abis_nm.c:258 OC=CHANNEL(03) INST=(00,00,05): STATE CHG: 
OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked
<0004> bts_ipaccess_nanobts.c:169 
NM_CHAN_OP(bts0-trx0-ts5)[0x558f2b1dd3d0]{DISABLED_NOTINSTALLED}: 
Received Event STATE_CHG_REP
<0004> abis_nm.c:258 OC=CHANNEL(03) INST=(00,00,06): STATE CHG: 
OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked
<0004> bts_ipaccess_nanobts.c:169 
NM_CHAN_OP(bts0-trx0-ts6)[0x558f2b1ddc60]{DISABLED_NOTINSTALLED}: 
Received Event STATE_CHG_REP
<0004> abis_nm.c:258 OC=CHANNEL(03) INST=(00,00,07): STATE CHG: 
OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked
<0004> bts_ipaccess_nanobts.c:169 
NM_CHAN_OP(bts0-trx0-ts7)[0x558f2b1de4f0]{DISABLED_NOTINSTALLED}: 
Received Event STATE_CHG_REP
<0004> abis_nm.c:258 OC=RADIO-CARRIER(02) INST=(00,00,ff): STATE CHG: 
OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked
<0004> bts_ipaccess_nanobts.c:173 
NM_RCARRIER_OP(bts0-trx0)[0x558f2b1da770]{DISABLED_NOTINSTALLED}: 
Received Event STATE_CHG_REP
<0004> abis_nm.c:258 OC=GPRS-NSE(f0) INST=(00,ff,ff): STATE CHG: 
OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked
<0004> bts_ipaccess_nanobts.c:177 
NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_NOTINSTALLED}: Received 
Event STATE_CHG_REP
<0004> abis_nm.c:258 OC=GPRS-CELL(f1) INST=(00,00,ff): STATE CHG: 
OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked
<0004> bts_ipaccess_nanobts.c:181 
NM_GPRS_CELL_OP(gprs-cell0)[0x558f2b1d5250]{DISABLED_NOTINSTALLED}: 
Received Event STATE_CHG_REP
<0004> abis_nm.c:258 OC=GPRS-NSVC(f2) INST=(00,00,ff): STATE CHG: 
OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked
<0004> bts_ipaccess_nanobts.c:188 
NM_GPRS_NSVC_OP(nsvc0)[0x558f2b1ded90]{DISABLED_NOTINSTALLED}: Received 
Event STATE_CHG_REP
<0004> abis_nm.c:258 OC=GPRS-NSVC(f2) INST=(00,01,ff): STATE CHG: 
OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked
<0004> abis_nm.c:724 OC=SITE-MANAGER(00) INST=(ff,ff,ff): Software 
Activate Request, ACKing and Activating
<0004> abis_nm.c:743 OC=SITE-MANAGER(00) INST=(ff,ff,ff): Found SW 
config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 09 76 32 36 37 62 35 
64 30 00
<0004> abis_nm.c:755 OC=SITE-MANAGER(00) INST=(ff,ff,ff): Selected sw 
description 0 of 1
<0004> abis_nm.c:258 OC=SITE-MANAGER(00) INST=(ff,ff,ff): STATE CHG: 
OP_STATE=Enabled AVAIL=OK(ff)
<0004> bts_ipaccess_nanobts.c:156 
NM_BTS_SM_OP(bts_sm)[0x558f2b1d17e0]{DISABLED_NOTINSTALLED}: Received 
Event STATE_CHG_REP
<0004> abis_nm.c:2186 OC=SITE-MANAGER(00) INST=(ff,ff,ff): Sending OPSTART
<0004> nm_bts_sm_fsm.c:83 
NM_BTS_SM_OP(bts_sm)[0x558f2b1d17e0]{DISABLED_NOTINSTALLED}: state_chg 
to ENABLED
<0004> abis_nm.c:478 OC=SITE-MANAGER(00) INST=(ff,ff,ff): Software 
Activated Report
<0004> bts_ipaccess_nanobts.c:211 
NM_BTS_SM_OP(bts_sm)[0x558f2b1d17e0]{ENABLED}: Received Event SW_ACT_REP
<0004> bts_ipaccess_nanobts.c:211 
NM_BTS_SM_OP(bts_sm)[0x558f2b1d17e0]{ENABLED}: Event SW_ACT_REP not 
permitted
<0004> abis_nm.c:724 OC=BTS(01) INST=(00,ff,ff): Software Activate 
Request, ACKing and Activating
<0004> abis_nm.c:743 OC=BTS(01) INST=(00,ff,ff): Found SW config: 42 12 
00 08 31 32 30 61 30 30 32 00 13 00 09 76 32 36 37 62 35 64 30 00
<0004> abis_nm.c:755 OC=BTS(01) INST=(00,ff,ff): Selected sw description 
0 of 1
<0004> abis_nm.c:724 OC=GPRS-NSE(f0) INST=(00,ff,ff): Software Activate 
Request, ACKing and Activating
<0004> abis_nm.c:743 OC=GPRS-NSE(f0) INST=(00,ff,ff): Found SW config: 
42 12 00 08 31 32 30 61 30 30 32 00 13 00 09 76 32 36 37 62 35 64 30 00
<0004> abis_nm.c:755 OC=GPRS-NSE(f0) INST=(00,ff,ff): Selected sw 
description 0 of 1
<0004> abis_nm.c:839 OC=SITE-MANAGER(00) INST=(ff,ff,ff): Opstart ACK
<0004> bts_ipaccess_nanobts.c:271 
NM_BTS_SM_OP(bts_sm)[0x558f2b1d17e0]{ENABLED}: Received Event OPSTART_ACK
<0004> abis_nm.c:258 OC=BTS(01) INST=(00,ff,ff): STATE CHG: 
OP_STATE=Disabled AVAIL=Dependency(05)
<0004> bts_ipaccess_nanobts.c:160 
NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_NOTINSTALLED}: Received Event 
STATE_CHG_REP
<0004> nm_bts_fsm.c:77 
NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_NOTINSTALLED}: state_chg to 
DISABLED_DEPENDENCY
<0004> nm_bts_fsm.c:153 
NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_DEPENDENCY}: state_chg to 
DISABLED_OFFLINE
<0004> abis_nm.c:1835 OC=BTS(01) INST=(00,ff,ff): Tx Get Attributes 
(Request)
<0004> abis_nm.c:478 OC=BTS(01) INST=(00,ff,ff): Software Activated Report
<0004> bts_ipaccess_nanobts.c:214 
NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_OFFLINE}: Received Event SW_ACT_REP
<0004> bts_ipaccess_nanobts.c:214 
NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_OFFLINE}: Event SW_ACT_REP not 
permitted
<0004> abis_nm.c:724 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): 
Software Activate Request, ACKing and Activating
<0004> abis_nm.c:743 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): Found 
SW config: 42 12 00 08 31 32 30 61 30 30 31 00 13 00 09 76 32 36 37 62 
35 64 30 00 42 12 00 08 31 32 30 61 30 30 32 00 13 00 09 76 32 36 37 62 
35 64 30 00
<0004> abis_nm.c:755 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): 
Selected sw description 0 of 2
<0004> abis_nm.c:724 OC=RADIO-CARRIER(02) INST=(00,00,ff): Software 
Activate Request, ACKing and Activating
<0004> abis_nm.c:743 OC=RADIO-CARRIER(02) INST=(00,00,ff): Found SW 
config: 42 12 00 08 31 32 30 61 30 30 31 00 13 00 09 76 32 36 37 62 35 
64 30 00 42 12 00 08 31 32 30 61 30 30 32 00 13 00 09 76 32 36 37 62 35 
64 30 00
<0004> abis_nm.c:755 OC=RADIO-CARRIER(02) INST=(00,00,ff): Selected sw 
description 0 of 2
<0004> abis_nm.c:258 OC=GPRS-NSE(f0) INST=(00,ff,ff): STATE CHG: 
OP_STATE=Disabled AVAIL=Dependency(05)
<0004> bts_ipaccess_nanobts.c:177 
NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_NOTINSTALLED}: Received 
Event STATE_CHG_REP
<0004> nm_gprs_nse_fsm.c:76 
NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_NOTINSTALLED}: state_chg 
to DISABLED_DEPENDENCY
<0004> nm_gprs_nse_fsm.c:131 
NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_DEPENDENCY}: state_chg to 
DISABLED_OFFLINE
<0004> abis_nm.c:478 OC=GPRS-NSE(f0) INST=(00,ff,ff): Software Activated 
Report
<0004> bts_ipaccess_nanobts.c:232 
NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_OFFLINE}: Received Event 
SW_ACT_REP
<0004> bts_ipaccess_nanobts.c:232 
NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_OFFLINE}: Event SW_ACT_REP 
not permitted
<0004> abis_nm.c:724 OC=GPRS-CELL(f1) INST=(00,00,ff): Software Activate 
Request, ACKing and Activating
<0004> abis_nm.c:743 OC=GPRS-CELL(f1) INST=(00,00,ff): Found SW config: 
42 12 00 08 31 32 30 61 30 30 32 00 13 00 09 76 32 36 37 62 35 64 30 00
<0004> abis_nm.c:755 OC=GPRS-CELL(f1) INST=(00,00,ff): Selected sw 
description 0 of 1
<0004> abis_nm.c:724 OC=GPRS-NSVC(f2) INST=(00,00,ff): Software Activate 
Request, ACKing and Activating
<0004> abis_nm.c:743 OC=GPRS-NSVC(f2) INST=(00,00,ff): Found SW config: 
42 12 00 08 31 32 30 61 30 30 32 00 13 00 09 76 32 36 37 62 35 64 30 00
<0004> abis_nm.c:755 OC=GPRS-NSVC(f2) INST=(00,00,ff): Selected sw 
description 0 of 1
<0004> abis_nm.c:724 OC=GPRS-NSVC(f2) INST=(00,01,ff): Software Activate 
Request, ACKing and Activating
<0004> abis_nm.c:743 OC=GPRS-NSVC(f2) INST=(00,01,ff): Found SW config: 
42 12 00 08 31 32 30 61 30 30 32 00 13 00 09 76 32 36 37 62 35 64 30 00
<0004> abis_nm.c:755 OC=GPRS-NSVC(f2) INST=(00,01,ff): Selected sw 
description 0 of 1
<0004> abis_nm.c:698 OC=BTS(01) INST=(00,ff,ff): Get Attributes Response
<0004> abis_nm.c:592 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: reported unexpectedly long (13 bytes) feature vector - most 
likely it was compiled against newer BSC headers. Consider upgrading 
your BSC to later version.
<0004> abis_nm.c:610 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: reported feature 'MULTI_TSC' is not supported, while we 
thought it is.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x17. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x1a. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x1c. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x1d. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x1e. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x21. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x22. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x24. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x27. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x29. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x2a. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x2b. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x31. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x32. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x37. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x39. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x3a. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x3e. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x3f. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x41. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x42. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x46. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x47. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x49. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x4a. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x4d. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x4f. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x51. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x52. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x53. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x56. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x57. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x59. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x5a. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x5b. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x5e. Consider upgrading osmo-bsc.
<0004> abis_nm.c:602 OC=BTS(01) INST=(00,ff,ff): Get Attributes 
Response: unknown feature 0x5f. Consider upgrading osmo-bsc.
<0004> abis_nm.c:633 OC=BTS(01) INST=(00,ff,ff): ARI reported sw[0/2]: 
120a004 is v267b5d0
<0004> abis_nm.c:633 OC=BTS(01) INST=(00,ff,ff): ARI reported sw[1/2]: 
120a002 is v267b5d0
<0004> bts_ipaccess_nanobts.c:361 
NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_OFFLINE}: Received Event 
GET_ATTR_REP
<0004> nm_bts_fsm.c:139 
NM_GPRS_NSVC_OP(nsvc0)[0x558f2b1ded90]{DISABLED_NOTINSTALLED}: Received 
Event FEATURE_NEGOTIATED
<0004> abis_nm.c:1847 OC=BTS(01) INST=(00,ff,ff): Set BTS Attr
<0004> abis_nm.c:258 OC=GPRS-CELL(f1) INST=(00,00,ff): STATE CHG: 
OP_STATE=Disabled AVAIL=Dependency(05)
<0004> bts_ipaccess_nanobts.c:181 
NM_GPRS_CELL_OP(gprs-cell0)[0x558f2b1d5250]{DISABLED_NOTINSTALLED}: 
Received Event STATE_CHG_REP
<0004> nm_gprs_cell_fsm.c:75 
NM_GPRS_CELL_OP(gprs-cell0)[0x558f2b1d5250]{DISABLED_NOTINSTALLED}: 
state_chg to DISABLED_DEPENDENCY
<0004> nm_gprs_cell_fsm.c:130 
NM_GPRS_CELL_OP(gprs-cell0)[0x558f2b1d5250]{DISABLED_DEPENDENCY}: 
state_chg to DISABLED_OFFLINE
<0004> abis_nm.c:478 OC=GPRS-CELL(f1) INST=(00,00,ff): Software 
Activated Report
<0004> bts_ipaccess_nanobts.c:235 
NM_GPRS_CELL_OP(gprs-cell0)[0x558f2b1d5250]{DISABLED_OFFLINE}: Received 
Event SW_ACT_REP
<0004> bts_ipaccess_nanobts.c:235 
NM_GPRS_CELL_OP(gprs-cell0)[0x558f2b1d5250]{DISABLED_OFFLINE}: Event 
SW_ACT_REP not permitted
<0004> abis_nm.c:258 OC=GPRS-NSVC(f2) INST=(00,00,ff): STATE CHG: 
OP_STATE=Disabled AVAIL=Off line(03)
<0004> bts_ipaccess_nanobts.c:188 
NM_GPRS_NSVC_OP(nsvc0)[0x558f2b1ded90]{DISABLED_NOTINSTALLED}: Received 
Event STATE_CHG_REP
<0004> nm_gprs_nsvc_fsm.c:83 
NM_GPRS_NSVC_OP(nsvc0)[0x558f2b1ded90]{DISABLED_NOTINSTALLED}: state_chg 
to DISABLED_OFFLINE
<0004> abis_nm.c:258 OC=GPRS-NSVC(f2) INST=(00,01,ff): STATE CHG: 
OP_STATE=Disabled AVAIL=Off line(03)
<0004> abis_nm.c:478 OC=GPRS-NSVC(f2) INST=(00,00,ff): Software 
Activated Report
<0004> bts_ipaccess_nanobts.c:240 
NM_GPRS_NSVC_OP(nsvc0)[0x558f2b1ded90]{DISABLED_OFFLINE}: Received Event 
SW_ACT_REP
<0004> bts_ipaccess_nanobts.c:240 
NM_GPRS_NSVC_OP(nsvc0)[0x558f2b1ded90]{DISABLED_OFFLINE}: Event 
SW_ACT_REP not permitted
<0004> abis_nm.c:478 OC=GPRS-NSVC(f2) INST=(00,01,ff): Software 
Activated Report
<0004> bts_ipaccess_nanobts.c:240 
NM_GPRS_NSVC_OP(nsvc1)[0x558f2b1defc0]{DISABLED_NOTINSTALLED}: Received 
Event SW_ACT_REP
<0004> abis_nm.c:2852 OC=GPRS-NSE(f0) INST=(00,ff,ff): Rx 
IPACCESS(0xf6): 9d 00 02 00 00 a0 00 07 03 03 03 03 1e 03 0a a1 00 0b 03 
03 03 03 03 0a 03 0a 03 0a 03
<0004> abis_nm.c:2909 OC=GPRS-NSE(f0) INST=(00,ff,ff): SET ATTR ACK
<0004> bts_ipaccess_nanobts.c:431 
NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_OFFLINE}: Received Event 
SET_ATTR_ACK
<0004> abis_nm.c:871 OC=BTS(01) INST=(00,ff,ff): Set BTS Attributes ACK
<0004> bts_ipaccess_nanobts.c:383 
NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_OFFLINE}: Received Event 
SET_ATTR_ACK
<0004> abis_nm.c:780 OC=GPRS-NSE(f0) INST=(00,ff,ff): Rx Change 
Administrative State ACK Unlocked
<0004> bts_ipaccess_nanobts.c:177 
NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_OFFLINE}: Received Event 
STATE_CHG_REP
<0004> abis_nm.c:2186 OC=GPRS-NSE(f0) INST=(00,ff,ff): Sending OPSTART
<0004> abis_nm.c:258 OC=GPRS-NSE(f0) INST=(00,ff,ff): STATE CHG: 
OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked (No State change 
detected)
<0004> abis_nm.c:780 OC=BTS(01) INST=(00,ff,ff): Rx Change 
Administrative State ACK Unlocked
<0004> bts_ipaccess_nanobts.c:160 
NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_OFFLINE}: Received Event 
STATE_CHG_REP
<0004> abis_nm.c:2186 OC=BTS(01) INST=(00,ff,ff): Sending OPSTART
<0004> abis_nm.c:258 OC=BTS(01) INST=(00,ff,ff): STATE CHG: 
OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked (No State change 
detected)
<0004> abis_nm.c:839 OC=GPRS-NSE(f0) INST=(00,ff,ff): Opstart ACK
<0004> bts_ipaccess_nanobts.c:290 
NM_GPRS_NSE_OP(nse0)[0x558f2b1debd0]{DISABLED_OFFLINE}: Received Event 
OPSTART_ACK
<0004> abis_nm.c:839 OC=BTS(01) INST=(00,ff,ff): Opstart ACK
<0004> bts_ipaccess_nanobts.c:274 
NM_BTS_OP(bts0)[0x558f2b1d5120]{DISABLED_OFFLINE}: Received Event 
OPSTART_ACK

After a while the OML connection is lost.

<0004> abis_nm.c:258 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): STATE 
CHG: OP_STATE=Disabled AVAIL=Dependency(05)
<0004> bts_ipaccess_nanobts.c:164 
NM_BB_TRANSC_OP(bts0-trx0)[0x56372d474940]{DISABLED_NOTINSTALLED}: 
Received Event STATE_CHG_REP
<0004> nm_bb_transc_fsm.c:75 
NM_BB_TRANSC_OP(bts0-trx0)[0x56372d474940]{DISABLED_NOTINSTALLED}: 
state_chg to DISABLED_DEPENDENCY
<0004> nm_bb_transc_fsm.c:132 
NM_BB_TRANSC_OP(bts0-trx0)[0x56372d474940]{DISABLED_DEPENDENCY}: 
state_chg to DISABLED_OFFLINE
<0004> abis_nm.c:1835 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): Tx 
Get Attributes (Request)
<0004> abis_nm.c:698 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): Get 
Attributes Response
<0004> abis_nm.c:633 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): ARI 
reported sw[0/3]: 120a004 is v267b5d0
<0004> abis_nm.c:633 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): ARI 
reported sw[1/3]: 120a002 is v267b5d0
<0004> abis_nm.c:633 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): ARI 
reported sw[2/3]: 120a001 is v267b5d0
<0004> abis_nm.c:551 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): Get 
Attributes Response Info: 2 bytes total with 1 unreported attributes
<0004> abis_nm.c:556 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): 
Attribute Manufacturer Dependent State is unreported
<0004> bts_ipaccess_nanobts.c:366 
NM_BB_TRANSC_OP(bts0-trx0)[0x56372d474940]{DISABLED_OFFLINE}: Received 
Event GET_ATTR_REP
<0004> abis_nm.c:945 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff): CHANGE 
ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed
<0004> osmo_bsc_main.c:229 Got CHANGE ADMINISTRATIVE STATE NACK going to 
drop the OML links.
<0017> bts_ipaccess_nanobts.c:620 (bts=0) Deferring Drop of OML link.
<0017> bts_ipaccess_nanobts.c:555 (bts=0) Dropping OML link: Deferred 
link drop
<0019> osmo_bsc_main.c:405 (bts=0,trx=0) Lost E1 OML link
<0019> osmo_bsc_main.c:405 (bts=0,trx=0) Lost E1 OSMO link
<0004> bts_ipaccess_nanobts.c:568 
NM_BB_TRANSC_OP(bts0-trx0)[0x56372d474940]{DISABLED_OFFLINE}: Received 
Event OML_DOWN
<0004> nm_bb_transc_fsm.c:291 
NM_BB_TRANSC_OP(bts0-trx0)[0x56372d474940]{DISABLED_OFFLINE}: state_chg 
to DISABLED_NOTINSTALLED
<0004> bts_ipaccess_nanobts.c:569 
NM_RCARRIER_OP(bts0-trx0)[0x56372d474770]{DISABLED_NOTINSTALLED}: 
Received Event OML_DOWN
<0004> bts_ipaccess_nanobts.c:572 
NM_CHAN_OP(bts0-trx0-ts0)[0x56372d474c40]{DISABLED_NOTINSTALLED}: 
Received Event OML_DOWN
<0004> bts_ipaccess_nanobts.c:572 
NM_CHAN_OP(bts0-trx0-ts1)[0x56372d475340]{DISABLED_NOTINSTALLED}: 
Received Event OML_DOWN
<0004> bts_ipaccess_nanobts.c:572 
NM_CHAN_OP(bts0-trx0-ts2)[0x56372d475b40]{DISABLED_NOTINSTALLED}: 
Received Event OML_DOWN
<0004> bts_ipaccess_nanobts.c:572 
NM_CHAN_OP(bts0-trx0-ts3)[0x56372d476340]{DISABLED_NOTINSTALLED}: 
Received Event OML_DOWN
<0004> bts_ipaccess_nanobts.c:572 
NM_CHAN_OP(bts0-trx0-ts4)[0x56372d476b40]{DISABLED_NOTINSTALLED}: 
Received Event OML_DOWN
<0004> bts_ipaccess_nanobts.c:572 
NM_CHAN_OP(bts0-trx0-ts5)[0x56372d4773d0]{DISABLED_NOTINSTALLED}: 
Received Event OML_DOWN
<0004> bts_ipaccess_nanobts.c:572 
NM_CHAN_OP(bts0-trx0-ts6)[0x56372d477c60]{DISABLED_NOTINSTALLED}: 
Received Event OML_DOWN
<0004> bts_ipaccess_nanobts.c:572 
NM_CHAN_OP(bts0-trx0-ts7)[0x56372d4784f0]{DISABLED_NOTINSTALLED}: 
Received Event OML_DOWN
<0004> bts_ipaccess_nanobts.c:576 
NM_BTS_SM_OP(bts_sm)[0x56372d46b7e0]{ENABLED}: Received Event OML_DOWN
<0004> nm_bts_sm_fsm.c:216 
NM_BTS_SM_OP(bts_sm)[0x56372d46b7e0]{ENABLED}: state_chg to 
DISABLED_NOTINSTALLED
<0004> bts_ipaccess_nanobts.c:577 
NM_GPRS_NSE_OP(nse0)[0x56372d478bd0]{DISABLED_OFFLINE}: Received Event 
OML_DOWN
<0004> nm_gprs_nse_fsm.c:298 
NM_GPRS_NSE_OP(nse0)[0x56372d478bd0]{DISABLED_OFFLINE}: state_chg to 
DISABLED_NOTINSTALLED
<0004> bts_ipaccess_nanobts.c:579 
NM_GPRS_NSVC_OP(nsvc0)[0x56372d478d90]{DISABLED_OFFLINE}: Received Event 
OML_DOWN
<0004> nm_gprs_nsvc_fsm.c:307 
NM_GPRS_NSVC_OP(nsvc0)[0x56372d478d90]{DISABLED_OFFLINE}: state_chg to 
DISABLED_NOTINSTALLED
<0004> bts_ipaccess_nanobts.c:579 
NM_GPRS_NSVC_OP(nsvc1)[0x56372d478fc0]{DISABLED_NOTINSTALLED}: Received 
Event OML_DOWN
<0004> bts_ipaccess_nanobts.c:581 
NM_BTS_OP(bts0)[0x56372d46f120]{DISABLED_OFFLINE}: Received Event OML_DOWN
<0004> nm_bts_fsm.c:319 
NM_BTS_OP(bts0)[0x56372d46f120]{DISABLED_OFFLINE}: state_chg to 
DISABLED_NOTINSTALLED
<0004> bts_ipaccess_nanobts.c:582 
NM_GPRS_CELL_OP(gprs-cell0)[0x56372d46f250]{DISABLED_OFFLINE}: Received 
Event OML_DOWN
<0004> nm_gprs_cell_fsm.c:296 
NM_GPRS_CELL_OP(gprs-cell0)[0x56372d46f250]{DISABLED_OFFLINE}: state_chg 
to DISABLED_NOTINSTALLED
^Csignal 2 received
<0004> bsc_init.c:66 shutting down OML for BTS 0



-------------- next part --------------
A non-text attachment was scrubbed...
Name: nanobts.pcap
Type: application/vnd.tcpdump.pcap
Size: 27391 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210710/e2801a8e/attachment.bin>
-------------- next part --------------
!
! OsmoBSC (1.7.0.185-05293) configuration saved from vty
!!
!
log stderr
 logging filter all 1
 logging color 1
 logging print category-hex 1
 logging print category 0
 logging print thread-id 0
 logging timestamp 0
 logging print file 1
 logging level rll notice
 logging level mm notice
 logging level rr notice
 logging level rsl notice
 logging level nm notice
 logging level pag notice
 logging level meas notice
 logging level msc notice
 logging level ho notice
 logging level hodec notice
 logging level ref notice
 logging level ctrl notice
 logging level filter notice
 logging level pcu notice
 logging level lcls notice
 logging level chan notice
 logging level ts notice
 logging level as notice
 logging level cbs notice
 logging level lcs notice
 logging level reset notice
 logging level lglobal notice
 logging level llapd notice
 logging level linp notice
 logging level lmux notice
 logging level lmi notice
 logging level lmib notice
 logging level lsms notice
 logging level lctrl notice
 logging level lgtp notice
 logging level lstats notice
 logging level lgsup notice
 logging level loap notice
 logging level lss7 notice
 logging level lsccp notice
 logging level lsua notice
 logging level lm3ua notice
 logging level lmgcp notice
 logging level ljibuf notice
 logging level lrspro notice
 logging level lns notice
 logging level lbssgp notice
 logging level lnsdata notice
 logging level lnssignal notice
!
stats interval 5
!
line vty
 no login
!
e1_input
 e1_line 0 driver ipa
 e1_line 0 port 0
 no e1_line 0 keepalive
cs7 instance 0
 point-code 1.23.3
 asp my-asp 2905 0 m3ua
  local-ip 10.0.0.16
  remote-ip 10.0.0.16
  sctp-role client
 sccp-address my-msc
  routing-indicator PC
  point-code 0.23.1
network
 network country code 001
 mobile network code 01
 encryption a5 1 3
 neci 0
 paging any use tch 0
 bts 0
  type nanobts
  band GSM900
  cell_identity 0
  location_area_code 23
  base_station_id_code 63
  ms max power 15
  cell reselection hysteresis 4
  rxlev access min 0
  radio-link-timeout 32
  channel allocator ascending
  rach tx integer 9
  rach max transmission 7
  rach max-delay 63
  channel-description attach 1
  channel-description bs-pa-mfrms 5
  channel-description bs-ag-blks-res 1
  no access-control-class-ramping
  early-classmark-sending forbidden
  early-classmark-sending-3g allowed
  ipa unit-id 1800 0
  oml ipa stream-id 255 line 0
  neighbor-list mode automatic
  codec-support fr hr efr amr
  amr tch-f modes 0 2 4 7
  amr tch-f threshold ms 32 32 32
  amr tch-f hysteresis ms 8 8 8
  amr tch-f threshold bts 32 32 32
  amr tch-f hysteresis bts 8 8 8
  amr tch-f start-mode auto
  amr tch-h modes 0 2 4
  amr tch-h threshold ms 32 32
  amr tch-h hysteresis ms 8 8
  amr tch-h threshold bts 32 32
  amr tch-h hysteresis bts 8 8
  amr tch-h start-mode auto
  gprs mode none
  bs-power-control
   mode static
  ms-power-control
   mode dyn-bts
   step-size inc 4 red 2
   rxlev-thresh lower 32 upper 38
   rxlev-thresh-comp lower 10 12 upper 19 20
   rxqual-thresh lower 3 upper 0
   rxqual-thresh-comp lower 5 7 upper 15 18
  trx 0
   rf_locked 0
   arfcn 124
   nominal power 23
   max_power_red 0
   rsl e1 tei 0
   timeslot 0
    phys_chan_config CCCH+SDCCH4
    hopping enabled 0
   timeslot 1
    phys_chan_config SDCCH8
    hopping enabled 0
   timeslot 2
    phys_chan_config TCH/F
    hopping enabled 0
   timeslot 3
    phys_chan_config TCH/F
    hopping enabled 0
   timeslot 4
    phys_chan_config TCH/F
    hopping enabled 0
   timeslot 5
    phys_chan_config TCH/F
    hopping enabled 0
   timeslot 6
    phys_chan_config TCH/F
    hopping enabled 0
   timeslot 7
    phys_chan_config TCH/F
    hopping enabled 0
msc 0
 codec-list fr1 hr1 fr2 fr3 hr3
 allow-emergency allow
 amr-config 12_2k forbidden
 amr-config 10_2k forbidden
 amr-config 7_95k forbidden
 amr-config 7_40k forbidden
 amr-config 6_70k forbidden
 amr-config 5_90k allowed
 amr-config 5_15k forbidden
 amr-config 4_75k forbidden
 amr-payload octet-aligned
 msc-addr my-msc
 asp-protocol m3ua
 lcls-mode disabled
 lcls-codec-mismatch forbidden
 mgw local-port 2727
 mgw remote-ip 10.0.0.16
 mgw remote-port 2427
bsc
 mid-call-timeout 0

From andreas at eversberg.eu  Sun Jul 11 06:50:13 2021
From: andreas at eversberg.eu (Andreas Eversberg)
Date: Sun, 11 Jul 2021 08:50:13 +0200
Subject: Nanobts will not correctly attach to osmo-bsc.
In-Reply-To: <24d8f22c-ffb3-6730-d105-ad0a575294e5@eversberg.eu>
References: <24d8f22c-ffb3-6730-d105-ad0a575294e5@eversberg.eu>
Message-ID: <14fe4269-8054-e2b8-5c42-ee9d25d0d619@eversberg.eu>

I tried different BTS and it works. Maybe it is just broken.

On 10.07.21 17:03, Andreas Eversberg wrote:
> It connects via OML, comes to a point where provisioning stops or 
> times out.


From nhofmeyr at sysmocom.de  Sun Jul 11 11:33:37 2021
From: nhofmeyr at sysmocom.de (Neels Hofmeyr)
Date: Sun, 11 Jul 2021 13:33:37 +0200
Subject: Nanobts will not correctly attach to osmo-bsc.
In-Reply-To: <14fe4269-8054-e2b8-5c42-ee9d25d0d619@eversberg.eu>
References: <24d8f22c-ffb3-6730-d105-ad0a575294e5@eversberg.eu>
 <14fe4269-8054-e2b8-5c42-ee9d25d0d619@eversberg.eu>
Message-ID: <20210711113336.GA4590@my.box>

On Sun, Jul 11, 2021 at 08:50:13AM +0200, Andreas Eversberg wrote:
> I tried different BTS and it works. Maybe it is just broken.

Good to hear that it worked out, and also nice to hear from you :)

~N


From pespin at sysmocom.de  Mon Jul 12 09:38:28 2021
From: pespin at sysmocom.de (Pau Espin Pedrol)
Date: Mon, 12 Jul 2021 11:38:28 +0200
Subject: Nanobts will not correctly attach to osmo-bsc.
In-Reply-To: <24d8f22c-ffb3-6730-d105-ad0a575294e5@eversberg.eu>
References: <24d8f22c-ffb3-6730-d105-ad0a575294e5@eversberg.eu>
Message-ID: <4d9f2570-ccd8-adb9-0795-4f42e8c0f06d@sysmocom.de>

Hi Andreas,

It would be great if you could provide a proper pcap file since as you 
may know order of such messages is rather important :)

I'm having difficulties matching 100% the log file vs the pcap. Using 
gmstap logging here may use in order to have all the info in the same 
place and more or less ordrered.

There seems to be an issue configuring the BTS object in OML. From pcap 
file, this is what looks like:

frame 10: BTS => BSC: BTS State Changed Event Report(Not installed, Locked)
frame 18: BTS => BSC: Software Activate Request
frame 21: BTS <= BSC: Software Activate Request ACK
frame 22: BTS <= BSC: Activate Software
frame 27: BTS => BSC: Activate Software ACK
frame 27: BTS => BSC: BTS State Changed Event Report(Disabled, Dependency)
frame 27: BTS => BSC: Software Activated Report
frame 29: BTS <= BSC: Get Attributes
frame 39: BTS => BSC: Get Attributes Response
frame 48: BTS <= BSC: Set BTS Attributes
frame 49: BTS => BSC: Set BTS Attributes ACK
frame 52: BTS <= BSC: Change Administrative State (Unlocked)
frame 55: BTS => BSC: Change Administrative State ACK (Unlocked)
frame 55: BTS => BSC: BTS State Changed Event Report(Dependency, Unlocked)
frame 61: BTS <= BSC: Opstart
frame 160: BTS => BSC: BTS State Changed Event Report(Enabled)
frame 200: BTS => BSC: Get Attributes Response  ?!?!?!?! where does this 
come from?!?!?!
frame 219: BTS <= BSC: Set BTS Attributes
frame238: BTS => BSC: Opstart ACK

Some of those, specially at the end, look really weird, but it could be 
due to your setup as you mentioned.

In any case, according to pcap the BSC receives a "BTS State Changed 
Event Report(Enabled)" at frame 160, but I never see that message being 
processed in the log file (NM_BTS_OP(bts0) FSM is still in state 
DISABLED_OFFLINE when receiving the OPSTART_ACK but it should have moved 
to ENABLED already when receiving such report afaict from nm_bts_fsm.c:230.

Feel free to create a ticket if you can sort out the proper recording of 
pcap file and you still find issues.

Regards,
Pau

-- 
- 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


From andreas at eversberg.eu  Tue Jul 13 14:02:57 2021
From: andreas at eversberg.eu (Andreas Eversberg)
Date: Tue, 13 Jul 2021 16:02:57 +0200
Subject: Nanobts will not correctly attach to osmo-bsc.
In-Reply-To: <4d9f2570-ccd8-adb9-0795-4f42e8c0f06d@sysmocom.de>
References: <24d8f22c-ffb3-6730-d105-ad0a575294e5@eversberg.eu>
 <4d9f2570-ccd8-adb9-0795-4f42e8c0f06d@sysmocom.de>
Message-ID: <9abd4292-5dcd-32bb-c859-30eb4d4e705d@eversberg.eu>

Pau Espin Pedrol wrote:
> Some of those, specially at the end, look really weird, but it could 
> be due to your setup as you mentioned.
>
> In any case, according to pcap the BSC receives a "BTS State Changed 
> Event Report(Enabled)" at frame 160, but I never see that message 
> being processed in the log file (NM_BTS_OP(bts0) FSM is still in state 
> DISABLED_OFFLINE when receiving the OPSTART_ACK but it should have 
> moved to ENABLED already when receiving such report afaict from 
> nm_bts_fsm.c:230. 
Hi Pau,

it is not a Software issue. The BTS crashes and reboots when it starts 
transmitting. Maybe a faulty solder connection. The other BTS works well!

Regards,

Andreas



From hncaga at gmail.com  Wed Jul 21 20:20:55 2021
From: hncaga at gmail.com (Henry Caga)
Date: Thu, 22 Jul 2021 04:20:55 +0800
Subject: No subject
Message-ID: <CAAfxn1_LoxbZV=4NT3U4N2dG+BucLz0Vpd+snCEeqRhpqpw7Sg@mail.gmail.com>

Hi,

I would like to know if it is possible to disconnect a connected device to
my osmo-bsc system?

After running my osmo-bsc setup and my test phone is connected to my usrp
via 2g, is it possible to send a vty command or what are the steps to make
the connected device to detach to my bts?

Thank you so much.

Hnjojo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210722/19b9f6d7/attachment.htm>

From nhofmeyr at sysmocom.de  Wed Jul 21 23:21:50 2021
From: nhofmeyr at sysmocom.de (Neels Hofmeyr)
Date: Thu, 22 Jul 2021 01:21:50 +0200
Subject: your mail
In-Reply-To: <CAAfxn1_LoxbZV=4NT3U4N2dG+BucLz0Vpd+snCEeqRhpqpw7Sg@mail.gmail.com>
References: <CAAfxn1_LoxbZV=4NT3U4N2dG+BucLz0Vpd+snCEeqRhpqpw7Sg@mail.gmail.com>
Message-ID: <20210721232150.GA25542@my.box>

On Thu, Jul 22, 2021 at 04:20:55AM +0800, Henry Caga wrote:
> Hi,
> 
> I would like to know if it is possible to disconnect a connected device to
> my osmo-bsc system?
> 
> After running my osmo-bsc setup and my test phone is connected to my usrp
> via 2g, is it possible to send a vty command or what are the steps to make
> the connected device to detach to my bts?
> 
> Thank you so much.
> 
> Hnjojo

On osmo-bsc level on a live channel you could try to release the lchan the
subscriber is using with this VTY command:

 enable
 bts <0-255> trx <0-255> timeslot <0-7> sub-slot <0-7> deactivate fr

Of course the subscriber is then still attached to the network on MSC level,
but the active connection should be interrupted.

The question is what exactly do you mean by "disconnect".

you can also put your phone in flight mode to disconnect it...


From hncaga at gmail.com  Thu Jul 22 00:59:55 2021
From: hncaga at gmail.com (Henry Caga)
Date: Thu, 22 Jul 2021 08:59:55 +0800
Subject: your mail
In-Reply-To: <20210721232150.GA25542@my.box>
References: <CAAfxn1_LoxbZV=4NT3U4N2dG+BucLz0Vpd+snCEeqRhpqpw7Sg@mail.gmail.com>
 <20210721232150.GA25542@my.box>
Message-ID: <CAAfxn1-r505KjFxC-_XWk9S=d_=hDhovKzWcQ-NX514UH-m4mw@mail.gmail.com>

Hello, thanks for the reply. What i mean about disconnecting is to make
camped devices as "un-camped" from my setup or bts. turning the phone in
flight mode is the correct example but is it possible to un-camped a
specific device from thw bts side or from my setup?

On Thu, Jul 22, 2021, 7:21 AM Neels Hofmeyr <nhofmeyr at sysmocom.de> wrote:

> On Thu, Jul 22, 2021 at 04:20:55AM +0800, Henry Caga wrote:
> > Hi,
> >
> > I would like to know if it is possible to disconnect a connected device
> to
> > my osmo-bsc system?
> >
> > After running my osmo-bsc setup and my test phone is connected to my usrp
> > via 2g, is it possible to send a vty command or what are the steps to
> make
> > the connected device to detach to my bts?
> >
> > Thank you so much.
> >
> > Hnjojo
>
> On osmo-bsc level on a live channel you could try to release the lchan the
> subscriber is using with this VTY command:
>
>  enable
>  bts <0-255> trx <0-255> timeslot <0-7> sub-slot <0-7> deactivate fr
>
> Of course the subscriber is then still attached to the network on MSC
> level,
> but the active connection should be interrupted.
>
> The question is what exactly do you mean by "disconnect".
>
> you can also put your phone in flight mode to disconnect it...
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210722/453198f4/attachment.htm>

From laforge at osmocom.org  Thu Jul 22 06:45:03 2021
From: laforge at osmocom.org (Harald Welte)
Date: Thu, 22 Jul 2021 08:45:03 +0200
Subject: Announcement of "OsmoDevCall" on July 23, 2021
Message-ID: <YPkT72WfjCWdToPk@nataraja>

Dear Osmocom community,

It's my pleasure to announce the next OsmoDevCall at

	July 23, 2021 at 20:00 CEST
at
	https://meeting4.franken.de/b/har-xbc-bsx-wvs

This meeting will have the following schedule:

20:00 meet + greet
20:15 presentation on "high-level overview on IMS, VoLTE, VoWiFi"
21:00 USSE: unstructured supplementary social event [*]
22:00 close of call

Attendance is free of charge and open to anyone with an interest
in Osmocom.

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 on Friday.

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 at osmocom.org>            http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)


From domi at tomcsanyi.net  Thu Jul 22 12:43:21 2021
From: domi at tomcsanyi.net (Tomcsanyi, Domonkos)
Date: Thu, 22 Jul 2021 14:43:21 +0200
Subject: your mail
In-Reply-To: <CAAfxn1-r505KjFxC-_XWk9S=d_=hDhovKzWcQ-NX514UH-m4mw@mail.gmail.com>
References: <CAAfxn1-r505KjFxC-_XWk9S=d_=hDhovKzWcQ-NX514UH-m4mw@mail.gmail.com>
Message-ID: <0862EC60-FBB3-4937-8596-24DD4FE6878A@tomcsanyi.net>

In case the phone tries to do a Location Area Update or any other transaction you could reject it with a proper reject cause.
If you want to detach a completely idle UE without waiting for an LU timer to expire you would need to page it and then reject it I think.

This is based purely signaling theory not actually looking into osmo-bsc?s features/options.

Cheers,
Domi

> 22.07.2021 d?tummal, 3:00 id?pontban Henry Caga <hncaga at gmail.com> ?rta:
> 
> ?
> Hello, thanks for the reply. What i mean about disconnecting is to make camped devices as "un-camped" from my setup or bts. turning the phone in flight mode is the correct example but is it possible to un-camped a specific device from thw bts side or from my setup?
> 
>> On Thu, Jul 22, 2021, 7:21 AM Neels Hofmeyr <nhofmeyr at sysmocom.de> wrote:
>> On Thu, Jul 22, 2021 at 04:20:55AM +0800, Henry Caga wrote:
>> > Hi,
>> > 
>> > I would like to know if it is possible to disconnect a connected device to
>> > my osmo-bsc system?
>> > 
>> > After running my osmo-bsc setup and my test phone is connected to my usrp
>> > via 2g, is it possible to send a vty command or what are the steps to make
>> > the connected device to detach to my bts?
>> > 
>> > Thank you so much.
>> > 
>> > Hnjojo
>> 
>> On osmo-bsc level on a live channel you could try to release the lchan the
>> subscriber is using with this VTY command:
>> 
>>  enable
>>  bts <0-255> trx <0-255> timeslot <0-7> sub-slot <0-7> deactivate fr
>> 
>> Of course the subscriber is then still attached to the network on MSC level,
>> but the active connection should be interrupted.
>> 
>> The question is what exactly do you mean by "disconnect".
>> 
>> you can also put your phone in flight mode to disconnect it...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210722/ad568380/attachment.htm>

From m10502215 at gmail.com  Fri Jul 16 03:43:00 2021
From: m10502215 at gmail.com (EmPa Kro)
Date: Fri, 16 Jul 2021 11:43:00 +0800
Subject: How to program EFAD(Administrative Data)
Message-ID: <CAKNV16WnghUGXbwHTPTfYVBw9aA2WOgVePR7=4sySM+LXjy7hQ@mail.gmail.com>

Hello develop,

I want to program Administrative Data update the MS operation mode.
Are there any option command can use on "pySim-prog.py" ?
I saw "update_ad" in the pySIM/cards.py it mean Update Administrative Data.

  Please help me......, thank you so much.

 Best Regards,
 Kenny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210716/728d7979/attachment.htm>

From m10502215 at gmail.com  Fri Jul 16 09:54:23 2021
From: m10502215 at gmail.com (EmPa Kro)
Date: Fri, 16 Jul 2021 17:54:23 +0800
Subject: How to program EFAD(Administrative Data)
In-Reply-To: <CAKNV16WnghUGXbwHTPTfYVBw9aA2WOgVePR7=4sySM+LXjy7hQ@mail.gmail.com>
References: <CAKNV16WnghUGXbwHTPTfYVBw9aA2WOgVePR7=4sySM+LXjy7hQ@mail.gmail.com>
Message-ID: <CAKNV16XYNaPfgOZ-JTtqeoe_SyRObC0=18+pmp8rokrg8YN1Rw@mail.gmail.com>

Hello develop,

I solve this question by new version with option "--opmode"

Thank you.

Best regards
Kenny

EmPa Kro <m10502215 at gmail.com> ? 2021?7?16? ?? ??11:43???

> Hello develop,
>
> I want to program Administrative Data update the MS operation mode.
> Are there any option command can use on "pySim-prog.py" ?
> I saw "update_ad" in the pySIM/cards.py it mean Update Administrative Data.
>
>   Please help me......, thank you so much.
>
>  Best Regards,
>  Kenny
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210716/cee5c140/attachment.htm>

From nhofmeyr at sysmocom.de  Sun Jul 25 23:40:14 2021
From: nhofmeyr at sysmocom.de (Neels Hofmeyr)
Date: Mon, 26 Jul 2021 01:40:14 +0200
Subject: your mail
In-Reply-To: <CAAfxn1-r505KjFxC-_XWk9S=d_=hDhovKzWcQ-NX514UH-m4mw@mail.gmail.com>
References: <CAAfxn1_LoxbZV=4NT3U4N2dG+BucLz0Vpd+snCEeqRhpqpw7Sg@mail.gmail.com>
 <20210721232150.GA25542@my.box>
 <CAAfxn1-r505KjFxC-_XWk9S=d_=hDhovKzWcQ-NX514UH-m4mw@mail.gmail.com>
Message-ID: <20210725234014.GA30257@my.box>

On Thu, Jul 22, 2021 at 08:59:55AM +0800, Henry Caga wrote:
> Hello, thanks for the reply. What i mean about disconnecting is to make
> camped devices as "un-camped" from my setup or bts. turning the phone in
> flight mode is the correct example but is it possible to un-camped a
> specific device from thw bts side or from my setup?

I'm still not sure I understand your actual practical aim.

osmo-bsc is responsible for actually active channels, e.g. while a voice call
is ongoing.

The "camping" part is done by the VLR in osmo-msc. You can "un-camp" a
subscriber via the osmo-msc VTY, see osmo-msc-vty-reference.pdf at
https://ftp.osmocom.org/docs/latest/ , command
'subscriber (msisdn|extension|imsi|tmsi|id) ID expire'.
The VLR forgets the subscriber, but the phone will not show any change. After
the Periodical Location Update period, the phone will simply re-attach. When it
tries to use any service, it will first re-attach.
You could read up on Periodical Location Update. Or look at what happens after
such an expiry in wireshark.

You can also prohibit attaching of a subscriber, via osmo-hlr: see
osmo-hlr-vty-reference.pdf at above link, command
'subscriber (imsi|msisdn|id|imei) IDENT update network-access-mode (none|cs|ps|cs+ps)'

HTH


From sonny.lafuente at entropysolution.com  Thu Jul 29 05:33:25 2021
From: sonny.lafuente at entropysolution.com (Sonny Lafuente)
Date: Thu, 29 Jul 2021 05:33:25 +0000
Subject: MS Power Transmit not changing
Message-ID: <ED4CEAF9-F7E2-4380-85C6-18DFD91A5CF2@entropysolution.com>

Hello Neels and Community,

Good day!

We are doing some testing on our Lab specifically in Voice. During this testing we observed that the MS power transmit is not changing during ongoing call and the value is 5dbm. We also do walk test in order to lower the received power level and to observed if the MS Transmit power will increase. We tried to change some parameters in osmo-bts-trx uplink-power-target but however, the MS Transmit power still the same which is 5dbm. The MS power in the osmo-nitb config is set to 23dbm.  Below is the version and configuration we used on our testing in Lab.


Version:

OpenBSC# show version
OpenBSC 1.3.2.2-d2550 (OpenBSC).
Copyright (C) 2008-2016 Harald Welte, Holger Freyther
Contributions by Daniel Willmann, Jan L?bbe, Stefan Schmidt
Dieter Spaar, Andreas Eversberg, Sylvain Munaut, Neels Hofmeyr

License AGPLv3+: GNU AGPL version 3 or later <http://gnu.org/licenses/agpl-3.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

OpenBSC#


OsmoBTS# show version
OsmoBTS 1.2.0.48-6392 (OsmoBTS).
Copyright (C) 2010, 2011 by Harald Welte, Andreas Eversberg and On-Waves
License AGPLv3+: GNU AGPL version 3 or later <http://gnu.org/licenses/agpl-3.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

OsmoBTS#


Logs:

OpenBSC# show lchan
BTS 0, TRX 1, Timeslot 0, Lchan 0: Type SDCCH
  Connection: 1, State: ACTIVE
  BS Power: 0 dBm, MS Power: 23 dBm
  Channel Mode / Codec: signalling
  Subscriber:
    ID: 1816, Authorized: 0
    Extension: 164324
    IMSI: 515039102991665
    Use count: 1
  Bound IP: 0.0.0.0 Port 0 RTP_TYPE2=0 CONN_ID=0
  Measurement Report:
    Flags: DLinval
    RXL-FULL-ul:  -50 dBm, RXL-SUB-ul:  -50 dBm RXQ-FULL-ul: 7, RXQ-SUB-ul: 7
BTS 0, TRX 1, Timeslot 6, Lchan 0: Type TCH_F
  Connection: 1, State: ACTIVE
  BS Power: 0 dBm, MS Power: 23 dBm
  Channel Mode / Codec: FR or HR
  Subscriber:
    ID: 1782, Authorized: 1
    Extension: 05837654321
    IMSI: 515032920153135
    Use count: 2
  Bound IP: X.X.X.X Port 16386 RTP_TYPE2=0 CONN_ID=0
  Measurement Report:
    Flags:
    MS Timing Offset: 0
    L1 MS Power: 5 dBm, Timing Advance: 0
    RXL-FULL-dl:  -47 dBm, RXL-SUB-dl:  -47 dBm RXQ-FULL-dl: 0, RXQ-SUB-dl: 0
    RXL-FULL-ul:  -47 dBm, RXL-SUB-ul:  -47 dBm RXQ-FULL-ul: 0, RXQ-SUB-ul: 0
BTS 0, TRX 1, Timeslot 7, Lchan 0: Type TCH_F
  Connection: 1, State: ACTIVE
  BS Power: 0 dBm, MS Power: 23 dBm
  Channel Mode / Codec: FR or HR
  Subscriber:
    ID: 4, Authorized: 1
    Extension: 05831234567
    IMSI: 515032919099978
    Use count: 2
  Bound IP: X.X.X.X Port 16384 RTP_TYPE2=0 CONN_ID=0
  Measurement Report:
    Flags:
    MS Timing Offset: 0
    L1 MS Power: 5 dBm, Timing Advance: 0
    RXL-FULL-dl:  -47 dBm, RXL-SUB-dl:  -47 dBm RXQ-FULL-dl: 4, RXQ-SUB-dl: 5
    RXL-FULL-ul:  -47 dBm, RXL-SUB-ul:  -47 dBm RXQ-FULL-ul: 7, RXQ-SUB-ul: 7
OpenBSC#


Ongoing Call Logs:

OpenBSC# show lchan summary
BTS 0, TRX 1, Timeslot 6 TCH/F, Lchan 0, Type TCH_F, State ACTIVE - L1 MS Power: 5 dBm RXL-FULL-dl:  -47 dBm RXL-FULL-ul:  -47 dBm
BTS 0, TRX 1, Timeslot 7 TCH/F, Lchan 0, Type TCH_F, State ACTIVE - L1 MS Power: 5 dBm RXL-FULL-dl:  -47 dBm RXL-FULL-ul:  -47 dBm
OpenBSC#


Osmo-BTS current config:

e1_input
 e1_line 0 driver ipa
 e1_line 0 port 0
 no e1_line 0 keepalive
phy 0
 osmotrx ip local 127.0.0.1
 osmotrx ip remote 127.0.0.1
 no osmotrx ms-power-loop
 osmotrx base-port local 5800
 osmotrx base-port remote 5700
 osmotrx fn-advance 20
 osmotrx rts-advance 5
 instance 0

  osmotrx rx-gain 0
  osmotrx tx-attenuation 13
  osmotrx maxdly 0

 instance 1

  osmotrx rx-gain 0
  osmotrx tx-attenuation 10
  osmotrx maxdly 0

bts 0
 band GSM900
 ipa unit-id 1000 0
 oml remote-ip x.x.x.x
 rtp jitter-buffer 100
 paging queue-size 200
 paging lifetime 0
 uplink-power-target -75
 gsmtap-sapi ccch
 gsmtap-sapi pdtch
 min-qual-rach 50
 min-qual-norm -5
 max-ber10k-rach 1707
 trx 0
  power-ramp max-initial 0 mdBm
  power-ramp step-size 2000 mdB
  power-ramp step-interval 1
  ms-power-control dsp
  phy 0 instance 0
 trx 1
  power-ramp max-initial 0 mdBm
  power-ramp step-size 2000 mdB
  power-ramp step-interval 1
  ms-power-control dsp
  phy 0 instance 1


Osmo-Nitb Current Config:

root at ubuntu:/etc/osmocom# cat osmo-nitb.cfg
!
log stderr
  logging filter all 1
  logging color 1
  logging print category 0
  logging timestamp 1
  logging level all everything
  logging level rll notice
  logging level cc notice
  logging level mm notice
  logging level rr notice
  logging level rsl notice
  logging level nm info
  logging level mncc notice
  logging level pag notice
  logging level meas notice
  logging level sccp notice
  logging level msc notice
  logging level mgcp notice
  logging level ho notice
  logging level db notice
  logging level ref notice
  logging level gprs debug
  logging level ns info
  logging level bssgp debug
  logging level llc debug
  logging level sndcp debug
  logging level nat notice
  logging level ctrl notice
  logging level smpp debug
  logging level filter debug
  logging level ranap debug
  logging level sua debug
  logging level pcu debug
  logging level lglobal notice
  logging level llapd notice
  logging level linp notice
  logging level lmux notice
  logging level lmi notice
  logging level lmib notice
  logging level lsms notice
  logging level lctrl notice
  logging level lgtp notice
  logging level lstats notice
  logging level lgsup notice
  logging level loap notice
  logging level lss7 notice
  logging level lsccp notice
  logging level lsua notice
  logging level lm3ua notice
  logging level lmgcp notice
!
stats interval 5
!
line vty
 no login
!
e1_input
 e1_line 0 driver ipa
 e1_line 0 port 0
 no e1_line 0 keepalive
network
 network country code 10
 mobile network code 1
 short name testnetwork
 long name testnetwork
 auth policy closed
 authorized-regexp .*
 location updating reject cause 13
 encryption a5 0
 neci 1
 paging any use tch 0
 rrlp mode none
 mm info 1
 handover 0
 handover window rxlev averaging 10
 handover window rxqual averaging 1
 handover window rxlev neighbor averaging 10
 handover power budget interval 6
 handover power budget hysteresis 3
 handover maximum distance 9999

 timer t3113 60

 timer t3103 1

 timer t3101 10

 timer t3109 1

 timer t3122 10

 timer t3105 1

 dyn_ts_allow_tch_f 0
 subscriber-keep-in-ram 1

 bts 0
  type sysmobts
  band GSM900
  cell_identity 1
  location_area_code 1
  base_station_id_code 63
  ms max power 23
  cell reselection hysteresis 4
  rxlev access min 0
  periodic location update 30
  radio-link-timeout 32
  channel allocator descending
  rach tx integer 9
  rach max transmission 7
  channel-descrption attach 1
  channel-descrption bs-pa-mfrms 5
  channel-descrption bs-ag-blks-res 1
  early-classmark-sending forbidden
  ip.access unit_id 1000 0
  oml ip.access stream_id 255 line 0
  neighbor-list mode automatic
  codec-support fr hr efr amr
  amr tch-h modes 0
  amr tch-h start-mode auto
  gprs mode gprs
  gprs 11bit_rach_support_for_egprs 0
  gprs routing area 1
  gprs network-control-order nc0
  gprs cell bvci 2
  gprs cell timer blocking-timer 3
  gprs cell timer blocking-retries 3
  gprs cell timer unblocking-retries 3
  gprs cell timer reset-timer 3
  gprs cell timer reset-retries 3
  gprs cell timer suspend-timer 10
  gprs cell timer suspend-retries 3
  gprs cell timer resume-timer 10
  gprs cell timer resume-retries 3
  gprs cell timer capability-update-timer 10
  gprs cell timer capability-update-retries 3
  gprs nsei 101
  gprs ns timer tns-block 3
  gprs ns timer tns-block-retries 3
  gprs ns timer tns-reset 3
  gprs ns timer tns-reset-retries 3
  gprs ns timer tns-test 30
  gprs ns timer tns-alive 3
  gprs ns timer tns-alive-retries 10
  gprs nsvc 0 nsvci 101
  gprs nsvc 0 local udp port 23000
  gprs nsvc 0 remote udp port 23000
  gprs nsvc 0 remote ip 127.0.0.2
  gprs nsvc 1 nsvci 0
  gprs nsvc 1 local udp port 0
  gprs nsvc 1 remote udp port 0
  gprs nsvc 1 remote ip 0.0.0.0
  no force-combined-si

  trx 0
   rf_locked 0
   arfcn 122
   nominal power 0
   rsl e1 tei 0

   timeslot 0
    phys_chan_config CCCH+SDCCH4
    hopping enabled 0
   timeslot 1
    phys_chan_config SDCCH8
    hopping enabled 0
   timeslot 2
    phys_chan_config SDCCH8
    hopping enabled 0
   timeslot 3
    phys_chan_config TCH/F
    hopping enabled 0
   timeslot 4
    phys_chan_config TCH/F
    hopping enabled 0
   timeslot 5
    phys_chan_config TCH/F
    hopping enabled 0
   timeslot 6
    phys_chan_config TCH/F
    hopping enabled 0
   timeslot 7
    phys_chan_config TCH/F
    hopping enabled 0
  trx 1
   rf_locked 0
   arfcn 42
   nominal power 0
   rsl e1 tei 0

   timeslot 0
    phys_chan_config CCCH+SDCCH4
    hopping enabled 0
   timeslot 1
    phys_chan_config TCH/F
    hopping enabled 0
   timeslot 2
    phys_chan_config TCH/F
    hopping enabled 0
   timeslot 3
    phys_chan_config TCH/F
    hopping enabled 0
   timeslot 4
    phys_chan_config TCH/F
    hopping enabled 0
   timeslot 5
    phys_chan_config TCH/F
    hopping enabled 0
   timeslot 6
    phys_chan_config TCH/F
    hopping enabled 0
   timeslot 7
    phys_chan_config TCH/F
    hopping enabled 0
mncc-int
 default-codec tch-f fr
 default-codec tch-h amr
nitb
 subscriber-create-on-demand

 subscriber-create-on-demand random 100000 199999
 no assign-tmsi
smpp
 local-tcp-ip 127.0.0.1 2776
 system-id password
 policy closed
 smpp-first
 esme admin
  password password
  default-route
Rootubuntu:/etc/osmocom#






Regards,

Sonny Lafuente | Systems Engineer | Entropy Solution Philippines
Mobile: +639985365206 | Office: 028931781 | Email: sonny.lafuente at entropysolution.com<mailto:sonny.lafuente at entropysolution.com>
Office Address: Unit 2103 Antel Corporate  Centre 121 Valero St. Salcedo Village Makati City Philippines 1227

[cid:936BCCE1-8AAB-4E96-8413-E1075D00DBE3]

Singapore * Philippines
Products:
Gridloc*Intelle*Hype*Lighthouse*Telco Services*Software Development
This email (including any attachment to it) is confidential and intended only for the use of the individual named above and may contain information that is privileged. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email or telephone and destroy the original message (including any attachment to it). Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210729/c1d6090c/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Entropy Logo Email.png
Type: image/png
Size: 57183 bytes
Desc: Entropy Logo Email.png
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210729/c1d6090c/attachment.png>

From keith at rhizomatica.org  Thu Jul 29 17:11:19 2021
From: keith at rhizomatica.org (Keith)
Date: Thu, 29 Jul 2021 12:11:19 -0500
Subject: MS Power Transmit not changing
In-Reply-To: <ED4CEAF9-F7E2-4380-85C6-18DFD91A5CF2@entropysolution.com>
References: <ED4CEAF9-F7E2-4380-85C6-18DFD91A5CF2@entropysolution.com>
Message-ID: <f2b3deca-6ba9-78fb-e4ae-a5362286aac4@rhizomatica.org>


On 29/07/2021 00:33, Sonny Lafuente wrote:
>
>
> the MS power transmit is not changing during ongoing call and the
> value is 5dbm. .
>
[...]
>
> ? ? RXL-FULL-dl: ?-47 dBm, RXL-SUB-dl: ?-47 dBm RXQ-FULL-dl: 0,
> RXQ-SUB-dl: 0
> ? ? RXL-FULL-ul: ?-47 dBm, RXL-SUB-ul: ?-47 dBm RXQ-FULL-ul: 0,
> RXQ-SUB-ul: 0

> uplink-power-target -75

Well, As long as you are getting -47dB on the UL, and the UL power
target is -75dB? the MS is not going to be instructed to increase TX power.

ms max power is the max power the MS uses for initial access to the
cell. After that, the power control kicks in and tells tells the MS to
drop down.

Put some serious attenuation on your UL (or put your MS in a tinfoil bag
or something, so that you get less than your uplink-power-target and see
if MS power increases on your show lchan (or better - configure the
meas-feed and use meas-vis or try using this:
https://gitlab.tic-ac.org/keith/meas_web

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210729/c4ee5073/attachment.htm>

From mauimauer at gmail.com  Fri Jul 30 14:49:25 2021
From: mauimauer at gmail.com (Sebastian Mauer)
Date: Fri, 30 Jul 2021 15:49:25 +0100
Subject: Can't establish calls between two handsets [nanoBTS 165AU]
Message-ID: <CAPy3zgFPmRcKNHC-t7wx22pKnYXnniVxip6yqP_OW-QrezsW6Q@mail.gmail.com>

Hello there,

In my lab I have access to an ip.access nanoBTS 165AU which I have
setup with OsmoBSC.
Sending SMS between my two test handsets (Nokia 105) are working fine,
however it seems there is a problem when making calls. From the logs
it seems the radio is unable
to assign a TCH_F channel.

Any idea what could be causing this and how I would debug this further?

Cheers,
Sebastian

<0003> abis_rsl.c:1533 (bts=0) CHAN RQD: reason: call re-establishment
(ra=0x49, neci=0x01, chreq_reason=0x02)
<000f> lchan_select.c:262
lchan(0-0-0-CCCH_SDCCH4-0)[0xaaaadc4251c0]{UNUSED}: (type=SDCCH)
Selected
<000f> lchan_fsm.c:636
lchan(0-0-0-CCCH_SDCCH4-0)[0xaaaadc4251c0]{WAIT_TS_READY}:
(type=SDCCH) Activation requested: FOR_MS_CHANNEL_REQUEST voice=no
MGW-ci=none type=SDCCH tch-mode=SIGNALLING encr-alg=A5/0 ck=none
<0007> osmo_bsc_sigtran.c:297 Initializing resources for new SCCP
connection to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP...
<0007> osmo_bsc_sigtran.c:343 Opening new SCCP connection (id=4) to
MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP
<0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP COMMON ID
<0007> osmo_bsc_bssap.c:1251 Rx MSC DTAP, SAPI: RR/MM/CC CHAN: 0
<0007> gsm_08_08.c:567 Tx MSC DTAP LINK_ID=0x00
<0007> osmo_bsc_sigtran.c:383 Tx MSC: DTAP
<0007> osmo_bsc_bssap.c:1251 Rx MSC DTAP, SAPI: RR/MM/CC CHAN: 2
<0007> osmo_bsc_bssap.c:1110 Rx MSC UDT BSSMAP PAGING
<0007> osmo_bsc_bssap.c:126 (msc0) Paging:
subscr-IMSI-901700000050081-TMSI-0x06e8ff82: (bts0) Paging on LAC 1
<0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP ASSIGNMENT REQ
<000f> lchan_select.c:262
lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{UNUSED}: (type=TCH_F) Selected
<0011> assignment_fsm.c:570
assignment(msc0-conn4_subscr-IMSI-901700000050080-TMSI-0xbf4aa84d_0-0-2-TCH_F-0)[0xaaaadc43e930]{WAIT_LCHAN_ACTIVE}:
(bts=0,trx=0,ts=2,ss=0) Starting Assignment: chan_mode=SPEECH_V1,
chan_type=FR, aoip=yes MSC-rtp=192.168.148.159:4074 (osmux=no)
<000f> lchan_fsm.c:636
lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{WAIT_TS_READY}: (type=TCH_F)
Activation requested: FOR_ASSIGNMENT voice=yes MGW-ci=new type=TCH_F
tch-mode=SPEECH_V1 encr-alg=A5/0 ck=none
<000f> lchan_fsm.c:81
lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{WAIT_RLL_RTP_ESTABLISH}:
(type=TCH_F) lchan-rtp failure in state WAIT_IPACC_CRCX_ACK: Received
NACK on IPACC CRCX
<000f> lchan_fsm.c:81
lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{WAIT_RLL_RTP_ESTABLISH}:
(type=TCH_F) lchan allocation failed in state WAIT_RLL_RTP_ESTABLISH:
Failed to setup RTP stream: LCHAN_EV_RTP_ERROR in state
WAIT_RLL_RTP_ESTABLISH

<000f> lchan_fsm.c:116
lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{WAIT_RLL_RTP_ESTABLISH}:
(type=TCH_F) Signalling Assignment FSM of error (lchan allocation
failed in state WAIT_RLL_RTP_ESTABLISH: Failed to setup RTP stream:
LCHAN_EV_RTP_ERROR in state WAIT_RLL_RTP_ESTABLISH
                )
<0011> assignment_fsm.c:821
assignment(msc0-conn4_subscr-IMSI-901700000050080-TMSI-0xbf4aa84d_0-0-2-TCH_F-0)[0xaaaadc43e930]{WAIT_RR_ASS_COMPLETE}:
(bts=0,trx=0,ts=2,ss=0) Assignment failed in state
WAIT_RR_ASS_COMPLETE, cause RADIO INTERFACE MESSAGE FAILURE: Failed to
activate lchan (bts=0,trx=0,ts=2,ss=0)
<0007> osmo_bsc_sigtran.c:379 Tx MSC: BSSMAP: ASSIGNMENT FAIL
<0011> assignment_fsm.c:148
assignment(msc0-conn4_subscr-IMSI-901700000050080-TMSI-0xbf4aa84d_0-0-2-TCH_F-0)[0xaaaadc43e930]{WAIT_RR_ASS_COMPLETE}:
(bts=0,trx=0,ts=2,ss=0) Assignment failed
<0007> osmo_bsc_bssap.c:1251 Rx MSC DTAP, SAPI: RR/MM/CC CHAN: 2
<0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP CLEAR COMMAND
<0007> osmo_bsc_sigtran.c:379 Tx MSC: BSSMAP: CLEAR COMPLETE
<0005> paging.c:84 (bts=0) Going to send paging commands:
subscr-IMSI-901700000050081-TMSI-0x06e8ff82 for ch. type 0 (attempt 0)
<000f> gsm_04_08_rr.c:1021
lchan(0-0-0-CCCH_SDCCH4-0)[0xaaaadc4251c0]{WAIT_BEFORE_RF_RELEASE}:
(type=SDCCH) Got data in non active state, discarding.
<0005> paging.c:84 (bts=0) Going to send paging commands:
subscr-IMSI-901700000050081-TMSI-0x06e8ff82 for ch. type 0 (attempt 1)
<0005> paging.c:84 (bts=0) Going to send paging commands:
subscr-IMSI-901700000050081-TMSI-0x06e8ff82 for ch. type 0 (attempt 2)
<0003> abis_rsl.c:1533 (bts=0) CHAN RQD: reason: answer to paging
(ra=0x9f, neci=0x01, chreq_reason=0x01)
<000f> lchan_select.c:262
lchan(0-0-0-CCCH_SDCCH4-1)[0xaaaadc425390]{UNUSED}: (type=SDCCH)
Selected
<000f> lchan_fsm.c:636
lchan(0-0-0-CCCH_SDCCH4-1)[0xaaaadc425390]{WAIT_TS_READY}:
(type=SDCCH) Activation requested: FOR_MS_CHANNEL_REQUEST voice=no
MGW-ci=none type=SDCCH tch-mode=SIGNALLING encr-alg=A5/0 ck=none
<0005> paging.c:84 (bts=0) Going to send paging commands:
subscr-IMSI-901700000050081-TMSI-0x06e8ff82 for ch. type 0 (attempt 3)
<0007> osmo_bsc_sigtran.c:297 Initializing resources for new SCCP
connection to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP...
<0007> osmo_bsc_sigtran.c:343 Opening new SCCP connection (id=5) to
MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP
<0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP COMMON ID
<0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP CLEAR COMMAND
<0007> osmo_bsc_sigtran.c:379 Tx MSC: BSSMAP: CLEAR COMPLETE
<0003> abis_rsl.c:1533 (bts=0) CHAN RQD: reason: answer to paging
(ra=0x88, neci=0x01, chreq_reason=0x01)
<000f> lchan_select.c:262
lchan(0-0-0-CCCH_SDCCH4-0)[0xaaaadc4251c0]{UNUSED}: (type=SDCCH)
Selected
<000f> lchan_fsm.c:636
lchan(0-0-0-CCCH_SDCCH4-0)[0xaaaadc4251c0]{WAIT_TS_READY}:
(type=SDCCH) Activation requested: FOR_MS_CHANNEL_REQUEST voice=no
MGW-ci=none type=SDCCH tch-mode=SIGNALLING encr-alg=A5/0 ck=none
<0007> osmo_bsc_sigtran.c:297 Initializing resources for new SCCP
connection to MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP...
<0007> osmo_bsc_sigtran.c:343 Opening new SCCP connection (id=6) to
MSC 0: RI=SSN_PC,PC=0.23.1,SSN=BSSAP
<0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP COMMON ID
<0007> osmo_bsc_bssap.c:1147 Rx MSC DT1 BSSMAP CLEAR COMMAND
<0007> osmo_bsc_sigtran.c:379 Tx MSC: BSSMAP: CLEAR COMPLETE


From pespin at sysmocom.de  Fri Jul 30 15:12:58 2021
From: pespin at sysmocom.de (Pau Espin Pedrol)
Date: Fri, 30 Jul 2021 17:12:58 +0200
Subject: Can't establish calls between two handsets [nanoBTS 165AU]
In-Reply-To: <CAPy3zgFPmRcKNHC-t7wx22pKnYXnniVxip6yqP_OW-QrezsW6Q@mail.gmail.com>
References: <CAPy3zgFPmRcKNHC-t7wx22pKnYXnniVxip6yqP_OW-QrezsW6Q@mail.gmail.com>
Message-ID: <06b0bc30-bdaa-daff-ae1e-ca0b4cc604b7@sysmocom.de>

Hi,

On 7/30/21 4:49 PM, Sebastian Mauer wrote:

> lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{WAIT_RLL_RTP_ESTABLISH}:
> (type=TCH_F) lchan-rtp failure in state WAIT_IPACC_CRCX_ACK: Received
> NACK on IPACC CRCX


You received a IPACC CRCX NACK from nanoBTS as an answer to IPACC_CRCX 
(that's sent osmoBSc->nanoBTS to configure the RTP stream on the nanoBTS 
side).
So it seems the nanoBTS is not liking the configuration you are 
requesting to it?
Providing a pcap file containing Abis RSL would help understand better 
by looking at what the IPACC CRCX contains.
I'd bet you are passing a loopback address to it or something similar, 
probably due to wrong osmo-mgw configuration.

-- 
- 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


From mauimauer at gmail.com  Fri Jul 30 15:51:17 2021
From: mauimauer at gmail.com (Sebastian Mauer)
Date: Fri, 30 Jul 2021 16:51:17 +0100
Subject: Can't establish calls between two handsets [nanoBTS 165AU]
In-Reply-To: <06b0bc30-bdaa-daff-ae1e-ca0b4cc604b7@sysmocom.de>
References: <CAPy3zgFPmRcKNHC-t7wx22pKnYXnniVxip6yqP_OW-QrezsW6Q@mail.gmail.com>
 <06b0bc30-bdaa-daff-ae1e-ca0b4cc604b7@sysmocom.de>
Message-ID: <CAPy3zgFYmGw1bMqv4zm1Zs9S9q8ChKPQMDrmXDvqt7ZushpwXA@mail.gmail.com>

Attached is a dump of the communication between BSC and nanoBTS when
attempting to make a call.
Thanks for helping with figuring this out.

Cheers,
Sebastian

On Fri, 30 Jul 2021 at 16:13, Pau Espin Pedrol <pespin at sysmocom.de> wrote:
>
> Hi,
>
> On 7/30/21 4:49 PM, Sebastian Mauer wrote:
>
> > lchan(0-0-2-TCH_F-0)[0xaaaadc432ba0]{WAIT_RLL_RTP_ESTABLISH}:
> > (type=TCH_F) lchan-rtp failure in state WAIT_IPACC_CRCX_ACK: Received
> > NACK on IPACC CRCX
>
>
> You received a IPACC CRCX NACK from nanoBTS as an answer to IPACC_CRCX
> (that's sent osmoBSc->nanoBTS to configure the RTP stream on the nanoBTS
> side).
> So it seems the nanoBTS is not liking the configuration you are
> requesting to it?
> Providing a pcap file containing Abis RSL would help understand better
> by looking at what the IPACC CRCX contains.
> I'd bet you are passing a loopback address to it or something similar,
> probably due to wrong osmo-mgw configuration.
>
> --
> - 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 --------------
A non-text attachment was scrubbed...
Name: dump_call_abis.pcap
Type: application/octet-stream
Size: 8846 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20210730/0dcba690/attachment.obj>