Do you type "reload" at the cli a few times a day? If so try not reloading Asterisk and I'll bet Asterisk stop blocking. If you don't normally reload the box you will need to trouble shot normally.
mattf wrote:
Hello,
I have had several instances over the last month of Asterisk freezing, sometimes after 12 hours, sometimes after 8 days. The common elements are that: - all Zap channels lock[hangups don't register and no new calls in or out] - no new in/outbound calls can be made on Zap or SIP channels - people who are still connected to calls can continue to talk - in the CLI interface, you can "show channels" and view other info like "sip show peers", but you cannot do a "stop now" only way to stop asterisk process is a kill -9 - all attempted connections to the manager interface time out - the processor load and RAM usage on the machine is low.
I am experiencing these freezes on two separate identical RedHat 9 machines. On each I have 4 T1s connected and a usual concurrent call volume of 45 Zap/SIP conversations at once 14 hours a day. The processor load is never that high and the RAM usage is less than half.
There are never any consistent errors or warnings in the logs or the CLI.
I do have several AGI perl scripts in the dialplan and the SIP phones that connect are almost all Grandstream 102's, That's all I can think of that may be causing any problems. I have mpg123/musiconhold deactivated.
Has this happened to anyone else out there?
Does anyone have any suggestions? or ideas as to what may be causing it?
Thanks for any help,
MATT---
_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
