You can still do that with mod_xml_curl Freeswitch will give your server side script all the details about the authentication so you can decide how to handle them. This may include checking them against a database table, or tracking statistics about them before deciding whether or not to return credentials and allow that client to register or authenticate. If you really don't want to use curl and insist that it runs on the same box, you can do something very similar with lua. There is a way to bind a lua script to directory lookups, so whenever a SIP auth happens, the xml is fed to your lua script and you can make similar decisions. I just like curl because it offloads all that onto another machine, and it's really easy to implement in a clustered environment. -Tim Chad Vogel wrote:
I'm not looking to use curl, I would like to use some kind of scripting so i can apply custom rules to track and reject authentication based on rate and origin of authentication from source ip address
On Sep 29, 2011, at 11:22 PM, Jack wrote:
Hi Chad, mod_curl works great for that.... Jack
On 9/29/2011 5:47 PM, Chad Vogel wrote:
Hello,
I am wondering if anyone has created any scripts to manage user authentication using a database?
Chad
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org