Brian,
Please forgive
my slowness, but I’m still having problems with this. When you say that I
“really didn’t auth the user”, did you mean the
endpoint/extension?
If you did, I
upped to svn1 16055 and placed a cidr attribute on the extension and reran the
test, resulting in the same output, going to context public.
Further, I’m
confused about your response about ACL compared with Billy W in an email of
12/22/2009.
“…you could simply put these entries in your
internal sofia profile.
<param name="apply-inbound-acl"
value="192.168.0.0/24"/> <param
name="apply-register-acl" value="192.168.0.0/24"/>
In that case, you do not need to include anything in the
directory. The cidr entries in the directory are for providing additional
control for each user id and what IPs they are allowed to make calls from.”
http://pastebin.freeswitch.org/11633
Linux fs
2.6.18-128.1.10.el5 #1 SMP Thu May 7 10:39:21 EDT 2009 i686 i686 i386 GNU/Linux
Thanks Lars
From:
freeswitch-users-bounces@lists.freeswitch.org
[mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Brian
West
Sent: Wednesday, December 23, 2009 6:03 PM
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] Local call uses public context?
2009-12-23 15:00:01.955357 [DEBUG] sofia.c:5322 IP 192.168.10.105 Approved by acl "192.168.10.0/24[]". Access Granted.
Because the context is set on the profile as
public... and you really didn't auth the user so user_context was never set.
/b
On Dec 23, 2009, at 7:49 PM, Lars Zeb wrote:
I am trying to setup a second
FS box from scratch using v16048.
What can cause a local call
(81002, or 9996) to use context public? It’s a standard vanilla install.
Thanks,
Lars
_______________________________________________
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