|
It seems to try to connect but it is fail. Any idea? I try both docker and build from source. I got the same. |
Replies: 10 comments 9 replies
|
The logs show that registration completes successfully but ~3 seconds later, the gNB sends a UEContextReleaseRequest with cause
|
i am using and however on this machine, I dont have to and to the container restart with It looks for |
|
It seems like your docker-compose has no volume mount for core.yaml and the container uses the config baked into the image, which hardcodes n6.name: "eth0". You may also want to start by running Ella Core from source before using Docker to root out any Docker-related issues. Also, |
|
Hi I now run from source with and I got the same error I am using ethernet now. |
|
Are you using the same gnb config as you were with Open5Gs? I see the Also, the UE context is released by the radio (with causes |
|
Thank you for your help. Now I copy gnb config for open5gs and change only AMF and bind IPs. Same error. here I dont know what it means. |
|
No PDU Session Establishment Request is ever sent by the UE. The gNB is releasing the UE because it lost radio contact, not because the core requested it. This could be an RF issue. Some things to try:
I'm no RF expert though, if you need help on that front I'd recommend engaging the OCUDU team. @ghislainbourgeois do you see something else I'm not seeing? |
|
Hello @fllay , your problem seems very similar to one we just observed with a different user where their SIM card had multiple home network keys configured and the UE used one that was different than the one configured in Ella Core. In Ella Core v1.6, we added the ability to configure multiple Home Network keys using Profile A and B. Can you try upgrading and updating the keys in the Operator page to match what you had in Open5Gs? |
|
Hello @fllay , I acquired a Samsung Galaxy A56 (SM-A566W) to reproduce this problem and I'm pretty sure I identified the root cause: the phone silently stop communicating with the network if the network does not claim to support IMS-VoPS as one if its features during initial context setup. I added the IMS-VoPS flag in #1157. Now the device correctly connects to the network. You can try again with Screenshots
|







Hello @fllay , I acquired a Samsung Galaxy A56 (SM-A566W) to reproduce this problem and I'm pretty sure I identified the root cause: the phone silently stop communicating with the network if the network does not claim to support IMS-VoPS as one if its features during initial context setup.
I added the IMS-VoPS flag in #1157. Now the device correctly connects to the network.
You can try again with
mainand your phone should connect.Screenshots