VONR : SIP REGISTERING : 403 Forbidden - HSS User Unknown about docker_open5gs

[herlesupreeth]

Please post a pcap file in order to know what/where the issue is. Also, are you using COTS UE or some VoIP UA?

[ismaelabdel]

Thank you for your answer. Here is the PCAP file. We can see that on the SIP register request we do not have the field " Authorization, digest username, realm, uri, algorithm etc..."
I'm using a smartphone Android ZEBRA where i provided a SIP account with username test password test but i don't where to provide the sip account username and password details on my 5G core to synchronize
PCAP FILE SIP.zip

[herlesupreeth]

but i don't where to provide the sip account username and password details on my 5G core to synchronize

If you are using pyHSS, then provide password in Ki field (as per maintainer of pyHSS). I haven't attempted it so let me know if it works for you

[ismaelabdel]

ok i'm going to try it thank you, we have to find the username field also

[herlesupreeth]

Its seems IMSI in the IMS subscriber is the username field

[ismaelabdel]

It works !!! with IMSI in the username field and KI in the password field. Thanks a lot for your answer.
I got the SIP Register status 200 ok.
But the Core send an SCSCF authentication request to the UE. Please find the PCAP file below.
Thank you.
UE SIP REGISTRATION SA-VONR.zip

[herlesupreeth]

But the Core send an SCSCF authentication request to the UE. Please find the PCAP file below.

I dont understand what you mean here. Can you please elaborate?

[ismaelabdel]

Have a look at the pcap and you'll understand

[ismaelabdel]

Hello, i have more detailled news for you.
My UE is almost Registred by SIP. But i get an error you must register with a SCSCF first. it looks like my UE doesn't reach the SCSCF to register. i provide my pcap file and also what i provided in my phone SIP account parameters.
Thank you.
sip registration.zip

[ismaelabdel]

here i give you a pcap file which is successful from an other contributor of your blog. Comparing this one to mine we can see that my P-CSCF is not adressing the I-CSCF to register the UE by the S-CSCF. The 3 network functions are not talking to each other
0403-4.zip

[herlesupreeth]

My UE is almost Registred by SIP. But i get an error you must register with a SCSCF first. it looks like my UE doesn't reach the SCSCF to register. i provide my pcap file and also what i provided in my phone SIP account parameters.
Thank you.
sip registration.zip

I dont see any major issue here except that UE is not sending SUBSCRIBE message with IMPU. And, you are seeing the below packet with 403 Forbidden in for the UE but for one of the previously registered SIP Contact i.e. different ports

Notice that there is 200OK (packet 14) for SIP OPTIONS done in packet 13 because it matches the SIP Contact which is currently registered

[ismaelabdel]

i noticed a difference between the successfull PCAP in the trying part. When the P-CSCF is trying to forward the Register to the I-SCSCF it uses Src. Port 5060 Dest Port 45797. Normally the P-CSCF has to perform the trying to I-CSCF with Src. port 5060 Dest. Port 5060 like in the screenshot below.

[ismaelabdel]

I think it's a routing or a port issue but i don't know where to fix it ? thanks for your help

[ismaelabdel]

here is the PCSCF logs
I noticed that in the first register request by the UE we cannot see the contact header

[ismaelabdel]

do you have some ideas ? i noticed that the PCAP successfull of our partners on your blog had the contact header filled in the first registration request of the UE

[b3c3ll]

@herlesupreeth
Hi
i have also registered with 5G network and both UEs have HD sign on the network!
but as soon as i call the other party, they fail to establish a call!

it works perfecto for 4G!

[b3c3ll]

i can see tel: +7 in the logs while the number starts with 01987...

Nor even sending SMS

[b3c3ll]

@herlesupreeth
Please find the pcap attached!
vonr.zip

[herlesupreeth]

but as soon as i call the other party, they fail to establish a call!

Thats because its not supported :) . The configuration files required to enable VoNR are not yet made public by the developer