Vonr issue in samsung mobile about docker_open5gs HOT 32 OPEN

Thanks for trying out the calling. Looks like Samsung is not picky about having a dedicated bearer for IMS call. Regarding VoLTE icon seen rather than VoNR, its upto the device settings. From the IMS perspective in that pcap attached I see a successful registration.

Also, the only identifier to know the RAT type is P-Access-Network-Info sent by UE and its sent as follows. IMS does not have any RAT type info unless UE sends it.

from docker_open5gs.

Thankyou for response. i need to know whether EPS fall back happened while making a call in 5G SA mode ? Please correct my understanding wrong.

from docker_open5gs.

i need to know whether EPS fall back happened while making a call in 5G SA mode ?

I dont think its doing EPS fallback since I dont see any NGAP packets when a IMS call is initiated. But honestly, there shouldn't be any difference between a IMS call over 4G or 5G.

from docker_open5gs.

from docker_open5gs.

No NGAP since you are attempting the call over 5G network and there are no 4G elements. So the only point of contact for gNB is AMF to which it talks NGAP.

from docker_open5gs.

from docker_open5gs.

hi @herlesupreeth samsung mobile to samsung mobile voice call is working fine but while making voice call from one plus mobile to Samsung mobile call is automatically dropped after 5 seconds.

Meanwhile i am not able to make voice call from samsung mobile to one plus mobile.

i am using latest commit only commit cb65f58 in open5gs_hss_cx branch

vonr_27_11_1.zip

as seen scp log timer expired

11/23 10:01:06.217: [sbi] WARNING: NF EndPoint updated [172.22.0.13:7777] (../lib/sbi/context.c:1532)
11/23 10:01:06.217: [sbi] INFO: [860a0150-89b8-41ee-92a4-51ea7388a47e] (NF-discover) NF Profile updated (../lib/sbi/nnrf-handler.c:856)
11/23 10:01:11.003: [sbi] INFO: RST_STREAM received: stream_id=113 (../lib/sbi/nghttp2-server.c:1186)
11/23 10:01:11.003: [sbi] ERROR: on_stream_close_callback() failed (5:STREAM_CLOSED) (../lib/sbi/nghttp2-server.c:1218)
11/23 10:01:11.003: [sbi] ERROR: Connection timer expired (../lib/sbi/client.c:533)
11/23 10:01:11.003: [scp] WARNING: response_handler() failed [-3] (../src/scp/sbi-path.c:539)
11/23 10:01:11.003: [sbi] ERROR: stream has already been removed (../lib/sbi/nghttp2-server.c:565)

AMF Logs:

11/23 10:01:06.074: [gmm] INFO: UE SUPI[imsi-001010000000002] DNN[ims] S_NSSAI[SST:1 SD:0xffffff] (../src/amf/gmm-handler.c:1247)
11/23 10:01:06.095: [amf] INFO: [imsi-001010000000002:1:11][0:0:NULL] /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify (../src/amf/nsmf-handler.c:837)
11/23 10:01:06.218: [amf] INFO: [imsi-001010000000002:2:11][0:0:NULL] /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify (../src/amf/nsmf-handler.c:837)
11/23 10:01:10.004: [amf] ERROR: Session has already been removed (../src/amf/amf-sm.c:692)
11/23 10:01:11.003: [sbi] ERROR: Connection timer expired (../lib/sbi/client.c:533)
11/23 10:01:11.003: [sbi] WARNING: ogs_sbi_client_handler() failed [-3] (../lib/sbi/path.c:59)
11/23 10:04:03.054: [amf] INFO: InitialUEMessage (../src/amf/ngap-handler.c:401)
11/23 10:04:03.054: [amf] INFO: [Added] Number of gNB-UEs is now 2 (../src/amf/context.c:2523)
11/23 10:04:03.054: [amf] INFO: RAN_UE_NGAP_ID[4] AMF_UE_NGAP_ID[5] TAC[1] CellID[0x19b0] (../src/amf/ngap-handler.c:562)
11/23 10:04:03.054: [amf] INFO: [suci-0-001-01-0-0-0-0000000001] Unknown UE by SUCI (../src/amf/context.c:1789)
11/23 10:04:03.054: [amf] INFO: [Added] Number of AMF-UEs is now 2 (../src/amf/context.c:1570)
11/23 10:04:03.054: [gmm] INFO: Registration request (../src/amf/gmm-sm.c:1061)
11/23 10:04:03.054: [gmm] INFO: [suci-0-001-01-0-0-0-0000000001] SUCI (../src/amf/gmm-handler.c:157)
11/23 10:04:03.500: [gmm] INFO: [imsi-001010000000001] Registration complete (../src/amf/gmm-sm.c:1993)
11/23 10:04:03.500: [amf] INFO: [imsi-001010000000001] Configuration update command (../src/amf/nas-path.c:612)
11/23 10:04:03.500: [gmm] INFO: UTC [2023-11-23T04:34:03] Timezone[0]/DST[0] (../src/amf/gmm-build.c:558

from docker_open5gs.

hi @herlesupreeth we try with one plus mobile to one plus mobile voice call is not establish but one plus to samsumg mobile working . please give some idea

from docker_open5gs.

Hey, I havent had time to take a look at the traces. But as I mentioned earlier the calling should not have worked because there is no way to enforce QoS for the VoNR call i.e dedicated bearer is not created for the call due to lack of N5 interface.

The reason call between Samsung devices worked because i guess it was not picky about having a dedicated bearer for the call. And the call went over default bearer which doesnt guarantee QoS

from docker_open5gs.

Thankyou @herlesupreeth

Please find the log for one plus to one plus call failure log . Please help me to fix issue once you free or give some idea .

Uploading 1+to1+_call_failure_log.zip…

from docker_open5gs.

hi @herlesupreeth as we analysis the wireshark log getting the precondition failure.When we see inside the we find out the media bearer loss.Can you please help us to Know the root cause for the issue.

1+to1+_call_failure_log.zip

We have some Queries:

1.We are enabling the developer mode for establishing the call.Will vonr will support ?
2.For Oneplus 9 we are using for Android 13(Latest update).Will it support it ?
3.Can we capture the logs when enabling developer mode through wireshark ?

Thank you,

from docker_open5gs.

When we see inside the we find out the media bearer loss.Can you please help us to Know the root cause for the issue.

This is what I mentioned earlier :) Its not the issue of the phone rather kamailio IMS does not support N5 interface in order to provision bearers for VoNR call. The registration works because it does not require dedicated bearers to be setup like its needed for VoNR call. This cant be supported in kamailio IMS easily and involves some effort

