Ticket #3742 (closed Bugs: invalid)

Opened 1 year ago

Last modified 1 year ago

asterisk crashes in voicemail

Reported by: novazur Assigned to:
Priority: crash Milestone: 2.6
Component: Voicemail Version: 2.5-branch
Keywords: Cc:
Confirmation: Unreviewed SVN Revision (if applicable):
Backend Engine: Asterisk 1.6 Backend Engine Version:

Description (Last modified by p_lindheimer)

Hi, That's not my first freepbx use. I installed asterisk-1.6.1.1 on a new server (gentoo x86_64). Didn't modify anything in the conf. Install freepbx after generating mysql tables (newinstall.sql) Connect to the gui, juste update all (no new module). create 2 extensions, 1 SIP, 1 IAX2. For the IAX2 extension, I just set cid num, cid name, password, activate voicemail with a password and email. All the rest is by default. I call IAX2 extension with a SIP extension (softphone). I fall on the voicemail (normal), and at the start recording, asterisk crashes :

    -- Goto (macro-vm,s-CHANUNAVAIL,1)
    -- Executing [s-CHANUNAVAIL@macro-vm:1] Macro("SIP/200-00b76bf8", "get-vmcontext,100") in new stack
    -- Executing [s@macro-get-vmcontext:1] Set("SIP/200-00b76bf8", "VMCONTEXT=default") in new stack
    -- Executing [s@macro-get-vmcontext:2] GotoIf("SIP/200-00b76bf8", "0?200:300") in new stack
    -- Goto (macro-get-vmcontext,s,300)
    -- Executing [s@macro-get-vmcontext:300] NoOp("SIP/200-00b76bf8", "") in new stack
    -- Executing [s-CHANUNAVAIL@macro-vm:2] VoiceMail("SIP/200-00b76bf8", "100@default,u""") in new stack
    -- <SIP/200-00b76bf8> Playing 'vm-theperson.gsm' (language 'en')
    -- <SIP/200-00b76bf8> Playing 'digits/1.gsm' (language 'en')
    -- <SIP/200-00b76bf8> Playing 'digits/0.gsm' (language 'en')
    -- <SIP/200-00b76bf8> Playing 'digits/0.gsm' (language 'en')
    -- <SIP/200-00b76bf8> Playing 'vm-isunavail.gsm' (language 'en')
    -- <SIP/200-00b76bf8> Playing 'vm-intro.gsm' (language 'en')
    -- <SIP/200-00b76bf8> Playing 'beep.gsm' (language 'en')
serveur2*CLI>
Disconnected from Asterisk server
Executing last minute cleanups

The file starts being recorded but stay empty :

# ls -la /var/spool/asterisk/voicemail/default/100/tmp/
total 8
drwxr-xr-x 2 asterisk asterisk 4096 juin 30 16:39 .
drwxr-xr-x 4 asterisk asterisk 4096 juin 30 16:19 ..
-rw-r--r-- 1 asterisk asterisk    0 juin 30 16:29 M4ukXu
-rw-r--r-- 1 asterisk asterisk    0 juin 30 16:39 xIdmT0
-rw-r--r-- 1 asterisk asterisk    0 juin 30 16:19 y7aulh

I think I have all requirements installed (sox...)

I can't find why it is crashing like that. Nothing more in logs.

(Sorry for my poor english)

Attachments

logs.txt (8.8 kB) - added by novazur on 06/30/09 13:42:41.
logs

Change History

06/30/09 13:42:41 changed by novazur

  • attachment logs.txt added.

logs

06/30/09 16:23:38 changed by p_lindheimer

  • description changed.

06/30/09 16:36:00 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to invalid.

there is nothing in this data that indicates a problem with FreePBX. Closing as invalid. You may want to seek further help on the forums and if you do come across something that points to a bug feel free to open a new ticket or reply to this with the new data if applicable.

(follow-up: ↓ 6 ) 06/30/09 23:07:38 changed by novazur

Nothing wrong ? That's a joke ? Asterisk crashes and that's normal ? I'm now sure it's because of freepbx. I desinstalled and reinstalled about 20 times, and 1 time, I had it working, but my installations wrere very durty after that. So I uninstalled all, cleaned all, and installed again from scrash, and now, I have the same problem again.

06/30/09 23:15:08 changed by novazur

Connected to Asterisk 1.6.1.0 currently running on serveur2 (pid = 21917)
Verbosity was 0 and is now 7
    -- <SIP/200-026281b8> Playing 'beep.gsm' (language 'fr')
serveur2*CLI>
Disconnected from Asterisk server
Executing last minute cleanups
02:09:32 root@serveur2 /etc # asterisk -rvvvvvvv
Asterisk 1.6.1.0, Copyright (C) 1999 - 2008 Digium, Inc. and others.
Created by Mark Spencer <markster@digium.com>
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core 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 'core show license' for details.
=========================================================================
  == Parsing '/etc/asterisk/asterisk.conf':   == Found
  == Parsing '/etc/asterisk/extconfig.conf':   == Found
Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)
02:09:35 root@serveur2 /etc # ll /var/run/asterisk/asterisk.ctl
srwxr----- 1 asterisk asterisk 0 juil.  1 02:09 /var/run/asterisk/asterisk.ctl
02:09:44 root@serveur2 /etc # ps axf | grep asterisk
22671 pts/1    S+     0:00              |   \_ grep --colour=auto asterisk
02:14:40 root@serveur2 /etc #

