tree da4529c9c1ae40c13262432f27e0f9e8abcb5706
parent d686a8a54873eb61fae7d55cb001378dae3fbd7d
author Pau Espin Pedrol <pespin@sysmocom.de> 1540406176 +0200
committer Pau Espin Pedrol <pespin@sysmocom.de> 1541521377 +0000

bts: f_est_dchan: verify Chan Rqd originated by RACH arrives on RSL

We cannot notify RSL Emulation layer about expecting a specific FN
(during ts_RSLDC_ChanRqd) because we only know the FN after sending the
RACH request, and since notification to RSL Emulation happens async, it
can happen (verified) that ChanRqd message from BTS arrives and is
handled before we register the RACH req into the ConnectionTable.

Change-Id: I438fd3ee82d88498d928dbcc89ce9bd80d37ab64