[asterisk-users] Asterisk Database Handling

[Alex Balashov]

Sanjay Rajdev wrote:
> I had a similar problem, but in my case we had a custom application that 
> was throwing an segmentation exception which was causing Asterisk to 
> Restart. And in that case It use to miss the log in database.
> You can determine the same by looking at the UNIQUEID being logged for 
> the call. The UNIQUEID actually comprises of 2 things 
> DateTimeString.CallNumber, everytime Asterisk restarts CallNumber will 
> start from 1. So you can check the 2-3 UNIQUEID before you missed entry 
> in CDR table and 2-3 after the missed entry to determine if Asterisk 
> Restarted.
> Other way is you can see the kernel logs to see if Asterisk has thrown 
> any exception. they can be found on Linux at /var/log/messages

There is no such thing as a segmentation "exception."  C does not have 
exception handling, and Asterisk does not throw any exceptions.

There is, however, a "segmentation fault."  That is a memory condition 
that causes the operating system to terminate the process, in absence of 
a signal handler for it.

None of these can or should be characterised as "exceptions," and have 
absolutely nothing to do with them.

-- 
Alex Balashov
Evariste Systems
Web    : http://www.evaristesys.com/
Tel    : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (706) 338-8599