1.We are enabling the developer mode for establishing the call.Will vonr will support ?

I think it should support. As long as UE is registering with IMS (i.e. sending SIP REGISTER) then it does support VoNR

2.For Oneplus 9 we are using for Android 13(Latest update).Will it support it ?

It depends completely on the settings on the phone

3.Can we capture the logs when enabling developer mode through wireshark ?

Depends on the chipset in the phone. If its a Qualcomm based chipset then you can capture IP traffic (not the radio packet such as L1, L2 logs) using QCSuper (github repo) or scat (github repo). But if you want L1, L2 logs then it wont be in wireshark format rather in the form of QXDM logs which is proprietary format and need to buy tools form Qualcomm to decode.

If its Mediatek chipset then you can capture logs but not sure what format its in

from docker_open5gs.

HI @herlesupreeth sorry to disturb you.

1. In samsung device i am able to make voice call in 5G SA that means N5 interface established correct . Please correct my understanding is wrong .

from docker_open5gs.

In samsung device i am able to make voice call in 5G SA that means N5 interface established correct . Please correct my understanding is wrong .

N5 interface is a control plane interface between kamailio P-CSCF and PCF. open5gs PCF supports this interface but kamailio P-CSCF does not. So it was never established even in the case of Samsung device. Its just that Samsung phones did not case whether a dedicated/media bearer was created or not for VoNR call whereas OnePlus phone cares about it. Setting a media bearer is only way to guarantee QoS for VoNR call

from docker_open5gs.

Hi @herlesupreeth thank you for detailed information.

Please give some idea or reference link or any document to change in the code so that we will try to implement code for establishing VoNR call.

from docker_open5gs.

Hey, unfortunately its not straightforward and few lines of change. All I can suggest are the following

1. You can take a look at https://kamailio.org/docs/modules/5.7.x/modules/http_async_client.html module and use in kamailio cfg file of P-CSCF to send the required SBI message and handle the response
2. Since the above module is only HTTP you would need to have nginx to do the talking from HTTP2<-->HTTP since open5gs only support HTTP2

For point 1 you would need to refer to the spec

from docker_open5gs.

Hi @herlesupreeth
As you suggested earlier to change in the config file and need to see the sbi messages.I have seen in the
specification for sbi message:
https://www.etsi.org/deliver/etsi_ts/123500_123599/123502/15.02.00_60/ts_123502v150200p.pdf
https://www.etsi.org/deliver/etsi_ts/129500_129599/129513/16.05.00_60/ts_129513v160500p.pdf-this is to know communication between p-cscf and pcf.
https://www.etsi.org/deliver/etsi_ts/129500_129599/129514/15.04.00_60/ts_129514v150400p.pdf-for the communication between af and pcf.

I have some queries:
1.I have seen that in docker file that cloning is happening but i am not able to see the c file inside that.Is there anything we need to change in docker file so that we can see those files.
2.How IMS is connected to 5G Core?
3.Can you give some information about nginx ?

As I am new to this project.Please correct me if I am wrong.

Thank you in Advance.

from docker_open5gs.

Hey @VAyushgupta

