<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
Oh... and Background() should also be given the same treatment.<br>
<br>
<br>
On 07/14/2010 01:23 PM, Mark Murawski wrote:
<blockquote cite="mid:4C3DF297.8060504@intellasoft.net" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<font size="+1">Here's the current info for quick reference<br>
<br>
Dial()<br>
d: Allow the calling user to dial a 1 digit extension while
waiting<br>
for a call to be answered. Exit to that extension if it
exists in the<br>
current context, or the context defined in the
${EXITCONTEXT} variable,<br>
if it exists.<br>
<br>
When using Dial from AGI, ${EXITCONTEXT} only is used for digit
matching, and control returns to the agi script... so having any
extens defined in the exit context is pretty useless in this
case. What I'm proposing is moving EXITCONTEXT to an option
parameter such as d[([digits][@context])].<br>
<br>
The parameter would be optional to maintain backwards
compatibility.<br>
@context could be passed in which would be used instead of
EXITCONTEXT,<br>
and, digits could be passed in, to have a more dynamic use of
the digit inturruption.<br>
<br>
Since interruption specifically only matches on single digits,
something like d(149) would match on either digit 1, or 4, or
9.<br>
Specifying 149@context (when not using AGI), would match digits
1, 4, and 9 only in context.<br>
In non-AGI, If 149@context is given, and context exists, but the
matched digit-exten does not, it would handle this the same as
any other non-existent exten, either by the 'i' if it exists, or
fallthrough.<br>
If using agi, specifying 149@context would just match on 1,4,9,
and context wouldn't get used.<br>
<br>
I know there's a movement to stray away from applications acting
on the values of variables anyway, so I think this would
accomplish two things:<br>
</font>- Supporting more parameter based options.<br>
- Not needing to dynamically create extens,contexts from agi when
needs for digit interruption change.<br>
<br>
I'm planning on writing and contributing code to support this...
what does everyone think about this design?<br>
<br>
</blockquote>
</body>
</html>