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

    Asterisk 1.8 package

    pfSense Packages
    59
    281
    208.8k
    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
      muchacha_grande
      last edited by

      Yes, they are there…

      More precisely in /usr/pbi/asterisk-i386/var/log/asterisk/

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

        @muchacha_grande:

        Yes, they are there…

        More precisely in /usr/pbi/asterisk-i386/var/log/asterisk/

        try to create a symlink to /var/log/asterisk

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

        Help a community developer! ;D

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

          I'd modified the paths of the PHPs. They are hardcoded for version 2.0.

          Thank you very much…

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

            Hi again,

            finally with an Asterisk up and running on pfSense 2.1 beta1.

            I'm trying to enable fax sending and receiving with res_fax.so and res_fax_digium.so.

            I've already registered my box with Digium's register method explained in Digiums site but theres a lib missing when I do module load res_fax_digium.so.

            Here is the output:

            Asterisk 1.8.19.0, Copyright (C) 1999 - 2012 Digium, Inc. and others.
            Created by Mark Spencer markster@digium.comAsterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
            This is free software, with components licensed under the GNU General Public
            License version 2 and other licenses; you are welcome to redistribute it under
            certain conditions. Type 'core show license' for details.

            == Parsing '/usr/pbi/asterisk-i386/etc/asterisk/asterisk.conf':  == Found
              == Parsing '/usr/pbi/asterisk-i386/etc/asterisk/extconfig.conf':  == Found
            Connected to Asterisk 1.8.19.0 currently running on pfsense (pid = 6011)
            Verbosity is at least 3
            pfsenseCLI> module load res_fax_digium.so                                                                                Unable to load module res_fax_digium.so
            Command 'module load res_fax_digium.so' failed.
            [Feb  7 21:26:58] WARNING[6011]: loader.c:409 load_dynamic_module: Error loading module 'res_fax_digium.so': Shared object "libc.so.6" not found, required by "res_fax_digium.so"
            [Feb  7 21:26:58] WARNING[6011]: loader.c:874 load_resource: Module 'res_fax_digium.so' could not be loaded.
            pfsense            CLI>

            There in no comments about this at Digium's site.

            Does anyone succeded on making fax module work on pfSense?

            Thanks…/markster@digium.com

            1 Reply Last reply Reply Quote 0
            • W
              whitewater
              last edited by

              Hello,
              I'm testing asterisk on pfsense since some weeks. It's very stable :)
              Thank you for this great work !

              I have 3 pfsense with an IPSEC vpn :
              site A : 192.168.1.0
              site B : 192.168.2.0 - with an pika warp / freepbx asterisk
              site C : 192.168.3.0 - with your package asterisk on pfsense.

              I would like to connect from site A to site C with a SIP client. Test with zoiper.

              zoiper site A to asterisk site B : ok. it works :)
              zoiper site A to asterisk pfsense site C : ko. it doesn't works :(

              On states pfsense, of the site A & C, i have :
              NO_TRAFFIC:SINGLE

              IPSEC VPN rules are corrects. * for all settings.
              what should i do ?
              thank you :)

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

                I see the asterisk gui, but the user and password do not work, edit manager.conf and nothing

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

                  I see that the GUI of the package needs some work to be compatible to 2.1. I'll soon post the necessary modifications.

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

                    Is there a place where I could push the modifications needed for this plugin to work with 2.1? Like GitGub, etc…?

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

                      I've just modified my config file editor page, with complete backup and restore options.

                      I've also optimized the installation to properly run on NanoBSD systems. I'm going to update them accordingly at https://github.com/pfsense/pfsense-packages/tree/master/config/asterisk

                      asterisk_edit_file.png
                      asterisk_edit_file.png_thumb

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

                        Hi,

                        this post refer to i thread i started because this the GUI was not working properly on PfSense 2.1 release
                        http://forum.pfsense.org/index.php?topic=66660.0

                        i find out at the moment that two file of the GUI need to be modified to point to the new location for the package:

                        asterisk_calls.php
                        path need to be modified to :
                        "/usr/pbi/asterisk-amd64/var/log/asterisk/cdr-csv/Master.csv"
                        or
                        "/usr/pbi/asterisk-i386/var/log/asterisk/cdr-csv/Master.csv"
                        depending of architecture instead of :
                        "/var/log/asterisk/cdr-csv/Master.csv"

                        asterisk_log.php
                        path need to be modified to :
                        "/usr/pbi/asterisk-amd64/var/log/asterisk/messages"
                        or
                        "/usr/pbi/asterisk-i386/var/log/asterisk/messages"
                        depending of architecture instead of :
                        "/var/log/asterisk/messages"

                        for edit config file, the new path is "/usr/pbi/asterisk-amd64/etc/asterisk" for the config file

                        i don't know where to go to do the modification or if someone have to do it at my place (never did it before) but this make the package working on PfSense 2.1 . It is working flawlessly for me for the moment but i have to mod the php file each time an update is done on the package.

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

                          Work is in progress just now with modifications to address these issues.

                          Actually paths will be corrected on the file system to point to writable locations (as /usr/pbi/…. is not writable on NanoBSD), symlinks will be used and Asterisk configuration files will be updated accordingly on first install.

                          Please be patient, soon the update will be available in the packages list.

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

                            Package update v0.3 should be online soon.

                            If you already installed asterisk package on v2.1, I suggest to start from scratch by creating a fresh install of pfSense, or at least uninstall the complete Asterisk package, remove these directories by hand, reboot and reinstall Asterisk package:

                            Spool directory:             /var/spool/asterisk
