Hello,
I want to try Trixbox 2.8 RC1 on my box with Sangoma a200 4fxo-2fxs
Which drivers should I use?
Anybody know where to find instructions on how to setup these.
Rgds,
Broadsurf
 
how to install sangoma a200 on trixbox 2.8 RC1
Submitted by broadsurf on Sat, 06/06/2009 - 8:10am.
Hi Broadsurf,
There is an R2
Mon, 06/08/2009 - 6:51am
Hi Broadsurf,
There is an R2 stack that can be used, for more details please go to http://wiki.sangoma.com/mfcr2. Now there is no RPM's for this so it will require compiling on your system.
--
Marc
 
I think he just want to use
Mon, 06/08/2009 - 11:16am
I think he just want to use a 4 port fxo card. Not an R2 type T1. I'm not sure we have an RPM yet but we should have a Sangoma RPM soon.
 
Please let people know when rpms are out
Mon, 06/08/2009 - 6:09pm
Ok I'll wait.
I have a new box with a sangoma card waiting to be deployed.
 
Wanpipe drivers for trixbox 2.8?
Mon, 06/22/2009 - 5:08pm
Hi!
If you're talking about the Wanpipe drivers for trixbox 2.8 I just tried to install them (using the web interface) and I got the following error message when it tried to resolve the zaptel dependency:
Transaction Check Error:
file /usr/share/man/man8/fxotune.8.gz from install of zaptel-1.4.11-1.i686 conflicts with file from package dahdi-tools-doc-2.2.0-3_trixbox.i386
file /usr/share/man/man8/xpp_blink.8.gz from install of zaptel-1.4.11-1.i686 conflicts with file from package dahdi-tools-doc-2.2.0-3_trixbox.i386
file /usr/share/man/man8/xpp_sync.8.gz from install of zaptel-1.4.11-1.i686 conflicts with file from package dahdi-tools-doc-2.2.0-3_trixbox.i386
file /usr/lib/libtonezone.so.1 from install of zaptel-1.4.11-1.i686 conflicts with file from package libtonezone-2.2.0-3_trixbox.i386
file /usr/lib/libtonezone.so.1.0 from install of zaptel-1.4.11-1.i686 conflicts with file from package libtonezone-2.2.0-3_trixbox.i386
file /etc/udev/rules.d/xpp.rules from install of zaptel-1.4.11-1.i686 conflicts with file from package dahdi-linux-2.2.0-3_RC4_trixbox.i386
file /usr/sbin/fpga_load from install of zaptel-1.4.11-1.i686 conflicts with file from package dahdi-tools-2.2.0-3_trixbox.i386
file /usr/sbin/fxotune from install of zaptel-1.4.11-1.i686 conflicts with file from package dahdi-tools-2.2.0-3_trixbox.i386
file /usr/sbin/xpp_blink from install of zaptel-1.4.11-1.i686 conflicts with file from package dahdi-tools-2.2.0-3_trixbox.i386
file /usr/sbin/xpp_sync from install of zaptel-1.4.11-1.i686 conflicts with file from package dahdi-tools-2.2.0-3_trixbox.i386
If I understood what I read about this correctly dahdi is the new name for zaptel so it kind of make sense they would conflict with each other...
What seems to be the problem (could be wrong though) is that the wanpipe drivers try to install the zaptel stuff but dahdi is already installed so it conflicts...
Have a nice day!
Nick
 
Hi,
Yes our RPM's are built
Tue, 06/23/2009 - 6:28am
Hi,
Yes our RPM's are built against zaptel,asterisk and the kernel, so with this said if you change any of these three then the RPM will no longer work. So if you are trying Trixbox 2.8 RC1 then i would recommend simply going to http://wiki.sangoma.com/wanpipe-asterisk-trixbox-rpms#drivfrmsour... and following these steps to compile from source. If you have any issues please enable SSH access and give me a call at 1-905-474-1990 x123.
--
Marc
 
Compilation procedure is against zaptel...
Tue, 06/23/2009 - 10:37am
Hi Marc!
The compilation procedure you referred to appears to be against zaptel...
I think the correct procedure against dahdi would be here: http://wiki.sangoma.com/wanpipe-linux-asterisk-dahdi .
I have decided to try 2.6.2.3 instead as there is still a problem with my Sangoma A200D we need to track down and I don't want to destabilize my trixbox/wanpipe installation just to try the latest and greatest version (which btw, is no longer RC, it's now a stable final version).
Let's hope 2.6.2.3 will recognize my NIC as most of the recent trixbox version had problems recognizing it and it's a mini-ITX and its sole slot is already occupied by the A200D...
Thank you and have a nice day!
Nick
 
2.6.2.3 dependencies broken as well...
Tue, 06/23/2009 - 1:22pm
The dependencies on 2.6.2.3 are broken as well, I now get the following error message:
--> Running transaction check
---> Package wanpipe-util.i686 0:3.3.15-0 set to be updated
---> Package wanpipe-modules-2.6.18-92.1.18.el5.i686 0:3.3.15-0 set to be updated
--> Processing Dependency: zaptel 1.4.12.1 for package: wanpipe-modules-2.6.18-92.1.18.el5
--> Finished Dependency Resolution
wanpipe-modules-2.6.18-92.1.18.el5-3.3.15-0.i686 from trixbox has depsolving problems
--> Missing Dependency: zaptel 1.4.12.1 is needed by package wanpipe-modules-2.6.18-92.1.18.el5-3.3.15-0.i686 (trixbox)
Error: Missing Dependency: zaptel 1.4.12.1 is needed by package wanpipe-modules-2.6.18-92.1.18.el5-3.3.15-0.i686 (trixbox)
2.6.2.3 comes with zaptel-1.4.12.9-1 ...
If the kernel version is supposed to match the version number shown in the name of the wanpipe drivers then there is a problem there as well as 2.6.2.3 comes with kernel 2.6.18-128.1.10.el5 ...
I guess I'll just compile everything and keep my fingers crossed...
Nick
 
Hi Nick,
Yes just compile
Wed, 06/24/2009 - 1:05pm
Hi Nick,
Yes just compile from source, we are working on getting RPM's built and they will be up on our wiki at http://wiki.sangoma.com/wanpipe-asterisk-trixbox-rpms#fstinall as soon as they are complete.
--
Marc
 
kernel-devel
Thu, 06/25/2009 - 7:36am
Hrm. Actually we can't compile our own wanpipe because it requires kernel-devel and the kernel-devel in the yum repository (-92) doesn't match the installed kernel (-128). So I think out of luck there also.
 
Your kidding me? The
Thu, 06/25/2009 - 10:23am
Your kidding me? The kernel-dev doesn't match.
This is why I never rush in to new releases. The repositiory needs to get cleaned up.
If Andrew would expose some of his processes we could understand how the development build environment makes it to the repo. It would also help me understand how build mistakes such asterisk-addons get into a so called "release version"
Thanks for pointing this out.
--
Scott
aka "Skyking"
 
Hi,
Please give me a call
Thu, 06/25/2009 - 12:22pm
Hi,
Please give me a call at 1-905-474-1990 x123 and we can look into this compiling issue.
--
Marc
 
kernel-devel...
Sat, 06/27/2009 - 2:00pm
Hi!
(Marc, this is not addressed to you since you already know about that problem...)
I was able to compile (up to a certain point) but there is another problem, there was an API change in dahdi 2.20...
Concerning the kernel-devel problem, I assumed the kernel had not been modified for trixbox so I activated the centos repositories, made a copy of the files and removed the kernel* exclusion that was present in them. I was then able to get a kernel-devel that match the kernel version. I then reverted to the original repo files...
Unfortunately, there was an API change (why they changed in such an incompatible way, I don't know) in dahdi 2.20 so the current drivers cannot currently compile with dahdi 2.20.
From looking at the code it looks like the one of the callback routines which seem to deal with echo cancelling had its name and signature changed...
This changed in API has affected other telephony cards drivers as well...
Have a nice day!
Nick
 
Sangoma A200 2FXS
Tue, 02/09/2010 - 9:25pm
Got Trix up No Problem
I went in to the Packages tab
I see two WanPipe Driver Installs should I use those and which?
 
Hi,
Please go to
Fri, 02/12/2010 - 9:35am
Hi,
Please go to http://wiki.sangoma.com/wanpipe-asterisk-trixbox-rpms#fstinall and follow the steps there to get the RPMS.
--
Marc
 
Member Since:
2006-06-15