Difference between revisions of "Freeswitch"
Line 13: | Line 13: | ||
{{Note box|If you have installed the '''[[Sogo|SOGo]]''' contrib, you will encounter a dependency issue with libmemcached. There is no resolution yet and your input is welcomed.}} | {{Note box|If you have installed the '''[[Sogo|SOGo]]''' contrib, you will encounter a dependency issue with libmemcached. There is no resolution yet and your input is welcomed.}} | ||
+ | |||
==Configuration== | ==Configuration== | ||
Line 29: | Line 30: | ||
service freeswitch start | service freeswitch start | ||
service freeswitch stop | service freeswitch stop | ||
+ | |||
===Configuration file=== | ===Configuration file=== | ||
[[Category:Howto]] | [[Category:Howto]] |
Revision as of 12:11, 21 February 2015
Is this article helpful to you?
Please consider donating or volunteering
Thank you!
About
Freeswitch is a scalable open source cross-platform telephony platform designed to route and interconnect popular communication protocols using audio, video, text or any other form of media. It was created in 2006 to fill the void left by proprietary commercial solutions. FreeSWITCH also provides a stable telephony platform on which many applications can be developed using a wide range of free tools
Installation
Both the Freeswitch and Epel repositories have to be anabled. Please enable these repositories first. After enabling the above repositories, one can install Freeswitch and it's dependencies with yum:
yum install --nogpgcheck freeswitch-config-vanilla --enablerepo=freeswitch --enablerepo=,epel
This will install about 60 RPM's with an installed size of 35M.
Configuration
Adding Freeswitch as a service and open ports
To automatically start Freeswitch at boot and configure the ports:
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S99freeswitch config set freeswitch service config setprop freeswitch status enabled config setprop freeswitch access private config setprop freeswitch UDPPorts "5060,5070,5080,3478,3479,16384:32768" config setprop freeswitch TCPPorts "5066,7443"
You can toggle the access property to enable public/private access. Then to apply the new service:
signal-event remoteaccess-update
Freeswitch can now be started and stopped with
service freeswitch start service freeswitch stop