a day declares the PRI trunk down and stops handling calls until the
asterisk is stopped, the zaptel/te120 modules reloaded, and asterisk
started.
Just before things go down, the log shows the following error:
ERROR[9424] chan_zap.c: Write to 28 failed: Unknown error 500
at which point a "show pri spans" reports "PRI span 1/0: Provisioned,
Down, Active" and a "pri show span 1" reports:
Primary D-channel: 24
Status: Provisioned, Down, Active
Switchtype: National ISDN
Type: CPE
Window Length: 0/7
Sentrej: 0
SolicitFbit: 0
Retrans: 0
Busy: 0
Overlap Dial: 0
T200 Timer: 1000
T203 Timer: 10000
T305 Timer: 30000
T308 Timer: 4000
T309 Timer: -1
T313 Timer: 4000
N200 Counter: 3
(a) What is causing this?
(b) How can it be fixed?
(c) Why does Asterisk not recover automatically to what appears to be an
intermittent problem?
--
George Pajari (dCAP), netVOICE communications 604 484 VOIP(8647) x102
www.digium.ca www.grandstream.ca www.sipura.ca www.snom.ca
Open Source VoIP/Telephony Specialists 1 877 NET VOIP (638 8647 x102)
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
No comments:
Post a Comment