similar to: odd T1 issue

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]

Maybe of you guys know the answer to this: We have T1's that come from both MCI and Global Crossing as channelized (24 Ports per T) with inband (DTMF) delivery of ANI and DNIS (format = *DNIS*ANI*). My old equipment was set for D4, AMI, SF and Wink Start and so is Asterisk. I've moved these T's to Asterisk TE410P and inbound calls are arriving to external voice mail system

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

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

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

Maybe of you guys know the answer to this: We have T1's that come from both MCI and Global Crossing as channelized (24 Ports per T) with inband (DTMF) delivery of ANI and DNIS (format = *DNIS*ANI*). My old equipment was set for D4, AMI, SF and Wink Start and so is Asterisk. I've moved these T's to Asterisk TE410P and inbound calls are arriving to external voice mail system correctly

Hello, I'm trying to make my asterisk box to act as a telco, in order to reproduce a US environment in europe. Our telco provider is giving us those settings: ESF B8ZF Inbound = E&M Immediate Outbound sig =Wink Start Yield to Glare = Yes Those trunks are using CAS for signaling. I have tried many configs/combinations in zaptel.conf and zapata-channels.conf In zaptel.conf, when having

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#

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

Hello to all, I have a problem with an asterisk qsig. I have three machines: Nortel CS1000 --- Card Sangoma PRI ---> Asterisk QSIG ---SIP Trunk---> Asterisk I use Snom phones on Asterisk. If I call from Asterisk to Nortel, Nortel reminds me of the name of the person i'm calling and I visualize on the display of Snom phone, but if I call from Nortel to Asterisk, the QSIG does not send

Here's my planed setup : PRI from telco <--> (port 1 of A104d) * (port 2 of A104d) <--> PM3 The PM3, for those who don't know is lucent's portmaster RAS dial-up router. I had setup asterisk, zaptel, libpri, wanpipe (as I have sangoma's cards). In wancfg, I have port 1 as TDM_VOICE, with hardware echo on, span 1. Port 2 is TDM_VOICE, without hw echo, Clock as

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

Hello. I'm having a strange problem with the IAX2 channel and IAXmodem and I was hoping to get some light from someone in these lists. On my logs and on the console I'm getting a bunch of lines with: [Oct 23 14:26:18] NOTICE[4417] chan_iax2.c: Peer 'XXX' is now UNREACHABLE! Time: 3 [Oct 23 14:26:28] NOTICE[4413] chan_iax2.c: Peer 'XXX' is now REACHABLE!

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 =

My Sangoma Experience in Asterisk: Followup 2005-05-06 original review can be found at: http://astguiclient.sourceforge.net/Sangoma_experience.txt It's now been a month since I finished my last round of tests with the Sangoma A104u board in Asterisk. I have had a lot of conversations with the guys at Sangoma about how my system runs so that they could set up their test systems to try to

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

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:

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