Hi Matthew, On Mon, Nov 14, 2022 at 09:03:23PM +0000, Matthew H wrote: > I have an ip.access NanoBTS 139U (Part No 139U V 139U V351800). I > believe it is operating on the 1800 MHz although admittedly that's a > guess from the part number. I've not found a definitive way of > confirming the supported band via Telnet or otherwise.
It's ages since I worked with those, so I don't recall. One strategy might be to look for RF filters in the RF frontend on the circuit board _if_ those carried readable part numbers. > I can see the BTS attempting to connect to the BSC, but after the "Set > Radio Carrier Attributes" request from the BSC, the BTS sends a NACK > and the OML link is dropped. > > <0004> abis_nm.c:984 OC=RADIO-CARRIER(02) INST=(00,00,ff): SET > RADIO ATTRIBUTE NACK CAUSE=Message cannot be performed > <0004> osmo_bsc_main.c:226 Got SET RADIO ATTRIBUTE NACK going to > drop the OML links. > > I've grabbed some debug info, you mentioned 'telnet' in the other mail. Are you referring to ipaccess-telnet in that case, i.e. the debug output of the nanoBTS itself? > It's worth noting that ipaccess-config tool also has an issue parsing > the frequency which may well be related: [...] it would be interesting to see a pcap of that. -- - Harald Welte <[email protected]> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
