Regarding:

serveur2*CLI> /usr/sbin/safe_asterisk: line 146: 19778 Erreur de segmentation  (core dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} > /dev/${TTY} 2>&1 < /dev/${TTY}
Asterisk ended with exit status 139
Asterisk exited on signal 11.

Have you checked to see why it is crashing? Did you check the Asterisk logs for any hints of errors. If FreePBX is providing bogus configuration information to make Asterisk core, that would be a bug in FreePBX, but is still very much a bug in Asterisk that needs to be understood. Asterisk should never core, it can shut down itself if it needs to from bogus info.

As far as getting help in general and in your comments in the ticket, you would be advised to not be quite so 'assertive' in your confidence as your tone is only going to result in people ignoring this and any thread associated with it. Countless people come by saying they are right, they know what they are doing, ... only to almost always result in some issue on their side. It's the best way to make everyone ignore your requests.

As far as the ticket being re-opened, as was indicated in the ticket, we can reopen a ticket as we have many times, when there is something that either points to a likely a bug in FreePBX, or some way that someone can independently reproduce the issue. Neither of those are present and given the thousands of active installs running with FreePBX, the current data seems to indicate that getting basic functionality up on 1.6 functions.

where's the log output at the time of the crash, it's not here (whether it appears helpful or not, knowing the last thing it did when starting up that made it crash may be valuable to someone.

Go to /var/spool/asterisk/voicemail/default and do

chmod -R 755 *

Then try again. The reason for the crash is lack of permission for the voicemail application to create the file.

If you Google for Asterisk ended with exit status 139 you will find numerous postings about this error, some of them are related to (fixed) bugs in Asterisk but most of them are faulty setups.

And NO, there is NO bug in FreePBX, it is certainly your setup that is failing.

And the bug is?

If you do not post it you are the laugh of the day.....

So it was your setup that was wrong.....

Did you simply have a configuration issue or was it something else?

If it was a config issue a thank you to the developers who assisted you. If you found a real bug it should be shared with the community.

Misconfiguration is not a bug.

OK, I see now that I have made a typo, it should have been chmod -R 775, not 755.
But still, if Asterisk crashes when creating the spool file it is not FreePBX fault.

The solution posted by me solves almost every cause when voicemail crashing after playing the beep (when typed correctly that is).

Still, what was the cause of your problem?

I can't help replying - even though it wont matter, I run asterisk 1.6 with freepbx without issues (actually i did some of the work keeping freepbx updated to work with 1.6). So it would be really interesting to now why your system crashed. If there is some issues using gentoo - that something we can work around in the install of freepbx.

And please behave a bit here - we are all adults and can discuss issues as adults.

/niklas

https://issues.asterisk.org/view.php?id=15428&nbn=4

There (novazur):
"I've first reported to freepbx, but I think the problem is more with asterisk."

Here (novazur):
"I found the bug, and i corrected it, and it works perfectly now..."

There (seanbright):
"I believe this has already been resolved in the 1.6.1 branch. Could you try the attached patch and report back your results?"

There (novazur):
"That's perfect !
You saved me.
I'm on that for 2 weeks, tried all what I could...
Thanks a lot."

LOL?

Well novazur, despite your remarks the issue was that you used a version of Asterisk 1.6 that had a bug in it.

On June 6:th you posted that you have fixed the "bug" but refused to tell us what the problem was.

On the very same day seanbright told you what the problem was with this remark:

Then on July 7:th you replied:

My point stands, it was your setup that was the issue, not FreePBX.

So LOL back to you.

PS. Your statement in the bug report is funny:

Well, if you install Asterisk on your machine, it is your setup

You blamed, loudly and very upset, that it was a bug with FreePBX. When everyone told you it was not and tried to help you, you eagerly continue to say it was FreePBX.

There where at least three developers that tried to help you, but no, you refused to listen to us.

And when you (finally) was convinced that it was not FreePBX that caused the error you had with your setup, you refused to tell us what it was.

We had to find out by ourself, and the remark that you put in when you filed the bug report at asterisk put a smile on our faces.

Take care,
Mikael Carlsson
Sweden

Well, the only thing that you have posted here are nothing but trouble pointing out that you are so perfect, the FreePBX does not work with Asterisk 1.6 etc etc.
This is what you wrote in the ticket:

Notice: "I'm now sure it's because of freepbx"

And by looking at the I desinstalled and reinstalled about 20 times I figured out that you are a Windows user because that is how they "solve" problems.

I guess that this discussion is ended.
There where no bug in FreePBX, there where a bug in Asterisk.
You got an answer, fixed it but would not tell us what it was. Why I don't know.

folks, it's not worth the effort. I'll make this comment and then bow out. I've already been asked by people in the community if I would lock this thread as it is really pointless but being one who does not like censorship, I would prefer not to.

I think there is a simple conclusion here. When things go wrong, one should not be so quick to point blame, and in particular, when people are trying to help.

If one has expectations beyond what one gets from free help, go to one of the many sources of paid support (though no guarantee they are going to be better).

And when someone asks for help, especially after so strongly implying there is a problem, but in any event, it is proper etiquette to post what the solution is. Even if you don't like what the people who tried to help you are telling you, the thread is there to be found by the countless google searches for someone who may have the same problem. Not posting what you found implies a level of 'selfishness' that "I don't care about the rest of the world, I expected them to help me find my bug, but once I found it, I'm not willing to post the solution for the next person that comes along."