Hello,
I have faced an issue when mhomed parameter working well only for udp
destinations in systems with multiple network interfaces.
If kamailio forward call to the UDP destination, mhomed option chooses the
correct Via and the correct network interface for sending.
But if the destination is tls, mhomed chooses first described in
configuration file "listen=" interface and use this IP in Via header
Network routes in the system are correct and "ip r get IP" returns the
correct route and interface.
Should mhomed work with tcp/tls or is this impossible with TCP design?
--
Aidar
Hi, everyone!
In one sentence, I want to know how to how to add the shared key (aka. K, Ki) used by AKA algorithm to Kamailio.
I’m using Kamailio as an IMS server to test my own 5G Core. As you know, UE would send its first SIP Registration message to Kamailio with its IMPI and IMPU, then Kamailio should use the shared key to proceed AKA algorithm to generate the authentication vector, then respond UE with 401 unauthorized message to challenge the UE. I’ve done my research and I still can’t figure out how to let Kamailio know this shared key. And when I was doing my test, it seems like Kamailio used some default key to generate the auth vector.
Could anybody help me? I’ve been stuck here for days.
