Hi all, Our asterisk PBX, randomly restarts all the channels of the E1 connection. It sends this message "There is no D-Channel, using channel 16 anyway".Then the asteisk recive (or it thinks it recives) yellow alarms at all the B-channels, after that it restart all the channels. When restarting the B-channels it cut all the conversations that is handling at that moment. Does anyone have an idea for what it is happening? We run a asterisk 1.2.1 on a HP Proliant ML310, PIV 3Ghz 2 Mb L2 cache, 1 Gb Ram. We have a TE210P digium card configured for E1. This pbx has been running for almost a moth before giving this problems, we have called our telco and seens that in their side all is ok. (Our telco is ONO- Spain) This is the zaptel.conf span=1,0,0,ccs,hdb3,crc4,yellow bchan = 1-15,17-31 dchan = 16 # Global data loadzone = es defaultzone = es this is the zapata.conf [trunkgroups] [channels] language=es context=from-pstn switchtype=euroisdn pridialplan=unknown signalling=pri_cpe busydetect=yes callprogress=yes usecallerid=yes hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes cancallforward=yes callreturn=yes echocancel=yes echocancelwhenbridged=yes echotraining=400 rxgain=0.0 txgain=0.0 group=1 callgroup=1 pickupgroup=1 immediate=no channel=>1-15,17-31 callerid=asreceived thanks in advance, Xavier Gil Estarellas. ______________________________________________ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y m?viles desde 1 c?ntimo por minuto. http://es.voice.yahoo.com
On 1/16/06, Xavier Gil <xgilest@yahoo.es> wrote:> Hi all, > Our asterisk PBX, randomly restarts all the channels of the E1 connection. It sends this message > "There is no D-Channel, using channel 16 anyway".Then the asteisk recive (or it thinks it > recives) yellow alarms at all the B-channels, after that it restart all the channels. When > restarting the B-channels it cut all the conversations that is handling at that moment. Does > anyone have an idea for what it is happening? > We run a asterisk 1.2.1 on a HP Proliant ML310, PIV 3Ghz 2 Mb L2 cache, 1 Gb Ram. We have a TE210P > digium card configured for E1. > > This pbx has been running for almost a moth before giving this problems, we have called our telco > and seens that in their side all is ok. (Our telco is ONO- Spain) > > This is the zaptel.conf > > span=1,0,0,ccs,hdb3,crc4,yellow > bchan = 1-15,17-31 > dchan = 16 > > > # Global data > > loadzone = es > defaultzone = es > > this is the zapata.conf > [trunkgroups] > > [channels] > > language=es > context=from-pstn > switchtype=euroisdn > pridialplan=unknown > signalling=pri_cpe > busydetect=yes > callprogress=yes > usecallerid=yes > hidecallerid=no > callwaiting=yes > usecallingpres=yes > callwaitingcallerid=yes > threewaycalling=yes > transfer=yes > cancallforward=yes > callreturn=yes > echocancel=yes > echocancelwhenbridged=yes > echotraining=400 > rxgain=0.0 > txgain=0.0 > group=1 > callgroup=1 > pickupgroup=1 > immediate=no > channel=>1-15,17-31 > callerid=asreceived > > thanks in advance, > Xavier Gil Estarellas. >Try adding resetinterval=never That may help. -- Bird's The Word Technologies, Inc. http://www.btwtech.com/
On 16 Jan 2006, at 11:05, Xavier Gil wrote:> > We run a asterisk 1.2.1 on a HP Proliant ML310, PIV 3Ghz 2 Mb L2 > cache, 1 Gb Ram. We have a TE210P > digium card configured for E1. > > This pbx has been running for almost a moth before giving this > problems, we have called our telco > and seens that in their side all is ok. (Our telco is ONO- Spain) > > This is the zaptel.conf > > span=1,0,0,ccs,hdb3,crc4,yellowI think you want that to be: span=1,1,0,ccs,hdb3,crc4 Meaning that you want to use the telco's clock as the primary timing source for the card. Anytime you connect a PRI to a 'real' telco you almost always want to use them as the timing source. What have you got on the other leg of the TE210P ? Tim. http://www.westhawk.co.uk/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060118/83418dc1/attachment.htm
>On 16 Jan 2006, at 11:05, Xavier Gil wrote: > >> >> We run a asterisk 1.2.1 on a HP Proliant ML310, PIV 3Ghz 2 Mb L2 >> cache, 1 Gb Ram. We have a TE210P >> digium card configured for E1. >> >> This pbx has been running for almost a moth before giving this >> problems, we have called our telco >> and seens that in their side all is ok. (Our telco is ONO- Spain) >> >> This is the zaptel.conf >> >> span=1,0,0,ccs,hdb3,crc4,yellow > >I think you want that to be: > >span=1,1,0,ccs,hdb3,crc4 > >Meaning that you want to use the telco's clock as the primary timing >source for the card. > > >Anytime you connect a PRI to a 'real' telco you almost always want to >use them as the timing source. > > >What have you got on the other leg of the TE210P ? > > > >Tim.We have changed span=1,0,0,ccs,hdb3,crc4,yellow -> to >> span=1,1,0,ccs,hdb3,crc4,yellow without any change. We still have the same problems. In the other leg is empty. Xavi. ______________________________________________ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y m?viles desde 1 c?ntimo por minuto. http://es.voice.yahoo.com
I had the horrible problems with a TE205P installtion with 1 E1 connected to the telco and the other E1 connected to a digital Panasonic PBX. I had frame slips, dropped calls, bad frames on D-Channel, and I did 2 things to stop most of these problems: First thing is suggested before: span=1,1,0,ccs,hdb3,crc4 The timing had to be adjusted for the telco and not internally (For both E1s) Second thing: IRQs. I discovered I had an IRQ conflict with the network card (the worst kind), I tried everything to avoid it and when I failed I disabled one serial port and one parallel part from the BIOS of the computer forcing some IRQs to become free and automatically linux assigned the Digium TE205P card to one of the freed IRQs. These 2 steps solved my problems with the E1 line and things became much more stable. I hope this was useful. Antoine Megalla.>> We run a asterisk 1.2.1 on a HP Proliant ML310, PIV3Ghz 2 Mb L2>> cache, 1 Gb Ram. We have a TE210P >> digium card configured for E1. >> >> This pbx has been running for almost a moth beforegiving this>> problems, we have called our telco >> and seens that in their side all is ok. (Our telcois ONO- Spain)>> >> This is the zaptel.conf >> >> span=1,0,0,ccs,hdb3,crc4,yellow > >I think you want that to be: > >span=1,1,0,ccs,hdb3,crc4 > >Meaning that you want to use the telco's clock as theprimary timing>source for the card. > > >Anytime you connect a PRI to a 'real' telco youalmost always want to>use them as the timing source. > > >What have you got on the other leg of the TE210P ? > > > >Tim.__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com