Thanks yes I have seen this. Im not doing too much with CDR currently so it
shouldn't be too much of an issue.
I saw there are Park changes as its now no longer in features.conf. I wont move
to PJSIP yet.
I think I will wait for the 13 upgrade until I have some time to test (goodness
knows when that will be).
Thanks all.
Regards
Michael Knill
From: Michael Keuter <li...@mksolutions.info>
Reply-To: AstLinux List <astlinux-users@lists.sourceforge.net>
Date: Monday, 20 March 2017 at 9:58 am
To: AstLinux List <astlinux-users@lists.sourceforge.net>
Subject: Re: [Astlinux-users] Getting seg fault in Asterisk
It is explained here (CDR section):
https://wiki.asterisk.org/wiki/display/AST/New+in+12
Sent from a mobile device.
Michael Keuter
Am 19.03.2017 um 23:37 schrieb David Kerr
<da...@kerr.net<mailto:da...@kerr.net>>:
Re CDR in Asterisk 12+, it not just group calls... if you ring multiple
extensions on incoming calls you get a CDR entry for each not just the one that
picks up. It makes for a much more cluttered CDR file. I can find no way to
have more granular control over CDRs.
David
On Sun, Mar 19, 2017 at 6:17 PM, Michael Keuter
<li...@mksolutions.info<mailto:li...@mksolutions.info>> wrote:
> Am 19.03.2017 um 21:02 schrieb Michael Knill
> <michael.kn...@ipcsolutions.com.au<mailto:michael.kn...@ipcsolutions.com.au>>:
>
> Thanks Lonnie. I don't really know what triggers the crash but I think I need
> to upgrade anyway.
> I really need to go to 13 but I don't have the time to update my configs and
> test (
>
> Here’s hoping!
>
> Regards
> Michael Knill
There was a similar case a few years ago, where a faulty libxml2 triggered such
a crash.
BTW: If you use "group calls", there is a big change in how CDR works since the
new bridging framework in Ast 12.
That means every called channel of a group call triggers its own CDR event (in
11 it's only one) …
> -----Original Message-----
> From: Lonnie Abelbeck
> <li...@lonnie.abelbeck.com<mailto:li...@lonnie.abelbeck.com>>
> Reply-To: AstLinux List
> <astlinux-users@lists.sourceforge.net<mailto:astlinux-users@lists.sourceforge.net>>
> Date: Monday, 20 March 2017 at 6:38 am
> To: AstLinux List
> <astlinux-users@lists.sourceforge.net<mailto:astlinux-users@lists.sourceforge.net>>
> Subject: Re: [Astlinux-users] Getting seg fault in Asterisk
>
> Michael,
>
> I'd try Asterisk 11.25.1 first, your 11.23.1 has this Asterisk bug:
> --
> pbx.c: Crash in handle_hint_change due to uninitialized values
> http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=commit;h=7b4db45cb7aaa9c9569d8e7e7804ee28a805b8f4
> --
>
> AstLinux 1.2.9 contains Asterisk 11.25.1
>
> Lonnie
>
>
> On Mar 19, 2017, at 2:06 PM, Michael Knill
> <michael.kn...@ipcsolutions.com.au<mailto:michael.kn...@ipcsolutions.com.au>>
> wrote:
>
>> Whoops I didn't specify any versions. Overworked (
>>
>> APU1
>> astlinux-1.2.8 x86_64
>> Asterisk 11.23.1
>>
>> I do have this version deployed and I have not had any issues. I have
>> changed a little bit of configuration in the lab, namely Park in
>> features.conf.
>>
>> Do you think I should just go straight to 13 considering 11 is EOL in
>> October?
>>
>> Thanks
>>
>> Regards
>> Michael Knill
>>
>> -----Original Message-----
>> From: Michael Keuter <li...@mksolutions.info<mailto:li...@mksolutions.info>>
>> Reply-To: AstLinux List
>> <astlinux-users@lists.sourceforge.net<mailto:astlinux-users@lists.sourceforge.net>>
>> Date: Sunday, 19 March 2017 at 9:55 pm
>> To: AstLinux List
>> <astlinux-users@lists.sourceforge.net<mailto:astlinux-users@lists.sourceforge.net>>
>> Subject: Re: [Astlinux-users] Getting seg fault in Asterisk
>>
>>
>>> Am 19.03.2017 um 07:57 schrieb Michael Knill
>>> <michael.kn...@ipcsolutions.com.au<mailto:michael.kn...@ipcsolutions.com.au>>:
>>>
>>> Hi group
>>>
>>> I am starting to get seg faults intermittently in Asterisk when I am doing
>>> a reload:
>>>
>>> Mar 19 17:35:43 3999-IBCBuild-CM1 user.info<http://user.info> kernel:
>>> asterisk[1085]: segfault at 4b84 ip 00002b829fe71ef2 sp 00002b82d00f6cd0
>>> error 4 in libc-2.18.so<http://libc-2.18.so>[2b829fe01000+16e000]
>>>
>>> Has anyone else seen this? Do you think I should go to 13 now?
>>>
>>> Regards
>>> Michael Knill
>>
>> I have not seen these errors yet (I mostly use Jetway NF9HG-2930).
>>
>> Which Asterisk version, AstLinux version, Linux version, Board + firmware
>> version?
>>
>> Michael
Michael
http://www.mksolutions.info
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org<http://Slashdot.org>! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net<mailto:Astlinux-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org<mailto:pay...@krisk.org>.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org<http://Slashdot.org>! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net<mailto:Astlinux-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org<mailto:pay...@krisk.org>.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
