Kamailio with an IMS client

[Funny-Potato]

Hello, thank you for your amazing project.

I'm trying to set up a simple Kamailio IMS core, so that IMS clients such as Boghe or LinPhone can connect to it and make calls. I've pulled and installed the necassary images for Open5gs and IMS and made the necessary records in PyHSS according to the tutorials provided in the .md file. I've also edited the line in e.164 dns file to account for my custom MCC.

When I open up the IMS client (Boghe) I need to provide the public identity, private identity, and password. For public identity I'm prepending tel:+ to the MSISDN for the IMS subscriber I've added to PyHSS and for the private one I'm prepending it to IMSI. I don't know if this step is correct or not. Also I don't know how I could register and provide the password that Boghe requires without needing to simulate the RAN or UE. I even don't know if such a use case is still feasible with Kamailio and this new HSS.

I've tried following this article from nickvsnetworking and using Ki for password, but I'm still getting the following errors:

 1(43) INFO: {1 17136 REGISTER 18fc0006-7761-0314-5166-2562deec0663 REGISTER} ims_registrar_pcscf [sec_agree.c:270]: cscf_get_security(): No security parameters found
 1(43) INFO: {1 17136 REGISTER 18fc0006-7761-0314-5166-2562deec0663 REGISTER} ims_registrar_pcscf [sec_agree.c:304]: cscf_get_security_verify(): No security-verify parameters found
 1(43) INFO: {1 17136 REGISTER 18fc0006-7761-0314-5166-2562deec0663 REGISTER} cdp [authstatemachine.c:291]: auth_client_statefull_sm_process(): after callback of event 1
94(136) INFO: cdp [authstatemachine.c:291]: auth_client_statefull_sm_process(): after callback of event 7
92(134) ERROR: {1 17136 REGISTER 18fc0006-7761-0314-5166-2562deec0663 REG_AAR_REPLY} <script>: Diameter: AAR failed on subscription to signalling

I would appreciate it if someone could help me fix this issue. I would also appreciate any help with regards to quickly setting up a simple simulated IMS call using Kamailio.

[herlesupreeth]

I've also edited the line in e.164 dns file to account for my custom MCC.

I am not sure why this was required. If you set the MCC value in .env the changes should be automatically taken into effect at all places

For public identity I'm prepending tel:+ to the MSISDN

Can you please remove that + as I dont think its supported in the IMS packed in this repo

Also I don't know how I could register and provide the password that Boghe requires without needing to simulate the RAN or UE

If you purely want to use SIP client and not real UE, you need to disable RX interface in P-CSCF i.e.

change #!define WITH_RX --> ##!define WITH_RX in pcscf.cfg in pcscf folder and redeploy

92(134) ERROR: {1 17136 REGISTER 18fc0006-7761-0314-5166-2562deec0663 REG_AAR_REPLY} <script>: Diameter: AAR failed on subscription to signalling

By disabling Rx, this issue should go away

[Funny-Potato]

I am not sure why this was required. If you set the MCC value in .env the changes should be automatically taken into effect at all places

Oh, I thought I had to do this step manually to convert the ENUM to SIP URI, since the deployed DNS config file had the MCC format for UK commented out as an example and the MCC for Germany configured. I thought maybe I should update it to my MCC. I had set it in the .env file.

If you purely want to use SIP client and not real UE, you need to disable RX interface in P-CSCF i.e.

Before I turned to this repo, I had built Kamailio from scratch using the Open5gs tutorial on this. I had commented out Rx and manually set the vendor ID for Cx in the Diameter peer configurations. I could register the clients fine, but I couldn't make the call. The LIA failed as FHoSS couldn't find the only S-SCSF. I figured maybe there is a problem between the old FHoSS using jdk7 and the newer versions of Kamailio. Then I switched to this modern dockerized repo with PyHSS, but I don't know what I should enter for password in the legacy IMS clients and how to configure/provision it in PyHSS.

I will try your suggestions tomorrow when I have time and get back to you. Thank you very much for your attention. 🙏🙏

[Funny-Potato]

@herlesupreeth I tried your suggestions. I commented out Rx, used tel:MSISDN for public identity and tel:IMSI for private identity, and tried using Ki for password. I'm getting this error on I-CSCF:

 3(37) INFO: {1 15233 REGISTER 4400de1a-7acc-c3e2-2648-d573b174bf95 register} ims_icscf [cxdx_uar.c:73]: create_uaa_return_code(): created AVP successfully : [uaa_return_code]
16(50) INFO: ims_icscf [cxdx_avp.c:140]: cxdx_get_avp(): cxdx_get_server_name: Failed finding avp
16(50) INFO: ims_icscf [cxdx_avp.c:140]: cxdx_get_avp(): cxdx_get_capabilities: Failed finding avp
16(50) INFO: ims_icscf [cxdx_avp.c:140]: cxdx_get_avp(): cxdx_get_result_code: Failed finding avp
16(50) INFO: ims_icscf [cxdx_uar.c:73]: create_uaa_return_code(): created AVP successfully : [uaa_return_code]
16(50) WARNING: tm [t_suspend.c:199]: t_continue_helper(): active transaction not found

[Funny-Potato]

capture1.zip

[herlesupreeth]

I see the following result code in reply from pyhss. So you have not configured the IMSI in the pyhss correctly (same for second client as well)

[Funny-Potato]

I'm sorry some things got tangled up. Please inspect this one. I think the key, opc, or the authentication algorithm is causing the issue.
capture_corrected.zip

[herlesupreeth]

Yes, I see the authentication failing. Is the MNC you are using 010 or is it only two digits 10 ?

[Funny-Potato]

I noticed the testbed automatically generates links where it prepends the 0 to the MNC so I was entering the 0 in my client.

I changed the MNC to 010 in my .env per your suggestion before it was solved. Thanks for you help.

[Funny-Potato]

If anyone else is looking to solve this issue, I tried using the Linphone client instead and the Ki for password and the call got through. I think it's because it supports AKAv1-MD5.

[simranku]

Hi @Funny-Potato , is this a IMS call with linphone client or simple VOIP call ? Could you please provide the pcap file for this call and changes required at Kamalio.

Thanks!