Attention is currently required from: laforge, pespin, dexter.

Hello Jenkins Builder, laforge, fixeria, dexter,

I'd like you to reexamine a change. Please visit

https://gerrit.osmocom.org/c/osmo-pcu/+/33119

to look at the new patch set (#2).

Change subject: Use always RFN when handling RACH indications ......................................................................

Use always RFN when handling RACH indications

The previous code was really confusing, passing full FNs as RFNs under certain external conditions, and then assuming the RFN input of rfn_to_fn() function could actually be a FN.

As a result, we had a lot of code behaving slightly different depending on whether the incomding FN from pcuif was filled in by a BSC or a BTS. Avoid this b ehavior differentiation and always assume the most restricted one, aka RFN.

Change-Id: Ib3b5702168195b595711cd0ff32c211b9aba429d --- M src/bts.cpp M src/bts.h M src/pcu_l1_if.cpp M src/pcu_utils.h M tests/tbf/TbfTest.cpp 5 files changed, 45 insertions(+), 23 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/osmo-pcu refs/changes/19/33119/2