Installing wanpipe on Asterisk@Home/Trixbox

To install wanpipe on Asterisk@Home/Trixbox you need to perform the following steps:
Note: Do not perform yum update after installing asterisk@home/Trixbox

1. Remove Zaptel autoload on bootup
2. Install required packages
3. Download and install zaptel sources
4. Install Wanpipe
5. Re-compile/re-install Zaptel
6. Configure Zaptel and Asterisk
7. Configure Sangoma cards
8. Add script to auto-execute Zaptel
9. Make sure your Zap channels registered in Asterisk
10. Configure your dialplan

1. Remove Zaptel autoload on bootup
Asterisk@Home/Trixbox comes with a script that loads Digium modules upon system bootup. If your system has only Sangoma cards, then you can remove that script:

#>rm /etc/init.d/zaptel

Remove the corresponding symbolic links

#>rm /etc/rc?.d/*zaptel -f

2. Install required packages
You will need a c++ compiler to be able to compile our utilities.

a. If your system is connected to the internet:

#>yum install gcc-c++

b. if your system is not connected to the internet, you will have to download the RPM packages and install them. libstdc++-devel is required to be able to install gcc-c++.

#>rpm --install libstdc++-devel-3.4.4-2.i386.rpm
#>rpm --install gcc-c++-3.4.4-2.i386.rpm
(Note: Any version of gcc-c++ and lidstdc++ should work)

You will need the yacc package to be able to compile our utilities.

a. If your system is connected to the internet:

#>yum install byacc

b. if your system is not connected to the internet, you will have to download the RPM package and install them.

#>rpm --install byacc-1.9-26.i386.rpm
(Note: Any version of byacc should work)

3. Download and install Zaptel sources (trixbox only)

             #> cd /usr/src/
             #> wget ftp://ftp.digium.com/pub/zaptel/zaptel-1.2-current.tar.gz
             #> tar xvfz zaptel-1.2-current.tar.gz
             #> ln -s zaptel-(the current zaptel version) /usr/src/zaptel
Reboot your system so that it loads without the zaptel/wct* modules

The current Trixbox kernel headers (Trixbox 1.1) have a typo and this causes Zaptel not to compile. See this

4. Install Wanpipe
Download the latest wanpipe drivers (2.3.3 or 2.3.4) here.
Untar them in the /usr/src/ directory.

    #>mv wanpipe-beta2-2.3.4.tgz /usr/src
    #>cd /usr/src
    #>tar xvfz wanpipe-beta2-2.3.4.tgz
    #>cd wanpipe
    #>./Setup install --protocol=TDM

    Select Yes for all (Y/N) prompt.
     After installation, type:

#>wanrouter hwprobe

To confirm that your wanpipe installation modules were installed properly.

4. Re-compile/re-install Zaptel (2.3.3 drivers only)
Wanpipe drivers patch Zaptel so that the HDLC framing is performed in hardware, therefore zaptel re-compilation/re-installation is needed.

a. If you have wanpipe 2.3.3 drivers, you need to re-compile/re-install zaptel

#>cd /usr/src/zaptel
#>make clean;make install; make install-udev

b. If you have wanipe 2.3.4 drivers or later, and you answered "yes" to the "Would you like to recompile/reinstall zaptel?" during step 3, then you do not have to recompile/reinstall zaptel.

5. Configure Zaptel and Asterisk
Sample zaptel.conf and zapata.conf files can be found here.

#>vi /etc/zaptel.conf
#>vi /etc/asterisk/zapata.conf

Note: for asterisk@home 2.5 or later, put the zapata settings in zapata-auto.conf instead of zapata.conf.

7. Configure Sangoma cards
Click here for information on how to configure Sangoma cards.

8. Add script to auto-execute Zaptel
Click here for information on how to auto-execute Zaptel after Wanpipe driver load.

9. Make sure your Zap channels are registered
In the Asterisk CLI, type:

#>zap show channels

Check that you have the correct amount of channels registered in Asterisk, and in the proper context.
You should an entry for each of your zap channels in addition to your pseudo channel, for example:
       Chan   Extension   Context
       pseudo                  from-incoming
       1                            from-pstn
     2                            from-pstn
       3                            from-pstn

10. Configure your dialplan
Configure your dialplan

#>vi /etc/asterisk/extensions_additional.conf or through the AMP Portal.

Comments

From davidy - 8/8/06 2:55 PM

Hi Underdog,

please send a support request to techdesk@sangoma.com with your /etc/wanpipe/wanpipe1.conf /etc/zaptel.conf /etc/asterisk/zapata.conf /etc/asterisk/zapata-auto.conf

>From UnDeRDoG - 8/7/06 4:40 PM [Delete]

>This is driving me bonkers, I have the A104 card and just can’t get rid of the echo. I loaded 1.0.0 and had no echo what so ever, load 1.1.1 and bad echo what gives? Been editing Zaptel.conf until I feel my eyes are going to pop out, I give up! Can someone help.

>No IRQ problems all is clear, Like I said had this working with no problems. I did load

Zaptel drivers old and new. No good! Please help…..

From UnDeRDoG - 8/7/06 4:40 PM

This is driving me bonkers, I have the A104 card and just can’t get rid of the echo. I loaded 1.0.0 and had no echo what so ever, load 1.1.1 and bad echo what gives? Been editing Zaptel.conf until I feel my eyes are going to pop out, I give up! Can someone help.

No IRQ problems all is clear, Like I said had this working with no problems. I did load

Zaptel drivers old and new. No good! Please help…..

From bthurber - 8/17/06 9:44 AM

Poking around on the sangoma ftp site, it looks like they are working on a trixbox RPM for the Sangoma drivers - I hope this bodes well for being able to yum update - would be good to get official word from Sangoma techs on this - Brad

From bthurber - 8/15/06 10:12 AM

I'm current running AAH 2.7 with an A200 card and the beta sangoma drivers from earlier this year. I'm considering starting over with TrixBox so that I can get updates automatically for all of the pieces. I know the instructions above say not to do a 'yum update' but no reason is given. Does this break sangoma drivers? Is there a workaround?

From davidy - 7/17/06 3:10 PM

Zaptel not compiling on some RedHat, CentOs and Trixbox systems.

If you are getting these errors when compiling zaptel:

/usr/src/zaptel/zaptel.c:384: error: syntax error before "zone_lock"
/usr/src/zaptel/zaptel.c:384: warning: type defaults to `int' in declaration of `zone_lock'
/usr/src/zaptel/zaptel.c:384: error: incompatible types in initialization
/usr/src/zaptel/zaptel.c:384: error: initializer element is not constant

:
:

There is a typo in your kernel headers.
View a file called spinlock.h in your kernel source directory:

#>vi /lib/modules/$(uname -r)/build/include/linux/spinlock.h
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

then try to recompile Zaptel again.

From davidy - 7/14/06 6:52 PM

There was a bug with the A104/A104D and reference clocking, if you were using the A104/A104D and was having problems with faxing, please use the new wanpipe drivers:

ftp://ftp.sangoma.com/linux/custom/2.3.4/wanpipe-beta5-pre22-2.3.4.tgz

Note: HWEC utils are included in this package.

We also saw a customer that was using Zaptel-1.2.5 and started getting Fax problems when using Zaptel-1.2.6, moving back to Zaptel-1.2.5 fixed his problem, so if you were not using the A104/A104d can you try to downgrade to zaptel-1.2.5 on your system and see if this makes a difference?

We are still running testing faxes in our labs and if you are still having problems with faxes, please email techdesk@sangoma.com and describe your fax setup.

From gcleaves - 7/10/06 9:14 AM

I am experiencing fax problems on my A104d card. What is Sangoma's response to these widespread fax complaints? A €2000+ piece of telephony equipment should be able to handle this most basic of features.

From current - 6/16/06 3:56 PM

You have to wget the sources for zaptel now as the zaptel source is not now on TrixBox

so you can't make clean make install as above on a fresh TrixBox install.

We need RPM for wanpipe.

Can Sangoma support please have a look at how TrixBox now works.

I also beleave there are Fax Problems with All Samgamo cards and there

are new beta5 drivers, which I have been unable to download as the ftp

site is down.

Alan

From current - 6/16/06 3:45 PM

The new version of A@H /TrixBox has a new update feature TrixBox-Update.sh

This is now RPM baised and using yum will break that update feature of TrixBox

A yum on trixbox may update Zaptel if a new version is released and you would

have to reinstall wanpipe.

At the moment all we can do to work with sangoma and TrixBox is to rebuild

Zaptel from source and install wanpipe, this is because TrixBox which is now RPM baised

has no RPM for wanpipe.

Alan

From MikeDent - 6/15/06 11:44 AM

At which stage is it safe to do a yum update? Surely not doing this leaves your system out of date, missing various patches/fixes and possibly vulnerable?

Which part of the update breaks things? Thanks
Mike

From borthner - 5/8/06 1:13 PM

If you are using A200 FXO trunks to allow PSTN users to call your system and you are using IVR, you may want to ensure that your zapata.conf (or zapata_sangoma.conf) file includes the setting:

relaxdtmf = yes

Without this setting, you may experience difficulties with responses to voice menus being misinterpreted. This proved especially problematic for our installation when using the Enable Direct Dial functionality - most attempts to directly dial extensions resulted in an invalid extension message, due to dtmf tones not being recognized properly. Adding the relaxdtmf = yes setting and increasing the rxgain from 0 to 3.0 (both suggestions from Sangoma) resolved the problem.

From coalescent - 5/3/06 3:31 PM

You should NEVER edit /etc/asterisk/extensions_additional.conf directly.

Site
Changes Index Search	�
User	�
Log In Register	�
�

Last Modified 10/5/06 10:50 AM