VoIP Mailing List Archives

[ronmccar at gmail.com]

Hi all,

I would like to setup FS to have many context, basically we just want to switch calls, and since we have been using Asterisk we want to keep the context names the same, and well it's easier it seems to me.

This is for termination only, so just sending calls out, I would think FS can do it the same way Asterisk does, where if the IP matches then it will use those settings with that gateway and diaplan since the context ties them all together. No matter what I try the context always goes to default, I even took off all the ACL's for internal and external profiles and tried gateways in each, still no luck, i can't get around the default context. We are going to be using IP based auth only, so no user/pass's ever.

Any help on this would be great, I have searched and searched and everyone just uses the default context, but I am trying to avoid that as the diaplan will get quite long as I will have to all kinds of crazy matching, when a context is much simpler, and I would think faster then using lots of dialplan logic.

Thanks for any help on this!

Ron

[brian at freeswitch.org]

On Dec 28, 2008, at 12:52 PM, Ron McCarthy wrote:

[ronmccar at gmail.com]

I see the "brian.xml" example has it, didn't check that one, whoops.

Now I have added a user in the directory with the correct CIDR attribute, yet when I send the call it seems to not use the directory, the calls is coming from a Asterisk box, I have the Asterisk box pointed to the "internal" profile's IP address, which I assume the directory would use, and it gets rejected as the ACL on the incoming profile blocks that IP.

The users in the direct should not register just to IP based auth, which the CIDR attribute takes care of?

Just looks like it's not seeing the users in the directory at all, anything I might be missing that just jumps right out?

Thanks
Ron

On Sun, Dec 28, 2008 at 4:20 PM, Brian West <brian@freeswitch.org (brian@freeswitch.org)> wrote:

[brian at freeswitch.org]

I can bet you're on a rev before 10981 and after 10917... update you
have a bug related to this.

/b

On Dec 28, 2008, at 5:54 PM, Ron McCarthy wrote:

[ronmccar at gmail.com]

Wow, 10171 I guess Im way far behind! I am building right now, ill let ya know if any issues, thanks again!



On Sun, Dec 28, 2008 at 4:58 PM, Brian West <brian@freeswitch.org (brian@freeswitch.org)> wrote:

[brian at freeswitch.org]

Wow then you didn't have this one bug.... but yah a little bit
behind ... update just to be safe. If you still have the problem
please post.

/b

On Dec 28, 2008, at 6:16 PM, Ron McCarthy wrote:

[ronmccar at gmail.com]

Running 10981 now, same error.

I have:

<user id="proxy-01" cidr="x.x.xx.x/32">
<params>
<param name="password" value="1"/>
</params>
<variables>
<variable name="accountcode" value="1000"/>
<variable name="user_context" value="newContext"/>
<variable name="effective_caller_id_name" value="CID TEST"/>
<variable name="effective_caller_id_number" value="1000"/>
</variables>
</user>

Anymore ideals?

Thansk


On Sun, Dec 28, 2008 at 5:28 PM, Brian West <brian@freeswitch.org (brian@freeswitch.org)> wrote:

[brian at freeswitch.org]

show me the output of reloadacl , Chances are the domain in the
acl.conf.xml and the one in your directory don't jive.

/b

On Dec 28, 2008, at 8:46 PM, Ron McCarthy wrote: