[Freeswitch-users] Internal Sip Profile public or default context?
shealyw2 at gmail.com
Fri Sep 26 06:55:48 MSD 2014
My Freeswitch is hosted on an external vps. Would I want to put the
Internal profile behind the firewall and not allow connections to it. Or
since I will be using Bria to make and receive my calls would I open it up
and connect my registered users that way?
---------- Forwarded message ----------
> From: Michael Collins <msc at freeswitch.org>
> To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
> Date: Mon, 22 Sep 2014 14:03:10 -0700
> Subject: Re: [Freeswitch-users] Internal Sip Profile public or default
> This would be the default context to use for any unauthenticated calls. In
> other words, that context parameter is telling the Internal SIP profile
> which dialplan context to use when an unauth'd call comes in. Typically
> this would be inbound SIP provider calls, such as calls in to a DID number.
> You definitely want unauth'd calls to be handled by your
> public/untrusted/paranoid dialplan context. To paraphrase Brian West:
> "paranoid by default" is a good policy. If the user is authenticated then
> the user_context value is used.
> On Sat, Sep 20, 2014 at 6:21 PM, Matthew Shealy <shealyw2 at gmail.com>
>> Hi guys,
>> In the documentation it says:
>> "Authenticated users of this profile are normally set (via the variable
>> user_context) to use the dialplan defined in the default context."
>> So why after a fresh compile is the $conf/sip_profiles/internal.xml
>> Profile set to <param name="context" value="public"/>
>> Professional FreeSWITCH Consulting Services:
>> consulting at freeswitch.org
>> Official FreeSWITCH Sites
>> FreeSWITCH-users mailing list
>> FreeSWITCH-users at lists.freeswitch.org
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
Join us at ClueCon 2016 Aug 8-12, 2016
More information about the FreeSWITCH-users