[asterisk-bugs] [JIRA] (ASTERISK-21916) Call hangs when FILTER function is used in dial plan

Michael L. Young (JIRA) noreply at issues.asterisk.org
Sun Jun 16 21:25:03 CDT 2013


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

Michael L. Young edited comment on ASTERISK-21916 at 6/16/13 9:24 PM:
----------------------------------------------------------------------

I tried to reproduce using the dial plan sample attached to this issue.  I was unable to reproduce the issue on 11.3 and on trunk.

I do not see the filter function being run in the debug logs.  Perhaps the levels need to be raised to 10 to get any information that could be of use.

If a deadlock is involved, we need the following.

Debugging deadlocks: Please select DEBUG_THREADS and DONT_OPTIMIZE in the Compiler Flags section of menuselect. Recompile and install Asterisk (i.e. make install).  This will then give you the console command "core show locks." When the symptoms of the deadlock present themselves again, please provide output of the deadlock via:

# asterisk -rx "core show locks" | tee /tmp/core-show-locks.txt
# gdb -se "asterisk" <pid of asterisk> | tee /tmp/backtrace.txt 
gdb> bt
gdb> bt full
gdb> thread apply all bt

Then attach the core-show-locks.txt and backtrace.txt files to this issue. Thanks!


                
      was (Author: elguero):
    I tried to reproduce using the dial plan sample attached this issue.  I was unable to reproduce on 11.3 and on trunk.

I do not see the filter function being run in the debug logs.  Perhaps the levels need to be raised to 10 to get any information that could be of use.

If a deadlock is involved, we need the following.

Debugging deadlocks: Please select DEBUG_THREADS and DONT_OPTIMIZE in the Compiler Flags section of menuselect. Recompile and install Asterisk (i.e. make install).  This will then give you the console command "core show locks." When the symptoms of the deadlock present themselves again, please provide output of the deadlock via:

# asterisk -rx "core show locks" | tee /tmp/core-show-locks.txt
# gdb -se "asterisk" <pid of asterisk> | tee /tmp/backtrace.txt 
gdb> bt
gdb> bt full
gdb> thread apply all bt

Then attach the core-show-locks.txt and backtrace.txt files to this issue. Thanks!


                  
> Call hangs when FILTER function is used in dial plan
> ----------------------------------------------------
>
>                 Key: ASTERISK-21916
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21916
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Functions/func_strings
>    Affects Versions: 11.4.0
>         Environment: Latest binaries of Asterisk 11.4.0 from Optware repository running on an Asus RT-n66u (Tomato USB based router, MIPS 74K V4.9) with firmware 3.0.0.4.270.25 (rmerlin variant) and Linux 2.6.22.19, installed on an ext3 partition on external HD
>            Reporter: Elizabeth Hudnott
>            Severity: Critical
>         Attachments: debug.log
>
>
> Whenever the FILTER function is used in the dial plan the call hangs.  No further dial plan steps get executed, ringing tone ceases, the call remains open until Asterisk is restarted and CPU utilization increases sharply.
> Simple dial plan extract to reproduce the problem:
> exten=>**4,1,Verbose(${FILTER(0-9,123)})
> same=>n,Hangup()
> This behaviour occurs consistently every time the extension is dialled from CSipSimple sofphone.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list