similar to: Asterisk 1.2.23 and Sangoma a102 no incoming call detected

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:

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, 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

I've replaced 2XTE110 with an A102 with echo cancellation specifically to deal with echo problems. However, user feedback has indicated to me that on some calls (not a lot, but some) the call is unusable, with audio artifiacts, described by one user, as: "very bad phasing reverb & feedback (from my rock & roll days)". This is quite intermittent, as in most cases, the user

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

I am having a problem trying to get a Sangoma A101 to work with Unicall. I have installed the sangoma drivers and everything seems to be well but when I try to run ztcfg I get the following error: CAS signalling on span 1 conflicts with HDLC with FCS check on channel 16. Here is my /etc/zaptel.conf # MFC/R2 normalmente no usa CRC4 span=1,0,0,cas,hdb3 cas=1-15:1101 dchan=16 cas=17-31:1101

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 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

Hello, I have following problem with Sangoma A104 card: CLI> pri show span 1 Primary D-channel: 16 Status: Provisioned, Down, Active Switchtype: EuroISDN Type: CPE Window Length: 0/7 Sentrej: 0 SolicitFbit: 0 Retrans: 0 Busy: 0 Overlap Dial: 0 T200 Timer: 1000 T203 Timer: 10000 T305 Timer: 30000 T308 Timer: 4000 T313 Timer: 4000 N200 Counter: 3 NOTICE[16509]: chan_zap.c:7494 pri_dchannel: PRI

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

Hi All I have problem with LIBMFCR2 for once Exchange I using Sangoma card, the firstly. my ssystem run successful with MFCR2, connected to E10 (Acatel Exchange), after that, i move connection connect to EWSD (Siemens), my system don't work. error protocol R2. my system: Asterisk CVS 1.1.X LibMFCR2 pre.005 and unicall-pre.005 this's my setting and my setting wanpipe1.conf

I think you are absolutely right. The audio I heard earlier sounds exactly like a timing issue. So: wanpipe1.conf: TE_CLOCK = NORMAL TE_REF_CLOCK = 0 wanpipe2.conf: TE_CLOCK = MASTER TE_REF_CLOCK = 1 zaptel.conf: span=1,1,0,esf,b8zs span=2,0,0,esf,b8zs I'm going to make this change and reload at lunchtime, I'll document it and post it to the list if it works.

Followup on this issue, it appears that using a single PRI's clock as the master clock avoids clock drift between the PRI's and we get no more artifacts. So, : wanpipe1.conf: TE_CLOCK = NORMAL TE_REF_CLOCK = 0 wanpipe2.conf: TE_CLOCK = MASTER TE_REF_CLOCK = 1 zaptel.conf: span=1,1,0,esf,b8zs span=2,0,0,esf,b8zs -----Original Message----- From: Michael L. Young

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, 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:

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#

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

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

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