6

You can use the following command: fs_cli -x "shutdown"


3

I wrote a plugin (in Perl) that checks various health parameters on a FreeSWITCH server. It takes advantage of the fs_cli FreeSWITCH command-line tool. It may be extended to check practically anything that fs_cli can check. It currently monitors a handful of things: sofia-status-internal - looks for the 'internal' Name and expects to find a state of ...


3

It is because not all legs / providers properly cancel echo in their network. So, in theory you should not need to have a line side echocan on a digital line, but in practice you sometimes do. For example, a provider might not cancel echo out to each analog endpoint in their network. If you have a digital connection to this network, you get the signal ...


2

conference_set_auto_outcall in mod_conference is doing exactly that -- it sets the destination endpoints which will be called out as soon as the conference starts. Use these flags to make sure the calling device can terminate the call and rest of the agents are silent: <action application="set" data="conference_auto_outcall_flags=mute"/> ... <...


2

Someone wrote their own health monitoring plugin and put it on github since Nagios does not offer one.


1

Edit /etc/freeswitch/sip_profiles/internal.xml. Change <!-- <param name="timer-T1X64" value="32000" /> --> to <param name="timer-T1X64" value="320000" />


1

So I solved this. I captured packets for calls that were working and calls that were not. It appeared Freeswitch was actually asking the clients to respond on an IP address that was similar to my public IP but not the same. The clients that worked appeared to ignore this and just respond locally. Some clients would do as instructed and send the ACK out to ...


1

use opus@8000h@20i with these settings in opus.conf.xml : <settings> <param name="use-vbr" value="1"/> <param name="use-dtx" value="0"/> <param name="complexity" value="10"/> <param name="maxaveragebitrate" value="14400"/> <param name="maxplaybackrate" value="8000"/> <param name="packet-loss-...


1

what's the network topology between the phones and FreeSWITCH server? Maybe there's a firewall that is doing NAT or SIP intelligence. Also if you run packet captures, it would help to determine where the delay is occurring.


1

Make sure you can run that perl script locally, as the nagios/nrpe user. Make sure that perl script doesn't depend on ENV (e.g., $PATH). Verify by running through env -i /usr/lib64/nagios/plugins/check_freeswitch_health.pl ... Use your generic check_nrpe command definition, instead of writing a check_{whatever} for every different NRPE command you want to ...


1

meni, You are trying to connect to localhost:8021. Do you have IPv6 enabled? You have freeSwitch IPv4 enabled, (0.0.0.0). On an IPv6 Windows 7 machine localhost is an IPv6 address (::1). Try using the IPv4 localhost address (127.0.0.1) instead of the abstract "localhost" name. Todd


1

I had the same problem after a clean install. I found the context in the Internal Profile was set to "public". After I changed this context to "default" the registrations worked as expected. Hope this will help.


1

If you're getting a segfault you should fill a JIRA at http://jira.freeswitch.org, With logs and all data needed to resolve the issue related to your crash. Start here: https://confluence.freeswitch.org/display/FREESWITCH/Reporting+Bugs


Only top voted, non community-wiki answers of a minimum length are eligible