-
Notifications
You must be signed in to change notification settings - Fork 18
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
IMS call One way Voice and call disconnect in 3 second not see any PDU modification request with QCI 1 #3
Comments
First of all kamailio P-CSCF does not implement SBI interface towards PCF (N5 interface) so its not possible to have VoNR working. Second, I see you have tried the above setup by disabling the Rx interface flag in kamailio cfg file. Rx interface is a diameter interface in 4G which allows P-CSCF to talk with PCRF in order to create dedicated bearers required for VoLTE call. |
Hi @herlesupreeth thanks for the reply. can you confirm one thing, can we have a VoLte call, with current setup which we are using? kindly let me know where we have to enable it ? |
I dont think so. Since you are using a gNB (5G Radio), your gNB would be connected to SA part of the open5gs core network. And, open5gs does not support fallback mechanism from VoNR to VoLTE as far as I know. If you want to test VoLTE with your setup you need to have eNB (4G Radio) to which UE is connected. |
thanks, very much. is RX interface configuration are ok with above comment Screenshot? is there any IMS open source which currently supporting VoNR? or are you planing to implement SBI interface (N5) for VoNR call? or any way to configure this interface? |
Hi @herlesupreeth @sonu5gc, |
I believe by default RX interface is enabled and are enabled/disabled in pcscf.cfg file.
Sadly none.
No. I stopped working on IMS and currently working on gNB. Its not possible to configure using cfg file rather you would have to put your hands into kamailio C code.
I would not consider the IMS registration as successful unless P-CSCF is able to talk with PCF. From the perspective of SIP signalling, yes, its correct and registration is successful. But that's just one part of the puzzle. And, in order for VoNR call to work, dedicated bearers are needed, which are created when P-CSCF talks with PCF over N5 interface. |
rather you would have to put your hands into kamailio C code. Can you give any idea about this, like which entity code we have to change or modify if i try ? what things must need to modify in code. Much appreciated. |
Its most of the files under the following module
This I cannot tell as I have not read the specification of N5. But if I were to approach the implementation I would start by adding feature to talk HTTP2 to NRF/SCP and send register with it and advertise the NF services. Once this is complete I would move on to next step of implementing the required NF service of N5 interface. |
Issue : IMS call One way Voice and call disconnect in 3 second not see any PDU modification request with QCI 1
Important info:- UE:- Samsung S21, Oneplus9
GnodeB:- Sercom
Kamalio and Open5GS installed.
Call Connect and UE registration Normal.
All setup are on Same VM kamalio and Open5GS.
Issue reproduce steps:--
Register both UE, Call from Oneplus UE to Samsung>>> than Call is connected>> Receive at Samsung UE>>> Observe the Issue one way sound oneplus have voice but Samsung no voice>>> and call got disconnected.
Expected behavior:- Call connect successful and RTP packets flow normally. call should not disconnect with in 3 seconds.
download logs from Here :-- https://github.com/open5gs/open5gs/files/12122557/onewayvoiceissue.zip
The text was updated successfully, but these errors were encountered: