TRX is not responding error message

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

Harald Welte laforge at gnumonks.org
Thu Dec 16 15:39:54 UTC 2010


On Thu, Dec 16, 2010 at 03:49:06PM +0100, Peter Hasse wrote:
> <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff)
> Failure Event Report Type=processing failure Severity=warning level
> failure
> <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff)
> Failure Event Report Type=processing failure Severity=warning level
> failure
> <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff)
> Failure Event Report Type=processing failure Severity=warning level
> failure

have you ever looked at those event reports using the abis_oml wireshark
dissector from openbsc.git/wireshark/ ?

this should give you some more information than just the BSC log.

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




More information about the OpenBSC mailing list