similar to: Sangoma A102 w/ EC module gets intermittent echo /audio artifacts

Hi, after many issues we finally managed to make our system do outgoing calls with perfect quality. However I cannot detect *any* form of incoming call. when I use an outside phone to call the E1 connected to the sangoma a102, I instantly get a fast busy tone. My /etc/zaptel.conf is: loadzone=us defaultzone=us #Sangoma A102 port 1 [slot:1 bus:4 span: 1] span=1,0,0,ccs,hdb3 bchan=1-15,17-31

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 =

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:

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

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

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

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

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

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

I have a system that I am trying to get a port on a Sangoma A104d card connected to an Adtran 850 with 5 FXS modules and 1 FXO module. A problem I am having is figuring out what cable should be used from the port on the Sangoma to the JP2 port on the Adtran. Tried was a cross-over T1 (1->4, 2->5, 4->1, 5->2) as well as a straight T1 (1->1, 2->2, 4->4, 5->5). Neither one

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

Aha, it just happened to me, so now I can characterize the audio: It basically sounds like it's missing every other sample - fuzzy and distorted. Timing?

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'm using Asterisk 1.4.5 (will try 1.4.6 on Thursday, but I don't see anything in the changelog after the 1.4.5 release dealing with distinctive ring), zaptel 1.4.3, and wanpipe 2.3.4-10 with a Sangoma A200 card. I enabled usedistinctiveringdetection in zapata.conf. However, on the Asterisk console, the output I get is: -- Detected ring pattern: 0,0,0 It would appear that Asterisk is

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#

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 |

Hey Guys! Please help me to find out issue. I have two PRI ## Span 1: WPT1/0 "wanpipe1 card 0" span=1,1,0,esf,b8zs bchan=1-23 hardhdlc=24 echocanceller=mg2,1-23 ## Span 2: WPT1/1 "wanpipe2 card 1" span=2,2,0,esf,b8zs bchan=25-47 hardhdlc=48 echocanceller=mg2,25-47 Sometime my calls got through but some time i am getting pri cause 44 sebpbx1*CLI> == Using SIP RTP