Hi list, There's something I don't understand: if I add my LAN cidr (allow) in the second block of acl.conf.xml (domains), I can't call anymore. <list name="domains" default="deny"> <node type="allow" domain="$${domain}"/> <!-- NAAA => CAN'T EVEN CALL IN SIP! --> <node type="allow" cidr="192.168.1.0/24"/> </list> From what I understood of the wiki, this should work because the block denies everyone but my line allows for LAN cidr. I guess I misunderstood something. JY --
Apologies for the late response... did you get this figured out? Most likely it's because your calls are hitting the public context instead of default. Before recommending a course of action it would probably be good to know what you had in mind for putting that ACL entry in there. -MC On Fri, Mar 16, 2012 at 5:17 PM, Bzzz <lazyvirus@gmx.com> wrote:
Hi list,
There's something I don't understand: if I add my LAN cidr (allow) in the second block of acl.conf.xml (domains), I can't call anymore.
<list name="domains" default="deny"> <node type="allow" domain="$${domain}"/> <!-- NAAA => CAN'T EVEN CALL IN SIP! --> <node type="allow" cidr="192.168.1.0/24"/> </list>
From what I understood of the wiki, this should work because the block denies everyone but my line allows for LAN cidr.
I guess I misunderstood something.
JY --
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
On Mon, 26 Mar 2012 11:15:19 -0700 Michael Collins <msc@freeswitch.org> wrote:
Apologies for the late response... did you get this figured out? Most likely it's because your calls are hitting the public context instead of default. Before recommending a course of action it would probably be good to know what you had in mind for putting that ACL entry in there.
Well, I was playing with FS to try to understand how it work more deeply. And no, this issue isn't fixed (but that may be connected to fusionPBX, I didn't tried w/ a default configuration). You're right about the public context, I just re-made the test and found this in the logs: mod_dialplan_xml.c:485 Processing jy test <01>->02 in context public For now, this isn't too much a problem as I'm learning how FS work and it is not blocking. BTW, is there an arborescence of FS conf files somewhere? (it is sometimes hard to know who's doing what). Jean-Yves --
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. -MC On Mon, Mar 26, 2012 at 11:31 AM, Bzzz <lazyvirus@gmx.com> wrote:
On Mon, 26 Mar 2012 11:15:19 -0700 Michael Collins <msc@freeswitch.org> wrote:
Apologies for the late response... did you get this figured out? Most likely it's because your calls are hitting the public context instead of default. Before recommending a course of action it would probably be good to know what you had in mind for putting that ACL entry in there.
Well, I was playing with FS to try to understand how it work more deeply. And no, this issue isn't fixed (but that may be connected to fusionPBX, I didn't tried w/ a default configuration).
You're right about the public context, I just re-made the test and found this in the logs: mod_dialplan_xml.c:485 Processing jy test <01>->02 in context public
For now, this isn't too much a problem as I'm learning how FS work and it is not blocking.
BTW, is there an arborescence of FS conf files somewhere? (it is sometimes hard to know who's doing what).
Jean-Yves --
On Mon, 26 Mar 2012 11:48:38 -0700 Michael Collins <msc@freeswitch.org> wrote:
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.
Thanks, that's good to know 'cos I prefer permanent setups in a network (opposed to ie DHCP). JY -- It's not whether you win or lose, it's how you place the blame.
participants (2)
-
Bzzz
-
Michael Collins