VoNR Guide with open5gs, srsRAN , and Kamilio

[AzeezEbrahim]

hey, 4 days ago kamilio published a video showing their VoNR support, so i wonder if anyone can help to configure it as well.
https://www.kamailio.org/w/2024/04/kamailio-powering-first-live-demo-of-5g-vonr-and-smsonr-with-oss-only/

i followed the steps with sa-vonr-deploy, and removed the checkout commit from the kamilio, but still can't make a call.
what else? what is missing? or is the setup way different than what presented here?

[herlesupreeth]

Hey @AzeezEbrahim the configuration files used in that demo is not made public yet. In this repo, using sa-vonr-deploy.yaml you can successfully perform VoNR registration but calling is not possible since there is no N5 interface to request QoS required for the call.

[AzeezEbrahim]

hey @herlesupreeth
Thank you for your clarification.

Quick question, do they mention when are they going to release the docs for the phone calls? are they even going to in the near future? if so, are you going to write a step by step document about it?

[herlesupreeth]

Quick question, do they mention when are they going to release the docs for the phone calls?

They plan to release the configuration files public once they are done with some level of testing. Not sure when. I am expecting in a month or two max.

are you going to write a step by step document about it?

Definitely yes

[sathyag85]

I am also setting up VONR until registration is successful with the help of SA-vonr-deploy.yaml file. The call is not working because there is no N5 interface to request the QoS required for the call. Please update if the configuration files are available for the above.Thanks.

[JoseVOliveria]

Hello,
I was able to establish a call using the sa-vonr-deploy.yaml file. I did not add any configurations. I used two xiaomi phones with srsran in a USRPB210. I leave the pcap fila attached.

call.pcap.zip

[JoseVOliveria]

Hello, yes it is
Sure.
Archive.zip

[sathyag85]

In your trace, there is no bearer allocation of 5QI = 1 happening during the call..

[JoseVOliveria]

There is no bearer allocation because there is no communication with the PCF for a Session Modification Request. Despite that, using the APN=ims and 5QI=5 the smartphone successfully registers in the IMS network and the call still goes through. To execute the registration we used an android app called Sipnetic.

[anhtrung87vn]

Hi @JoseVOliveria, which Xiaomi phone model and PLMN are you using for VoNR?

[JoseVOliveria]

Hi I was using the Redmi Model:M2007J22G and the PLMN 00101

[herlesupreeth]

For those who are interested in trying out VoNR calling- here is a branch https://github.com/herlesupreeth/docker_open5gs/tree/exp_5g_ims_pyhss which contains the necessary N5 interface implementatio for P-CSCF so that it can talk with PCF. Huge shoutout to @NUCLEAR-WAR for this efforts. Please try it out and let me know if it works

[BurmazDaniel]

@NUCLEAR-WAR dose oai overcome this issue somehow?

UEs connect but when i try to make a call the gnb crashes.

[NR_RRC]   Cant' handle NGAP_ProtocolIE_ID_id_PDUSessionAggregateMaximumBitRate
[NR_RRC]   could not found protocolIEs id 139
[NR_RRC]   index 0, QOS flow 0, 5QI 5 
[NR_RRC]   add NAS info with size 85 (pdusession id 1)
[NR_RRC]   [gNB 0] Frame 0, Logical Channel DL-DCCH, Generate RRCReconfiguration (bytes 99, UE RNTI a397)
[NR_RRC]   UE 1: Receive RRC Reconfiguration Complete message (xid 0)
[NR_RRC]   send message NGAP_PDUSESSION_MODIFY_RESP 
[NR_RRC]   update pdu session 1 
[NR_RRC]   Modify Resp (msg index 0, pdu session index 0, status 2, xid 0): nb_of_pduSessions 1,  pdusession_id 1

[NUCLEAR-WAR]

Try to compile the last version of gNB from srsRAN Repo, it will be less crushing, or use the master branch's gNB it also has the last version.

I just updated the issue on srsRAN Repo with files requested, I hope they can add the support for Modify QoS Sessions

[NUCLEAR-WAR]

and regarding OAI, it also does not support QoS modification, there Repo also not easelly accessible to report the issue

[BurmazDaniel]

@NUCLEAR-WAR thank you. Yes im using the lates commit 4ac5300 for srsRAN, compiled from source. Ive tested quite a lot the vonr and it seems to be more stable using mimo 2x2. The packet ok/nok rate seem to be the same but the vonr dropouts were significantly reduced. Quite an interesting behavior.

[NUCLEAR-WAR]

this is because srsRAN does not know what to do with the modify QoS Request, what is happening is that the device will detach and reattach again, you will see it in the trace als, the last version can hold longer but it has at the end the same fate, sometimes it silently stops working after few requests and need to be restarted .

I provided more logs to the issue in srsRAN, the whole N5 with Kamailio is new, and not been tried before so I was expecting some issues with some elements.

may I ask if you tried a call between two UEs and how was the signalling ? can you provide me with a Trace ?