tree a11218ee9b963be540a306f862beae41bd8ea2ae
parent 96b7a3ec72bbf8e01bda80ee441ac09f5a7c7c9d
author Pau Espin Pedrol <pespin@sysmocom.de> 1685553051 +0200
committer Pau Espin Pedrol <pespin@sysmocom.de> 1685558996 +0200

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