Can I fire REGISTER's w/o authentication but then process 401/407 in a failure route and somehow tell UAC module which ha1 to use? Keeping all the timers functionality and uac_reg_lookup feature? Or at least if I process 401/407 in a failure_route and manually create the Auth header, will UAC module still be able to keep track of the registrations?

The failure_route is not executed for local generated requests, only for requests received and then forwarded by kamailio.

You can try to play with event_route[tm:local-request] -- if there is an Authorization header, remove it and add another one that you build yourself with the ha1 value, using eventually some embedded scripting such as Lua or Python. In uac_reg table set some dummy value for the plain text password.

But could get complex -- like I said in the previous email, I find it better to extend the module.

Cheers,
Daniel

Anyway, an in-memory registration table is preferred as I'm using an API which will push all trunks inside Kamailio... Using a database is the worst scenario in my case.
________________________________

Regards,

Alexandru Covalschi

VoIP Engineer and System Administrator
tel: +37367367850

28 авг. 2019 г., в 16:15, Alexandru Covalschi <568691@gmail.com> написал(а):

Hello, 

I'm trying to make Kamailio to SIP register on a remote server. However storing plaintext password looks very unsecure.

Is there a possibility to store password for uac module using ha1 hash instead of the plaintext password? I see there's a row for it in the database, but in the source code it's not used and it seems i can't neither use it in db neither set up in-memory as avp.

Maybe there's a workaround to directly access the in-memory uac registration htable?

________________________________

Regards,

Alexandru Covalschi

VoIP Engineer and System Administrator
tel: +37367367850

_______________________________________________
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