SANGOMA

Wanpipe RPMs for TrixBox

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. Updating Wanpipe Driver ( Wanpipe RPMS update instructions)
  3. Installing Wanpipe RPMs for BRI and/or Hardware DTMF ( A500-BRI users)
  4. Installing Wanpipe driver and zaptel from the source (in some cases)
  5. Trixbox ISO (with sangoma drivers already loaded)
  6. Appendix ( Sample Configuration)
  7. Manual Wanpipe Stop/Start Operation

 

Installing Wanpipe RPMs on Trixbox

For manual RPM installation: 

I. Installation 

To install wanpipe on Trixbox you need to perform the following steps:

1. Download Wanpipe RPMS

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

    #> uname -a
    eg: # Linux asterisk1.local 2.6.9-34.0.2.ELsmp #1 SMP Fri Jul 7 19:52:49 CDT 2006 i686 i686 i386 GNU/Linux
    Check if image that you are running is SMP or Non SMP as the uname -a command indicates above.
     

 

 

 

    
 


You can download RPMs in any local directory on your system (e.g. /usr/src/). You can use "wget" to download RPMs on your system.
e.g.# > wget ftp://ftp.sangoma.com/linux/RPMS/Trixbox-2.2-8/wanpipe-util-3.2.1-0.i686.rpm                   

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  


2. 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

 


3. 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
 Wanpipe Version
(Change Log )
Wanpipe Utilities RPM  Wanpipe Modules RPM(non-SMP) 
Wanpipe Modules RPM(SMP)
 
2.6.0.x  1.4.10-1
 3.3.10  util-rpm  wanpipe-mod-rpms
2.6.0.7   1.4.9.2-8 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. 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)


III. 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

 

 IV. Woomera Configuration using FreePBX

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


 

4. Installation of Wanpipe driver from source code

  1. #>amportal stop
     
  2. #>service zaptel stop
     
  3. #>wanrouter stop
     
  4. Find wanpipe RPM and remove wanpipe RPMS  
    #>rpm -qa | grep wanpipe
    #>rpm -e wanpipe-modules-<version>
    #>rpm -e wanpipe-util-<version>
     
  5.  #>yum install kernel-devel                   or    #>yum install kernel-smp-devel (for smp kernel)
     
  6. #>yum install byacc
     
  7. #>vi /lib/modules/$(uname -r)/build/include/linux/spinlock.h
    [ spinlock.h need to edit manually in order to compile zaptel ]

    look for this line:
    #define DEFINE_RWLOCK(x) rw_lock_t x = RW__LOCK_UNLOCK
     

    (it is around line 407)
    and change it to:
    #define DEFINE_RWLOCK(x) rwlock_t x = RW__LOCK_UNLOCK

  8. Go to www.asterisk.org and download zaptel
    #>tar xvfz zaptel(version)
              Make a symbolic link /usr/src/zaptel to the actual zaptel directory.
              #>ln -s zaptel(version) zaptel
              #>make
              #>make install
     
  9. Install Wanpipe driver from source     

    Wanpipe TDM Installation

    1. Download the appropriate WANPIPE® Release based on the Sangoma Hardware. Refer to Wanpipe Drivers section.
    2. Untar wanpipe release in arbitrary directory (/usr/src/) and hwec-utils is you have a hardware echo canceller.
      #>tar xvfz wanpipe(version)
      After untarring WANPIPE®, the wanpipe/ directory will be created.
    3. Run ./Setup install

      Proceed with installation Select "Y" for each option.

      Under compilation mode:  Select "TDM Only drivers" (Option #2).

      Setup will ask you for location of zaptel sources?
      [By default Setup will look in /usr/src/zaptel]

      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/reistall Zaptel

      Proceed to compile wanpipe drivers.
    4. Proceed with Defaults for the rest of the compilation.
              If any errors are encountered during the compilation of the utilities, click here for assistance.
  10. At the end of driver installation, wancfg_zaptel utility will automatically generate configuration files for you 

 


5. 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




6. 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




7. Manual Wanpipe Stop/Start Operation

      

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

 

Comments

From tirvin - 3/29/08 12:29 PM

I recently upgraded my trixbox 2.2 system using yum, and then installed the newest Sangoma driver RPMs.  I ran into this error:

 /lib/modules/2.6.9-34.0.2.ELsmp/extra/zaptel.ko needs unknown symbol oslec_echo_can_traintap 

Doing some searches online I discovered that a new RPM was needed due to some zaptel echo cancelation changes:  oslec-modules

So, this was the entire procedure: 

  1. mkdir /etc/asterisk-config-backup
  2. cp /etc/zaptel.conf /etc/asterisk/zapata* /etc/wanpipe/wanpipe* /etc/wanpipe/wanrouter.rc /etc/asterisk-config-backup/
  3. yum update
  4. cd /usr/src
  5. wget ftp://ftp.sangoma.com/linux/RPMS/Trixbox-2.2.12/wanpipe-util-3.2.3-0.i686.rpm
    wget ftp://ftp.sangoma.com/linux/RPMS/Trixbox-2.2.12/wanpipe-modules-2.6.9-34.0.2.ELsmp-3.2.3-0.i686.rpm
  6. rpm -e wanpipe-modules-2.6.9-34.0.2.ELsmp
    rpm -e wanpipe-util-3.2.1
  7. yum install oslec oslec-modules
  8. rpm -i wanpipe-modules-2.6.9-34.0.2.ELsmp-3.2.3-0.i686.rpm
    rpm -i wanpipe-util-3.2.3-0.i686.rpm
  9. cp /etc/asterisk-config-backup/wanrouter.rc /etc/wanpipe/wanrouter.rc   (diff the other files to see if you need to restore them -- this was the only file I needed to restore)
  10. reboot

From willie - 3/18/08 2:35 PM

please help me.

the command "setup-sangoma" returns an invalid command message

i don't know what to do?Frown I've followed the advice of various forums but i'm sure there's something elementary that i am missing. what am i doing wrong because this Sangoma A200d card just doesn't want to flow with Trixbox 2.4 PLEASE HELP!!!!!!

From Konrad - 11/1/07 8:00 AM

If you are seeing increasing "overruns" when you run "ifconfig" and you have audio quality issues, check whether or not your system is using XT-PIC or IO-APIC.  You can check this by running the command "cat /proc/interrupts".  XT-PIC is an older interrupt controller that can't always handle the number of interrupts generated by real-time communications. 

For Trixbox 2.2.3

You need to put ACPI=ON APIC=ON at the end of the title line

title CentOS-4 i386 (2.6.9-34.0.2.ELsmp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-34.0.2.ELsmp ro root=LABEL=/1 acpi=on apic=on
        initrd /initrd-2.6.9-34.0.2.ELsmp.img

 

From MikeDent - 1/6/08 10:24 AM

Could I ask what echo cancelling is used in the Trixbox 2.2 ISO for Sangoma A200/Zaptel ?

 

Site

Changes
Index
Search

 

User

 

Log In
Register

 
 

Last Modified 5/16/08 12:32 PM