similar to: B-channels resetting every 60 minutes?

Hi All, Hope you all are fine and good, Today i have found that Mine all PRI Channels are restating after every interval of one hour, and i have search and psot on fourms and everyone said that this is a normal behaviour. If this is a normal behaviour is there is any way to stop it { i still don't know what is the reson to restart ever hour } . Because this is listed everywhere that

Hey, I'm up and running fine with 30 Polycom 500s connected to Asterisk 1.2Beta on Cent OS 4.1 with a Digium TE110 connected to a PRI line. Nearly every hour, almost on the hour I get this: Sep 29 23:01:38 VERBOSE[3567] logger.c: -- B-channel 0/1 successfully restarted on span 1 Sep 29 23:01:38 VERBOSE[3567] logger.c: -- B-channel 0/2 successfully restarted on span 1 Sep 29

Hi , I'm having a problem that really bothers me , I have looked for similar cases but couldn't really find an answer . I keep getting messages which says that -- B-channel xx successfully restarted on span x and this causes the calls to be disconnected if somone is already using the channel that is being restarted, plz notice below the under lined text in which I was testing and

In my efforts to solve a mystery of asterisk slowly loosing it's ability to take incoming and outgoing calls I set asterisk to restart b-channels every 60 seconds hoping I would find something odd after some time. So now I am looking at the CLI a few hours later and look what happens when asterisk restarts the 23 b-channels I have. pbx1*CLI> -- B-channel 0/19 successfully restarted on

We are using AAH with Asterisk 1.2.7.1 with a TE405P as listed below. We are getting frequent restarts on the spans which lead to dropped calls. I have pasted some hopefully pertinent information below -- anyone have any clues that might help? Thanks Next line is repeated throughout messages, going through every channel in every connected span. asterisk/full.1:Apr 24 01:15:25 VERBOSE[4196]

Hi Guys, I have been checking logs and noticed this over the last night. Should I be concerned? and where to look for further details? Sample: [2010-04-13 04:31:27] VERBOSE[3844] logger.c: -- B-channel 0/1 successfully restarted on span 1 [2010-04-13 04:31:27] VERBOSE[3844] logger.c: -- B-channel 0/2 successfully restarted on span 1 [2010-04-13 04:31:27] VERBOSE[3844] logger.c: --

My TE110P reset some times in the day. E this cause an interruption in the service. How I decide this problem? my zaptel.conf span=1,1,0,esf,b8zs bchan=1-23 # set this to 1-15,17-31 for E1 dchan=24 # set this to 16 for E1 defaultzone=us loadzone=us my zapata.conf [channels] language=en signalling=pri_cpe switchtype=national echocancel=yes echocancelwhenbridged=yes echotraining=200 ; Asterisk

Hi all, We keep getting these and all the calls between these two asterisk boxes get dropped. what is going on here, I have been trying to solve this problem on my own but maybe I don't have the trunk setup right. also I have posed the output of my full log of the machine with the zap interface, the other is using ztdummy. IAX.conf on machine 1: [general] port=5036 ;iaxcompat=yes

Is it normal for the following to occur hourly on an E1 PRI ? -- B-channel 0/1 successfully restarted on span 1 -- B-channel 0/2 successfully restarted on span 1 -- B-channel 0/3 successfully restarted on span 1 -- B-channel 0/4 successfully restarted on span 1 -- B-channel 0/5 successfully restarted on span 1 -- B-channel 0/6 successfully restarted on span 1 --

Hi! I have an Asterisk Box with one E1. This is connected with PSTN. My problem is that periodically the Asterisk console shows the following message. -- B-channel 0/1 succesfully restarted on span 1 -- B-channel 0/2 succesfully restarted on span 1 -- B-channel 0/3 succesfully restarted on span 1 -- B-channel 0/4 succesfully restarted on span 1 -- B-channel 0/5 succesfully restarted on span 1 --

I have just finished installing a new asterisk box at my work. The box is quite hefty, dual Zeon 2.8s with SCSI drives and 2Gb of memory. I have a 4 port Digium T1 card for channel bank and PRI access. I activated a PRI from a local CLEC (DMS-500 based, National protocol). This PRI is on slot 2 of the card and is set as the primary timing source. It is ESF/B8ZS. All the software is latest

I managed to get Asterisk working with my PBX using T1, now I am moving on to trying to make PRI work. I have my zaptel.conf and zapata.conf configured as follows: Zaptel.conf: span=1,1,0,esf,b8zs bchan=1-23 dchan=24 loadzone=us defaultzone=us Zapata.conf: [channels] transfer=yes immediate=yes callprogress=yes language=en context=default switchtype=national signalling=pri_net group=1

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

Greetings. Today I've installed a fresh new E100P on a EuroISDN PRI. It seems to work well, accepting calls, but, when I start *, I have the screen flooded with this message: PRI got event: 8 (or 6) If i look into /var/log/asterisk/messages i've this Error: File chan_zap.c, Line 5341 (zt_pri_error): PRI: Read on 35 failed: Unknown error 500 Repeated indefinitely. Also, i've a

Hi, I'm getting the following error from an asterisk 1.6.0.9 installation: [May 20 06:07:18] ERROR[18517]: chan_dahdi.c:10515 dahdi_pri_error: Asked to delete sched id -1??? [May 20 06:07:18] ERROR[18517]: chan_dahdi.c:10515 dahdi_pri_error: No more room in scheduler This repeats a few times, then asterisk crashes. I can't seem to locate any info on this error at all. I'm using

We fairly recently switched service providers for our 4 PRI circuits. Since that time, we started to notice some failed inbound calls. These calls terminate with an ISDN cause code 47 'resource unavailble'. Most of the time I see this error on the first or second channel on the second span in a trunk group (This is the providers trunk group for hunting, not an Asterisk trunk group). All

Has anyone else had this symptom? It seems like my PRI ?restarts? each hour. I?ve got a PRI from Qwest in central California. What I don?t know is if this is on the * side or on the telco side. I don?t use my system enough to know if this is a big problem, a minor glitch or just an ?undocumented feature? - ? Any suggestions on how to track the source of these ?restarts?? Anybody else seen

Hi, Does anyone have any good empirical data suggesting what the maximum number of PRI calls (incoming and outgoing) without hardware echo cancellation can be handled on a single box is? I have a TE410P T1 (1st gen) card and I'm seeing interesting errors of D-Channels going down and then coming back up (See below). I've looked at the number of simultaneous calls at each of these points,

Perhaps everything isn't as spiffy as I thought When running zttool the card still reports as internally clocked Zaptel.conf: # Global data span=1,1,0,ccs,hdb3,crc4 bchan=1-15 dchan=16 bchan=17-31 loadzone=se defaultzone=se And as pointed out by Peter I do get a lot of D-channel warnings ... Aug 9 16:21:25 NOTICE[1350]: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 And

Hello! I am trying to install a TN405P on a P4-3GHz-HT machine running Debian Sarge with kernel 2.4.27. When I start Asterisk in -vvvvc mode it always shows == D-Channel on span 1 up == Restart on requested on entire span 1 == D-Channel on span 3 up == D-Channel on span 2 up == Restart on requested on entire span 3 == Restart on requested on entire span 2 == D-Channel on span 4 up == Restart