Nanobts will not correctly attach to osmo-bsc.

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

Pau Espin Pedrol pespin at sysmocom.de
Mon Jul 12 09:38:28 UTC 2021


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



More information about the OpenBSC mailing list