[asterisk-users] PRI worked fine for months, now it stopps working after 2-3 hours

[Loic Didelot]

Hi,
finally I got even more logs from dmesg that could be useful.

[ 1380.149049] wcte12xp0: Missed interrupt. Increasing latency to 5 ms
in order to compensate.
[ 1446.621237] wcte12xp: turning off tone detection
[ 1802.551501] wcte12xp: turning off tone detection
[ 1979.801185] wcte12xp0: Missed interrupt. Increasing latency to 6 ms
in order to compensate.
[ 2579.233403] wcte12xp0: Missed interrupt. Increasing latency to 7 ms
in order to compensate.
[ 3179.055821] wcte12xp: NMF workaround on!
[ 3179.055825] wcte12xp: Setting yellow alarm
[ 3179.055847] Zaptel: Master changed to XBUS-00/XPD-00
[ 3179.055941] wcte12xp0: Missed interrupt. Increasing latency to 8 ms
in order to compensate.
[ 3179.120989] wcte12xp: NMF workaround off!
[ 3184.118231] Zaptel: Master changed to WCT1/0
[ 3184.174181] wcte12xp: Clearing yellow alarm
[ 3778.467882] wcte12xp0: Missed interrupt. Increasing latency to 9 ms
in order to compensate.


Does zaptel really need to increase the latency and to change the
master?

Best regards,
Loïc Didelot.


On Wed, 2009-08-26 at 10:34 +0300, Tzafrir Cohen wrote:
> On Wed, Aug 26, 2009 at 08:53:18AM +0200, Loic Didelot wrote:
> > Hello,
> > we have several customers with a PRI line and a Wildcard TE121.
> > Everything worked fine, but now are one customer the PRI stops working
> > after a few hours.
> > 
> > "zap show channel 1" shows that the channel is InAlarm. I the log files
> > of asterisk I see that the D-Channel seems down. Restarting asterisk
> > does not help, but rebooting the whole server resolves the problem for
> > another 2-3 hours.
> 
> The obvious stupid question: Does Zaptel (The kernel) report that the
> span is in alarm? 
> 
> cat /proc/zaptel/1
> 
-- 
Loïc DIDELOT
MIXvoip S.a.
Tel: +352 20 3333 20
Fax: +352 20 3333 90
ldidelot at mixvoip.com
http://www.mixvoip.com