-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
srsRAN gNB with srsUE over usrp b210 frontends #933
Comments
UL signal is too strong at the gnb. Please try to tune down srsUE tx_gain and gnb rx_gain. |
Hi @pgawlowicz thank you for the reply. Attached are also the latest logs of gnb and srsue and the confs. |
any suggestions on this topic ?? |
could you try to apply the patch from this comment to srsUE, recompile and try again? |
@pgawlowicz Piotr we have done the changes you suggested . and amf in open5gs which is in the same machine with gnb reports this : which seems that amf rejects the srsue . Do you know why? ( And another question is why do i need to restart several times both srsue and gnb in order to have this connection open and not the Scheduling request failed : releasing RRC connection? |
Any suggestions on this? |
it seems the problem is on the core network side, did you add the UE to the subscriber database? |
Issue Description
I'm following the recent tutorial 'srsRAN gNB with srsUE' from here https://docs.srsran.com/projects/project/en/latest/tutorials/source/srsUE/source/index.html. However, the UE (srsue) never obtains an IP from srsgnb staying at this :
Setup Details
e.g. Network configuration, Operation System, Hardware, RF front-end, library and driver versions
Expected Behavior
Cannot use srsue since it is not properly connected to the gnb
Actual Behaviour
[What happens instead e.g. error message]
Seems like UE attempted a scheduling request but didn't receive a response from the gNB. Not sure though
Steps to reproduce the problem
Additional Information
[Any additional information, configuration or data that might be necessary to reproduce the issue]
gnb.log.txt
ue.log.txt
ue.conf.txt
gnb-config.yml.txt
The text was updated successfully, but these errors were encountered: