This might not help, but you don't have to use different contexts when
using GoSub, here is an example: https://pastebin.com/ftwWwpKt
On 1/5/22 22:22, Dovid Bender wrote:
Steve,
I thought of this but that would mean I would need to add this to the
beginning of every context which I can do, b
On Wed, 5 Jan 2022, Dovid Bender wrote:
I thought of this but that would mean I would need to add this to the
beginning of every context which I can do, but I was trying to avoid.
Every extension in every context.
Or maybe get funky with a wildcard extension with priority = 1 and
starting al
Steve,
I thought of this but that would mean I would need to add this to the
beginning of every context which I can do, but I was trying to avoid.
On Wed, Jan 5, 2022 at 10:06 PM Steve Edwards
wrote:
> On Wed, 5 Jan 2022, Steve Edwards wrote:
>
> > same = n, set(LAS
On Wed, 5 Jan 2022, Steve Edwards wrote:
same = n, set(LAST-CONTEXT=${context}
Double damn. I munged the case on ${CONTEXT}. I give up for today :)
--
Thanks in advance,
-
Steve Edwards
On Wed, 5 Jan 2022, Steve Edwards wrote:
same = n, set(LAST-CONTEXT=${context}
Damn. forgot the closing parentheses :)
--
Thanks in advance,
-
Steve Edwards sedwa...@sedwards.com V
On Wed, 5 Jan 2022, Dovid Bender wrote:
I have a hangup handler that's added at the beginning of a call. It logs
all the call details. Using the CONTEXT variable I am always going to
get the context where the code is being ran and not the last context
that the caller is in. Is there any creati
Hi,
I have a hangup handler that's added at the beginning of a call. It logs
all the call details. Using the CONTEXT variable I am always going to get
the context where the code is being ran and not the last context that the
caller is in. Is there any creative way to get the last context at the ca
