<div dir="ltr">You can set a cidr="" attribute on a user in the user directory, the calls from IPs matching that cidr will then authenticate as that user (by IP instead of by password). You then have the ability in the user directory to set variables which will be set when the call comes in from that address.<div><br></div><div>You can use mod_xml_curl to generate the user directory dynamically, which allows you to integrate it with a database if you wished.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 1 October 2015 at 18:09, Dominique Jeannerod <span dir="ltr"><<a href="mailto:dominique.jeannerod@interact-iv.com" target="_blank">dominique.jeannerod@interact-iv.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hello,</div><div>I think it's a kind of newbie question, but i'm trying to find the simplest way of detecting the source of a call (public trunks), which of course rely on the source IP of the call.</div><div><br></div><div>I already defined one ACL per trunk, to authorize only allowed IP adresses, and test the different acls in the dialplan to identify the source trunk of a call, and set the associated accountcode.</div><div>Example :</div><div><div> <condition field="${acl(${network_addr} T_CNX_VPN)}" expression="true" break="on-true"></div><div> <action inline="true" application="set" data="accountcode=T_CNX"/></div><div> </condition></div></div><div>It works but the dialplan needs to be modified for each new trunk.</div><div><br></div><div>I am wondering if there is a best way to do that, using for example a channel variable, containing the ACL which matched for the call.</div><div>I tested sip_acl_authed_by, but this seems to be available only when the call is authenticated (?)</div><div><br></div><div>I'm sure a lot of people had the same question</div><div>What would be your advice ?</div><div><br></div><div>D. Jeannerod</div></div>
<br>_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" rel="noreferrer" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" rel="noreferrer" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://confluence.freeswitch.org" rel="noreferrer" target="_blank">http://confluence.freeswitch.org</a><br>
<a href="http://www.cluecon.com" rel="noreferrer" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" rel="noreferrer" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" rel="noreferrer" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" rel="noreferrer" target="_blank">http://www.freeswitch.org</a><br></blockquote></div><br></div>