I have submitted both as bugs. One other unrelated follow-up question.
Before moving to callweaver we were using asterisk realtime. In the old
asterisk realtime there was a requirement for each new context to be
registered in extensions.conf to let the program know that the
information existed in the database rather than in the file.

As an example:

[1_1]
switch => realtime/[EMAIL PROTECTED]

Has there been a workaround yet so that it is not required to add these
to extensions.conf every time?

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brandon
Mackie
Sent: September-11-08 2:02 AM
To: Users Mailing List - Non-Commercial Discussion
Subject: [Callweaver-users] Crash and safe_callweaver doesn't restart

Good morning,

Two things... first off voicemail([EMAIL PROTECTED],ug5) causes a seg fault on 
our
server running callweaver 1.2.0.1. The gain parameter of the voicemail
function hasn't worked for some time. Is there anything else that must
be installed in order for this to work?

Second we're using Redhat Linux Enterprise 4 using the daemon script
provided with the callweaver source which is supposed to call
safe_callweaver. When running as a daemon and the above happens forcing
callweaver's face into the dirt it does not restart. When
safe_callweaver is called directly it restarts properly. Anybody know
why?
_______________________________________________
Callweaver-users mailing list
Callweaver-users@callweaver.org
http://lists.callweaver.org/mailman/listinfo/callweaver-users
_______________________________________________
Callweaver-users mailing list
Callweaver-users@callweaver.org
http://lists.callweaver.org/mailman/listinfo/callweaver-users

Reply via email to