Ok... I had an interesting problem. After over a year of un-interrupted Asterisk service on my server, I had an unscheduled forced asterisk restart. I had to invoke a kill -9 for my asterisk process. This has been probably the first time I did a forceful kill on my Asterisk service on the production box.
A "restart gracefully, reload, stop" did not work. Doing a sip show peers also showed every phone and carrier was connected. But when someone tried to make a call, there was no verbose info or anything. At the time I am still under the CLI. Invoking the combinations of restart and stop simply took me back to the CLI prompt. I verified ALL logs, incoming and outgoing calls... and from the period of encountering this issue, no incoming or outgoing calls were present. I killed the process with a -9. Started asterisk from the shell prompt, and all was back and alive within seconds. I will be closely monitoring the box over the next week or so - but if anyone can shed some light with the hypothetical scenarios on why this would happen... that is a reload, restart, or stop would not work but take you back on the CLI... its appreciated! Cheers! Reza.
