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

    Scheduled Pinned Locked Moved pfSense Packages
    314 Posts 39 Posters 305.7k Views
    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.
    • C
      cybrsrfr
      last edited by

      New Version 0.9.3.1
      FreeSWITCH package smtp auth and tls previously worked but plain smtp needed a bug fix, adjust huntgroup and ivr wording replace default with internal, fix a bug on huntgroup that prevented it from working completely when there is more than one huntgroup.

      https://rcs.pfsense.org/projects/pfsense-packages/repos/mainline/commits/b93e6a5e5e234af0fb4df61c989f6cc1e607707f

      Also upgraded someone this evening that was on a version that was several months old. The upgrade went smoothly without a single problem. Over the past 3 work days I have gotten 3 new systems up and running. Upgrading another one right now. [Update] Just completed another upgrade and it went perfectly smooth like the one I did earlier.

      If anyone is having problems feel free to ask on the forum on FreeNODE #pfsense-freeswitch channel, help is also available through pfSense official commercial support.

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

        HI,

        I just did a fresh install of pfSense 1.2.2 and Freeswitch (0.9.3.1) but Freeswitch won't start. If I go to the console and attempt to start it manually, I get:

        Cannt lock pid file: /usr/local/freeswitch/log/freeswitch.pid

        :(

        1 Reply Last reply Reply Quote 0
        • A
          adrianhensler
          last edited by

          Just a guess, is it a stale PID file?  Just go delete that file and try to start freeSwitch again?

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

            @adrianhensler:

            Just a guess, is it a stale PID file?  Just go delete that file and try to start freeSwitch again?

            Yeah, I tried that, but didn't help. The file get's recreated again without it ever starting. Strangely enough, it is empty, doesn't contain any PID. I also reinstalled the package and tried to reboot but also no luck. I always get that when I try to start FreeSwitch from the console.

            Update: I talked to mcrane over the irc channel and he said I had to upgrade to 1.2.3 snapshot. After that, it all worked well. If someone has the same problem, probably they need to upgrade as well.

            Thanks.

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

              The FreeSWITCH package requires pfSense 1.2.3 RC1 or higher in other words FreeBSD 7.1 or FreeBSD 7.x.

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

                FreeSWITCH Package new version 0.9.4.1

                1. add ping parameter to advanced gateway options helps keep connections alive behind NAT
                2. fix warning message when a gateway is disabled and later deleted
                3. add sip-force-contact to advanced extension options
                4. comment out the operator extension from the default dialplan
                5. add ability to disable an extension without removing it
                6. add effective_caller_id_name, effective_caller_id_number, outbound_caller_id_name, outbound_caller_id_number to the gateway
                7. patched a bug found with suppress_cng

                1 Reply Last reply Reply Quote 0
                • A
                  adrianhensler
                  last edited by

                  Slow down man, I haven't tried 0.9.3.1 yet!

                  ;)

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

                    Got a couple of questions:

                    I am just getting back to playing with pfsense/freeswitch after being pulled away for a couple of weeks. I upgraded the install.

                    When I dial my voicemail, I get "the person at extension 1001 is not available." When I dial 4000, I just get "goodbye". Same with 5000. What have I screwed up?

                    And - If a person wanted to completely delete all of freewitch from a firewall and reinstall from scratch, what are the file to get rid of?

                    Thanks again for all your hard work!

                    Library Mark

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

                      @librarymark:

                      I am just getting back to playing with pfsense/freeswitch after being pulled away for a couple of weeks. I upgraded the install.

                      Welcome back!

                      @librarymark:

                      When I dial my voicemail, I get "the person at extension 1001 is not available." When I dial 4000, I just get "goodbye". Same with 5000. What have I screwed up?

                      In the latest version all default FreeSWITCH feature codes have been moved behind the * so 4000 is now *4000, 5000 is now *5000, 9999 is now *9999 and so on. Another recent change is *4000 is the general voicemail box and *98 is the voicemail box that auto detects your extension so that it only need to ask for the password. The reason the feature codes have been moved behind the * is because this makes those number available for you and others so that they can use any 3 or 4 digit number for extensions, auto attendants(IVR), and hunt groups.

                      One other thing to note after doing an upgrade from an older version. The textareas in the GUI are handy because they give a lot of flexibility to you for advanced configuration. However it also creates an issue for the upgrade. That is that the installation does not update the textareas with the new default config. Why because I don't want to wipe out any of your customizations to those files. So to make it easier I created a 'Restore Default' on the bottom of each one of the textareas. So if you have no customizations simply click on those buttons to set it back to the default. You may need to do this for 'Vars' tab Public -> public.xml, 'Dialplan' tab -> default.xml, and occasionally for the Profiles tab for the internal, and the external profile. Please note this is not always necessary. It is only needed if the version of FreeSWITCH has changed and the default config has changed enough to conflict with your current settings.

                      @librarymark:

                      And - If a person wanted to completely delete all of freewitch from a firewall and reinstall from scratch, what are the file to get rid of?

                      You would need to go to System -> Packages and Remove the FreeSWITCH package. This will remove the package files but not the configuration that is stored in pfsense's xml config file. To get rid of the config require manually to remove the freeswitch tags in the xml from the config.xml. Warning! you have to do this carefully or you can break pfsense and prevent it from loading.
                      Because of that I suggest you first backup the file to something like config.xml.bak

                      You can open the file with Diagnostics -> Edit File once you have loaded /cf/conf/config.xml change the path to /cf/conf/config.xml.bak and click on save. That will create a current backup. Next remove all tags that use 'freeswitch' anywhere in the tag name. Make sure to delete everything between the start and close tag.

                      Then to get pfsense to see the change delete the config.cache from the /tmp directory.
                      rm /tmp/config.cache

                      @librarymark:

                      Thanks again for all your hard work!

                      You're welcome.

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

                        Wow, mcrane - you just flat-out rock! Thanks for the info.

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

                          I'm not keeping up well with update changes so iced98lx has volunteered to update the pfSense FreeSWITCH wiki with the changes
                          http://doc.pfsense.org/index.php/FreeSWITCH#Change_Log_.2F_Revision_History

                          Also commits to the package can be monitored here.
                          https://rcs.pfsense.org/users/mcrane

                          and here

                          https://rcs.pfsense.org/projects/pfsense-packages

                          1 Reply Last reply Reply Quote 0
                          • S
                            scsikid
                            last edited by

                            I just did a fresh install of pfsense 1.2.2. After which I installed freeswitch I looked at the service and it was not started. I attempted to start it which responded telling me it was started, however the icon showed stopped. I went into /usr/local/freeswitch/bin and tried to start it manually. The following is the error I get.

                            ./freeswitch

                            Error: stacksize 240 is too large: run ulimit -s 240 or run ./freeswitch -waste.
                            auto-adjusting stack size for optimal performance….
                            Cannot lock pid file /usr/local/freeswitch/log/freeswitch.pid.

                            This is likely because I'm not running 1.2.3-RC1? Is there a way to get this to run on 1.2.2? I tried 1.2.3-RC1 fresh install but it ran horribly on my system.

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

                              @scsikid:

                              ./freeswitch

                              Error: stacksize 240 is too large: run ulimit -s 240 or run ./freeswitch -waste.
                              auto-adjusting stack size for optimal performance….
                              Cannot lock pid file /usr/local/freeswitch/log/freeswitch.pid.

                              This is likely because I'm not running 1.2.3-RC1?

                              Yes I guarantee that is the reason.

                              @scsikid:

                              Is there a way to get this to run on 1.2.2? I tried 1.2.3-RC1 fresh install but it ran horribly on my system.

                              Current package requires 1.2.3 or pfsense 2.0. The reason why is that FreeSWITCH is compiled for freebsd 7.2. In order to get FreeSWITCH to work good on 1.2.x it has to be compiled for the version of freebsd that pfsense uses.

                              1 Reply Last reply Reply Quote 0
                              • S
                                scsikid
                                last edited by

                                Thanks mcrane, I updated pfSense to 1.2.3-RC3 and it runs. However it looks like when running the fs_cli command via ssh it doesnt work. Here is the error I get.

                                ./fs_cli

                                [ERROR] libs/esl/fs_cli.c:652 main() Error Connecting [Connection Error]

                                However in the GUI the status shows things correctly.

                                Any tips on this? Maybe I'm just missing a package?

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

                                  pfsense by default blocks communication on 127.0.0.1 which is what fs_cli tries by default instead tell it to use your lan ip address.

                                  ./fs_cli -H 192.168.1.1

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    scsikid
                                    last edited by

                                    thanks mcrane

                                    1 Reply Last reply Reply Quote 0
                                    • S
                                      scsikid
                                      last edited by

                                      Having an issue. I use dual wan, whenever my DSL IP is renewed the freeswitch service stops working. Looking at the system logs it shows the following.

                                      php: : pfSense package system has detected an ip change 67.55.21.X -> 69.172.115.X … Restarting packages.

                                      After this my pfsense service shows stopped. Any tips as to why?

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        scsikid
                                        last edited by

                                        Sorry here is another line with more relevant information. "missing required dependencies" any idea which?
                                        php: : pfSense package system has detected an ip change 69.172.115.239 -> 67.55.20.155 … Restarting packages.
                                        php: : The FreeSWITCH package is missing required dependencies and must be reinstalled.

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

                                          What version of the pfsense freeswitch package are you using? freeswitch or freeswitch dev

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            scsikid
                                            last edited by

                                            I'm using freeswitch 0.9.5. On 1.2.3-RC3.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.