Okay, no worries. FYI, if you want to associate an IP address with a specific user so that all calls from a specific IP address are considered as being "from that user" then do the cidr='x.x.x.x/32' trick in the user directory entry.<br>
<br>-MC<br><br><div class="gmail_quote">On Mon, Mar 26, 2012 at 11:31 AM, Bzzz <span dir="ltr"><<a href="mailto:lazyvirus@gmx.com">lazyvirus@gmx.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, 26 Mar 2012 11:15:19 -0700<br>
Michael Collins <<a href="mailto:msc@freeswitch.org">msc@freeswitch.org</a>> wrote:<br>
<br>
> Apologies for the late response... did you get this figured out? Most<br>
> likely it's because your calls are hitting the public context instead of<br>
> default. Before recommending a course of action it would probably be good<br>
> to know what you had in mind for putting that ACL entry in there.<br>
<br>
Well, I was playing with FS to try to understand how it work more<br>
deeply. And no, this issue isn't fixed (but that may be connected<br>
to fusionPBX, I didn't tried w/ a default configuration).<br>
<br>
You're right about the public context, I just re-made the test and<br>
found this in the logs:<br>
mod_dialplan_xml.c:485 Processing jy test <01>->02 in context public<br>
<br>
For now, this isn't too much a problem as I'm learning how FS work<br>
and it is not blocking.<br>
<br>
BTW, is there an arborescence of FS conf files somewhere? (it is<br>
sometimes hard to know who's doing what).<br>
<br>
Jean-Yves<br>
--<br>
<br><br></blockquote></div>