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

    Asterisk 1.8 package

    Scheduled Pinned Locked Moved pfSense Packages
    281 Posts 59 Posters 235.6k 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.
    • M
      matthijs
      last edited by

      The Asterisk 1.8 package is not working\installing correctly under PFsense 2.2 i386 nanobsd (4 Gig dist) :(
      I am trying to install on an Alix board (alix2d13).
      Installing through the web interface does not seem to be the right way because this takes so long the web browser times out.
      So I also tried to install the package using the console (pfSsh.php playback installpkg Asterisk)
      The package seems to install correctly, but after the installation is done I am unable to start the service using de webinterface.
      When starting Asterisk using the console by starting /usr/pbi/bin/asterisk as root, the service starts and Asterisk is running fine. It Does not seem to be an Asterisk configuration issue (this also happens with de default Asterisk config)

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

        Some additional info
        It looks like de asterisk.inc file is not executed correctly
        After a reboot, /var/log/asterisk for example is not created

        Here also some logging after the manual start as root from the console

        [Jan 26 20:34:01] NOTICE[-1] cdr.c: CDR simple logging enabled.
        [Jan 26 20:34:02] WARNING[-1] db.c: Unable to open Asterisk database '/var/db/asterisk/astdb': No such file or directory
        [Jan 26 20:34:02] NOTICE[-1] loader.c: 162 modules will be loaded.
        [Jan 26 20:34:02] WARNING[-1] loader.c: Error loading module 'res_snmp.so': Shared object "libperl.so" not found, required by "libnetsnmpmibs.so.30"
        [Jan 26 20:34:03] WARNING[-1] res_fax.c: 'modems' setting 'V17,V27,V29' is no longer accepted with 'minrate' setting 2400
        [Jan 26 20:34:03] WARNING[-1] res_fax.c: 'minrate' has been reset to 4800, please update res_fax.conf.
        [Jan 26 20:34:03] NOTICE[-1] pbx_lua.c: Lua PBX Switch loaded.
        [Jan 26 20:34:03] WARNING[-1] loader.c: Error loading module 'res_snmp.so': Shared object "libperl.so" not found, required by "libnetsnmpmibs.so.30"
        [Jan 26 20:34:03] WARNING[-1] loader.c: Module 'res_snmp.so' could not be loaded.
        [Jan 26 20:34:04] NOTICE[-1] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener.
        [Jan 26 20:34:04] WARNING[-1] db.c: Unable to open Asterisk database '/var/db/asterisk/astdb': No such file or directory
        [Jan 26 20:34:04] WARNING[-1] db.c: Unable to open Asterisk database '/var/db/asterisk/astdb': No such file or directory
        [Jan 26 20:34:04] WARNING[-1] db.c: Unable to open Asterisk database '/var/db/asterisk/astdb': No such file or directory
        [Jan 26 20:34:04] WARNING[-1] db.c: Unable to open Asterisk database '/var/db/asterisk/astdb': No such file or directory
        [Jan 26 20:34:04] WARNING[-1] db.c: Unable to open Asterisk database '/var/db/asterisk/astdb': No such file or directory
        [Jan 26 20:34:04] WARNING[-1] db.c: Unable to open Asterisk database '/var/db/asterisk/astdb': No such file or directory
        [Jan 26 20:34:04] WARNING[-1] db.c: Unable to open Asterisk database '/var/db/asterisk/astdb': No such file or directory
        [Jan 26 20:34:04] WARNING[-1] db.c: Unable to open Asterisk database '/var/db/asterisk/astdb': No such file or directory
        [Jan 26 20:34:04] WARNING[-1] db.c: Unable to open Asterisk database '/var/db/asterisk/astdb': No such file or directory
        [Jan 26 20:34:04] WARNING[-1] db.c: Database unavailable
        [Jan 26 20:34:04] NOTICE[-1] cel_custom.c: No mappings found in cel_custom.conf. Not logging CEL to custom CSVs.
        [Jan 26 20:34:06] WARNING[-1] db.c: Unable to open Asterisk database '/var/db/asterisk/astdb': No such file or directory
        [Jan 26 20:34:06] WARNING[-1] db.c: Database unavailable
        [Jan 26 20:34:06] WARNING[-1] db.c: Unable to open Asterisk database '/var/db/asterisk/astdb': No such file or directory
        [Jan 26 20:34:06] WARNING[-1] db.c: Database unavailable
        [Jan 26 20:36:11] WARNING[-1] db.c: Unable to open Asterisk database '/var/db/asterisk/astdb': No such file or directory

        1 Reply Last reply Reply Quote 0
        • marcellocM
          marcelloc
          last edited by

          @matthijs:

          The Asterisk 1.8 package is not working\installing correctly under PFsense 2.2 i386 nanobsd (4 Gig dist) :(

          I did not had time to look asterisk package yet.

          these "missing" folder maybe under /usr/pbi dir.

          If you know how to symlinks dirs on unix systems, you may get it running.

          Treinamentos de Elite: http://sys-squad.com

          Help a community developer! ;D

          1 Reply Last reply Reply Quote 0
          • R
            robi
            last edited by

            Hi guys,

            It works if you log in by ssh shell and just type in "asterisk", but log file is not seen by the web interface.
            I'll have a look at this in the next few days, shouldn't be hard to fix.

            By the way, marcelloc, do you think it would be possible to have a newer asterisk package for 2.2?
            I'm thinking of Asterisk v11.10 at least, with extra support for the super-high quality and open opus audio codec.

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

              I changed

              $replace[2]='astdbdir => /tmp';

              in /usr/local/pkg/asterisk.inc

              the astdb file gets created there after a reboot
              Unfortunatly the asterisk service is still not started automaticly after a reboot and I am also still unable to manualy start the service by using the webinterface (still have to start /usr/pbi/bin/asterisk via the ssh console)

              After starting Asterisk I still see the following in the asterisk log
              (Maybe some issues are related to my specific asterisk configuration)

              ==>

              [Jan 27 10:15:59] NOTICE[-1] cdr.c: CDR simple logging enabled.
              [Jan 27 10:15:59] NOTICE[-1] loader.c: 162 modules will be loaded.
              [Jan 27 10:16:00] WARNING[-1] loader.c: Error loading module 'res_snmp.so': Shared object "libperl.so" not found, required by "libnetsnmpmibs.so.30"
              [Jan 27 10:16:00] WARNING[-1] res_fax.c: 'modems' setting 'V17,V27,V29' is no longer accepted with 'minrate' setting 2400
              [Jan 27 10:16:00] WARNING[-1] res_fax.c: 'minrate' has been reset to 4800, please update res_fax.conf.
              [Jan 27 10:16:00] NOTICE[-1] pbx_lua.c: Lua PBX Switch loaded.
              [Jan 27 10:16:01] WARNING[-1] loader.c: Error loading module 'res_snmp.so': Shared object "libperl.so" not found, required by "libnetsnmpmibs.so.30"
              [Jan 27 10:16:01] WARNING[-1] loader.c: Module 'res_snmp.so' could not be loaded.
              [Jan 27 10:16:01] NOTICE[-1] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener.
              [Jan 27 10:16:01] NOTICE[-1] cel_custom.c: No mappings found in cel_custom.conf. Not logging CEL to custom CSVs.

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

                Disabled the loading of res_snmp.so
                And changed minrate' setting to 4800 in res_fax.conf
                (wich I guess was specific for my configuration)
                No more logging errors\issues now

                Asterisk still not  starting after a reboot (any hint on where to seach for to fix this ?)
                If I run asterisk via the webinterface (diagnostics ==> command prompt) Asterisk also starts.

                1 Reply Last reply Reply Quote 0
                • E
                  eepstein
                  last edited by

                  I'm not sure why the Asterisk is not loading at boot. PFSense is my first experience with BSD.

                  I did have a thought for a workaround though, have you considered cron? Using the special keyword @reboot you could run a custom start up script.

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

                    @robi:

                    By the way, marcelloc, do you think it would be possible to have a newer asterisk package for 2.2?
                    I'm thinking of Asterisk v11.10 at least, with extra support for the super-high quality and open opus audio codec.

                    Sorry I was not following very accurately.
                    I suffer from the same issues and revert back to pfsense 2.1.5.

                    Is there any way to contact the person/team who created the previous package ?

                    1 Reply Last reply Reply Quote 0
                    • R
                      robi
                      last edited by

                      marcelloc is the author, contact via this forum/topic.

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

                        Hi All,

                        "/var/run" is cleaned at startup and hence "/var/run/asterisk" needs to be chowned in the asterisk init script. Here is a quick fix (amd64) :

                        1- Edit "/usr/pbi/asterisk-amd64/local/etc/rc.d/asterisk" and after the line "reload_cmd=asterisk_reload", add the following one :
                        start_precmd="chown -R asterisk:wheel /var/run/asterisk"

                        2- Create the missed link

                        ln /usr/pbi/asterisk-amd64/local/etc/rc.d/asterisk /usr/local/etc/rc.d/asterisk

                        3- Start asterisk or reboot

                        /usr/local/etc/rc.d/asterisk start

                        Regards,

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

                          Hi Bastion,

                          I tried your solution but Asterisk is not starting after a reboot in my situation (Alix board i386)
                          (I have to manualy start it)

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

                            Hi matthijs,

                            I've tested it on amd64/i386 with 2.2 and 2.2.1 many times, and had it working on all tests.
                            Did you try it on a fresh install  !!?

                            Cordially,

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

                              Hi Bastion, strange, it worked after a second reboot (I didnt change anything)

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

                                Rebooted again and it failed again to autostart, it sometimes works sometimes not
                                Did also a clean install, same behaviour, did you also test it on a nanobsd i386 (Alix board) ?
                                Because sometimes I also have the issue that OpenVPN fails to autostart
                                The Alix board is quite slow at things, so maybe things are not proparly stopped at a shut down\reboot, or things time-out or something during startup.

                                1 Reply Last reply Reply Quote 0
                                • D
                                  doktornotor Banned
                                  last edited by

                                  I bet about 99% of the inexplicable package issues would be solved by abandoning the PBI packaging POS. Really hope it happens very soon.

                                  (And pretty much can understand that people's motivation to maintain packages in their free time is about zero at this point. Most of time is wasted on debugging the packaging, instead of development and features.  >:( )

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

                                    Rebooted again and everything started succesfully
                                    This time I waited a little longer before logging into the webinterface.
                                    Maybe the problem is related with logging into soon after a reboot (interfering with processes still starting in the background)

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

                                      matthijs,

                                      After rebooting, pfSense normally needs a bit "patience/time" to autostart all services …

                                      P.S : Agree ! doktornotor  ;)

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

                                        Package seems to be broken..

                                        install on new 2.2.2 -> asterisk dont start

                                        after apply Bastions dirty workaround ends up with -> no asterisk_enable in rc.conf after manual add-in in rc.conf -> pam_error

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

                                          Update:

                                          after make a new /etc/rc.asterisk an put asterisk_enable=YES into it … it works again

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

                                            I just installed Asterisk on PfSense 2.2.2.
                                            I ran into some of the problems mentioned in this thread.
                                            These are my notes on solutions to the problems.

                                            1. Installation

                                            Installation takes a long, long time (on my box, about 24.5 minutes AFTER download is complete).
                                            You can't see what's going on in the web UI.
                                            I recommend enabling ssh, logging in to ssh and issuing the following command at the ssh command prompt:

                                            pfSsh.php playback installpkg Asterisk

                                            After a few minutes it will say 'Done' and the cursor will remain at the end of that line.
                                            It isn't done: it's just done with the download.
                                            Wait until it's really done – you'll know from the console output. Be patient.

                                            I'm not sure if this method installs the PfSense GUI stuff.
                                            If, after this step, you don't have an Asterisk entry in the PfSense Status menu, go to
                                            System->Packages and under Installed Packages->Asterisk click on the 'xml' button.

                                            2. Post-install fixes

                                            First, do this stuff:

                                            https://forum.pfsense.org/index.php?topic=47210.msg490067#msg490067

                                            Next, to fix the Asterisk log warnings about res_snmp.so and libperl.so, do the following:

                                            • under Diagnostics->NanoBSD set Media Read/Write status to Read/Write

                                            • log in with ssh, start a shell and cd to /usr/pbi/asterisk-<arch>/local/lib
                                                  note: replace <arch>with i386 or amd64, depending on your system

                                            • issue the following command at the ssh command prompt:
                                                  ln -s perl5/5.18/mach/CORE/libperl.so

                                            • under Diagnostics->NanoBSD set Media Read/Write status to Read-Only

                                            • under Status->Asterisk->Log press 'Clear log'

                                            • under Status->Asterisk->Commands press 'Restart Asterisk'

                                            • under Status->Asterisk->Log check the log; there should be no WARNINGs

                                            Hope this helps. I wanted to summarize everything in one place.</arch></arch>

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