srs 5G SA UE with Amarisoft gNB/Core: UE Fails 2nd RRC

[Clay-Uhing-APL]

Issue Description

5G SA srsUE runs and connects to Amarisoft gNB. As long as the connection stays active, data can be passed (ping and iPerf). Once the UE goes to RRC idle, I am not able to initiate data connections from the UE or the gNB. srsUE has stdout 'Scheduling Request failed: releasing rrc connection...' with 7 RACH attempts.

Setup Details

Amarisoft Callbox Classic version 2022-03-18, b210 for UE, RF cabled, gps fed into both.
UHD 3.15, srsRAN 22.04, Dell Precision 7510 with Xeon processor running Ubuntu 22.04

Expected Behavior

srsUE should be able to transition from idle to active.

Actual Behaviour

When I try to ping from the gNB or UE after not running data for >10 seconds, the srsUE has stdout 'Scheduling Request failed: releasing rrc connection...' with 7 RACH attempts. The UE is not able to establish an RRC connection

Steps to reproduce the problem

Run 5G SA UE and connect to Amarisoft basestation. Do not run traffic/ping for 10 seconds. Try to ping (Either UE->gNB, or gNB->UE).

Additional Information

srsue.log.txt
enb.cfg.txt
srsue_amarisoft.conf.txt

[andrepuschmann]

Hey @Clay-Uhing-APL, it's a known limitation in the UE. It simply can't get into RRC connected after going to RRC dile. The only thing you can do right now is to increase the inactivity timer in the eNB.

[robertfalkenberg]

Related issue: #862