SIP registration problem about docker_open5gs HOT 10 OPEN

To add to this:

Right now in the PCRF and PCSCF, I'm seeing the diameter logs where it shows they both correctly connect to each other, but when I check my pcap there is nothing there? What's happening? I even captured the pcap from the individual containers but there is nothing there.

I should elaborate there is nothing between PCRF and PCSCF. I can see the packets exchanged between PCRF and SMF correctly, but PCRF doesn't talk to PCSCF but somehow it says its connected?!

from docker_open5gs.

I'm seeing the following log from PCRF, is it an issue?

Those are just warning which can be ignored.

I took a look at the pcap and I see 401 Unauthorized not answered by the UE which can suggest only one thing, i.e. Ki or OP/OPc value programmed on the SIM or the details entered in pyHSS is wrong

from docker_open5gs.

Ki and OP can be desired value but OPc is a derived value from Ki and OP so your OPc is wrong what you entered in open5gs Web UI

from docker_open5gs.

I verified the Ki and OPc value in the simcard as well as HSS and PyHSS but still no change. It's really odd.

I can see that I'm getting Multimedia-Auth Answer and then 401 Unauthorized but then I get nothing back from the UE.

Could it possibly be a UE or eNB issue? Something I need to change?

Here's the new pcap:
any10.pcap.tar.gz

from docker_open5gs.

Is it possible that my UE doesn't understand the requested Authentication algorithm so it can't respond? Is it possible to change the algorithm from PyHSS?

from docker_open5gs.

I verified the Ki and OPc value in the simcard as well as HSS and PyHSS but still no change.

As I mentioned earlier the value of Ki and OPc is wrong both in your SIM and HSS and pyHSS. Please reprogram your SIM with following details and update the same in HSS and pyHSS. Since you are using COTS UE the Authentication Algorithm should be supported

Ki: 8baf473f2f8fd09487cccbd7097c6862
OP: 11111111111111111111111111111111
OPc: 8E27B6AF0E692E750F32667A3B14605D

from docker_open5gs.

Ki: 8baf473f2f8fd09487cccbd7097c6862
OP: 11111111111111111111111111111111
OPc: 8E27B6AF0E692E750F32667A3B14605D

Thanks I'll try it again. Could I ask how you got these values from the pcap? Or are these just a sample ki and OPc? thanks

from docker_open5gs.

Also shouldn't the SQN value in the HSS database (MongoDB) be matched with the PYHSS database? (mysql)?

from docker_open5gs.

Could I ask how you got these values from the pcap?

OPc is computed based on Ki and OP value. Say you fix Ki: 8baf473f2f8fd09487cccbd7097c6862 and OP: 11111111111111111111111111111111 , you can use this repo to compute OPc - https://github.com/herlesupreeth/kiopcgenerator

Also shouldn't the SQN value in the HSS database (MongoDB) be matched with the PYHSS database? (mysql)?

No need. pyHSS will compensate for it

from docker_open5gs.

@ali-foroughi hope you have solved your issue.
btw: did you have to do something to make the Samsung device initiate the IMS REGISTER process?
Maybe changing the MCC MNC to 42402?

from docker_open5gs.