Log directory:               /var/log/asterisk
Run/Sockets directory:       /var/run/asterisk
ASTDB:                       /var/db/asterisk/astdb

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

                              Note to users upgrading from pfSense v2.0.x:

                              Asterisk package was converted to PBI, thus the system file locations for it have been changed. That means that the asterisk.conf file on the 2.0.x and 2.1 will have different [directories] sections. Please revise the directory paths on the fresh install of Asterisk on v2.1, and correct them manually before restoring the configuration from 2.0.x.

                              On simpler scenarios, where only SIP protocol is used, the first approach to upgrade Asterisk would be to actually install it fresh on a v2.1 box, and replace sip.conf and extensions.conf files with the previous ones. All the other config files can be left in their default state if you didn't modify them earlier.

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

                                @robi:

                                Work is in progress just now with modifications to address these issues.

                                Actually paths will be corrected on the file system to point to writable locations (as /usr/pbi/…. is not writable on NanoBSD), symlinks will be used and Asterisk configuration files will be updated accordingly on first install.

                                Please be patient, soon the update will be available in the packages list.

                                Thanks robi for the quick answer :)

                                @robi:

                                Package update v0.3 should be online soon.

                                If you already installed asterisk package on v2.1, I suggest to start from scratch by creating a fresh install of pfSense, or at least uninstall the complete Asterisk package, remove these directories by hand, reboot and reinstall Asterisk package:

                                Spool directory:             /var/spool/asterisk
Log directory:               /var/log/asterisk
Run/Sockets directory:       /var/run/asterisk
ASTDB:                       /var/db/asterisk/astdb

                                i'll have to reinstall my setup from scratch on 2.1 cause my HDD is failing

                                if i have little time, i'll post the name of the file and what to temporary modify as a workaround until the package is completely updated.

                                you do a great job here folks :)

                                thanks

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

                                  It's already done, devs from pfSense need to pull it in to the servers…

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

                                    @robi:

                                    It's already done, devs from pfSense need to pull it in to the servers…

                                    awsome !!

                                    i'll wait and test it :)

                                    thanks

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

                                      is the last update Asterisk 1.8 pkg v0.3 broken for you ?

                                      • does'nt want to start via web GUI (via status -> service or via Asterisk command page).
                                      • asterisk log page is broken (parse error)
                                      • it start manually but extension won't register (no modification in conf file from 1.8 pkg v0.2)

                                      EDIT :
                                      nevermind for extension not registering

                                      BUT
                                      still need to start manually via shell ( asterisk -C /usr/pbi/asterisk-amd64/etc/asterisk/asterisk.conf )

                                      and log page is missing a ")" on line 70

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

                                        Yes, I've fixed them yesterday evening, pushed them to the server, still waiting to be pulled in.

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

                                          Hi roby,

                                          I've tested it on 2.1 and code was not working correctly.

                                          I did some changes and at least on 2.1 it's working fine now.

                                          Check if it's ok on nanobsd too.

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

                                          Help a community developer! ;D

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

                                            It's broken again, sent you a PM with the reason why.

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