<br><br><div class="gmail_quote">On Thu, Jul 10, 2008 at 9:07 PM, Tilghman Lesher <<a href="mailto:tilghman@mail.jeffandtilghman.com">tilghman@mail.jeffandtilghman.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Thursday 10 July 2008 19:13:50 Douglas Garstang wrote:<br>
> It's a known problem.<br>
><br>
> If you call Background() in a macro, then Asterisk will look for the<br>
> extensions to jump to in the CALLING Macro/context and NOT the Macro that<br>
> the Background() app was called in.<br>
<br>
</div>I wouldn't call it a known problem. It works precisely as it was designed to<br>
work. It may not work the way that you want it to, but it works like a Macro:<br>
an independent set of instructions, with substitution, that acts as if it were<br>
invoked inline with the calling location. That is why Background will match<br>
in the context of the calling location: it acts like it never left that<br>
original context (and, in a way, it really didn't).<br>
<br>
Subroutines are a different beast, and they are available with the Gosub/<br>
Return set of routines in app_stack.so.<br>
<br>
--<br>
<font color="#888888">Tilghman</font></blockquote><div><br><br>See this thread for info on who paid for ExternalIVR, who uses(used?) it and some history.<br></div><div><a href="http://www.asteriskguru.com/archives/image-vp255203.html">http://www.asteriskguru.com/archives/image-vp255203.html</a><br>
</div></div><br><br>Thanks,<br>Steve Totaro<br>