similar to: Load testing/burn-in for Sangoma quad PRI card

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"

I've been working with a telco for the past two days trying to get a PRI span up and running. This is a small-ish telco and I get the feeling they don't do this very often. Anyway, they specified a pretty standard setup: ni2 switchtype, esf framing, b8zs coding, etc. All of my b-channels are up, but we're having a heck of a time getting the d-channel to come up. He finds out that

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

Following the successful deployment of asterisk servers at several of our branch offices, in the near future, I'll likely be implmenting an asterisk server at our HQ. We currently have a T1 PRI terminated on a legacy PBX. I'll be doing a stepped deployment in which, via a dual T1 linecard, the asterisk server will initially pass all incoming/outgoing calls directly through to the PBX.

At work, I have 4 branch offices at which I've deployed asterisk. Call termination/origination at each branch office is handled either through a frac PRI or 3rd party SIP provider. Soon, I'll be replacing the legacy PBX at our HQ with asterisk. Each branch office has between 3 and 20 employees, each with their own extension and DID, and at headquarters, we have about 70 people, again

Hello my friends, I want to make fax work in the following scenario: My versions are: Asterisk 1.4.21.2 WANPIPE Release: 3.4.7 Zaptel Version: 1.4.11 libpri version: 1.4.5 Digium Card TDM 410P The E1 pri is connected to our Sangoma A102DE, we also have a SIP Mediant Audiocodes 1000 where we have some fax machines connected to fxs ports, what we need is to make fax machines through mediant

need help trying to figure out why calls hang when using multple ports on Sangoma card. we have 1 quad card with 3 T1 ports configured, Port1 acts as connection to teleco (to our T1 PRI) port 2 connects second system and routes calls to port1 port 3 is Asterisk pbx calls all go in and out properly but sometimes we get a call hang on when both sides hangup. this causes all calls to fail until

Thanks James, What i need is to make the fax machines connected to the audiocodes mediant 1000 be able to send and receive fax throught Asterisk (connected to a pri) I know it's not reliable, but it should work at leaste, what should i do on Asterisk and Mediant to make this work? Im quite confuse with all these fax issues :S Thanks in advance > > Message: 11 > Date: Fri, 9 Apr

I'm trying to install wanpipe on my new 2.6.21-2-amd64 core 2 duo machine (Debian's amd64 works with EMT64 too) to run Asterisk. I'm getting compilation errors when trying to install the wanpipe utilities. We are intending to use a Sangoma A102 card for ISDN30 in the UK. I've tried both the current stable 2.3.4-10 release and the new wanpipe-3.1.3 beta release of wanpipe. The

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

Hello - I have (finally) obtained a fair amount of success in connecting my Intertel Axxess PBX to an asterisk box via a T1 PRI. I can place calls from the Intertel side through the T1, out to an IAX2 softphone and the calls get routed correctly and all of the CID information stays intact. However, when I call from the IAX side to an extension which should route back through to the Intertel

I have installed Asterisk on a CentOS4 box and then installed Asterisk from CVS. I installed a Sangoma A101 and connected it to a Adtran 600 using a T1 Crossover cable. The 600 has 12 x FXS, 12 x FXO interfaces. I ran through the wanpipe install instructions and configured it, now I can run [root@altpbx asterisk]# wanrouter hwprobe ------------------------------- | Wanpipe Hardware Probe Info

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

Hiya all, I have had no end of trouble trying to get my A101 E1 card working on a new asterisk installation. The sangoma tech people have ignored my emails about this. All the installation of wanpipe seems to go ok, and zaptel. it all installed compiled and does all the wanpipe hwprobe exactly as documented. Asterisk compiled ok, but when I run it give me Jun 27 11:12:18 ERROR[10528]:

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

Hi, I have Sangoma A101DE 1 Port E1/T1 With Hardware Echo Cancellation ( PCI Express ) Card installed on the box. *Its not detected.* Details are as below :- [root at asterisk ~]# lspci 00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 01) 00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge 00:04.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge 00:05.0 PCI bridge: ATI

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

Hello, I've recently bought a new Sangoma A104d PCI-card. WANPIPE release is 3.4.7. Machine is a dual Xeon with Debian 5.0.3. Asterisk is 1.6.11 with recent libpri and dahdi. When I boot the machine (including hardware and wanpipe and dahdi drivers) and start asterisk, everthing runs fine for almost 5 minutes. Then every few seconds HDLC errors occour. I also tried booting - and starting