Hello,

you can also do authentication for requests within dialog. The default kamailio.cfg is doing auth only for initial requests because (at least in the past) there were devices not able to do auth for requests within dialog. You have to execute route(AUTH) for what requests you want to authenticate, being initial or within dialog -- it is your choice, the default kamailio.cfg is more like a starting point for what people need out there.

Cheers,
Daniel

Hello. Have a question on auth and default kamailio.cfg.

Default behavior of kamailio on auth is:

Auth initial requests, delete auth headers before forwarding to next hop.

In-dialog requests are forwarded "as-is" so all auth related info is propagated to uplinks or just another Kami users.

How should it be done correctly or "kamailio-way"? As for now, I just delete auth headers for all in-dialog requests, but I'm not sure it is correct.

I looked how it works on softswitches like Yate. Registers and initial Invites are authenticated, ACK is not authenticated, but all other requests like reINVITE and BYE are.

How is should be done?

Thanks.

--
sent from myMail for Android

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com