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!
- Installing Wanpipe RPMs On Trixbox
- Installing Wanpipe RPMs for BRI and/or Hardware DTMF (A500-BRI users)
Updating Wanpipe- RPM
- Updating Wanpipe Driver (Wanpipe RPMS update instructions)
- Updating trixbox (wanpipe - RPM update + yum update for Zaptel & Asterisk)
Installation from the source / trixbox ISO with Sangoma Driver
- Installing Wanpipe driver and zaptel from the source (in some cases)
- Trixbox ISO (with Sangoma drivers already loaded
Appendix / Operation / RPM Check
- Appendix (Sample Configuration)
- Manual Wanpipe Stop/Start Operation
- Checking installed Wanpipe / Zaptel / Asterisk RPMs
Installing Wanpipe RPMs on Trixbox
For manual RPM installation:
I. Installation
To install Wanpipe on Trixbox 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.
Also check install Zaptel Module RPMS
e.g. # rpm -qa | grep zaptel
zaptel-modules-1.4.10.1-2.2.6.18_53.1.4.el5
zaptel-1.4.10.1-2
[Note: Wanpipe-3.2.x-Module-RPM has dependency check for Zaptel]
- Download Sangoma Wanpipe RPM based on above info (SMP or Non SMP)
Click on each link to download Sangoma Wanpipe RPM
Recent Stable trixbox Releases:
Old trixbox releases:
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
- 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
- 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 )
- To manually stop wanpipe you must stop asterisk first
#> amportal stop (or run "stop now" on Asterisk CLI
#> wanrouter stop
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:
Old trixbox release:
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
- 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
- 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)
- 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) .
- 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.
- Stop Asterisk, Wanpipe and Zaptel (Note: This will drop all the active calls)
#> amportal stop
#> wanrouter stop
#>service zaptel stop
- Remove wanpipe-rpms
#>rpm -qa | grep wanpipe (Search for Installed wanpipe RPMs)
Remove wanpipe RPMS
#>rpm -e wanpipe-modules-
#>rpm -e wanpipe-util-
- Use " yum update" to update Zaptel and Asterisk
- Go to http://wiki.sangoma.com/wanpipe-asterisk-trixbox-rpms#fstinall and follow instruction to install new RPMs.
- 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
- #>amportal stop
- #>service zaptel stop
- #>wanrouter stop
- Find wanpipe RPM and remove wanpipe RPMS
#>rpm -qa | grep wanpipe
#>rpm -e wanpipe-modules-<version>
#>rpm -e wanpipe-util-<version>
- #>yum install kernel-devel or #>yum install kernel-smp-devel (for smp kernel)
- #>yum install byacc
- #>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
- 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
- Install Wanpipe driver from source
Wanpipe TDM Installation
- Download the appropriate WANPIPE® Release based on the Sangoma Hardware. Refer to Wanpipe Drivers section.
- 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.
- 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.
- Proceed with Defaults for the rest of the compilation.
If any errors are encountered during the compilation of the utilities, click here for assistance.
- At the end of driver installation, wancfg_zaptel utility will automatically generate configuration files for you
6. trixbox ISO with Sangoma Wanpipe Drivers Installed
- trixbox ISO 2.2.12 with Stable Wanpipe Voice Drivers trixbox-2.2.12-wanpipe-3.2.3.iso
- trixbox ISO 2.2 with Stable Wanpipe Voice Drivers trixbox-2.2-2-wanpipe-2.3.4-9.iso
3. Upgrade of the driver
- Stop Asterisk and Wanrouter
#>amportal stop
#>wanrouter stop
#>service zaptel stop
- 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>
- 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
- To manually stop Wanpipe you must stop Asterisk first
#> amportal stop
#>smg_ctrl stop (only for A500 BRI users)
#> wanrouter stop
#>service zaptel stop
- 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
- Checking for Wanpipe RPMS
#> rpm -qa | grep wanpipe
- Checking for Zaptel RPMs
#> rpm -qa | grep zaptel
- Checking for Asterisk
#> rpm -qa | grep Asterisk
| 
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!!!!!!