Configuration is Network In The Box with everything running on a LimeNET Micro (RPi CM3+), using Raspbian 10 and osmocom:latest packages via OBS. UEs can register fine and send/receive SMS, but when I attempt to make a call I see the Rx RR Assignment Failure error from osmo-bsc.
The same hardware and CNI configuration works fine when used with an old RPi image that has packages from late 2019.
Configs and error log attached. Would appreciate any suggestions for things to try.
Regards,
Andrew
//
Hi Andrew,
what I see in your log is that your osmo-bsc receives an Assignment Failure message from the BTS:
lchan(0-0-0-CCCH_SDCCH4-1)[0x18b8650]{ESTABLISHED}: (type=SDCCH) Rx ASSIGNMENT FAILURE
So the reason for the assignment failure is closer to the radio. You may want to look at the BTS logs?
~N
Hi Neels,
On 12/04/2022 15:08, Neels Hofmeyr wrote:
Hi Andrew,
what I see in your log is that your osmo-bsc receives an Assignment Failure message from the BTS:
lchan(0-0-0-CCCH_SDCCH4-1)[0x18b8650]{ESTABLISHED}: (type=SDCCH) Rx ASSIGNMENT FAILURE
So the reason for the assignment failure is closer to the radio. You may want to look at the BTS logs?
Thanks. I didn't spot anything obvious, to me at least. Here are the osmo-bts-trx logs from when call setup fails:
https://gist.github.com/9600/9be4e1bbf09e47d722cd6c8a1e0ef963
Andrew
Hi Andrew,
sorry for the very late response.
It would be best if you could provide a pcap file that contains the relevant interfaces (at least Abis + A, i.e. tcp port 3002 + 3003 and all sctp traffic, as well as udp port 2727), and enable logging to gsmtap on the relevant network elements (osmo-bts + osmo-bsc).
This way a single file contains all of the log output and the signalling in one timeline, and one is able to easily filter log verbosity / subsystems in the wireshark dissector for gsmtap_log.
Also, DTRX DEBUG should really be avoided, unless you are debugging something low level on the TRX<->BTS interface. It spans the logs and increases the CPU usage quite a bit, which might cause new troubles...
In fact, I only see DTRX, DL1P and DL1C in the osmo-bts logs (all related to TRX interface) but not the more relevant sub-systems that handle the RSL / RR / Abis side of things.
-
Andrew Back -
Harald Welte -
Neels Hofmeyr