FreeSWITCH package for pfSense 1.2.1 and 2.0 released. PBX or Proxy
-
I tried to shutdown FreeSWITCH a few days ago and afterwards I then noted that swap increased drastically on 1st page and there was a large amount of FreeSWITCH related stuff in system log. I didn't take more detailed notice of the contents. I then noted, earlier today, that I now have almost all tabs in FreeSWITCH GUI yielding 404:s.
I then removed FreeSWITCH from package manager.
rebooted
Checked imspector status: RED
Can't start it, again.reboot again
still cant start imspector
So, imspector won't start due to libiconv.so.3 missing and pkg_info | grep libiconv yields response: "libiconv-1.11_1".
Your symptoms of loosing files could be explained by failing data storage (Hard Drive, or Compact Flash.)
========
Adding:
And trying: "pkg_add -r libiconv" yields error about URLs being incorrect for both http and ftp for the FreeBSD 7.0 version.. files not available it says.If you are using 1.2.1, 1.2.2 they are FreeBSD 7.0. I suggest that you use pfSense 1.2.3 RC1 because it is running FreeBSD 7.1 and has security patches as well as additional fixes that you will benefit from.
. Why is packages obviously ripping shared files or configs pointers being used by others? This is not the first time I've seen this.
The package does add files to /usr/local/lib but does not remove them on when the package is removed because I don't know if some other package is dependent on them.
Is FreeSWITCH to blame here somehow?
I don't think so.
Am I sitting with a mix of older version configs of FreeSWITCH causing this?
I mix of older configs being stored in the pfsense config can make it harder to get working.
The configs that could cause problems is the pages that use textareas.How do I make sure absolutely everything related to FreeSWITH is removed from the system? One would think it should be possible to remove enough so that a perfectly clean re-install of this (or any other package) is possible?
The correct process to upgrade is:
1. Backup the package from the status page
2. Remove the package. The settings for packages persist in the config.xml.
3. Then install the package again.When the package is removed it does the following.
exec("killall -9 freeswitch");
unlink_if_exists("/usr/local/pkg/freeswitch.xml");
unlink_if_exists("/usr/local/pkg/freeswitch.inc");
unlink_if_exists("/usr/local/pkg/freeswitch_dialplan.xml");
unlink_if_exists("/usr/local/pkg/freeswitch_extensions.xml");
unlink_if_exists("/usr/local/pkg/freeswitch_external.xml");
unlink_if_exists("/usr/local/pkg/freeswitch_internal.xml");
unlink_if_exists("/usr/local/pkg/freeswitch_modules.xml");
unlink_if_exists("/usr/local/pkg/freeswitch_public.xml");
unlink_if_exists("/usr/local/pkg/freeswitch_vars.xml");exec("rm -R /usr/local/freeswitch/");
exec("rm -R /usr/local/www/freeswitch/");
exec("rm -R /usr/local/www/packages/freeswitch/");
unlink_if_exists("/usr/local/etc/rc.d/freeswitch.sh");
unlink_if_exists("/tmp/freeswitch.tar.gz");
unlink_if_exists("/tmp/pkg_mgr_FreeSWITCH.log");Also I think I may have misunderstood some of the config, and turning to guides online can be a bit confusing since they often tend to target installations without any GUI components, only directly editing config files. Are such guides relevant 100% to pfSense version of FreeSWITCH?
This documentation is related to the pfSense FreeSWITCH package interface.
http://doc.pfsense.org/index.php/FreeSWITCH#IP_address_or_DomainStandard FreeSWITCH documentation that is related to the config.
http://wiki.freeswitch.org/wiki/Main_PageOne thing to note about the pfSense FreeSWITCH interface is that the names used are the same names in the config. The GUI gives you paths to the config files that are being edited. The goal of this interface is to make it easier to setup FreeSWITCH and at the same time educate the user. Making it possible for the knowledge gained from the config or the interface would be as interchangeable as possible.
When installing FreeSWITCH in pfSense, the config options of editing XML directly and using the nice GUI to manually adding/editing stuff - which is the case on several tabs - is either of them optional or not etc, this is not apparent from GUI and I guess some errors are present in some installations if XML is not edited at all?
You can install the package and not use the GUI if desired. Or you can use the GUI and still modify xml files that the GUI does not use.
I don't get the feeling that it's clear whether or not editing the GUI is just another way of editing the XML or not.
GUI reads the pfSense config for information and then writes certain xml files but does not write every single xml file. It starts with a default configuration and the GUI modifies areas that are noted in the GUI.
-
Thanks for your thorough answer, I'll try to make some wise re-install choices.
Cheers,
-
@mcrane:
Your symptoms of loosing files could be explained by failing data storage (Hard Drive, or Compact Flash.)
Always a valid point, I'll try to do some checking on that, perhaps boot a "ultimate boot cd"/Hirens/etc boot cd and do some HD tests and read out SMART data, if available. I do however use other packages that write/read to disk, like lightsquid, so if so I should get some weird behaviour or errors from other parts of the system I think. I will still check it out though.
Thanks,
-
Hello, I'm quite new here so sorry for my question if it's lame… I have a following configuration:
(X-Lite clients-LAN)----(LAN-Pfsense-WAN)----(Internet)----(someNAT)----(X-Lite clients)
I don't need to call outside using a provider, I just need some inter-company communication.
I have allowed this on the firewall on the WAN interface:
TCP/UDP 5060 - 5090
UDP 16384 - 32768Then I have added 3 users (extersions), all the same user context and group (default)
And to get SIP server listening on both interfaces I have copied the whole Internal profile tab and pasted it over to External profile tab with these changes:
Internal:
<param name="rtp-ip" value="192.168.0.84">
<param name="sip-ip" value="192.168.0.84">
(192.168.0.84 is my LAN IP on pfsense)
External:
<profile name="external">The problem:
Communication of LAN-LAN users works great, WAN-WAN as well, calling from LAN to a user who is connected to WAN works as well, but (!!) when a WAN-connected user wants to call a user connected to LAN he gots "the person at extension xxxx is not available"Any suggestions? I havent touched any other config files, have version 0.8.5.4
edit: if I run whireshark at the LAN user I'm trying to reach from WAN he receives no packets, so the call gets lost somewhere in pfsense...</profile>
-
@mcrane:
The package does add files to /usr/local/lib but does not remove them on when the package is removed because I don't know if some other package is dependent on them.
BTW: I reinstalled FreeSWITCH and imspector starts again.
I guess that if I uninstall only FreeSWITCH now imspector shouldn't stop working if FreeSWITCH doesn't remove anything. I'll try that later and if imspector still stops working I'll report back.
-
And to get SIP server listening on both interfaces I have copied the whole Internal profile tab and pasted it over to External profile tab with these changes:
Internal:
<param name="rtp-ip" value="192.168.0.84">
<param name="sip-ip" value="192.168.0.84">
(192.168.0.84 is my LAN IP on pfsense)
External:
<profile name="external">The problem:
Communication of LAN-LAN users works great, WAN-WAN as well, calling from LAN to a user who is connected to WAN works as well, but (!!) when a WAN-connected user wants to call a user connected to LAN he gots "the person at extension xxxx is not available"</profile>Internal profile is the profile that handles registrations. Most often used for extensions but can also be used to connect to by other devices such as FreeSWITCH.
External profile does not do registration.
Their names are a little misleading. By default FreeSWITCH binds to the WAN on pfSense for both Internal and External profiles. If you don't have a static IP address then you would need to use dynamic DNS with pfSense so that the location of the phone system would be constant. Phones on LAN can by default reach the WAN ip where FreeSWITCH is bound to without problem. Phones from the Internet need ports opened for the WAN interface but don't require NAT since its on the WAN.
Earlier this week others have requested ability to connect when using VPNs. To do that FreeSWITCH needs to be listening on an internal address that is reachable from the VPN. This will require copying a profile similar to what you have done. I don't suggest changing the External profile instead copy the internal profile and make a new one from it called something like 'LAN'. Inside the profile you would also need to change the name and remove the alias so that it doesn't conflict with the internal profile. Then restart freeSWITCH.
Soon as I have time I will be creating a new tab called 'Profiles' and will move the Internal and External tabs to that tab. Then will make it possible to manage profiles from there. I'm also thinking add a default to the new installs that include the LAN profile by default. Then people would be able to register to the LAN IP which is what most people are likely used to.
-
I for one would definitely be for binding to the LAN interface by default.
-
@mcrane:
And to get SIP server listening on both interfaces I have copied the whole Internal profile tab and pasted it over to External profile tab with these changes:
Internal:
<param name="rtp-ip" value="192.168.0.84">
<param name="sip-ip" value="192.168.0.84">
(192.168.0.84 is my LAN IP on pfsense)
External:
<profile name="external">The problem:
Communication of LAN-LAN users works great, WAN-WAN as well, calling from LAN to a user who is connected to WAN works as well, but (!!) when a WAN-connected user wants to call a user connected to LAN he gots "the person at extension xxxx is not available"</profile>Internal profile is the profile that handles registrations. Most often used for extensions but can also be used to connect to by other devices such as FreeSWITCH.
…yes, I know that, I just used the profile filename so I could edit it using the web interface. Just imagine I have the origin profile internal and it's copy running on another ip address, both are shown in status and running ok. The only problem is routing between these profiles when someone from WAN calls to LAN. Calling from LAN to WAN works.
-
What kind of phones are you using on the remote side?
-
@mcrane:
What kind of phones are you using on the remote side?
x-lite
-
Well, after 8 months of working waayyyy too many hours, I finally have some extra time to play with FS, so I upgraded, and ran right smack into my same original problems with caller ID. After fighting with it for way too long, I bring you a solution. If you're using Voicepulse, make sure your outbound_caller_id and outbound_caller_name match, and are 10 digit numbers. Simple, huh? I knew this 8 months ago, just forgot. … :P
-
Fun scenario…
Call to PSTN number succeeds from phone connected to Linksys PAP2.
Make call to extension on default extension from phone connected to Linksys PAP2.
Hang up while call still ringing
Attempt call to same PSTN number
Call will failWhy?
-
Fun scenario…
Call to PSTN number succeeds from phone connected to Linksys PAP2.
Make call to extension on default extension from phone connected to Linksys PAP2.
Hang up while call still ringing
Attempt call to same PSTN number
Call will failWhy?
I don't think you have provided enough information to answer this but I can say that it works fine with my Linksys PAP2T.
-
pfSense FreeSWITCH package version 0.8.7.4 is now available.
Latest improvements include:
SIP profile management.
Default LAN SIP profile that binds to the LAN IP address. This enables registration to the LAN IP.
Textareas now use editarea which provides syntax highlighting, line numbering and more.
Dialplan default.xml, public.xml and vars.xml textareas now have 'Restore Default'
Status page now shows all SIP profiles.
tail command for log viewing on the 'Status' tab increased to 500 lines, also using editarea
and more… -
Hey mcrane,
Just wanted to let you know, I was playing around in freeswitch trying to setup inbound faxing, and ran into an issue with mod_fax not loading properly. I was able to get things sorted eventually by trying to load the mod_fax.so object manually from fs_cli.so; when I tried that it complained that /usr/local/lib/libspandsp.so.2 didn't exist, and indeed it doesn't, at least not on 1.2.3-RC1. Symlinking libspandsp.so.1 to libspandsp.so.2 appears to have fixed everything right up for me though, although I'm not sure that's the "right" way to get things working.
Thanks again for all your work on the pfsense package.
-
Just wanted to let you know, I was playing around in freeswitch trying to setup inbound faxing, and ran into an issue with mod_fax not loading properly. I was able to get things sorted eventually by trying to load the mod_fax.so object manually from fs_cli.so; when I tried that it complained that /usr/local/lib/libspandsp.so.2 didn't exist, and indeed it doesn't, at least not on 1.2.3-RC1. Symlinking libspandsp.so.1 to libspandsp.so.2 appears to have fixed everything right up for me though, although I'm not sure that's the "right" way to get things working.
Thanks to your post I was able to load mod_fax. I didn't stop there I immediately started to build a GUI interface for it. Should be done sometime this week. So lists the fax as a tiff file for download, and converts the fax to png and pdf. FAX to email and a method to send the fax is next.
Best Regards,
mcrane -
Can I request one feature? A quick button that resets all settings to default.
I had everything working for the last while (still have not had time to play with IVR), and I did a freeswitch upgrade and now my incoming calls go right through to voicemail. I can't even do local transfers.
I am guessing the reason is that I did some changes to the original settings to force freeswitch to my Lan ip's to get registrations working. Due to all the changes done to freeswich (looks good, interface is much better), I see that my changes could be the problem. Outbound calls to provider work, incoming go right to voicemail now (not available), and internal calls are not available. It was working previously.
Honestly the easiest way would be to start with default settings and set things up again. If I uninstall and reinstall, all the settings are saved. I tried modifying the settings file, and always seem to corrupt it.
I can't see that I am the only one who may want to hit a button to reset to mcrane default settings.Update. Ok, I just need to look some more. Looks like mcrane has already done this. Wow, snuck this in on me… :)
Update 2. Defaults did not make things better. Still getting errors on internal transfers in the log..
IP 192.168.0.6 Rejected by acl "domains". Falling back to Digest auth
So much for things running smoothly for the last couple of months..Update 3. Restore settings on the Lan.xlm does not work.
-
Can someone PM me with a cut/paste of their lan.xml?
My test machine is busy right now, and I can't delete the drive and install a fresh pfsense/freeswitch right now.
I'm hoping that will restore my internal and inbound calling…Thanks!
Update. The restore does work on the lan file. The confusing part was that it put my ip in the file, so I thought it was my modified one (I had to put the local ip in the internal file and then I could get internal calling).
ANyways, I'm back to still not working. Whatever the changes were to the last couple of releases were, killed my internal and inbound calling. Not sure why internal callings would fail, and send it to voicemail.
Is it normal to have no internal registrations, and all the phones on the Lan? (i would assume so)
Also the log is getting user not registered on to of the rejected by acl domains even though the phones are clearly registered under the lan.I'd install an older version if I could as things were working before.
Oh well, I guess this is the fun of working with these packages!
-
tester_02: a tool that would help see what is going on is to use the freeswitch console.
From the pfsense console do the following:
cd /usr/local/freeswitch/bin
./fs_cli -H 192.168.1For more help please use IRC -> freenode -> #pfsense-freeswitch
IRC clients that work well
Firefox add on chatzilla
xchat
http://www.mibbit.com/chat/ (online IRC client) -
tester_02, I've had the same symptoms when registered on LAN profile. I have just used the WAN address to register my ATA and all works well registered to the Internal profile.
db