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

[Steven T. Wheeler (JIRA)]

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

Steven T. Wheeler commented on ASTERISK-20639:
----------------------------------------------

That patch fixes the issue for me.  What are the odds of getting it in the 1.8 branch?  Also, I would like to note that this isn't a minor bug as it frequently causes queue members to become unavailable and stop receiving calls which really upsets our end users.
                
> 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/PBX
>    Affects Versions: 1.8.14.1
>            Reporter: Steven T. Wheeler
>            Assignee: Steven T. Wheeler
>            Severity: Minor
>              Labels: dynamic, hints
>         Attachments: asterisk-20639-dynamic-hint-underscore.diff, 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