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? 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 <568...@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
