similar to: Zap PRI failed with Cause 34 - Where to check for problems?

Just to share some experience with everyone about what happened today to our Asterisk 1.4 box with Digium TE412P card. We had an unscheduled power outage which shut down the Asterisk box. When the power went up, Asterisk came back up okay but the ports on the card were all red. Zttool show red alarm and cat /proc/zaptel/1 show red alarm today. Both incoming and outgoing cannot be made. When a

Nik, Looks like you're making some progress. When I first started using A@H I had trouble getting the outbound dialing to work. I wasn't sure where to start, so what I did was skip the macros in the dial plan. I wanted to play around with exactly what digits the telco wanted to see. So I put a specific extension in my [default] context like this: exten =>

Hi, I'm running Asterisk SVN-trunk-r226890 and whenever I restart asterisk and try to make a call I get the following error message: ======================================================================================== -- Executing [6781948 at default:1] Dial("IAX2/iaxy-7477", "DAHDI/g1/96781948") in new stack [Apr 25 13:00:10] WARNING[3772]: app_dial.c:1806

hi i've configured a TE205P on asterisk at home this is my zaptel.conf span=1,0,0,ccs,hdb3,crc4,yellow span=2,0,0,ccs,hdb3,crc4,yellow bchan = 1-15, 17-31 dchan = 16 bchan = 32-46,48-62 dchan = 47 loadzone = it defaultzone = it and my zapata.conf signalling=pri_cpe ; pri_cpe = PRI slave ; pri_net = PRI master switchtype=national usecallerid=yes hidecallerid=no callwaiting=yes

Hi Guys, I am running a PBXinaFLASH server. I replaced contents of /usr/src/libpri with the new version of Libpri v1.4.11. The installed one was v1.4.10. System is running Asterisk 1.4.21.2. I did the following after: cd /usr/src/libpri/ make make clean make install Install end with these lines.....: *ln -sf libpri.so.1.4 libpri.so* *mkdir -p /usr/lib* *mkdir -p /usr/include* *install -m 644

Nik, Just curious - what is your telco setup? Do you have PRI with the specified D channels? You need to make sure that your telco is set up to have the D channels on 16 and 47. When you first start Asterisk, or when you log on to the CLI, do you ever see messages stating the B channels are successfully started? Let us know. -MC -----Original Message----- From:

Nik, This definitely helps! Please check your dial command. You've got "Dial(Zap/0/mynumber)" and I think you might possibly want it to be something like this: Dial(Zap/1/mynumber) or Dial(Zap/g0/mynumber) I don't recall there being a zap channel zero, but it is common to have a group zero. I would recommend trying Zap channel 1 - Dial(Zap/1/mynumber) - before trying the

Following is my scenario to connect back to back PRI of two asterisk server. PRI cards are Sangoma A102D [Asterisk1]------------[PRI]-Cross Cable---------[Asterisk2] Asterisk1 ; Span 1 (MASTER) switchtype = national ; commonly referred to as NI2 context = from-pstn group = 0,24 echocancel = yes signalling = pri_net channel => 1-23 Asterisk2 ; Span 1 switchtype = national ; commonly

When Asterisk first starts up, it will attempt to "bring up" the B channels on any PRI circuits. If you are using A@H then you can log on to the Asterisk CLI (asterisk -r) and then do "stop now" to stop asterisk. Start up Asterisk again by typing asterisk -cvvv at the Linux command line. You should see a bunch of messages on the terminal and then you'll get the Asterisk

Hi, I would like to use a digum card to call an external number through my PSTN. I think that I have a problem in the configuration. Asterisk returns me app_dial.c:764 dial_exec: Unable to create channel of type 'Zap' I use Fedora core 3. I installed libpri, zaptel and asterisk. I plugged my line on the FXS module (green part). I make modprobe zaptel && modprobe wctdm without

Hi All, I have one rather annoying problem...my PBX can work great for weeks, when suddenly I start receiving these messages when I try to make a zaptel call: Oct 31 13:52:47 NOTICE[15636] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) Oct 31 13:52:49 NOTICE[15648] channel.c: Unable to request channel ZAP/g1/247 I'm using Sangoma

Nik, I'm not sure that "NOP" is correct, but I'm in the states so I'll to defer to someone who knows E1/PRI. When I run zttool I have "OK" under the alarms. Is there a way you can call the telco and confirm the settings? Make sure that framing, coding and D channels are set up on their end the same way you're set up. As for asterisk, here's what I get

So I reached the point where my PRI is accepting incoming calls, but I cannot dialout. I must be doing something stupid, but I can't figure it out. The Asterisk box is sitting between the Mitel and the phone company, and has PRI lines to each. Asterisk was built from CVS r1-0 Log for a call from mitel heading outbound: ------------------------- -- Accepting call from '' to

I have two servers, each connected to the PTSN via PRI. When I call from site A (951-999-9999) to site B (555-1212) and the phone at site B is on the phone, I hear the normal ring tone for about 20 seconds, then the message "all circuits are busy now. please try your call again latter" followed by the congestion tone. Instead, I want this to busy ring and then hang up without any

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 having problems getting an Xorcom USB Bri 4 dialling out in Australia. I can receive calls into the system without an issue, but I can not for the life of me dial out of the system. Below are my configs, I'm hoping its something simple that I just can't see as I've been looking at it for to long. Can any one point me in the right direction. P.S. Yes it is meant to be in TE

Just a quick question ---cut--- [Sep 17 15:52:14] WARNING[8232] app_dial.c: Unable to create channel of type 'IAX2' (cause 34 - Circuit/channel congestion) [Sep 17 15:52:14] WARNING[8232] chan_iax2.c: No more space [Sep 17 15:52:14] WARNING[8232] chan_iax2.c: Unable to create call [Sep 17 15:52:14] WARNING[8232] app_dial.c: Unable to create channel of type 'IAX2' (cause 34 -

Hey everybody, I've, within the last 3 weeks, moved over to a PRI from SBC/AT&T. I've received several complaints about dropped calls. Reviewing the archives on PRI and dropped calls shows that I should set the resetinterval=never in the zapata.conf and restart. This hasn't helped. The dropped calls have to date only been on outbound calls. Usually within 2 to 3 minutes

Hi Everyone, Just noted that PBXinaFLASH failed me again on yet something else. The uniqueid field didn't update on the asteriskcdrdb in the past few months but it is available in the .csv files in /var/log/asterisk/cdr-csv/*.csv I have already re-did the asterisk-addons install with correct parameters to include future calls "uniqueid" in the table (I have no clue why these

Hi, I just compiled and installed Asterisk-1.4.2 along with zaptel-1.4.1 and libpri-1.4.0 on a Debian machine with a TDM400P card. Everything goes ok but when I try to make a call through the ZAP channel get an error message about NO ZAP CHANNEL AVAILABLE. Ztcfg and zttool show the card correctly installed. When I tried to use the debug command ZAP SHOW, it was not present in the CLI. My