[Freeswitch-docs] FreeSWITCH 1.8 New Configs
bote_radio at botecomm.com
Wed Feb 17 20:09:17 MSK 2016
Agreed. There is danger in over-thinking the problem.
From: Mario G
Sent: Wednesday, 17 February, 2016 12:03
Subject: Re: [Freeswitch-docs] FreeSWITCH 1.8 New Configs
Not sure why you need to add this to FreeSwitch config/install for OS X but
I documented auto startup for OS X here:
And for OS X config should all be in one place as it is now. Otherwise there
could be permissions problems, etc.
On Feb 17, 2016, at 6:53 AM, Sergey Safarov <s.safarov at gmail.com> wrote:
Oops. Systemd error :o)
I made smal search and find:
1) MacOS systemd alternative - launchd
2) BSD systemd alternative - relaunchd
3) Windows systemd alternative - SCM
Unlike many bootstrapping daemons, launchd has no explicit dependency
model. Interdependencies are
expected to be solved through the use of IPC. It is therefore in the
best interest of a job developer
who expects dependents to define all of the sockets in the
configuration file. This has the added bene-fit benefit
fit of making it possible to start the job based on demand instead of
Please read "The launchd Startup Process
_Startup_Process> " and "How to communicate with a LaunchAgent via Unix
This tool is not installed to FreeBSD in default configuration. But may be
installed and used like launchd in MacOS.
DependOnService - Lists the names of Windows services on which this service
depends. SCM must start these services before it starts this service. This
value can be an empty string if the service has no dependencies.
One more link
PS. About changes I will write late.
On Wed, Feb 17, 2016 at 4:28 PM, Brian West <brian at freeswitch.org> wrote:
Now you're thinking linux only, now apply your mindset to Mac, Windows,
*BSD, have you reviewed the changes I've made last week to the sample
configs in the fsconfig18 repo?
On Wed, Feb 17, 2016 at 4:12 AM, Sergey Safarov <s.safarov at gmail.com> wrote:
At present time FS config file is solid. Loaded ones at startup for all
modules. Also module loading is executed as modules listed in modules.conf
I think FS get more flexibility if config files will be spited of pisses for
each module and modules will be loaded using systemd.
1) freeswitch.service contain strings "Requires=freeswitch-config.service
2) freeswitch-config.service contains string "Wants=
3) freeswitch-mod-*.service unit files contains strings
"ExecStart=/usr/bin/freeswitch -x 'load <mod_module>'". Where <mod_module>
is name of module
4) freeswitch-directory.service contains string like
ExecStart=/usr/bin/freeswitch -x 'load directory'"
This case of loading FS has following features:
1) management of module dependency and module loading order via systemd;
2) allow at preprocessor level abbility to implement construction like "if
module loaded; then else; fi" and "case where". This allow dialplan will be
polymorphic for FS configuration;
On Mon, Dec 7, 2015 at 7:57 PM, Brian West <brian at freeswitch.org> wrote:
FS-8609 is raised to get a rough outline of a completely new config sample
that will be used in 1.8, So we are reaching out to the community for input
and direction, I have also created a hipchat room FS-8609 on
hipchat.freeswitch.org <http://hipchat.freeswitch.org/> if you wish to join
in. Lets start the discussion on this topic.
brian at freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
Join us at ClueCon 2016 Aug 8-12, 2016
More information about the Freeswitch-docs