Wanpipe RPMs for TrixBox CE

    Wanpipe Trixbox RPMs are built for original kernel and Zaptel modules that comes with Default Trixbox.

    Wanpipe modules are dependent on kernel modules and Zaptel modules!
    If you recompiled a newer kernel or Zaptel, you will need to compile Wanpipe drivers manually! 


     

    1. Installing Wanpipe RPMs On Trixbox
    2. Installing Wanpipe RPMs for BRI and/or Hardware DTMF(B600 & A500-BRI users)

      Updating Wanpipe- RPM
    3. Updating Wanpipe Driver (Wanpipe RPMS update instructions)
    4. Updating trixbox  (wanpipe - RPM update  + yum update for Zaptel & Asterisk)
       
      Installation from the source / trixbox ISO with Sangoma Driver
    5. Installing Wanpipe driver and zaptel from the source (in some cases)
    6. Trixbox ISO (with Sangoma drivers already loaded

      Appendix / Operation / RPM Check
    7. Appendix (Sample Configuration)
    8. Manual Wanpipe Stop/Start Operation
    9. Checking installed Wanpipe / Zaptel / Asterisk RPMs
    10. Installing Voice Time

     

    Installing Wanpipe RPMs on Trixbox

    For manual RPM installation: 

    I. Installation 

    To install Wanpipe on Trixbox perform the following steps:

    1. Download Wanpipe RPMS

    a) Run the command "uname -a" to get the kernel version of your Trixbox. The output should look like the output below. Now as you can see in the output below the kernel version is "2.6.18-128.1.10.el5" so note this down.

    Linux trixbox1.localdomain 2.6.18-128.1.10.el5 #1 SMP

    b) Next run the command "rpm -qa | grep zaptel" (or rpm -qa | grep dahdi the output will be simular) and you will get the output below. Now as you can see in the output below the zaptel version is "1.4.12.9-1" so note this down as well.

    zaptel-1.4.12.9-1_trixbox
    zaptel-modules-1.4.12.9-1_trixbox.2.6.18_128.1.10.el5

    c) Next run the command "asterisk -V" and the output will be simular to the one below.

    Asterisk 1.4.22-4 RPM by vc-rpms@voipconsulting.nl

    d) Now that you have the zaptel/dahdi version, kernel version and the Asterisk version noted down find a RPM below that is built for your all three of those. It is important to have a RPM built for all 3 of those componets because the RPM builds with the source of zaptel/dahdi, linux kernel and Asterisk. Now note that some RPMs do not require a certain Asterisk version and this why that is not specified below for some rpms. Now if you can not find a RPM built for the combination you have then you have to go upgrade one of the components to use one of the RPMs below or compile from source as shown at http://wiki.sangoma.com/wanpipe-asterisk-trixbox-rpms#drivfrmsource.

    e) Once you have located the RPMs for your system then simply download the RPMs by right clicking on the link and selecting "Copy Link Location" in your browser (this may vary depending on which browser you use). Once you click this you have the URL in your clip board (copy/paste) so you can simply run the command "wget " in your SSH window and then paste the URL into the window after this. Do this for both the Utils and the Modules and the two commands should look simular to the ones below. Once the files are downloaded please move to the next step.

    wget ftp://ftp.sangoma.com/linux/RPMS/2.6.2.3/wanpipe-util-3.5.4.8-0.i686.rpm
    wget ftp://ftp.sangoma.com/linux/RPMS/2.6.2.3/wanpipe-modules-2.6.18-128.1.10.el5-3.5.4.8-0.i686.rpm

    * BRI Support Coming Soon


     

     

     

     

    2. Install the Wanpipe rpms:

    #>rpm -i wanpipe-modules-<version>.rpm
    #>rpm -i wanpipe-util-<version>.rpm

    3. Run following command to check for detected Sangoma card

               #> wanrouter hwprobe
               #> wanrouter hwprobe verbose (To check FXO/FXS modules for Analog cards)

     

    II. Configuration

    1. For all Sangoma AFT cards run:

      #>setup-sangoma

      The setup-sangoma script will automatically configure all AFT cards on your system.
      Please follow setup-sangoma prompts and configure your cards based on Telco Line information.
      (Eg: T1/E1, Clock MASTER/NORMAL)


    III. Operation

    1. To manually start wanpipe devices, zaptel and asterisk run:
      #> wanrouter start
      #> ztcfg   -vvv           
      #> amportal start (or run #>asterisk)
      #> asterisk -r ( to connect with Asterisk server )  
    2. To manually stop wanpipe you must stop asterisk first
      #> amportal stop (or run "stop now" on Asterisk CLI
      #> wanrouter stop 

    NOTE:

    The latest stable driver: the 3.4 series support the BRI card (A500).

    Also a new parameter has been added in the wanpipe configuration. Please see the change log for more info: ftp://ftp.sangoma.com/linux/current_wanpipe/ChangeLog.stable


    2. Installing Wanpipe RPMs for A500(BRI) and/or Hardware DTMF

      Note: A500 BRI cards uses chan_woomera.so to communicate with Asterisk, therefore it requires to create custom Woomera trunk for FreePBX 
                interface. Instructions to create and configure Woomera trunk can be found at http://wiki.sangoma.com/WoomeraFreepbx 

    I. Download Wanpipe RPMS

    • Check your TrixBox Kernel Image (SMP or Non SMP)

      #> uname -a
      eg: Linux tesla 2.6.18-8.el5 #1 SMP Thu Mar 15 19:57:35 EDT 2007 i686 i686 i386 GNU/Linux
       
      Check if image that you are running is SMP or Non SMP as the uname -a command indicates above.  
    Download Sangoma Wanpipe RPM based on above info (SMP or Non SMP)
    Click on each link to download Sangoma Wanpipe RPM

               Recent trixbox Releases:

    Trixbox
    CE
    Zaptel-
    Headers
    Asterisk  Wanpipe Version
    (Change Log )
    Wanpipe Utilities RPM  Wanpipe Modules RPM(non-SMP) 
    Wanpipe Modules RPM(SMP)
     
    2.6.2.3 1.4.12.9-1 1.4.22-4 3.4.2.3 util-rpm wanpipe-mod-rpm
    2.6.2.1 1.4.12.1-1 1.4.22-2 3.4.2.3 util-rpm wanpipe-mod-rpm
    2.6.2.1-2 1.4.12.1-1 1.4.22-2 3.3.16 util-rpm wanpipe-mod-rpms
    2.6.1  1.4.10.1-2     3.3.10  util-rpm wanpipe-mod-rpms
    2.2.12   1.2.22   3.3.8 util-rpm non-smp-mod-rpm  smp-mod-rpm
    Old trixbox release:
    Trixbox
    CE
     Wanpipe Version
    (Change Log )
    Wanpipe Utilities RPM  Wanpipe Modules RPM(non-SMP) 
    Wanpipe Modules RPM(SMP)
     
    2.2 3.3.0.19 util-rpm non-smp-mod-rpm smp-mod-rpm


     

     

     

    2. Install the Wanpipe rpms:
    #>rpm -i wanpipe-modules-<version>.rpm
    #>rpm -i --force wanpipe-util-<version>.rpm 
     II. Hardware Detection
    After the RPM installation is completed, run "wanrouter hwprobe" command and confirm the hardware is detected by the driver. A500-BRI and Analog card users can run the command "wanrouter hwprobe verbose" and confirm the port is detected/or configured as desired. A500 ports should be configured as TE mode if the line is connected with the Telco and only configured as NT mode, if you are connecting ISDN phones with the card. Visit A500 hardware configuration to confirm your hardware is configured properly. 
    Example:
    # wanrouter hwprobe verbose
    -----------------------------------------
    | Wanpipe Hardware Probe Info (verbose) |
    -----------------------------------------
    1 . AFT-A500-SH : SLOT=0 : BUS=8 : IRQ=11 : PORT=1 : HWEC=64 : V=32
    +01:TE
    2 . AFT-A500-SH : SLOT=0 : BUS=8 : IRQ=11 : PORT=2 : HWEC=64 : V=32
    +02:TE

     

    III. Configuration

    1. For all Sangoma AFT cards run:

      #>setup-sangoma

      The wancfg_smg script will automatically configure A500 and all AFT cards on your system.
      Please follow wancfg_smg prompts and configure your cards based on Telco Line information.
      (Eg: T1/E1, Clock MASTER/NORMAL)


    IV. Operation

    1. To manually start wanpipe devices, zaptel and asterisk run:
      #> wanrouter start
      #>smg_ctrl start
      #> ztcfg        (If you have AFT series T1/E1 or Analog cards)         
      #> amportal start
      #> asterisk  -r (To connect with Asterisk server)  
    2. To manually stop wanpipe you must stop asterisk first
       #>amportal stop
      #>smg_ctrl stop
      #> wanrouter stop
      #>service zaptel stop

     

      V. Woomera Configuration using FreePBX

    A500 uses woomera to communicate with Asterisk. You will need to add customize the Woomera Trunk. Step by Step instructions for the Woomera Trunk can be found at http://wiki.sangoma.com/WoomeraFreepbx 


     

     


    4. Updating trixbox  (wanpipe + yum update for Zaptel & Asterisk)

     

     Note: You will be following this instruction in case where you are using yum update to update to latest trixbox (for example updating from 2.6.0.7 to 2.6.1) .

    1. Back up following configuration files and directories
      /etc/wanpipe/
      /etc/zaptel.conf and
      /etc/asterisk/
      You can use "cp" to back up files and "tar" to backup directory.
    2. Stop Asterisk, Wanpipe and Zaptel (Note: This will drop all the active calls)
      #> amportal stop
      #> wanrouter stop
      #>service zaptel stop
    3. Remove wanpipe-rpms

      #>rpm -qa | grep wanpipe (Search for Installed wanpipe RPMs)

      Remove wanpipe RPMS

      #>rpm -e wanpipe-modules-
      #>rpm -e wanpipe-util-
    4. Use " yum update" to update Zaptel and Asterisk
    5. Go to http://wiki.sangoma.com/wanpipe-asterisk-trixbox-rpms#fstinall and follow instruction to install new RPMs.
    6.  Note: Installed Zaptel version must match corresponding Zaptel-version, trixbox-version and wanpipe-rpms.
      For example. To use trixbox-2.6.1 RPMS from the table installed zaptel version should be zaptel-1.4.10.1-2  .
      You can use "rpm -qa | grep zaptel" to check install Zaptel version. 

     

     

     


     

     

     

    5. Installation of Wanpipe driver from source code

    a) Zaptel Method (Up to and including Trixbox 2.6)

    1) Copy and paste the commands below into your SSH window and this will automatically get the required packages.

    yum -y install kernel-devel-$(uname -r);
    yum -y install libtool;
    yum -y install gcc;
    yum -y install patch;
    yum -y install perl;
    yum -y install bison;
    yum -y install gcc-c++;
    yum -y install ncurses;
    yum -y install ncurses-devel;
    yum -y install flex;
    yum -y install libtermcap-devel;
    yum -y install lksctp-tools-devel ;
    rpm -qa | grep zaptel

    2) Then you should see the following output on the screen.Now the Zaptel version is 1.4.12.1 in the following example, it is not 1.4.12.1-1 because the "-1" is a Trixbox version and we are just considered about the Zaptel version.

    zaptel-1.4.12.1-1_trixbox
    zaptel-modules-1.4.12.1-1_trixbox.2.6.18_128.1.10.el5

    3) Once we have the Zaptel version go to http://downloads.asterisk.org/pub/telephony/zaptel/releases/ and look for the version from the previous step. So in this case the file would be called zaptel-1.4.12.1.tar.gz. So to download this file simply run the commands below.

    •     cd /usr/src/
    •     wget http://downloads.asterisk.org/pub/telephony/zaptel/releases/zaptel-1.4.12.1.tar.gz    *NOTE: Change this for your Zaptel Version

    4) Next untar the file using the command below.

    • tar xvfz zaptel-<version>.tar.gz

    5) Once this is complete download the Wanpipe version of your choice from http://wiki.sangoma.com/wanpipe-linux-drivers

    6) Once the version is found run the commands below to get it on to the system and start compiling

    • wget ftp://ftp.sangoma.com/linux/current_wanpipe/wanpipe-<version>.tgz
    • tar xvfz wanpipe-<version>.tgz
    • cd wanpipe-<version>
    • ./Setup install

    7) Proceed with installation Select "Y" for each option. Under compilation mode:  Select "TDM Only drivers" (Option #2). Proceed with Defaults for the rest of the compilation. Last step in installation will ask you to configure wanpipe cards for Zaptel. (Note wancfg_zaptel configurator will overrite your zaptel.conf and zapata.conf files and save the originals as  zaptel.conf.bak and zapata.conf.conf.bak)

    b) Dahdi Method (Trixbox 2.8 and greater)

    1) Copy and paste the commands below into your SSH window and this will automatically get the required packages.

    yum -y install kernel-devel-$(uname -r);
    yum -y install libtool;
    yum -y install gcc;
    yum -y install patch;
    yum -y install perl;
    yum -y install bison;
    yum -y install gcc-c++;
    yum -y install ncurses;
    yum -y install ncurses-devel;
    yum -y install flex;
    yum -y install libtermcap-devel;
    yum -y install lksctp-tools-devel ;
    rpm -qa | grep dahdi

    2) Then you should see the following output on the screen.Now the Dahdi-Linux version is 2.2.0 in the following example, it is not 2.2.0-4 because the "-4" is a Trixbox version and we are just considered about the Dahdi-Linux version.

    dahdi-tools-doc-2.2.0-4_trixbox
    dahdi-tools-2.2.0-4_trixbox
    asterisk16-dahdi-1.6.0.10-1_trixbox
    dahdi-linux-2.2.0-4_trixbox
    kmod-dahdi-linux-2.2.0-4_trixbox.2.6.18_128.1.10.el5

    3) Once we have the Dahdi-Linux version go to http://downloads.asterisk.org/pub/telephony/dahdi-linux/releases/ and look for the version from the previous step. So in this case the file would be called dahdi-linux-2.2.0.tar.gz. So to download this file simply run the commands below.

    •     cd /usr/src/
    •     wget http://downloads.asterisk.org/pub/telephony/dahdi-linux/releases/dahdi-linux-2.2.0.tar.gz    *NOTE: Change this for your Dahdi Version

    4) Next untar the file using the commands below.

    • tar xvfz dahdi-linux-<version>.tar.gz

    5) Once this is complete download the Wanpipe version of your choice from http://wiki.sangoma.com/wanpipe-linux-drivers

    6) Once the version is found run the commands below to get it on to the system and start compiling

    • wget ftp://ftp.sangoma.com/linux/current_wanpipe/wanpipe-<version>.tgz
    • tar xvfz wanpipe-<version>.tgz
    • cd wanpipe-<version>
    • ./Setup install

    7) Proceed with installation Select "Y" for each option. Under compilation mode:  Select "TDM Only drivers" (Option #2). Proceed with Defaults for the rest of the compilation. Last step in installation will ask you to configure wanpipe cards for Dahdi. (Note wancfg_dahdi configurator will overrite your system.conf and chan_dahdi.conf files and save the originals as system.conf.bak and chan_dahdi.conf.bak)


    6. trixbox ISO with Sangoma Wanpipe Drivers Installed

    1. trixbox  ISO 2.2.12 with Stable Wanpipe Voice Drivers                             trixbox-2.2.12-wanpipe-3.2.3.iso
    2. trixbox ISO 2.2 with Stable Wanpipe Voice Drivers                                   trixbox-2.2-2-wanpipe-2.3.4-9.iso

     

     



    3. Upgrade of the driver

     

    1. Stop Asterisk and Wanrouter
      #>amportal stop
      #>wanrouter stop
      #>service zaptel stop
    2. Remove the previous driver:
      #>uname -a (To check kernel version)
      #> rpm -qa | grep wanpipe (Search for Installed RPMs)
      Remove wanpipe RPMS
      #>rpm -e  wanpipe-modules-<version>
      #>rpm -e  wanpipe-util-<version>
    3. Following the instructions at the this link to download and install the new drivers. A500 BRI and hardware DTMF use 3.3.x RPMS




    7. Appendix

    Note: Always use "setup-sangoma" utility to configure wanpipe, zaptel and asterisk 

    For other additional information, view the Wanpipe-Asterisk Appendix

    Sample Configuration files:
    1 Incoming T1 ISDN PRI line and 1 T1 connecting to a channel bank with 24 fxs channels

    Your zaptel.conf

     

     #incoming PRI
    span = 1,1,0,esf,b8zs
    bchan = 1-23
    dchan = 24

    #outgoing T1 to channel bank
    span = 2,0,0,esf,b8zs
    fxoks = 25-47

     

    Your zapata-auto.conf

     

    #incoming pri
    signalling = pri_cpe
    context=from-zaptel
    group=0
    channels=>1-23

    #outgoing T1 to channel bank
    signalling = fxo_ks
    context=from-internal
    group=1
    channels=> 25-48

     

    2 Incoming E1 EuroISDN lines from a Telco

    Your zaptel.conf

     

     #first incoming PRI
    span = 1,1,0,ccs,hdb3,crc4
    bchan = 1-23
    dchan = 24

    #second incoming PRI
    span = 2,2,0,ccs,hdb3,crc4
    bchan = 1-15,17-31
    dchan = 16

     

    Your zapata-auto.conf

    signalling = pri_cpe
    group = 0
    context = from-zaptel
    channels=> 1-15,17-31

    signalling = pri_cpe
    group = 0
    context = from-zaptel
    channels=> 32-46,48-72




    8. Manual Wanpipe Stop/Start Operation

     

    1. To manually stop Wanpipe you must stop Asterisk first
      #> amportal stop 
      #>smg_ctrl stop   (only for A500 BRI users)
      #> wanrouter stop
      #>service zaptel stop
    2. To manually start Wanpipe devices, Zaptel and Asterisk run:
      #> wanrouter start
      #>smg_ctrl start    (only for A500 BRI users)
      #> ztcfg   -vvvv     (If you have AFT series T1/E1 or Analog cards)         
      #>amportal start

      9. Checking installed Wanpipe / Zaptel / Asterisk RPMs

    1.  Checking for Wanpipe RPMS
      #> rpm -qa | grep wanpipe
    2. Checking for Zaptel RPMs
      #> rpm -qa | grep zaptel
    3. Checking for Asterisk
      #> rpm -qa | grep Asterisk

     


    Voice Time Installation

    • Insure you have installed all of the required packages listed below.

    yum -y install kernel-devel-$(uname -r)
    yum -y install gcc
    yum -y install patch
    yum -y install perl
    yum -y install bison
    yum -y install gcc-c++
    yum -y install ncurses
    yum -y install ncurses-devel
    yum -y install flex
    yum -y install libtermcap-devel
    yum -y install lksctp-tools-devel

    • Insert the USB Wanpipe VoiceTime Device into the Server USB Port.  
    • Run the command "rpm –qa | grep zaptel" to get your zaptel version and then go to  http://downloads.asterisk.org/pub/telephony/zaptel/releases/ to download the source to /usr/src/. Eg wget http://downloads.asterisk.org/pub/telephony/zaptel/releases/zaptel-1.4.11.tar.gz
    • Next go to /usr/src/zaptel-<version> and run "./configure", "make", "make install" and "make config"
    • Then download the Wanpipe Voicetime Driver
    • Untar and change directory
      -> tar xfz wanpipe-voicetime-<ver>.tgz
      -> cd wanpipe-voicetime-<ver>  
    • Build Wanpipe VoiceTime for Currently Running Zaptel Module
      -> make ZAPDIR=/usr/src/zaptel-<ver>

      ZAPDIR= location of zaptel source used to build and install zaptel
      By default ZAPDIR=/usr/src/zaptel  
    • Install VoiceTime module into current system
      -> make install  
    • Install bootup startup script for VoiceTime
      -> make boot
    • Next stop Asterisk by running "amportal stop" and then stop zaptel with "/etc/init.d/zaptel stop"
    • Start Wanpipe VoiceTime using Zaptel Startup Script
      -> /etc/init.d/zaptel start 
    • Then start Asterisk up again using "amportal start"
    • Confirm that VoiceTime Sync Tool is working
      -> zttest
      -> asterisk -rx "zap show status"    - Insure it says Voice Time in the output.