similar to: Sangoma A104 - D-Channel problem

Hi all, My problem boils down to these errors: ... Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) == Everyone is busy/congested at this time This is triggered by lines in extentions.conf such as: exten => _X.,1,Dial(ZAP/g1/${EXTEN},,W) The system is CentOS v5.2 with Asterisk 1.4.23 (druid-asterisk-1.4.23.1-2), a Sangoma A104

Hi, I'm using Sangoma's wanpipe together with dahdi, all software downloaded today at most recent version. Hardware is Sangoma A104, a 4xE1 card. Installation went well. Anyway, wanrouter status shows a different result than dahdi_tool or dahdi_scan. I've just put a hardware loop on port 1. All the other ports are open. wanrouter status shows the expected result: Device name |

I upgraded from Tormenta2 to Sangoma A101. I followed the instructions, and installation was successful. zttool, ztcfg, all show card is installed properly. I copied the parameters from my old working zaptel.conf, zapata.conf and zapata-auto.conf. Verified on Sangoma website that these files are correct. Also configured wanpipe1.conf. But doing all this didn't start the PRI channels. It says

I have used asterisk-1.4.14, zaptel-1.4.7, chan_ss7-1.0.0 on FC7 all went okay. using sangoma a104dx on both machine. I followed the write up on http://www.voip-info.org/wiki/index.php?page=Asterisk+ss7+setup I have the cross over cable between them. however, wanpipe shows connected but the signaling link does not align. i have my configs for host A ##wanpipe1.conf [devices] wanpipe1 =

Hi all, I've done this a few times with other PBX's but swyx has stumped me! I'm having some trouble getting Asterisk connected to a Swyx system using a sangoma A104dx... currently the setup is: BT <-> Swyx The above setup works fine... what i'm trying to achieve is BT & SIP Trunks <-> Asterisk <-> Swyx I have connected to our BT (2 x ISDN30 UK) with

Hello, We are having issues with a NEW Sangoma A108D: -- Executing [691918892 at pbx1:1] Dial("SIP/xtravoip200-009d24b0", "DAHDI/g0/691918892|30|m") in new stack [Oct 1 10:04:43] WARNING[14171]: channel.c:3170 ast_request: No translator path exists for channel type DAHDI (native 76) to 256 [Oct 1 10:04:43] WARNING[14171]: app_dial.c:1237 dial_exec_full: Unable to create

Hi there, we have a problem with dahdi and overlapdial. We are running an E1 in Germany and are in need of overlapdial. The E1 is connected to a Sangoma A101. As soon as overlapdial is set to "yes" we have problems with incoming audio on the dahdi channels. When set to "no" all audio is fine. Basically we can choose between being able to receive calls or to place calls

Do you have any extension in default context of your extensions.conf file to accept incoming calls ? It must be something like; exten => 12345678,1,Answer() exten => 12345678,2,Playback(Welcome) ... 12345678 = The DID number you are calling to reach E1 Idris -----Original Message----- From: Erick Perez [mailto:eaperezh at gmail.com] Sent: Thursday, July 26, 2007 7:03 AM To:

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 all, Can somebody help me out, to get the call going through to my provider? I connected my A104D Sangoma card to E1/isdn and each I tried to make call I get the errors below. My protocol analyzer can see only setup info and release complete. WIRELESS2*CLI> set debug 9 Core debug was 0 and is now 9 WIRELESS2*CLI> pri intense debug span 1 Enabled EXTENSIVE debugging on span 1 T203

Greetings folks- I'm experiencing issues with a freshly installed box. When a call comes in via PRI (Sangoma AFT-A104), I see this in my logs: [Dec 15 14:26:10] WARNING[23546] chan_dahdi.c: Unable to enable echo cancellation on channel 12 (Invalid argument) [Dec 15 14:26:10] WARNING[23546] chan_dahdi.c: Unable to enable echo cancellation on channel 8 (Invalid argument) [Dec 15 14:26:10]

Hi, Does anybody have an idea as to why dahdi_test results drop to unacceptable levels after doing a wanrouter stop/start using a Sangoma card? See below that it drops from 99.99% to 98.55%: [root at bin]# dahdi_test Opened pseudo dahdi interface, measuring accuracy... 99.999512% 99.992874% --- Results after 2 passes --- Best: 100.000 -- Worst: 99.993 -- Average: 99.996193, Difference:

I am sure many of you have seen my post asking question that I cannot seem to resolve. While the responses i have been getting have been helpful i still cannot seem to get this working 100%. So I have waving the white flag here. I give up. I need someone to come to my office and help me get this working. If anyone is interested the office is in Lexington KY. If someone is interested we can

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#

I have installed Asterisk on a CentOS4 box and then installed Asterisk from CVS. I installed a Sangoma A101 and connected it to a Adtran 600 using a T1 Crossover cable. The 600 has 12 x FXS, 12 x FXO interfaces. I ran through the wanpipe install instructions and configured it, now I can run [root@altpbx asterisk]# wanrouter hwprobe ------------------------------- | Wanpipe Hardware Probe Info

I have a problem with a Sangoma card. It worked until yesterday. Now I keep getting this error: Jul 29 17:45:17 pbxacura kernel: wanpipe1: Enable E1 CAS signalling mode! Jul 29 17:45:17 pbxacura kernel: wanpipe1:w1g1: Rx Error: No 'DeviceSelect' from target: pci fatal error! (0x000FA000) Jul 29 17:45:48 pbxacura last message repeated 30946 times It is using Wanpipe 3.5.6 and Zaptel

Hello, We have an Asterisk 1.0.9 machine with a Sangoma A101 card fitted, it is connected to a Telstra OnRamp E1 in Melbourne, Australia. The problem we are experiencing is extreme echo and clicking noises. These are only audible to the calling party, e.g. the person calling in from the PSTN to Asterisk via the E1, the person on the SIP handset cannot hear any echo or clicking, only the

Hi, I am trying to validate a setup with a sangoma A116 card (16PRI in one card). I currently have two machines set up, each with a sangoma A116 card. Those are interconnected with crossed PRI cables. One of them is in NT mode, the other in TE. The ports are configured in E1 mode, asterisk is all set up and I can make calls between them, filling up all 480 (16 * 30) channels. Now, I learned

Hi, got a Sangoma A200 with a bunch of extension cards and having real problems getting it to deal with a normal single BT line Symptoms are that incoming calls are fine. Outgoing calls ring the far end, BUT asterisk never sees that the call is answered (ie no message in the logs files saying so), as a result the remove end can hear the PBX side talking, but there is no audio back from the

Hi everyone, I am reading through Sangoma Wiki right now. But someone may already and quickly notice this. I have a system that is down since the morning (maybe power intruptions). All seems fine except for "wanrouter status" shows disconnected. Following are the alarms raised. Should I call telco (they have long wait times) or should I just keep searching online for troubleshooting