Summary:	ASTERISK-14218: AEL Macro Records [s] for DST in CDR
Reporter:	Leo Brown (netfuse)	Labels:
Date Opened:	2009-05-28 12:14:35	Date Closed:	2011-06-07 14:07:58
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	PBX/pbx_ael
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	If Macros are used to dial in AEL2, the DST field is not correctly set. ****** ADDITIONAL INFORMATION ****** This is essentially a rehash of https://issues.asterisk.org/view.php?id=1141 The fact that AEL2 doesnt actually *use* macros means that the problem has reoccurred.
Comments:	By: Steve Murphy (murf) 2009-05-28 12:34:47 I'm assuming that by "SVN", you are using trunk, which means that AEL is using gosub instead of macro to implement an AEL "macro". Are you saying that if you extensions.conf, and call the "Macro" app to execute a macro, that you are getting different CDR results than you would get if you use extensions.conf, and use the "Gosub" app to do the same thing? Or are you saying that AEL's use of Gosub yields different CDR results than if you extensions.conf to call Gosub? Is this a problem with AEL, or a difference between Gosub and Macro? By: Leo Brown (netfuse) 2009-05-29 05:38:22 Very good question! Surely we have to see AEL as an emulator of extensions.conf. It provides Macro, While, all the features from extensions.conf - but While() is implemented using Goto(), Macro() is implemented using Gosub() etc. This was to work around restrictions of existing features. If it was a valid wish to have Macro() in extensions.conf to preserve CDR, surely the same should be expected of Macro() in extensions.ael? If you disagree, that's fine, I already have another approach I could use - but this seems like an unfortunate side-effect of the GoSub() implementation of Macro(). By: Leif Madsen (lmadsen) 2009-09-14 12:40:43 This is an unfortunate side-effect of using GoSub, but at this time, this is the expected behaviour.