Sorry Supreeth for the late reply. I finally got around to make the necessary changes as per your suggestion and test. The issue is resolved. Thanks a lot for your prompt help. Best regards, Shantanu
On Thu, May 30, 2024 at 11:23 AM Shantanu K Roy <[email protected]> wrote: > Thanks Supreeth. > I will let you know once I set this up on my setup and run the tests. > Best regards, > Shantanu > > On Tue, May 28, 2024 at 1:30 PM Supreeth Herle <[email protected]> > wrote: > >> Hi Shantanu, >> >> It looks like Authentication is failing. I dont think sipp supports >> Digest-AKAv1-MD5. Have you ensured that correct (Digest-MD5) Algorithm is >> selected in FHoSS? >> >> Then, restart S-CSCF just in case there is cached registration data and >> give it a try. >> >> Best Regards, >> Supreeth >> >> >> >> On Sun, 26 May 2024 at 20:58, Shantanu K Roy <[email protected]> >> wrote: >> >>> Hi Supreeth, >>> I made necessary changes in the sipp side to put the domain name instead >>> of the IP of the xcscf. Now the SIP registration progresses to the point >>> where the xcscf is challenging sipp with 401 Unauthorized and sipp is >>> responding back with the authentication credentials (e.g for the 1st UE -> >>> [authentication username=001010123456791 >>> aka_OP=0x11111111111111111111111111111111 >>> aka_K=0x8baf473f2f8fd09487cccbd7097c6862 aka_AMF=0x8000];) I took the OP, K >>> and AMF values as programmed in the FHoSS. >>> I am enclosing the pcap and syslog snips for the transaction. >>> Please let me know if any more information is required. >>> Regards, >>> Shantanu >>> >>> >>> On Fri, May 24, 2024 at 11:18 AM Supreeth Herle <[email protected]> >>> wrote: >>> >>>> Hi Shantanu, >>>> >>>> While using sipp to test IMS, I would suggest setting the IP of P-CSCF >>>> as ims.mnc001.mcc001.3gppnetwork.org rather than harcoding the IP >>>> address of the P-CSCF (192.168.50.169). >>>> >>>> Btw, I dont see the Rx signalling in the pcap attached. >>>> >>>> BR, >>>> Supreeth >>>> >>>> On Thu, 23 May 2024 at 21:46, Shantanu K Roy via sr-users < >>>> [email protected]> wrote: >>>> >>>>> Hello, >>>>> We are trying to integrate Kamailio as the IMS server with our 5G core >>>>> emulator by following the steps listed out at >>>>> https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/. In our >>>>> case, we have our own 5G core emulator instead of the Open5GS core. >>>>> We are using sipp scripts to generate the SIP calls. The PCRF >>>>> component of the 5G core is emulated by us and is capable of handling >>>>> Diamater calls from Kamailio over the Rx interface. >>>>> We have got the setup working to the point where the SIP Register >>>>> calls are landing on the PCSCF which in turn is sending out AA Requests to >>>>> PCRF and the PCRF is responding. However there is an internal error in the >>>>> Kamailio log >>>>> "4(3682133) ERROR: ims_qos [ims_qos_mod.c:1305]: w_rx_aar_register(): >>>>> This contact does not exist in PCSCF usrloc - error in cfg file" >>>>> Please help us in identifying if we are missing anything in the >>>>> Kamailio set up. >>>>> The packet capture and syslog excerpts from the VM where Kamailio is >>>>> running are attached; here we are trying to perform SIP Registration for >>>>> three SIP endpoints 001010123456791, 001010123456792 and 001010123456793. >>>>> If there is any additional information required, please let us know. >>>>> Regards, >>>>> Shantanu Kumar Roy >>>>> >>>>> __________________________________________________________ >>>>> Kamailio - Users Mailing List - Non Commercial Discussions >>>>> To unsubscribe send an email to [email protected] >>>>> Important: keep the mailing list in the recipients, do not reply only >>>>> to the sender! >>>>> Edit mailing list options or unsubscribe: >>>>> >>>>
__________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
