Hello I'm a bit confused at the difference between those two concepts. Contexts are created in the /dialplan, and are refered to by items in /SIP_profiles and extensions in /directory. What purpose do contexts and profiles play? Thank you. -- View this message in context: http://old.nabble.com/Context-vs.-profile--tp26778101p26778101.html Sent from the Freeswitch-users mailing list archive at Nabble.com.
Profile is a collection of preferences uses by conferences etc. In the case of SIP a profile is also the name for the resulting SIP UA created by a particular profile. Context is a narrowed down view of something, in the case of the dialplan a context is a set of extensions. It's like having a dedicated set of extensions per distinct context name like parallel universes. both the foo context and the bar context can have extension 2001. On Mon, Dec 14, 2009 at 7:53 AM, Fred-145 <codecomplete@free.fr> wrote:
Hello
I'm a bit confused at the difference between those two concepts. Contexts are created in the /dialplan, and are refered to by items in /SIP_profiles and extensions in /directory.
What purpose do contexts and profiles play?
Thank you. -- View this message in context: http://old.nabble.com/Context-vs.-profile--tp26778101p26778101.html Sent from the Freeswitch-users mailing list archive at Nabble.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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:213-799-1400
Thanks Anthony for the tip. Would you say this is a correct representation of things? "Contexts are a set of extensions in conf/dialplan/ (eg. default, public, etc.) Extensions are configured through files in conf/directory/. Each extension maps to a context (<variable name="user_context" value="default"/>). Profiles refer to contexts in a dialplan (eg. ). Profiles are groups of settings used by different parts of the network, eg. Internal (private LAN), External (Internet-accessible, public LAN), etc. Each profile has a unique IP + port number. " -- View this message in context: http://old.nabble.com/Context-vs.-profile--tp26778101p26779926.html Sent from the Freeswitch-users mailing list archive at Nabble.com.
On Mon, Dec 14, 2009 at 9:12 AM, Fred-145 <codecomplete@free.fr> wrote:
Thanks Anthony for the tip.
Would you say this is a correct representation of things?
"Contexts are a set of extensions in conf/dialplan/ (eg. default, public, etc.)
Extensions are configured through files in conf/directory/. Each extension maps to a context (<variable name="user_context" value="default"/>).
It would be more correct to say that "users are configured in conf/directory"
Profiles refer to contexts in a dialplan (eg. ). Profiles are groups of settings used by different parts of the network, eg.
A better way to say this would be that a "SIP profile defines a SIP *User Agent*." (If you don't know what a SIP user agent is that's okay - just know that a profile listens for connections on a particular IP + Port and also sends outbound traffic via the same IP/port.) A SIP profile routes unauth'd incoming calls to a pre-defined dialplan and context. Users who have auth'd to the SIP profile have a little more control - the user_context can be defined at the user level in the directory. (Normally a user will just use the "default" context but it needn't be that way - you could have a context for two different entities, e.g. two different businesses running on the same FS server.) Are you typing up something for posterity's sake? If so let me know. I'll be happy to proof-read the finished product and offer suggestions. -MC Internal (private LAN), External (Internet-accessible, public LAN), etc.
Each profile has a unique IP + port number. " -- View this message in context: http://old.nabble.com/Context-vs.-profile--tp26778101p26779926.html Sent from the Freeswitch-users mailing list archive at Nabble.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
Are you typing up something for posterity's sake? If so let me know. I'll be happy to proof-read the finished product and offer suggestions. Thanks much for the clarification. I'm used to writing short documentation when I learn a new tool, so 1) it helps me understand how it works, 2) I can perform a new install faster, and 3) it helps newbies get a head-start. So in short: - profiles = User Agents ("end points of a phone call", says Wikipedia) where each profile listens on a given IP/port so that a single Freeswitch server can handle several profiles concurrently, eg. one end-point for internal, authenticated users, and another end-point for incoming calls from a VoIP provider - contexts = tells what a caller can do; a call can go through multiple contexts during the length of the call. In a dialplan, contexts = groups of extensions Thank you. -- View this message in context: http://old.nabble.com/Context-vs.-profile--tp26778101p26793258.html Sent from the Freeswitch-users mailing list archive at Nabble.com.
Profile is a collection of preferences uses by conferences etc. In the case of SIP a profile is also the name for the resulting SIP UA created by a particular profile. Context is a narrowed down view of something, in the case of the dialplan a context is a set of extensions. It's like having a dedicated set of extensions per distinct context name like parallel universes. both the foo context and the bar context can have extension 2001. A classic example of this is with the default dialing range of 1000-1019. This range appears in all three contexts that are defined in the default configuration: conf/dialplan/public.xml in "public_extensions" conf/dialplan/features.xml in "please_hold" conf/dialplan/default.xml in "Local_Extension" If a call comes in on the public context and gets routed to 1000 (or 1001, 1002,...1019) then it gets handled by "public_extensions" in public.xml. That extension transfers the call to 1000 in the features context (defined in features.xml) which executes a "please hold while I transfer your call" kind of operation and then transfers the call to 1000 in the default context (which is defined in default.xml). Check out those three files. You'll see some cool stuff! -MC
participants (3)
-
Anthony Minessale
-
Fred-145
-
Michael Collins