Elastix v2.0.3 Sangoma A200 PCI undetected

Discussion in 'General' started by apmuthu, Dec 3, 2010.

  1. apmuthu

    Joined:
    Aug 1, 2009
    Messages:
    60
    Likes Received:
    0
    A fresh install of v2.0.3 (v2.0.0-58) of Elastix on Intel 865 Mainboard with Celeron 2.6 GHz / 512 MB RAM did not detect a PCI Sangoma A200 card populated with 2 FXS and 2 FXO modules and no lines or phones attached and the GUI Detect Hardware with Advanced checkbox ticked and the Detect Sangoma Hardware checkbox ticked.
     
  2. apmuthu

    Joined:
    Aug 1, 2009
    Messages:
    60
    Likes Received:
    0
    Manually ran wancfg_dahdi and then it was okay.
    Get detailed instructions here.

    1. Log in to terminal
      Type "lspci" in terminal and verify that your Sangoma device in listed

      Run "wancfg_dahdi" Wanpipe configuration tool. Answer to questions based on your area/HW. When prompted "Would you like Wanrouter to automatically start on startup" You should answer "Yes".

      Save the configuration file and your Wanpipe is configured.

      Verify that Elastix sees your Sangoma device by opening your Elastix backend in browser and select "System - Hardware detection". If you don't see your devices ports listed in Hardware detection section try ticking boxes "Replace file chan_dahdi.conf" and "Detect Sangoma hardware", and click "Detect new hardware".

      Try that everything works
     
  3. veritech

    Joined:
    Jul 16, 2008
    Messages:
    92
    Likes Received:
    0
    I found that the default install of Elastix 2.0.3 sets CentOS as the default kernel.

    Code:
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE:  You have a /boot partition.  This means that
    #          all kernel and initrd paths are relative to /boot/, eg.
    #          root (hd0,0)
    #          kernel /vmlinuz-version ro root=/dev/VolGroup01/LogVol00
    #          initrd /initrd-version.img
    #boot=/dev/cciss/c0d0
    default=0
    timeout=5
    splashimage=(hd0,0)/grub/splash.xpm.gz
    hiddenmenu
    title CentOS (2.6.18-238.9.1.el5)
            root (hd0,0)
            kernel /vmlinuz-2.6.18-238.9.1.el5 ro root=/dev/VolGroup01/LogVol00 divider=10 clocksource=acpi_pm
            initrd /initrd-2.6.18-238.9.1.el5.img
    title Elastix (2.6.18-194.3.1.el5)
            root (hd0,0)
            kernel /vmlinuz-2.6.18-194.3.1.el5 ro root=/dev/VolGroup01/LogVol00 divider=10 clocksource=acpi_pm
            initrd /initrd-2.6.18-194.3.1.el5.img
    
    but the sangoma modules are installed into the vmlinuz-2.6.18-194.3.1.el5 kernel. Change default to 1 in the grub.conf file and reboot
     
  4. jgutierrez

    Joined:
    Feb 28, 2008
    Messages:
    5,737
    Likes Received:
    0
    Elastix was booting up with another kernel due to an old bug on an update, this bug was long corrected, the correct procedure that needed to be run was:
    1. yum update elastix
    2. yum update
     

Share This Page