[asterisk-bugs] [JIRA] (ASTERISK-19189) AEL Macro and AELSub functions do not pass EXTEN variable, breaking CDR destination field

[Joshua Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-19189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua Colp updated ASTERISK-19189:
-----------------------------------

    Affects Version/s: 13.18.4

> AEL Macro and AELSub functions do not pass EXTEN variable, breaking CDR destination field
> -----------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-19189
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19189
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: PBX/pbx_ael
>    Affects Versions: 1.8.8.1, 10.0.0, 13.18.4
>         Environment: OpenBSD 5.0
>            Reporter: Chris Cappuccio
>            Severity: Minor
>
> Ever since AEL's Macro facility was changed to use Gosub, instead of stack-based design, CDR destination column logging has been broken for calls which flow through AEL Macros.
> This appears to happen because Macro() no longer passes EXTEN. After Asterisk internally converts the Macro to Gosub, the EXTEN variable is set to ~~s~~ and that is recorded in the CDR destination field!
> I was unable to fix this by manually forcing the Macro to Set/MSet EXTEN/~~EXTEN~~ to the destination number. The CDRs would still log ~~s~~ as destination.
> My work-around is to change Macros to contexts with the old Macro statements inside the _XXX. => portion of the context. I use Gosub instead of Macro, use {$ARG} variables in the new context and an able to completely replicate the functionality of the original, stack-based Macro call. This produces proper CDR records because EXTEN gets preserved after Gosub.
> As a wrapper to the Macro call, AELSub suffers from the same problem.



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