Hello,

maybe some other IMS guys are able to help more, but in general the authentication in handled in the configuration file of Kamailio by calling various auth functions. You have to spot where those are used and why is responding with 401. Eventually run it with debug=3 in kamailio.cfg to get more verbosity of what it is done in the code.

Also, it may help to check the emails from Franz Edler during January and February on this list, he provided configs and many details about building a prototype IMS platform. See next link and follow up discussion:

- http://lists.sip-router.org/pipermail/sr-users/2016-January/091204.html

Cheers,
Daniel

On 03/02/16 11:58, Cristina Caridi wrote:

Hello,

I'm a new starter of Kamailio (SER). I am using the version 4.4.0-dev6 in a Debian machine.

I've configured all the IMS network elements, the FHoSS and also Boghe IMS/RCS client in a Windows machine.

When an IMS user belonging to my network tries to register and IP SEC mechanism is enabled, the registration flow stops at 401 Unauthorized from S-CSCF -> I-CSCF -> P-CSCF -> client.

The problem is that the HSS in MAA message does not send the SIP-Auth-Data-item that should be cointain the Confidentiality Key and the Integrity Key; so the client is not able to challenge the S-CSCF sending another REGISTER message.

Do you have any suggestions about this? When IP SEC is disabled (by managing client options), the registration works well.

Maybe is there any configuration at HSS level that i'm not considering?

Thank you in advance for your help,

Cristina
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu