similar to: Sangoma - how to show channels in use?

Hello List I am having a rather big problem with a sangoma A104 card, I just installed to replace a Digium TE410 card, that was acting up. But now we have a problem with the sangoma card. It runs great after being started, and calls proceed as normal, but after about 1 hour, it stops being able to make and receive calls. If I run wanpipemon debug, can see that the card still receives

asterisk 1.4.35 dahdi 2.3.0.1+2.3.0 one span on a 4port T1 card Got complaints this morning that outbound and inbound calls were "scratchy" and I made a few test calls. It kind of sounds like the gain is too high somewhere, and the audio is overdriven. Is this a problem at the carrier? I'm trying to call them now, but it's Sunday morning in the sticks, and my chances of

I've been going back and forth with my telco for several days, trying different configurations to get a new PRI to come up. The bchannels are all up and the T1 is not in alarm status. The dchannel refuses to come up however. We've tried ni2, qsig, and now dms100 for the switchtype. The telco tech I've been working with says that he's been sending "reset all channels"

Upgrading an ancient customer installation... was running 1.4.23.1 (Trixbox) with Zaptel 1.4.12.9 and a Sangoma A102D, which has been running fine for 5+ years. Customer getting anxious about hardware failure, so we built a new box and installed 1.8.24.0, Dahdi 2.7.0.1, and a new Sangoma A104D. The single active span is an RBS T1 B8ZS/ESF/E&M Wink. I tried to move one span over one

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, 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 been using Asterisk 1.2.6 with a 4 port FXO Sangoma A200 card for the past month without many problems (other than the fact that the Sangoma card doesn't disconnect hung up calls immediately, which I posted about in another thread, and has still not been fixed), however, I had a call from one of our clients today and they complained that our phone system kept ringing through when they

As far as I can tell, after discussing this matter with other asterisk users in my area, my telco _does_ provide disconnect supervision.. It seems that the problem is actually related to the Sangoma A200 card I'm using, as two other people both using this same card have expressed the same problem.. Are there any other users on this list using the Sangoma A200 FXO port card, and experiencing

Hi, Has anyone ever experienced crosstalk with sangoma analogue cards on 64bit? We have exhausted every test to try and replicate this and find a solution with Sangoma tech support, but we can not fix it. We are about to try the card and four *seperate* UK BT lines in a 32bit system. The current system is a 4gb, dual core cpu with pbx in a flash 1.4, Zaptel and Asterisk 1.4.21-2 Currently we

Hey all, I had a user complaining of calls which were dropping mid-conversation. I looked into the time of one of the calls, and saw the following: Apr 4 12:13:03 WARNING[6670] chan_zap.c: No D-channels available! Using Primary channel 28 as D-channel anyway! Apr 4 12:13:05 WARNING[6660] channel.c: Avoided initial deadlock for '0x82b8430', 10 retries! Apr 4 12:13:05 WARNING[6660]

I'm a long time user of Digium carts and stupid me i wanted to give Sangoma a try. We got Sangoma A400 with 6 FXO ports. Asterisk version: 1.4.35 Zaptel version: 1.4.11 Wanpipe version: 3.5.11 we tried to use fxtune but looks like it wont work with Sangoma card, ( please correct me if i'm wrong) Echo is really bad and also we have background noise on all lines. We tried both mg2 and

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

Hi folks I've tried asking this in private mail for quite some time, but sadly got no reply. So I end up needing to raise the question here. Sangoma's s setup process includes a small patch to Zaptel. I have some technical reservations with that patch. It seems that under certain circumstances it may cause unexpected behavior when used with other Zaptel channel drivers. I also don't

Dear Folks, Anyone knows if Sangoma supports or going to provide support for battery removal detection on FXO lines?? As Tzafrir said earlier DAHDI supports it, which is a very nice feature but what about Sangoma? Regards. -- M. Shokuie Nia. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I migrated from asterisk 1.6 to 11.3. The Server has a Sangoma A104 quadPri card installed. OS is a fresh installed Ubuntu 12.04 64bit libpri, dahdi etc. all latest releases.. Sangoma says... driver is compatible with ANY asterisk version... I tried driver 3.5.8... Setup ended with error. I tried (latest) driver 7.0.1 Setup went through, Asterisk is showing dahdi channels... all fine....

Hi, I have A101DE Sangoma Card( http://www.sangoma.com/products/hardware_products/digital_voice_and_data_networking/a101.html ) lspci shows as 03:04.0 Network controller: Sangoma Technologies Corp. A200/Remora FXO/FXS Analog AFT card [root at asterisk ~]# lspci -vvv -s 03:04.0 03:04.0 Network controller: Sangoma Technologies Corp. A200/Remora FXO/FXS Analog AFT card Subsystem: Unknown device

I have an issue that hopefully you can help me solve. I've got the sangoma a101 card and installed it on freebsd but I according to the manual I should be see when running dmesg PCi0 vendor..... something that tells me sangoma it's being recognized by the system. Now this is the 2nd card I try, the first one according to support was faulty and they sent me a new one. Is it possible to be

Hi all Hi,I'm facing a strange issue where by SANGOMA not detected by goautodial system , Thats the problem : Configuring ISDN BRI cards [A500/B700] ------------------------------------ No Sangoma ISDN BRI cards detected Press any key to continue: ------------------------------------ Configuring GSM cards [W400] ------------------------------------ No Sangoma GSM cards detected

Hello, there has been a post to this list somewhere arount april which said that it is possible to use a Sangoma BRI A500 card with zaptel and asterisk bristuff. That is, without sangoma_brid and sangoma_mgd daemons and without woomera channels. Could anybody give me a short hint how to configure this? I tried wanpipe-driver + zaptel + asterisk-bristuffed, but I couldn't get zaptel to

Hello List! I wanted to share to everyone the following compatible connectivity products that my company installed in our Asterisk based soft switch. I already sent these to the Asterisk.org site many days ago but for some reason they still have to post it. 1. Sangoma A101 single port E1/T1/PRI Card 2. Sangoma A102 dual port E1/T1/PRI Card 3. Sangoma A104 quad port E1/T1/PRI Card 4. Sangoma