similar to: Asterisk 1.2.23 and Sangoma a102 no incoming calldetected

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 =

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

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, There are 3 PRI's connected to the card each from different operators. Especially echo occured on span 3 is really annoying. Configuration files are as follows. Is there something wrong in conf ? Zapata.conf -------------------------- [channels] context=default switchtype=euroisdn usecallerid=yes hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes

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

Hi, You can try ChanSpy http://www.voip-info.org/wiki/view/Asterisk+cmd+ChanSpy. Idris _____ From: phil.dawson@marnock.com [mailto:phil.dawson@marnock.com] Sent: Wednesday, June 21, 2006 12:23 PM To: asterisk-users@lists.digium.com Subject: [Asterisk-Users] Monitor a particular SIP call for training purposes Hi, I've been asked if it is possible to allow a user to

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

Hello, in our company we are trying to do this: Fax <--> Traditional PBX <--> Asterisk <--> PSTN In practice, we have put an Asterisk equipped with a Sangoma A102 (2 PRI ports) between our PBX (Siemens HiCom) and the PSTN in order to have a VoIP network along the traditional telephony network. The problem is with the fax. We just want to send and receive faxes from/to our fax

Does anyone have any experience ith configureing the sangoma A102 card for testing using a e1 cross cable i've configured and installed the cards properly even the lights on the card are green which proves that my cross cable is properly built too. my problem is with asterisk which gives me these errors PRI got event: HDLC Abort (6)on Primary D-channel of span 1 PRI got event: HDLC Bad FCS

Has anyone seen something like this before. Randomly, on longish calls, the local side of the call audio goes dead. Meaning remote caller can hear us but we cannot hear the remote person? Linux voip 2.6.18-128.1.6.el5 #1 SMP Wed Apr 1 09:10:25 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux Asterisk 1.4.24.1, Copyright (C) 1999 - 2008 Digium, Inc. and others. WANPIPE Release: 3.4.1 Wanpipe Config:

Shortly, I'll be purchasing a Sangoma A102. I'm wondering if I should spring for the hardware echo cancellation circuit or not. Upon initial implementation, the 2 T1 Ports will be used as a passthrough as we slowly transition off of a legacy PBX. Eventually, we'll only be using one of the ports, and will be providing VoIP service to a bunch of SIP deskphones. So - with that usage

Any benefit on getting the PCI Express version? Bill -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070222/62f79910/attachment.htm

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.