I have seen that in docker file that cloning is happening but i am not able to see the c file inside that.Is there anything we need to change in docker file so that we can see those files.

Docker file is cloning the repo which has C code. So you would have to fork the kamailio repo and add your features and modify the github URL in the docker file to your forked repo.

How IMS is connected to 5G Core?

Through the docker networking. I am not sure whether I answered your question. If not please elaborate.

Can you give some information about nginx ?

Rather than using nginx you can follow as mentioned below by the maintainer of kamailio

If it is about a HTTP2 server, I added microhttpd module:

• https://www.kamailio.org/docs/modules/devel/modules/microhttpd.html

which uses libmicrohttpd and I expect it supports HTTP2, but for the moment, I haven't tested it.

An alternative would be to use embedded Python3 (via KEMI plus evrexec module to instantiate a HTTP server using python library.

For http client, there are http_client and http_async_client modules, the use libcurl, which should support http2, not sure if the modules set some restriction on it, but if they do, I guess it can be changed. Also for http client, the KEMI with embedded Python can be a variant.

Overall, I think Kamailio has the needed components, maybe some tuning is still required.

from docker_open5gs.

Thank you for the response @herlesupreeth .

I have some more queries:

1.I have not seen any message between the AF and PCF inside the code. Should we need to implement the api for the message between them.
I am referring spec:
https://www.etsi.org/deliver/etsi_ts/129500_129599/129514/16.05.00_60/ts_129514v160500p.pdf

Please correct me if I am wrong.

from docker_open5gs.

1.I have not seen any message between the AF and PCF inside the code. Should we need to implement the api for the message between them.
I am referring spec:

I am not sure which code you are referring here. The AF needs to send request for Policy Authorization and PCF needs to reply. The replying part of PCF has been implemented in open5gs as far as I know.

from docker_open5gs.

Thank you for the response @herlesupreeth.

from docker_open5gs.

Hi @herlesupreeth,

Sorry i have misinterpretation earlier. As per my understanding we just need to change only in the p-cscf cfg file for vonr as you mention : open5gs PCF supports this interface(N5) but kamailio P-CSCF does not. Correct me if I am wrong.

Or any other changes we require for establishing the vonr call ?

Thank you in Advance.

from docker_open5gs.

open5gs PCF supports this interface(N5) but kamailio P-CSCF does not.

This is correct.

As per my understanding we just need to change only in the p-cscf cfg file for vonr as you mention

This I dont know whether its enough or not to just modify p-cscf cfg file. You may need to put your hands into the kamailio C code

from docker_open5gs.

Thank you for the response @herlesupreeth.

from docker_open5gs.

Hi @herlesupreeth @Sivanesh1992

Case 1: We have test Samsung to Samsung Call with commit 795d8ba (HEAD -> open5gs_hss_cx, origin/open5gs_hss_cx) call is established for both volte and VoNR.But with your latest commit on open5gs_hss_cx branch call is not established.Can you give some input for it.

Case2: We have test Samsung to Oneplus with your latest commit on open5gs_hss_cx branch the precondition issue is resolved but we are getting some other issue regarding delay(408 Request timeout in wireshark).Can you please provide some fix for it.

Wireshark logs:
log_vonr (1).zip

Thank you in advance.

from docker_open5gs.

I checked the pcap and I see that one of the Samsung phone didnt register with IMS thats the reason call between Samsung to Samsung failed. Also, there is something strange, the Samsung phone is using tel:xxxxx format to issue SUBSCRIBE during registration rather than sip:xxx@realm format. Did you change any Samsung IMS settings?

from docker_open5gs.

For Samsung to Samsung, can modify the below parameter in kamailio_pcscf.cfg and give me the pcap of reg+call?

modparam("ims_registrar_pcscf", "is_registered_fallback2ip", 2)

from docker_open5gs.

Thank you for the response @herlesupreeth

As you suggested We have changed in the kamailio_pcscf.cfg but stil Call is not established . As we saw in wireshark logs getting some error indication when UE inital message.

Please look into the kamailio_pcscf.cfg and Wireshark log:

kamailio_pcscf.zip
vonr_samsung_samsung_after_change.zip

from docker_open5gs.

In the above attached pcap, the phone did not even attempt to register with IMS i.e. no SIP REGISTER sent by UE

from docker_open5gs.

Hi @herlesupreeth

Thank you for info. if i am using commit 795d8ba for voice call and sms both working in two samsung mobile but new commit its not working.

so from my understanding it's not a issue in UE side only code we need to check . please correct me if i am wrong .

from docker_open5gs.

ya right.Thank you for let us know @herlesupreeth.

Any suggestion or code change for the issue why ue is not attempting to register with ims network ?

from docker_open5gs.

@Sivanesh1992 can you please post the pcap of voice call when using the latest commits?

Any suggestion or code change for the issue why ue is not attempting to register with ims network ?

@VAyushgupta this is completely upto UE settings

from docker_open5gs.