07/01/09 09:40:42 changed by novazur

(in reply to: ↑ 3 ) 07/01/09 10:29:05 changed by p_lindheimer

Replying to novazur:

Nothing wrong ? That's a joke ? Asterisk crashes and that's normal ? I'm now sure it's because of freepbx. I desinstalled and reinstalled about 20 times, and 1 time, I had it working, but my installations wrere very durty after that. So I uninstalled all, cleaned all, and installed again from scrash, and now, I have the same problem again.

Please note my comment: "there is nothing in this data that indicates a problem with FreePBX" which means exactly that. Clearly Asterisk is crashing in your case, but that does not make it a FreePBX bug and nothing you provided could be at all conclusive. As mentioned, if further data is uncovered, we are happy to look at it. But this is not a help forum for installation which is likely the issue. That is why you were pointed there. We can't debug something (or keep a bug open) that does not point to anything on the FreePBX side.

07/02/09 08:42:15 changed by novazur

The forum is useless. I posted there, but anybody to answer.

I don't need help to install FreePBX, I already have 2 installed and working, but with asterisk 1.2 There is a problem with a freepbx & asterisk 1.6 from scratch, that's sure. If you don't want to understand that, you always will have this bug.

07/02/09 09:01:47 changed by p_lindheimer

lots of people are using FreePBX with Asterisk 1.6. There is no information in your bug report that can point to a bug in FreePBX. That does not mean there is not one, but a bug report that is effectively "my install does not work and I don't know why" is not something that a developer can act on.

If you are not getting traction in the forum, it's likely because there is not enough information there for someone to help you with, or alternatively because it's summer and a lot of people take vacations in the summer... Also keep in mind that when Asterisk crashes, it signifies a bug in Asterisk and you may want to check their forum and IRC channel. Even if FreePBX were to have provided bogus configuration information to Asterisk (which is probably not the case), Asterisk should never crash, when it does, it means Asterisk has a problem or there are other system issues related to that.

In any event, this is not a discussion forum so do please keep the discussions on the forums.

07/02/09 11:38:10 changed by novazur

Not enough information at http://www.freepbx.org/forum/freepbx/installation/fresh-install-voicemail-makes-asterisk-crashing#comment-20679 I don't know what you want. You just want a patch ? I can't do it for the moment, but when I will find the bug, not sure I'll be insterested to share it

I think you didn't read all what I explained. Sure, english is not my langage, but I give so mutch information to answer like you do : "Even if FreePBX were to have provided bogus configuration information to Asterisk (which is probably not the case)"

Probably not the case ? Splendid ! I'm surely stupid so.

If you want me to respond in the forum, so go in the forum to answer me first. I'm just talking alone there.

For your information, I just downgrade asterisk to 1.2, and then to 1.4, and all works fine with freepbx. I'll upgrade to 1.6 soon, and if it works too, it will perfectly show that it is a fresh asterisk/freepbx install that is buggy, may be the install process.

07/02/09 15:34:55 changed by mbrevda

"I just downgrade asterisk to 1.2, and then to 1.4, and all works fine" So your saying the problem only develops when you upgrade asterisk to 1.6?

07/02/09 16:28:08 changed by novazur

That's very difficult for me to make you understand me. I never "upgraded" to asterisk 1.6, because at the first time (and tried several times), I directly installed asterisk 1.6 (that's a new server, and I want to test 1.6 on it).

To verify if it works with a upgrade, I downgraded to 1.2 (the version I use elsewhere, to be sure all works fine in my config), then upgraded to 1.4, and I'll upgrade to 1.6, to test if the problem is only with a fresh 1.6 install. If it works when I upgrade to 1.6, that will prove that the problem is really there. If it doesn't work, it won't prove anything, except that i'll have to work more...

07/02/09 23:35:30 changed by mbrevda

I have no clue what your on about other than that in your previous post you said that things work perfectly fine in 1.2 and 1.4. Hence, one must conclude that the problem lies with 1.6 or you method of upgrade. Or in other words, this isn't a freepbx issue

07/03/09 09:50:38 changed by novazur

Ok, forget it. You don't want to understand.

My conclusion is : never open a ticket if you can't provide a patch.

EOT.

07/03/09 12:39:50 changed by p_lindheimer

novazur,

everyone is going out of their way to be 'kind' to you, here and on the forum. You have a bit to learn about interacting with people who are trying to help you out of kindness. There are a lot of paid support options, apparently you may be better off with one of those?

07/07/09 23:32:16 changed by mickecarlsson

For those who have followed this ticket:

It was not a bug with FreeePBX but in fact it was the reporters (old) version of Asterisk 1.6 that was the cause.

He reported it to asterisk bug tracker and got a response: https://issues.asterisk.org/view.php?id=15428&nbn=4

"Already fixed in the 1.6.1 branch. "