[asterisk-users] Asterisk as an IVR solution

[Douglas Garstang]

Well I can tell you that it makes a difficult programming environment, just a little more difficult. It means I can't implement a menu as a single reusable piece of code inside a macro. 


----- Original Message ----
From: Tilghman Lesher <tilghman at mail.jeffandtilghman.com>
To: Asterisk Users Mailing List - Non-Commercial Discussion <asterisk-users at lists.digium.com>
Sent: Thursday, July 10, 2008 6:07:36 PM
Subject: Re: [asterisk-users] Asterisk as an IVR solution

On Thursday 10 July 2008 19:13:50 Douglas Garstang wrote:
> It's a known problem.
>
> If you call Background() in a macro, then Asterisk will look for the
> extensions to jump to in the CALLING Macro/context and NOT the Macro that
> the Background() app was called in.

I wouldn't call it a known problem.  It works precisely as it was designed to
work.  It may not work the way that you want it to, but it works like a Macro:
an independent set of instructions, with substitution, that acts as if it were
invoked inline with the calling location.  That is why Background will match
in the context of the calling location: it acts like it never left that
original context (and, in a way, it really didn't).

Subroutines are a different beast, and they are available with the Gosub/
Return set of routines in app_stack.so.

-- 
Tilghman

_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080710/7daf0c5e/attachment.htm