[asterisk-bugs] [JIRA] (ASTERISK-20639) Dynamic hints are not properly initialized when the extension contains an underscore.

[Michael L. Young (JIRA)]

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

Michael L. Young commented on ASTERISK-20639:
---------------------------------------------

Rusty, I see in the code where it checks if the extension contains an underscore and if it does it will not evaluate the variables and global variables.

My question is whether or not that check should be removed or not, or, if it should be only checking that the extension doesn't start with the underscore.
                
> Dynamic hints are not properly initialized when the extension contains an underscore.
> -------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20639
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20639
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Configuration, Functions/func_odbc
>    Affects Versions: 1.8.14.1
>            Reporter: Steven T. Wheeler
>            Assignee: Steven T. Wheeler
>         Attachments: bugreport.txt
>
>
> We use dynamic hints with a func_odbc call to load the hints from a database.  However, when the extension contains an underscore the func_odbc call is not evaluated.
> Our hint context:
> {code}
> [blf]
> exten => _[+A-Za-z0-9*#].,hint,${READ_BLF_PHONE_LIST(${EXTEN})}
> {code}
> When we look up the hint for extension johnDoe we get something like:
> Hint: SIP/phoneA&SIP/phoneB
> But when we look up the hint for extension john_doe we get:
> Hint: ${READ_BLF_PHONE_LIST(${EXTEN})}
> As you can see the variables are not even being evaluated.  If there is any more information you need to debug this please let me know.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira