Skip to content
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

VoLTE don't work #301

Open
Maraticus1 opened this issue Apr 3, 2024 · 15 comments
Open

VoLTE don't work #301

Maraticus1 opened this issue Apr 3, 2024 · 15 comments

Comments

@Maraticus1
Copy link

Hello, @herlesupreeth!
I installed docker_open5gs (open5gs_hss_cx branch) on Ubuntu 22.04.
I used "docker" instruction and "VoLTE and SMS Configuration for docker_open5gs".
I additionally prescribed the "ogstun" and "ogstun2" interfaces because for unknown reason they did not exist initially.
I use external macro BS 4G and UE Xiaomi 12.
I don't see QCI=5 and any SIP packets in wireshark.
Internet working.
dump_open5gs.zip
OPEN5GS_hss_profile
sim_photo
sim_profile
image

@platini2
Copy link
Contributor

platini2 commented Apr 3, 2024

Your sim card doesnt seem to be a VoLTE ISIM. OR at least your programmer isnt. Where are your IMS parameters?

@Maraticus1
Copy link
Author

@platini2
You mean IMS parameters of SIM? Like IMPI, IMPU? I don't write this parameters to SIM. Don't know about availability USIM/ISIM on SIM.
Is it necessary to have ISIM on the SIM card for VoLTE? Or is it possible to work with USIM?
This card support VoLTE in another test Core.
I know that VoLTE can work with USIM by 3GPP TS 23.003, but I don't know does docker_open5gs cx support this mode of operation?

@Maraticus1
Copy link
Author

@herlesupreeth
Can you tell about possibility working OPEN5GScx VoLTE with USIM?
I don't use CoIMS because my mcc/mnc is allowed for VoLTE.

@herlesupreeth
Copy link
Owner

@Maraticus1 Hey, ISIM is not a mandatory requirement for VoLTE to work. USIM is just fine. The UE forms the IMPU and IMPI based on the IMSI and the PLMN of the network.

I dont see UE requesting a PDN connection for "ims" APN in the trace you attached. This mean VoLTE is not activated on the phone

@herlesupreeth
Copy link
Owner

I additionally prescribed the "ogstun" and "ogstun2" interfaces because for unknown reason they did not exist initially.

You dont need to create ogstun and ogstun2 to be created outside of the docker network like you did. They are created inside UPF container.

If you login to container as follows you will see those interface created when you deploy

docker exec -ti upf bash
ip a

@herlesupreeth
Copy link
Owner

herlesupreeth commented Apr 4, 2024

Also, these settings are wrong. You have created IMS APN under SST2 (a different slice), it should be under SST1

image

please remove 00101 from FPLMN when you program the SIM

@Maraticus1
Copy link
Author

@herlesupreeth
Thanks for your help!
I change SST and get QCI=5 and IMS request in signalling.
VoLTE shortcut don't show.
Is it necessary to use CoIMS for a successful VoLTE (mcc=001,mnc=01)?
Why can IMS_SIP_Register be unanswered?

photo1712330042 (1)
photo1712330042 (2)
photo1712330042
qci
1.zip

@helloTkk
Copy link

helloTkk commented Apr 5, 2024

@herlesupreeth Thanks for your help! I change SST and get QCI=5 and IMS request in signalling. VoLTE shortcut don't show. Is it necessary to use CoIMS for a successful VoLTE (mcc=001,mnc=01)? Why can IMS_SIP_Register be unanswered?

photo1712330042 (1) photo1712330042 (2) photo1712330042 qci 1.zip

Hi @Maraticus1, I'm facing similar issue as you, may I have your email or wechat ID please? We can help each other maybe. My email is: tukai2259@gmail.com, we can start from there if it's okay for you.

@herlesupreeth
Copy link
Owner

@Maraticus1 I still dont see UE attempting to attach to ims APN in a proper way (you should NOT select ims APN from APN menu, internet should be selected). I would suggest to use CoIMS app to enable VoLTE

@Maraticus1
Copy link
Author

Maraticus1 commented Apr 9, 2024

@herlesupreeth
Volte work now and calls successful.
Videocall work without sound.
I don't hear the voice in calls.
I attach pcaps by URL (any and ens interfaces) and strange assigned QCI in my BS (QCI duplicated).
https://dropmefiles.com/8bav3
QCI_list
Snipaste_09-04-2024_15-39-29
Snipaste_09-04-2024_15-40-33
Snipaste_09-04-2024_15-41-03
.

@Maraticus1
Copy link
Author

@herlesupreeth
And call usually take long for 1 minute and break.

@Maraticus1
Copy link
Author

This is my pcscf log and rtpengine log.
image
image

@herlesupreeth
Copy link
Owner

In order for video calls to work you need to add the QCI 2 ARP 4 entry for your UEs in the open5gs WebUI

image

@Maraticus1
Copy link
Author

@herlesupreeth
I set this config for HSS profiles.
image
Video work good, but i don't hear audio.
Can this be problem NAT-ipsec in Docker_Open5gs (master branch)?
Or this problem of UE (Xiaomi 13 and Xiaomi 12)?
I have 401 mistake between UE/SMF/PCSCF in dump.
Pcap sent earlier (https://dropmefiles.com/8bav3).
This is route table.
image
And NAT table
image

@herlesupreeth
Copy link
Owner

I dont see any issue in the pcap you uploaded. All the RTP ports are fine and the dedicated bearer has all the correct TFTs.

I would suggest to take a pcap of only the video call (your currently uploaded pcap is very huge and hard to debug which is a video call). i.e. bring down all components, start all components, start wireshark/tcpdump, attach UEs and then attempt video call directly. Send me this pcap

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants