similar to: Phone lines

I have two data frames with a number of common variables that I wish to put into "long format". The first contains the variables es(Csales) [1] "terr" "Dec.02" "Jan.03" "Feb.03" "Mar.03" "Apr.03" "May.03" "Jun.03" [9] "Jul.03" "Aug.03" "Sep.03" "Oct.03"

I receive this error on the asterisk console and it is pretty much ALWAYS coming up. Sometimes there will be a break where it does not display. We had our PRI provider test the lines and they claim that there is no signalling problem. It doesn't matter if there are no calls or if there are 10 calls in progress the error is still displayed. I also get an annoying popping or clicking sound

Hi fellow asterisk users, I am running Asterisk 1.4.29 with an Digium TE121 card (wcte12xp kernel module) an approx. 100 snom320. The whole installation is running without issues since 5 months. Without having changed anything on the asterisk server for at least 2 months, i noticed "clicking sounds" at external calls over the PRI. Asterisk constantly throws the following messages: ...

Hi all, Last night I went to replace an Asterisk 1.4 + mISDN + b410p box with Asterisk 1.6.2 and DAHDI BRI - to no avail. I had two servers so copied network setting etc from the working one, moved the card across, ran dahdi_genconf etc and it didn't work. Here's the console output with notices disabled: lucas*CLI> pri intense debug span 1 Enabled debugging on span 1 [Dec 16

I'm running an E400P. Every now and then Asterisk stops receiving incoming calls. This turns up in the messages log: Nov 25 10:49:12 WARNING[65541]: File chan_zap.c, Line 5793 (pri_dchannel): Ring requested on channel 1 already in use on span 1. Hanging up owner. Nov 25 10:49:15 WARNING[81926]: File chan_zap.c, Line 5793 (pri_dchannel): Ring requested on channel 1 already in use on

Hi all, as good? I am trying to go up a board TE110P with link E1 ISDN PRI to establish connection with a central office Siemens HiPath 4000. But I am having the following errors: Server1:~ # asterisk -r Asterisk 1.2.10, Copyright (C) 1999 - 2006 Digium, Inc. and others. Created by Mark Spencer <markster@digium.com> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'show warranty'

Hi all, I just posted this question before last week. Meanwhile after upgrading Asterisk 1.0.7-BRIstuffed-0.2.0-RCg to 1.0.8-BRIstuffed-0.2.0-RCh the same problem occurs, but seems to be more seldom. Attached is now the output of "zap show channel" . - I'm running a stable Asterisk on a HP DL380G2 1.4Ghz 0,5GB RAM equipped with 1x TE410P and 2xJunghanns OctoBRI running in NT-mode.

Hi, I am getting this message on the * console on my first pri span. Pri show span show it is down, and I can't make any calls from the span. Apr 27 07:40:23 NOTICE[23988]: chan_zap.c:8202 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 27 07:40:23 NOTICE[23988]: chan_zap.c:8202 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Apr 27

hello all, i'm using TE110P and all configuration prosess is done. but after i do the 'modprobe' for zaptel and wcte11xp, follow by ztcfg -vv and asterisk -vvvgc i have this error. *CLI> May 27 14:44:33 WARNING[3059]: chan_zap.c:8534 pri_dchannel: PRI Error: We think we're the network, but they think they're the network, too. May 27 14:44:34 WARNING[3059]: chan_zap.c:8534

I thought this problem with PRI and channels getting out of sync was fixed in the 1.2.x release of Asterisk. Here are the errors: Jan 5 13:59:05 WARNING[1253]: chan_zap.c:8360 pri_dchannel: Ring requested on channel 0/2 already in use on span 1. Hanging up owner. Jan 5 13:59:11 WARNING[1253]: chan_zap.c:8360 pri_dchannel: Ring requested on channel 0/2 already in use on span 1. Hanging up

System have been working great for weeks, using an average 40 of 120 dahdi channels. But today, I suddenly see scary things like this: -- Moving call from channel 5 to channel 7 [Feb 25 10:18:12] WARNING[17129]: chan_dahdi.c:10608 pri_fixup_principle: Can't fix up channel from 5 to 7 because 7 is already in use [Feb 25 10:18:12] WARNING[17129]: chan_dahdi.c:11535 pri_dchannel: Ringing

Hi, For a significant time now (since about 0.2.0-rc8n) the qozap driver has become very verbose if an ISDN line is not connected... I get the messages below every couple of seconds in the asterisk logs. The "flaw" in the messages is the "Alarm cleared" message - The alarm cannot possibly be cleared because there is no physical media connected into that port!!! (BTW - All

Is a normal functionality? when I do #dahdi_cfg -vvvvvv In my Asterisk console shows this.... [Jul 24 13:39:08] NOTICE[30263]: chan_dahdi.c:9461 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 If I do this a lot of times...then [Jul 24 13:39:20] NOTICE[30263]: chan_dahdi.c:9461 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 [Jul 24

What am I doing wrong here? Why is this happening? libpri is version 1.0.7-1 (debian package) asterisk is version 1.0.7.dfsg.1-2 (debian package) zaptel is version 1.0.9.2 -- Executing Dial("SIP/739-5935", "Zap/g1/0916000739") in new stack -- Called g1/0916000739 -- Channel 0/1, span 1 got hangup Oct 10 13:14:45 WARNING[7544]: app_dial.c:412 wait_for_answer:

I am trying to test out my PRI configuration on a server by conection another asterisk server to it. I have the T-1 cards up and both set to bchan=1-23 and dchan=24 in zaptel.conf I am getting lost on the signalling in zapata.conf. using pri_cpe makes sense for my target box, but I am getting the following errors on my source box if I use pri_net or pri_cpe signalling. May 31 17:15:06

I've read as much as I can on this error and still can't seem to figure out what's causing this error: Jun 23 20:54:58 NOTICE[7483]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 23 20:55:03 NOTICE[7483]: chan_zap.c:7395 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 Jun 23 20:55:03 NOTICE[7483]:

Hi!, this issue makes me crazy. I read a lot of docs, also * mailling list and I try a lot of things without success. Any help will be appreciated. Here is the info: Hardware: -------------------------------------------- Supermicro Server with motherboard X7DB8, chipset Intel 5000P, Xeon 5050 Digium TE110P Software --------------------------------------------- Asterisk version 1.2.12.1

Hi, I got a problem with PRI that I'm not sure how to solve. Asterisk sits between PABX and PRI. PRI is span 1 and PABX is span 2. After every single call (no matter in what direction) I get "pri_fixup_principle: Call specified, but not found?" and "pri_dchannel: Hangup on bad channel" messages and the channel in question is restarted. As far as I can see, all

Today is the first time I've had any show stopping errors with asterisk since I started using it over 8 months ago... While I wait on the telco to check the circuit I thought I would post this here. Not sure yet but I thinks my 4-port PRI card is gone!!! I made a call and right when the person answered - BOOM. This is only a little better than it not working at all.

We've had a recurring issue on one of our servers where one or more zap channels from a PRI will get "stuck" causing incoming calls to fail. I happened to have a CLI session when it happened this morning. The start of the problem looked like: -- Channel 0/3, span 1 got hangup -- Channel 0/3, span 1 got hangup Jul 18 08:34:54 WARNING[20343]: chan_zap.c:7585 pri_dchannel: Ring