[asterisk-bugs] [JIRA] (ASTERISK-25348) Asterisk Crashes after caller records name with the Privacy Options

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-25348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227372#comment-227372 ] 

Asterisk Team commented on ASTERISK-25348:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> Asterisk Crashes after caller records name with the Privacy Options
> -------------------------------------------------------------------
>
>                 Key: ASTERISK-25348
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25348
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_dial, Applications/app_privacy
>    Affects Versions: 12.8.0, 12.8.1
>         Environment: Centos 6.6.
> Hosted on Amazon EC2
> Asterisk 12.8 with FreePBX12
>            Reporter: Pramod Venugopal
>
> Every so often, when a call comes in to an account with Privacy Screening, after the caller records their name, the phone rings and is answered. When the recorded caller name is played to the user, asterisk crashes. 
> The log /var/log/asterisk/full shows around 1.6million lines for that call with the following:
> "[2015-08-26 09:13:38] ERROR[18320][C-00000469] astobj2.c: bad magic number for object 0x7fd1acb994e8. Object is likely destroyed."
> Just prior to this are the following lines:
> [2015-08-26 09:13:20] VERBOSE[18320][C-00000469] app_dial.c:     -- SIP/709-00000605 is ringing
> [2015-08-26 09:13:25] VERBOSE[18320][C-00000469] app_dial.c:     -- SIP/709-00000605 answered SIP/from-trunk-00000604
> [2015-08-26 09:13:25] VERBOSE[18320][C-00000469] file.c:     -- <SIP/709-00000605> Playing 'priv-callpending.ulaw' (language 'en')
> [2015-08-26 09:13:30] VERBOSE[18320][C-00000469] file.c:     -- <SIP/709-00000605> Playing 'priv-callerintros/2066337888.slin' (language 'en')
> [2015-08-26 09:13:31] VERBOSE[18320][C-00000469] file.c:     -- <SIP/709-00000605> Playing 'screen-callee-options.ulaw' (language 'en')
> I have the full call log ( without the 1.6 million astobj2.c ). I also have a backtrace setup , but since I am using the official RPM, its not built with DONT_OPTIMIZE.



--
This message was sent by Atlassian JIRA
(v6.2#6252)