Internal.xml using Public context/dialplan?
Hello I'm going through the various configuration files to figure out how they work together, and noticed the following references: sofia.conf.xml -> sip_profiles/internal.xml -> "public" context. 1. Am I right in understanding that a context is a file in the dialplan/ subdirectory? 2. Shouldn't the internal.xml SIP profile refer to the "default" (internal) context instead of "public" (external)? Thank you. -- View this message in context: http://www.nabble.com/Internal.xml-using-Public-context-dialplan--tp23175441... Sent from the Freeswitch-users mailing list archive at Nabble.com.
The internal profile requires authentication. Every user on that profile would use the user_context variable to override the profile context. Me being paranoid when I wrote the configs I set the internal profile to public just incase you misconfigure your system then you're not open to the world. /b On Apr 22, 2009, at 8:30 AM, Fred-145 wrote:
Hello
I'm going through the various configuration files to figure out how they work together, and noticed the following references: sofia.conf.xml -> sip_profiles/internal.xml -> "public" context.
1. Am I right in understanding that a context is a file in the dialplan/ subdirectory? 2. Shouldn't the internal.xml SIP profile refer to the "default" (internal) context instead of "public" (external)?
Thank you.
Brian West brian@freeswitch.org -- Meet us at ClueCon! http://www.cluecon.com
Brian West-3 wrote:
The internal profile requires authentication. Every user on that profile would use the user_context variable to override the profile context. Me being paranoid when I wrote the configs I set the internal profile to public just incase you misconfigure your system then you're not open to the world
Thanks Brian. So, to be safe, the "context" parameter in internal.xml refers to the "public" dialplan, and extensions are expected to overrule this setting with "user_context"? I also assume that, by default, profiles expect extensions to authenticate, which would explain why external.xml has the setting "auth-calls" set to "false", while internal.xml doesn't have this setting at all? If I'm right, I think I finally figured it out. I was confused with profiles, contexts, extensions, and dialplans. Here's how I _think_ these four thingies work together: 1. conf/dialplan/ contain XML files. Each file contains a bunch of extensions. "context" is a synonym for "dialplan" 2. conf/sip_profiles/ contains SIP profiles, eg. Internal/Default and External/Outbound 3. conf/directory/ contains extensions: The name of the XML file corresponds to a profile (eg. default.xml matches conf/sip_profiles/default.xml. This means that any extension in conf/directory/default/ belongs to the Internal/Default SIP profile. Each extension contains a parameter "context" that matches a diaplan in conf/dialplan/ Here's a diagram: http://img7.imageshack.us/img7/8670/freeswitchdpprofext.jpg Did I get right this time? :-) -- View this message in context: http://www.nabble.com/Internal.xml-using-Public-context-dialplan--tp23175441... Sent from the Freeswitch-users mailing list archive at Nabble.com.
On Apr 23, 2009, at 12:45 PM, Fred-145 wrote:
Thanks Brian. So, to be safe, the "context" parameter in internal.xml refers to the "public" dialplan, and extensions are expected to overrule this setting with "user_context"? I also assume that, by default, profiles expect extensions to authenticate, which would explain why external.xml has the setting "auth-calls" set to "false", while internal.xml doesn't have this setting at all?
internal has it set to true.
Brian West brian@freeswitch.org -- Meet us at ClueCon! http://www.cluecon.com
Thanks Brian. I'd like to make sure I finally got how dialplans, contexts, domains, SIP profiles, and extensions in the directory work together: "Freeswitch supports different SIP profiles in conf/sip_profiles/ ("internal.xml", "external.xml", etc.), which are loaded through conf/autoload_configs/sofia.conf.xml. Each profile maps to a domain, which corresponds to the part after @ (eg. "1000@192.168.0.1": The Freeswitch server is listening on 192.168.0.1, and this is the domain to which extension 1000 belongs.) Each profile also maps to a context (dialplan) located under conf/dialplan/. Note that, for security reasons, by default, all SIP profiles are set to use the Public context; Internal extensions must map to the Default (private) context explicitely through the "user_context" variable. Extensions are located under conf/directory/. Each sub-directory matches the domain to which an extension belongs. As set in conf/vars.xml, the default domain matches the server's IP address which itself maps to the Default domain, so all extensions that belong to this domain are located under conf/directory/default/." Is this correct? -- View this message in context: http://www.nabble.com/Internal.xml-using-Public-context-dialplan--tp23175441... Sent from the Freeswitch-users mailing list archive at Nabble.com.
participants (2)
-
Brian West
-
Fred-145