Summary:	ASTERISK-04653: Callscreen function in app_dial not working
Reporter:	tgledhill (tgledhill)	Labels:
Date Opened:	2005-07-21 20:45:56	Date Closed:	2011-06-07 14:10:34
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Applications/app_dial
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	The callscreen function does not accept DTMF from the callee, instead it immediately plays vm-sorry.   exten => 555,1,Dial(SIP/cisco7970|35|mpA(beep))
Comments:	By: tgledhill (tgledhill) 2005-07-21 23:02:28 It's actually playing vm-sorry immediately after the callee message is played.  It accepts a digit if you press it during the play.  It doesn't seem to be 'waiting' after the message is played. By: Brian West (bkw918) 2005-07-22 00:02:32 It shows you how to use this in README.privacy Please re-read that and try again because  it takes a bit more than JUST the 'p' flag on dial if I recall correctly. /b By: recursion (recursion) 2005-07-22 01:54:26 I can reporduce this.  The modifiers for 'p' -  'n' and 'N' have no effect as well. I'm using the string that's "almost" exactly the same as in README.privacy: exten => 3,3,Dial(SIP/phone2|35|tmpA(beep)) By: recursion (recursion) 2005-07-22 02:10:09 Is it just me, or does it seem to be out of place to have all this TORTURE stuff in app_dial in the first place?  I would NEVER allow features like this in a business PBX.  Shouldn't this belong in addons or at least in it's own app? Now call screening I understand, but the rest of this stuff really clutters app_dial. By: Kevin P. Fleming (kpfleming) 2005-08-22 15:57:38 We aren't going to be able to move on this bug without a debug log and call trace to see what is happening, along with a description of what you are expecting to be happening. By: Michael Jerris (mikej) 2005-08-27 23:57:41 Unfortunately we can not debug this issue further without the requested information.  I am suspending the bug pending that information, please re-open when you have that ready to upload.