[Home]

Summary:ASTERISK-01686: PRI: Read on 39 failed: Unknown error 500 (PRI resets)
Reporter:mike9 (mike9)Labels:
Date Opened:2004-05-24 10:55:03Date Closed:2011-06-07 14:05:17
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 1: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 1
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 2: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 2
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 3: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 3
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 4: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 4
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 5: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 5
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 6: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 6
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 7: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 7
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 8: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 8
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 9: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 9
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 10: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 10
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 11: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 11
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 12: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 12
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 13: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 13
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 14: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 14
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 15: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 15
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 16: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 16
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 17: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 17
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 18: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 18
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 19: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 19
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 20: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 20
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 21: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 21
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 22: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 22
May 24 02:37:55 WARNING[1184099120]: Detected alarm on channel 23: Red Alarm
May 24 02:37:55 WARNING[1184099120]: Unable to disable echo cancellation on channel 23
May 24 02:37:55 WARNING[1175706416]: PRI: Read on 39 failed: Unknown error 500
May 24 02:37:55 NOTICE[1175706416]: PRI got event: 4 on span 1
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 1
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 2
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 3
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 4
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 5
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 6
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 7
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 8
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 9
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 10
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 11
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 12
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 13
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 14
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 15
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 16
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 17
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 18
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 19
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 20
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 21
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 22
May 24 02:38:00 NOTICE[1184099120]: Alarm cleared on channel 23
May 24 02:38:00 WARNING[1175706416]: PRI: Read on 39 failed: Unknown error 500
May 24 02:38:00 NOTICE[1175706416]: PRI got event: 5 on span 1


****** ADDITIONAL INFORMATION ******

First occurence in log file was December 14, 2003.
Happens at least twice daily, causing pri reset, and all calls are dropped. Can happen in the middle of the day, or at 2:00 in the morning when the phone system has been idle for hours. Telco has confirmed they provide line timing.
I can provide any more info that is needed.

System:
RedHat 9 (Linux 2.4.20-30.9)
P-III 1Ghz

/etc/zaptel.conf:
span=1,1,0,esf,b8zs
bchan=1-23
dchan=24
loadzone = us
defaultzone=us

[root@xenon src]# cat /proc/interrupts
          CPU0
 0:   35422695          XT-PIC  timer
 1:         32          XT-PIC  keyboard
 2:          0          XT-PIC  cascade
 5:  354144864          XT-PIC  t1xxp
 8:          1          XT-PIC  rtc
 9:   13866125          XT-PIC  eth0
14:     454604          XT-PIC  ide0
NMI:          0
ERR:          0
Comments:By: Mark Spencer (markster) 2004-05-24 11:51:14

Have you contact Digium technical support about this issue?
By: mike9 (mike9) 2004-05-24 11:54:09

Yes, the first time I talked to somebody (about a month ago), I was told they were starting to get a lot of reports on this, and were working to solve it. When I called back last week to check the status, I was told to submit a bug report.. I'm thinking since this is involving purchased hardware, it would have been more of a Digium issue, than an asterisk developer problem.
By: Mark Spencer (markster) 2004-05-24 12:03:39

Yes, it is, and I'm a bit concerned about the response you received.  Please find me on IRC (kram, irc.freenode.net)
By: Mark Spencer (markster) 2004-05-24 15:51:07

This is a tech support issue.  RMA will be issued.