similar to: Is it recommended to let Asterisk run with "backtrace options"

On Fri, Feb 17, 2017 at 5:17 AM, Olivier <oza.4h07 at gmail.com> wrote: > Hi George, > > How does ast_coredumper compare to ast_grab_core ) ? > Is it worth learning to use both or shall favor one ? > > PS: As I don't know either program, yet, my question may seem silly. > Please, forgive me for this > Not silly at all. ast_grab_core actually kills asterisk to

Hi all, I just upgraded a production server to asterisk 1.4.25, compiling with the following: [*] 1. DONT_OPTIMIZE [*] 2. DEBUG_CHANNEL_LOCKS [*] 3. DEBUG_THREADS [*] 4. DEBUG_FD_LEAKS [ ] 5. LOW_MEMORY [*] 6.

2016-09-06 17:48 GMT+02:00 Tzafrir Cohen <tzafrir.cohen at xorcom.com>: > On Tue, Sep 06, 2016 at 06:37:52AM -0600, George Joseph wrote: > > On Tue, Sep 6, 2016 at 1:55 AM, Olivier <oza.4h07 at gmail.com> wrote: > > > > Where should core file be created when Asterisk is run as a daemon by > > > asterisk user and group ? > > > Is there a setting I

Hello asterisk-users, We've been having intermittent issues with chan_sip - it stops responding to cli requests, trying to reload chan_sip from cli doesn't seem to have any effect, initiated calls carry on for a short period, but no new SIP requests are processed ('sip show channels' hangs forever, server stops responding to SIP OPTIONS, or any other SIP messages). We have updated

hi all, I'm have a bit of a hard time with some segfaults on running 1.4.23.1 and mISDN 1.1.8. I already enabled " DONT_OPTIMIZE" and " DEBUG_THREADS" in asterisk so I can now generate a bt. I did that (following the instructions on voip-info) but I'm not sure how to "read' the output now. By looking at the bt below, can one see if the problem is caused by

I think were getting closer: I did: - I edited /etc/default/asterisk to include : AST_USER="root" AST_GROUP="root" # systemctl daemon-reload # systemctl start asterisk # ps aux | grep asterisk root 3602 7.1 2.5 60332 26012 ? Ssl 16:00 0:03 /usr/sbin/asterisk -U root -G root -g # rasterisk # pkill -SEGV asterisk Then console showed: Segmentation error (core

Hi everybody, sometimes we have an Asterisk-crash, but no clue why this is happening, so I'm trying to make a coredump to analyse it. I compiled Asterisk 1.4.20.1 on CentOS 5.4 i386 with "DEBUG_THREADS" and "DONT_OPTIMIZE", then I start it with: # /bin/bash /usr/sbin/safe_asterisk This should do an "ulimit -c unlimited", but I entered it in the terminal again.

Somehow I can't get 1.6.2.13 to compile with DEBUG_CHANNEL_LOCKS. Downloaded latest tgz and extracted $ ./configure $ make menuselect (select the needed options from compiler flags) $ grep DEBUG_CHANNEL_LOCKS menuselect.makeopts MENUSELECT_CFLAGS=DONT_OPTIMIZE LOADABLE_MODULES DEBUG_CHANNEL_LOCKS MALLOC_DEBUG $ make && make install $ asterisk && asterisk -rx "core show

On Tue, Feb 14, 2017 at 2:51 PM, George Joseph <gjoseph at digium.com> wrote: > > > On Tue, Feb 14, 2017 at 10:21 AM, Olivier <oza.4h07 at gmail.com> wrote: > >> Hello, >> >> I've got a 13.13.1 system using PJSIP stack on debian Jessie. >> It runs from 50 to 100 simultaneous calls (so 100 to 200 PJSIP channels) >> all day long. >>

Hello For users who 1) don't have a QoS-capable ADSL router and 2) would like to run Asterisk with a couple of SIP trunks, I was wondering what hardware is recommend to run any of the main open-source *WRT projects to which Asterisk has been ported: (http://en.wikipedia.org/wiki/List_of_wireless_router_firmware_projects Thank you.

Ok , digging more into this i could see that (timers=no) and (timers=forced) not work asterisk not pay attention to this options when is reloaded cli not say anything and when the pjsip show endpoint <endpoint> it show always timers=yes when (timers=no) and (timers=forced) to that endpoint. I wonder to force asterisk to refresh the session in some cases when is needed . pjsip is able to

Hello, I've got a 13.13.1 system using PJSIP stack on debian Jessie. It runs from 50 to 100 simultaneous calls (so 100 to 200 PJSIP channels) all day long. >From time to time, roughly meaning once a month, it segfaults with lines (from dmesg -T output) like this: asterisk[1160]: segfault at 7efffffe ip 00000000005881d6 sp 00007fec95c33910 error 4 in asterisk[400000+2a2000] Debug level

Hello! I clear remarks in Makefile: DEBUG_THREADS = -DDEBUG_THREADS -DDETECT_DEADLOCKS But same things in CLI: Aug 30 18:16:31 WARNING[22292]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x82f2fe0', 9 retries! -- Zap/32-1 is proceeding passing it to Zap/31-1 -- Zap/32-1 is ringing -- Accepting call from '2177' to '7141278' on channel

Does anyone know of an American made option like the ISDN Guard? I'm looking for something that will listen for a heartbeat from Asterisk and if it fails, flip the PRIs over to a backup box.

Hi Josua, Sorry for writing wrong the parameter but i just copy paste the examples on pjsip.conf it wasn?t a "typo? error of timers parameters, i have an error on global tag and can?t load the timers I was getting this : [Apr 29 17:21:49] WARNING[16144]: config.c:1796 process_text_line: parse error: No category context for line 631 of /etc/asterisk/pjsip.conf after fix global issue

I have Asterisk running on a Ubuntu 18.0.4 on Digital Ocean. Every so often asterisk crashes and then restarts. I am not seeing any core dumps on the box. The only I thing I see every time is a second before Asterisk crashes there is a AAAA lookup for the boxes hostname. As soon as it gets the response I see that asterisk is restarting. Any idea what would cause this and how would get a dump or

The Asterisk Development Team would like to announce the release of asterisk-18.21.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/18.21.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!

The Asterisk Development Team would like to announce the release of asterisk-18.21.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/18.21.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!

The Asterisk Development Team would like to announce the release of asterisk-20.6.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/20.6.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!

The Asterisk Development Team would like to announce the release of asterisk-20.6.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/20.6.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!