Summary:	ASTERISK-15386: call answer macro not being called in cmd Dial
Reporter:	Abeer (zzabeerss)	Labels:
Date Opened:	2010-01-01 10:18:42.000-0600	Date Closed:	2011-06-07 14:08:15
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_dahdi
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	When i do this "exten => s,n,Dial(${QDIALER_CHANNEL},30,gM(queuedial-answer^${UNIQUEID}^${GM}^${QDIALER_QUEUE}^${QDIALER_AGENT}^${ST}))" queuedial-answer macro is called when call is answered But when i do this "exten => s,n,Dial(${QDIALER_CHANNEL},30,gRMT(queuedial-answer^${UNIQUEID}^${GM}^${QDIALER_QUEUE}^${QDIALER_AGENT}^${ST}))" Note: RT parameters the queuedial-answer macro is not called when the call is answered.
Comments:	By: Leif Madsen (lmadsen) 2010-01-04 10:20:41.000-0600 I don't have an "R" option on my version, so not sure what that is. Can you try with just the "T" option, and then without the "T" option? I have a feeling it is causing the channel to be bridged before the Macro() can be triggered. Perhaps something needs to be flipped around in the order to cause the Macro() to be triggered before the bridging for the "T" happens -- although I'm entirely speculating. By: Abeer (zzabeerss) 2010-01-05 03:09:14.000-0600 it doesn't work with "T". gM (Works) gMR (doesn't Work) gMT (doesn't Work) By: Leif Madsen (lmadsen) 2010-01-05 08:50:50.000-0600 I'd still like to know what 'R' is By: Abeer (zzabeerss) 2010-01-05 09:08:20.000-0600 R: Indicate ringing to the calling party when the called party indicates ringing, pass no audio until answered. This is available only if you are using kapejod's Bristuff. Reference: http://www.voip-info.org/wiki/view/Asterisk+cmd+Dial By: Abeer (zzabeerss) 2010-01-05 09:09:12.000-0600 Please also check this: http://www.voip-info.org/wiki/view/Bristuff I didn't do any patch thou By: Leif Madsen (lmadsen) 2010-01-05 13:21:40.000-0600 We are interested in solving the problem, but if you can reproduce this issue without the BRIstuff patch set (i.e. vanilla Asterisk) and the latest version of Asterisk, then please open a new issue, otherwise, there isn't anything we can do to support these third-party changes.