Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    FreeSWITCH package for pfSense 1.2.1 and 2.0 released. PBX or Proxy

    pfSense Packages
    39
    314
    269.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      bigboy
      last edited by

      @mcrane:

      @bigboy:

      I note that mod_openzap.so is missing in latest installation.

      Next version will have mod_openzap.so file but in order for it to work zaptel has to be compiled into the FreeBSD kernel which it isn't at this time. I've worked on doing that but so far have not succeeded.

      Shouldn't we just install from port version? I managed to install Zaptel from freebsd port on pfsense 1.2.2 Dev ISO and have it started and detect by adding script file in rc.d, similar to freeswitch.sh but start zaptel instead.

      1 Reply Last reply Reply Quote 0
      • C
        cybrsrfr
        last edited by

        The dev iso has the tools necessary to compile a port. Standard pfsense install does not have those tools. If I or someone else can come up with a process that adds the compiling tools back into pfsense then I will add it to the FreeSWITCH package or create a package specifically for compiling ports.

        Mark

        1 Reply Last reply Reply Quote 0
        • T
          tester_02
          last edited by

          mcrane.  How do we uninstall freeswitch so that it does not save any settings?

          I'm having issues with my setup.  With changing the internal Ip settings, the phones can register to freeswitch, but I can't get it to talk to each other (dial another extension and I get a couple of tones and goodbye).   I still thing it's that it shows my wan ip as internal…

          Anyways, I wanted to uninstall freeswitch, and then reinstall from scratch.  The problem is that when I reinstall, it puts back all my settings.
          I even uninstalled, rebooted, and ssh into the box to see that the backup file in /tmp does not exist.  It still gets the settings!

          One last question.  Can you see any issues with this package and a provider that uses a non-standard port?  vbuzzer uses port 80.

          thanks!

          1 Reply Last reply Reply Quote 0
          • C
            cybrsrfr
            last edited by

            @tester_02:

            mcrane.  How do we uninstall freeswitch so that it does not save any settings?

            Diagnostics -> Backup Restore
            Download the configuration then edit it and remove references to any tag that says <freeswitch*<br>Then restore the configuration.

            @tester_02:

            One last question.  Can you see any issues with this package and a provider that uses a non-standard port?  vbuzzer uses port 80.

            Try putting the domain:port when you are setting up the gateway's proxy.</freeswitch*<br>

            1 Reply Last reply Reply Quote 0
            • C
              cybrsrfr
              last edited by

              pfSense FreeSWITCH package version 0.8.1 is now available.

              1. It includes FreeSWITCH version 1.0.3 revision 12228.
              2. Fixed a minor install error.
              3. Added new dependency files that were required for 1.0.3.
              4. Created a backup directory to store a copy of the original config. /usr/local/freeswitch/conf.rev.orig

              1 Reply Last reply Reply Quote 0
              • T
                tester_02
                last edited by

                @mcrane:

                pfSense FreeSWITCH package version 0.8.1 is now available.

                yayyyy!
                0.8.0 went BOOM!!!

                Update:
                Actually both my systems went boom on even the 0.8.1 update..  Won't start up due to line errors on freeswitch.inc

                Here is some more info from the status page….
                unable to connect to 68.XXX.XXX.XXX:8021 in /usr/local/pkg/freeswitch.inc on line 97 Warning: socket_set_blocking(): supplied argument is not a valid stream resource in /usr/local/pkg/freeswitch.inc on line 98 Warning: fsockopen(): unable to connect to 192.168.0.3:8021 in /usr/local/pkg/freeswitch.inc on line 97 Warning: socket_set_blocking(): supplied argument is not a valid stream resource in /usr/local/pkg/freeswitch.inc on line 98 no handle

                Update 2:
                ok, I crashed my test machine by editing the backup and restoring (that's why it's a test machine).
                Anyways, fresh install of pfsense 1.2.2
                Freeswitch installs with the above errors.

                So I'd say it's temporarily broken..  Do not update!!

                1 Reply Last reply Reply Quote 0
                • O
                  oln
                  last edited by

                  After update to FreeSWITCH 0.8.1:

                  Service Freeswitch  does not start and nothing is written to the log.

                  1 Reply Last reply Reply Quote 0
                  • B
                    bigboy
                    last edited by

                    @oln:

                    After update to FreeSWITCH 0.8.1:

                    Service Freeswitch  does not start and nothing is written to the log.

                    I am having the same issues.

                    1 Reply Last reply Reply Quote 0
                    • B
                      billm
                      last edited by

                      No issues here on 2.0 (other than the unrelated php xml bugs we're fighting in 2.0).

                      –Bill

                      pfSense core developer
                      blog - http://www.ucsecurity.com/
                      twitter - billmarquette

                      1 Reply Last reply Reply Quote 0
                      • I
                        iced98lx
                        last edited by

                        @bigboy:

                        @oln:

                        After update to FreeSWITCH 0.8.1:

                        Service Freeswitch  does not start and nothing is written to the log.

                        I am having the same issues.

                        Also having this issue on 1.2.2

                        1 Reply Last reply Reply Quote 0
                        • L
                          ldavismead
                          last edited by

                          I can confirm this behavior.  When attempting to start FreeSWITCH as root from the console (module version 0.8.1 on pfSense 1.2.2), it fails to start saying that it can't lock the pid file (/usr/local/freeswitch/log/freeswitch.pid, IIRC).  Removing this file or creating it ahead of time with world-writable permissions had no effect.

                          I upgraded pfSense to the latest 1.2.3 nightly, and this cleared up the FreeSWITCH issue; I can now start it from the console as well as manage it from the webConfig services interface.  So I'd hazard a guess that its some sort of dependency issue with 1.2.2 that goes away in 1.2.3 (and presumably also 2.0).

                          1 Reply Last reply Reply Quote 0
                          • I
                            iced98lx
                            last edited by

                            @ldavismead:

                            I can confirm this behavior.  When attempting to start FreeSWITCH as root from the console (module version 0.8.1 on pfSense 1.2.2), it fails to start saying that it can't lock the pid file (/usr/local/freeswitch/log/freeswitch.pid, IIRC).  Removing this file or creating it ahead of time with world-writable permissions had no effect.

                            I upgraded pfSense to the latest 1.2.3 nightly, and this cleared up the FreeSWITCH issue; I can now start it from the console as well as manage it from the webConfig services interface.  So I'd hazard a guess that its some sort of dependency issue with 1.2.2 that goes away in 1.2.3 (and presumably also 2.0).

                            Interesting just upgraded to latest nightly snapshot and still no freeswitch for me..

                            1 Reply Last reply Reply Quote 0
                            • T
                              tester_02
                              last edited by

                              So I guess the common theme is
                              1.  If you are running 1.2.1 or 1.2.2.  DO NOT UPGRADE TO THE LATEST VERSION.  Until we hear back from mcrane
                              2.  If you are running 1.2.3 or 2.0  take your own risk if you want.  It may/may not work.
                              3.  If you upgraded already and it's crashed your freeswitch, then we are out of luck until mcrane comes up with something..

                              wait…

                              1 Reply Last reply Reply Quote 0
                              • C
                                cybrsrfr
                                last edited by

                                The system I'm running is working fine on pfSense 1.2.3.

                                I'm currently on IRC at #pfsense-freeswitch. Those with problems please contact me there and I will help you get your systems working. As the problem is identified I will get it fixed in the package.

                                Mark

                                1 Reply Last reply Reply Quote 0
                                • T
                                  tester_02
                                  last edited by

                                  I updated my test 1.2.2 machine to 1.2.3 (today's build) and freeswitch was a no-go just like 1.2.2

                                  I then updated to 2.0 and it looked like it was running (service was running) but I could not get to it from the web admin page.  That does not say much to me, as when I rebooted I could not get to even the login page.  I count that as a pfsense issue.

                                  I then reinstalled a fresh copy of 1.2.3 (not upgrade as in 1st attempt).  Still no go (even after reboot).

                                  Service won't start…

                                  So it's either that some 1.2.3 build let freeswitch work, while the new build does not.  That or it's related to a specific hardware that it's working/not working.

                                  I don't have too much of specialized hardware.  Main pfsense is an AMD Sempron LE-1150, 1 VIA onboard NIC, 1 Intel PIC NIC.
                                  Other test machine is an ATOM 330 with 2 realtek NICS (yah they suck, but it's a test machine)

                                  Maybe you can go back to older and freeswitch build until the 0.8 bugs are worked out?

                                  1 Reply Last reply Reply Quote 0
                                  • chpalmerC
                                    chpalmer
                                    last edited by

                                    Running 2.0-ALPHA-ALPHA built on Thu Jan 15 23:00:25 EST 2009 FreeBSD 7.1-RELEASE-p2 still here.

                                    latest freeswitch package installed fine for me. Running now…

                                    Triggering snowflakes one by one..
                                    Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                                    1 Reply Last reply Reply Quote 0
                                    • I
                                      iced98lx
                                      last edited by

                                      Mcrane is working on resurrecting an older version for us 1.2.2 guys- this is a known bug for FS and freebsd 7.0..

                                      I'll be happy to test and confirm…  ;D ;D

                                      1 Reply Last reply Reply Quote 0
                                      • C
                                        cybrsrfr
                                        last edited by

                                        I have a work around until the bug is fixed for FreeSWITCH on FreeBSD 7.0 (pfSense 1.2.1 or 1.2.2)

                                        Once you have the package installed go to Diagnostics -> Command -> PHP Execute then run the following commands. The following PHP code will download a FreeSWITCH build from Jan 2009 and replace the build that comes in the package. (please note this is not the entire install procedure so you must have the package already installed)

                                        require_once("config.inc");
                                        require_once("/usr/local/pkg/freeswitch.inc");
                                        exec("cd /tmp/;fetch http://portableusbapps.com/packages/config/freeswitch/freeswitch.1.jan.2009.tgz");
                                        exec("cp /tmp/freeswitch.1.jan.2009.tgz /tmp/freeswitch.tgz");
                                        unlink_if_exists("/tmp/freeswitch.1.jan.2009.tgz");
                                        freeswitch_php_install_command();

                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          mrguitar
                                          last edited by

                                          I'm running 1.2.3 from Feb 18th and I also couldn't get the new FS package working. Mcrane's php fix worked for my system; I'm back up now.

                                          This issue brings up an interesting scenario that pfSense really needs some type of version control for packages, or at least a "roll back" feature (sorry to use a M$ term).

                                          Thanks for fixing this Mcrane; I bet that was a lot of work.

                                          1 Reply Last reply Reply Quote 0
                                          • M
                                            mannix
                                            last edited by

                                            Thank you, the workaround works for me

                                            Bye

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post