On 19 Mar 2015, at 18:38, canuck15 canuc...@hotmail.com wrote:
It looks like auth_check() will work. It seems intelligent enough to scan all
instances of the same domain as long as the username is unique so that should
get things working.
The problem here is that there is a fundamental
i suggest you use tls common names to identify servers behind your
trunks,
-- juha
___
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
Please keep in mind that I have no control over SIP trunk providers.
The vast majority do not allow me to do any of these things as far as I
know. This is something that needs to be solved in Kamailio with
standard user/pass/realm authentication. TLS is not an option for me.
On 3/18/2015
canuck15 writes:
The vast majority do not allow me to do any of these things as far as I
know. This is something that needs to be solved in Kamailio with
standard user/pass/realm authentication. TLS is not an option for me.
then the vast majority don't care a bit about security, which is
It looks like auth_check() will work. It seems intelligent enough to
scan all instances of the same domain as long as the username is unique
so that should get things working.
The problem here is that there is a fundamental difference between
Asterisk and Kamailio authentication. Asterisk
Been struggling with this for awhile now.
So far I am finding it rather difficult to come up with way to
authenticate SIP trunks taking into account all possible scenarios. My
setup is Kamailio combined with Asterisk realtime. Everything is in a
MySQL database. All authentication is done
