That can very well be the cause - there is a known issue, first stated by
"mattf" on this list, about trouble when a manager API client looses the
connection and then another API client (maybe the same using a different
connection) comes into play.
Thankfully I read about that in the wiki and used a version of his idea to implement a central daemon that handles all connections. The daemon runs on the local machine so it shouldn't loose the connection unless asterisk dumps it.
So: Stop using that deamon and see if Asterisk becomes stable.
You could also introduce regular - but not too many! - "reloads", e.g. 1-
4 times a day plus one "restart" during night time with the help of a
CRON job.
Unfortunately we can't without loosing our ability to function as a call center, since the daemon is required to handle logins/logouts of our agents and reporting back to us queue statistics. Do the reloads help clean out pending troubles? I read a little about doing the restarts (which is still difficult since it logs our agents out) but maybe if reloads help we could try that.
Also: Check /tmp for a core file and run gdb and a backtrace if you find
one. Search for "debugging" on the Wiki for more detailed instructions.
No luck there, I guess I'll have to keep waiting for it to happen again, it's been 2 days now, funny how it happens all the time when you're not waiting.
Thanks,
--Daniel Daley-- [EMAIL PROTECTED]
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
