I haven’t started digging through the code yet (as I am not a c programmer myself). I am kind of hoping someone might know this off the top of their head.
I’ve been using Trixbox 1.2.2 for a few months now as a voicemail platform for a Cisco CallManager 5.0.4. Occasionally * would lock up on me, it has maybe a total of 4 times now. This last time I actually had enough debugging and verbosity on so that I might know what it died doing. The last item I show in my log for asterisk is a debug message from app_voicemail.c calling a script that writes a call file that is used to turn on/off mwi on the phones on Cisco CallManager. (Script is an extremely short/simple shell script).
Now this is my viewpoint, it seems that * become totally unresponsive and I have to issue a “service asterisk stop” and a “service asterisk start” to get any activity to happen. Nothing more is written to the logfiles when asterisk has “frozen”. If I issue the command “asterisk -r” to get to the command prompt of asterisk I get the following:
[b][root@asterisk1 ~]# asterisk -r
Asterisk 1.2.11 svn rev 40948, Copyright © 1999 - 2006 Digium, Inc. and others.
Created by Mark Spencer email@example.com
Asterisk comes with ABSOLUTELY NO WARRANTY; type ‘show warranty’ for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type ‘show license’ for details.
Note the fact that I don’t get a prompt. I expected a asterisk1*CLI>.
Sorry for being so longwinded. Does the app_voicemail.c when calling the externnotify application expect a return code or anything else? Can a problem in the script being run cause asterisk to lockup?