[asterisk-bugs] [JIRA] (ASTERISK-29486) Hint-like extension value lookup function without device state

[George Joseph (JIRA)]

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

George Joseph commented on ASTERISK-29486:
------------------------------------------

bq. So this would be a function that essentially executes dialplan at that point, no? I'm not sure what other implications might arise from that, but it's not compartmentalized like LOOKUP is. (Simple explanation: in the CLI, you don't see what LOOKUP is doing, as it's a function, and that's how functions work... but CALL_SUB spawns dialplan, which seems like new territory).

Sorry.  I just meant that as an aside.  You'd mentioned "since it locks into the GoSub framework of returning something at priority 1" and I was clarifying that Gosub isn't limited to starting at priority 1 and will return whatever you put in a Return().

bq.  I am not sure why calling LOOKUP would be any different for Lua/AEL than any other function, such as calling SHELL or CURL directly. I guess "execution" could mean different things but LOOKUP is certainly not limited to returning "simple values", as the examples above show.

Lua or AEL _using_ LOOKUP should be just fine.  I was thinking of calling _into_  Lua or AEL from LOOKUP, not the other way around.  This works for AEL but not for Lua since Lua expects to execute commands.  Probably not a big issue.




> Hint-like extension value lookup function without device state
> --------------------------------------------------------------
>
>                 Key: ASTERISK-29486
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29486
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Functions/NewFeature
>    Affects Versions: 18.4.0
>            Reporter: N A
>            Assignee: N A
>
> This is a new function that works like the HINT function, only a separate priority is used so that device state overhead is not added. This can provide a mechanism for a fast, efficient, and clean extension value lookup in the dialplan using native core extension pattern matching capabilities to retrieve extension values, including substituting variables.



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