similar to: Sangoma A101DE 1 Port E1/T1 With Hardware Echo Cancellation ( PCI Express ) Card

Hi, I have A101DE Sangoma Card( http://www.sangoma.com/products/hardware_products/digital_voice_and_data_networking/a101.html ) lspci shows as 03:04.0 Network controller: Sangoma Technologies Corp. A200/Remora FXO/FXS Analog AFT card [root at asterisk ~]# lspci -vvv -s 03:04.0 03:04.0 Network controller: Sangoma Technologies Corp. A200/Remora FXO/FXS Analog AFT card Subsystem: Unknown device

Hi, I have Sangoma A101DE 1 Port E1/T1 With Hardware Echo Cancellation ( PCI Express ) Card installed on the box. *Its not detected.* Details are as below :- [root at asterisk ~]# lspci 00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 01) 00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge 00:04.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge 00:05.0 PCI bridge: ATI

Hello there, recently installed CentOS6 on a (quite old) 64-bit system, and from the GNOME's sound preference app, I can see that the Output volume range is said "amplified" from 63% to 100%. Below 63% it's unamplified. No idea what's implied behind this amplification (I don't see this on other desktops), but I notice that when "amplified" the sound is pretty

I have installed CentOS 4.2 on an AMD based machine using the ATI chipset (xpress 200) and I am having issues with it. It seems to be a very Linux unfriendly chipset. I have looked at the ATI proprietary drivers but they seem to be for video. My problem is the IDE channel on which you cannot enable DMA. There is serious clock slew also as well as nic issues. There is supposed to be an ATI

Hello all, I was wondering if CAST5 encryption is currently being added the openssh? It's a steller block cipher. No one's found any weaknesses in it yet and it's free for non profit use. TTYL JLC -- #!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj $/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1

For compiling the xen kernel we use -nostdinc which means we don''t want to rely on any external headers. That also counts vor stdarg.h. Use the external header when we compile the tools. Adapt libelf-loader.c which is compiled in the kernel and with the tools. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- ---to satisfy European Law for business letters: Advanced

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is another ati driver RC aimed at server 1.3. Still not randr-1.2. It contains a bunch of fixes for the upcoming (I swear) 6.7 release. Main features: fix a serious crasher in DPMS code, addition of EXA hook for zero-copy TFP and RS480 support. Along with numerous other cleanups There is a blocker bug 11749 for the 6.7 release in

LD [M] /root/wanpipe/patches/kdrivers/wanec/wanec.o Building modules, stage 2. MODPOST *** Warning: "register_wanec_iface" [/root/wanpipe/patches/kdrivers/wanec/wanec.ko] undefined! *** Warning: "unregister_wanec_iface" [/root/wanpipe/patches/kdrivers/wanec/wanec.ko] undefined! CC /root/wanpipe/patches/kdrivers/wanec/wanec.mod.o LD [M]

Hi all, as good? I try to install asterisk-1.2.14, zaptel-1.2.12,libpri-1.2.4,addons-1.2.5 , sounds-1.2.1 and wanpipe-2.3.4-3 and hwec-utils-beta4-2.3.4 But it is not compiling drivers of the Sangoma, why udev's for board in "/dev/zap"(1-31, channel,ctl,pseudo,timer) is not created. But when I install a board TE110P Digium, udev's is created and asterisk functions perfectly. : )

Hey! I am installing Sangoma A102D wanpipe driver and i got following error. what is this ? why dir isn't there ? wanpipe-3.5.16 # make dahdi DAHDI_DIR=/usr/src/dahdi wanpipe-3.5.16 # make install ....Send .... .... Installing Wanpipe Firmware update utility in /etc/wanpipe/util/wan_aftup install -D wan_aftup /usr/sbin/wan_aftup install -d /etc/wanpipe/util/wan_aftup/scripts install:

Newest wanpipe (3.3.16) beta drivers do not compile against dahdi-linux 2.2.0-rc2 which is what you get when you get dahdi-linux-current.tar.gz Anyone have a workaround or patch? Error below ==================== Building modules, stage 2. MODPOST CC /usr/src/wanpipe-3.3.16/patches/kdrivers/wanec/wanec.mod.o LD [M] /usr/src/wanpipe-3.3.16/patches/kdrivers/wanec/wanec.ko make[1]:

Hi all, I have tried to install Wanpipe 7.0.20 in a fresh-installed Debian 8.5 (Jessie) server, but when I reach to the point where I have to enter the Linux Headers directory *(installed in default with ?apt-get install linux-headers-$(uname -r)?)*, I get an error, the package refuses to compile and installation aborts. If I try the same process with Debian 7 (Wheezy), installation works just

Trying to install wanpipe 3.5.18. No errors during compile. But when I reach the point where wanpipe and dahdi_cfg is started, I encountered an error. Starting WAN Router... Loading WAN drivers: wanpipe done. Starting up device: wanpipe1 wanconfig: WAN device wanpipe1 driver load failed !! : ioctl(wanpipe1,ROUTER_SETUP) failed: : 22 - Invalid

Hi everyone, I'm trying to get a Sangoma A101D-X card talking to a Sasktel PRI (Megalink) circuit and having some trouble getting it to handshake. Thanks for any help or suggestions to diagnose this problem. The problem is that Asterisk has trouble bringing up the link. I see the following lines every couple of minutes: == Primary D-Channel on span 1 up == Primary D-Channel on

Hi, I'm trying to install asterisk(v1.2.22) with FreepBX(v2.2.3) with a 4-Port FXO Sangoma card A200. I'm using Fedora 7 (x86_64) kernel version 2.6.22.1-27.fc7, but i'm having these errors: $ ztcfg -vvvv Channel map: Channel 01: FXS Kewlstart (Default) (Slaves: 01) Channel 02: FXS Kewlstart (Default) (Slaves: 02) Channel 03: FXS Kewlstart (Default) (Slaves: 03) Channel 04: FXS

Hello, there has been a post to this list somewhere arount april which said that it is possible to use a Sangoma BRI A500 card with zaptel and asterisk bristuff. That is, without sangoma_brid and sangoma_mgd daemons and without woomera channels. Could anybody give me a short hint how to configure this? I tried wanpipe-driver + zaptel + asterisk-bristuffed, but I couldn't get zaptel to

Hey Guy, I have ubuntu 10.04 64bit and compiled dahdi / wanpipe 3.5.19 /asterisk-1.8.x I didn't understand what is the relation between wanpipe and dahdi ? do i need to start wanrouter service ? I am getting weird errors and my system got kernel panic many time when i restart dahdi service. any idea ? what is the startup sequence of all these service ? root at example:/etc/asterisk#

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ATI 6.8 pre-release This is the long awaited radeon driver with randr 1.2 support. radeon 6.7 was pretty much a dead end, so it's been branched for those that still want to play with it. In addition to randr support there are quite a few other goodies: zero copy tfp, improved connector table parsing, TV-out support, and much more. Changes since

Hello, I'm getting a KErnel Pannic every time i restart the server, what could be happening? I just make: "shutdown -r now" and the server gets Kernel Panic. I'have to go on site and press the power button Here you have my sotware versions: Asterisk 1.4.24.1 DAHDI Tools Version - 2.1.0.2 DAHDI Version: 2.1.0.4 libpri version: 1.4.10.1 WANPIPE Release: 3.5.4 IS there

Hi! I've went through the READMEs and could not answer this question: During installation, the Setup program asks: Would you like update/upgrade wanpipe drivers? (y/n) For a pure Asterisk TDM installation - is it required to patch the kernel or is this only when using the sangoma cards as WAN router? regards klaus