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

[Elizabeth Hudnott (JIRA)]

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

Elizabeth Hudnott commented on ASTERISK-21916:
----------------------------------------------

Asterisk compiles on my system, just with important functionality missing, like SIP.  I shall re-examine things when I can find some free time, particularly with regard to seeing if I can insert some debug statements and then trigger a call using a call file on the binary compiled from source.
                
> 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
>            Assignee: 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:
> {noformat}
> exten=>**4,1,Verbose(${FILTER(0-9,123)})
> same=>n,Hangup()
> {noformat}
> 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