USB FXO (U100)

    Additional Links:

    [ FreeSWITCH users Click Here ]


    IMPORTANT LIMITATIONS: The USB FXO drivers are only guaranteed to work on Centos Installations.Due to rapidly changing kernel USB core we have to limit the USB FXO drivers to Centos installations only.
    If you are trying to use the USB FXO on anything else than Centos and you have issues we might not be able to help you.

    DAHDI 2.6 Currently not supported, please use DAHDI 2.5.0.2 or below

    For maximum reliablity, the USB FXO should not be used through a USB Hub. While some hubs and configurations work successfully, we cannot guarantee the device will function properly through hub devices on all systems. If you are encountering issues with using this device through a USB hub, please try connecting it directly to the system USB bus.

     


    Driver Requirements

    There are system requirements before you can install the Sangoma USBFXO driver.

    -> Go to USBFXO Wanpipe Requirements to download all the system requirements prior to Driver installation


    Download Drivers

    Download:
    -> LINUX: Wanpipe-<Latest>.tgz


    Firmware Installation

    Firmware can be found at http://wiki.sangoma.com/sangoma-hardware#aft_firmware

    Update Instructions can be found at http://wiki.sangoma.com/wanpipe-linux-aft-firmware-update


    Hardware Installation

    You will just simply have to plug the USB cable into the U100 and then into the server.
     
    NOTE: The current driver does not support hot-plug functionality, so after our drivers are started you can not safely add/remove the device. To check if the drivers are running run "wanrouter status", if they are running run "wanrouter stop all" after insuring Asterisk is stopped. Please see USBfxo Configuration/Operation for further details. 
     

    Driver Installation 

     

    1. Untar wanpipe release in arbitrary directory (/usr/src/ is recommended).
       #>tar xvfz wanpipe-<version>.tgz
       #>cd wanpipe-<version>

              After untarring WANPIPE, the wanpipe<version>/ directory will be created.  

        2.   Run ./Setup install from the newly created wanpipe-<version> directory 
        
                    #>./Setup install 
     
              Proceed with installation Select "Y" for each option.       
        3.   Under compilation mode:  Select "TDM Only drivers" (Option #2).

               Setup will ask you for location of sources

               For Zaptel:

              -> [By default Setup will look in /usr/src/zaptel]
     
              Zaptel 1.4 -> wanpipe drivers use zaptel supported hwdchan so no patching is needed.
                                     Zaptel does not need to be recompiled
     
              Zaptel 1.2-> Setup will ask you if you would like to add support for Sangoma HW HDLC DCHAN PRI

                                    to Zaptel.
                                   "Enable TDMV DCHAN Native HDLC Support & Patch Zaptel ? (y/n)"
                                    Select "Y" to Enable HW HDLC on DCHAN PRI in Zaptel.


                                  Setup will ask you if you would like to recompile/reinstall Zaptel.
                                 "Recompile/reinstall zaptel (recommended) ? (y/n) "
                                  Select "Y" to recompile/reinstall Zaptel

                For Dahdi: 

              -> [By default Setup will look in /usr/src/dahdi]

        4.     Proceed with Defaults for the rest of the compilation.  

        5.     Last step in installation will ask you to configure wanpipe cards

                Proceed with YES this is your initial installation

         For Zaptel: 
            -> Note wancfg_zaptel  will overwrite your zaptel.conf and zapata.conf files and save the originals

                as zaptel.conf.bak and zapata.conf.bak

                 For Dahdi: 
                    -> Note wancfg_dahdi  will overwrite your system.conf and chan_dahdi.conf files and save the

                        originals as system.conf.bak and chan_dahdi.conf.bak

                The configuration process continues on Configuration Section

                If any errors are encountered during the compilation of the utilities, click here for assistance.

     
    Confirm Successful Wanpipe Zaptel/Dahdi Installation

    1. Confirm successful Wanpipe Zaptel/Dahdi installation run:
      #>wanrouter hwprobe
      -------------------------------
      | Wanpipe Hardware Probe Info |
      -------------------------------
      1. U100       : BUS=2 : V=00

      Card Cnt: U100=1

      This command will load the wanpipe and zaptel/Dahdi modules and will print out list of all Sangoma hardware installed on the system. 

     

     


    USBfxo Configuration/Operation

         For Zaptel

               1) To configure the device just simply run "wancfg_zaptel" from the command line.

          2) To start the device with Asterisk follow the three steps below.

        # wanrouter start (to start our drivers)

        # ztcfg -vvv (to start Zaptel)

        # asterisk (to start Asterisk)

        # asterisk -r (to login to the Asterisk CLI)

        # zap show channels (to see all the zap channels)

     

    For Dahdi

      1) To configure the device just simply run "wancfg_dahdi" from the command line.

      2) To start the device with Asterisk follow the three steps below.

          # wanrouter start (to start our drivers)

          # dahdi_cfg  (to start Dahdi)

          # asterisk (to start Asterisk)

          # asterisk -r (to login to the Asterisk CLI)

          # dahdi show channels (to see all the dahdi channels)

     

    To stop the device with Asterisk follow the two steps below.

         # asterisk -r (to login to the Asterisk CLI)

         # stop now (to stop Asterisk)

         # wanrouter stop (to stop our drivers)


    LED Status Indication

    1. After power up, green and red will cycle for about 10 seconds, this is the bootloader running
    2. Red blinking means driver didn’t connect to the device, either because wanrouter wasn’t started yet or because some IDs were not read properly from the device
    3. Red solid means the driver is connected and things are running normal