Mike Coakley wrote:
Chris,
Actually it is a documented feature of Macro. Macro only executes
extension s there are no other extensions in the macro context. I ran
into this while working through building our dial plan. It was driving
me nutz. (But the WIKI rescued me.) What I had to do is use
On Aug 11, 2004, at 9:45 AM, Christopher L. Wade wrote:
Mike Coakley wrote:
Chris,
Actually it is a documented feature of Macro. Macro only executes
extension s there are no other extensions in the macro context. I
ran into this while working through building our dial plan. It was
driving me
Mike Coakley wrote:
Anyone out there with * code experience that can put this question to bed.
Actually, it is in bed. Any 'user defined' extension will work inside a
macro. What won't work is any 'system' extension whose execution is
based on an 'exception', which AbsoluteTimeout and the 'T'
On Aug 11, 2004, at 12:04 PM, Christopher L. Wade wrote:
Mike Coakley wrote:
Anyone out there with * code experience that can put this question to
bed.
Actually, it is in bed. Any 'user defined' extension will work inside
a macro. What won't work is any 'system' extension whose execution is
Mike Coakley wrote:
Hmm... I couldn't get my Macro to work and your comments have me
thinking I'm stupid again. I think I'm going to setup another test bed
and wack the crap out of this one... next question to ask the
developers... why wouldn't they include the system extensions. That
would
Christopher L. Wade wrote:
Hi all,
Is it just me and not reading the docs right, or has anybody else had
problems with the AbsoluteTimeout application and the 'T' extension when
used inside a macro?
[macro-attended]
; ARG1 is the device to dial out on, SIP or Zap, or whatever
; ARG2 is the
For one thing it's 't' not 'T', just like invalid is 'i' not 'I'
-Chris
- Original Message -
From: Christopher L. Wade [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 10, 2004 10:03 AM
Subject: Re: [Asterisk-Users] AbsoluteTimeout Inside A Macro
Christopher L. Wade
-Users] AbsoluteTimeout Inside A Macro
Christopher L. Wade wrote:
Hi all,
Is it just me and not reading the docs right, or has anybody else had
problems with the AbsoluteTimeout application and the 'T' extension when
used inside a macro?
[macro-attended]
; ARG1 is the device to dial out
On Tue, 2004-08-10 at 13:11, Chris Shaw wrote:
For one thing it's 't' not 'T', just like invalid is 'i' not 'I'
-Chris
Christopher L. Wade wrote:
Hi all,
Is it just me and not reading the docs right, or has anybody else had
problems with the AbsoluteTimeout application
Josh Roberson wrote:
Absolute timeout is 'T', and your standard timeout is 't'. If he's
looking for absolute timeout, he is, indeed, looking for the T extension.
They are case sensitive, and should work.
Mr. Wade: Have you tried using the T extension outside of the macro?
Although it
Roberson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 10, 2004 10:32 AM
Subject: Re: [Asterisk-Users] AbsoluteTimeout Inside A Macro
Absolute timeout is 'T', and your standard timeout is 't'. If he's
looking for absolute timeout, he is, indeed, looking for the T extension
Interesting thing...
If I put my 'T' extension in the context that called the macro, yet put
the AbsoluteTimeout command inside the macro, my 'T' extension from
outside the macro gets called...
Is this a bug? (Or a feature?)
Thanks,
Chris
___
Chris Shaw wrote:
Hmm you're right, sorry about that...
Have you seen this comment in the wiki?
if you connect a client to a sip peer with the option canreinvite=yes, then
absolutetimeout command has no effect.
Is it happening in both SIP and ZAP or just SIP?
-Chris
Combination of SIP and ZAP,
PROTECTED] On Behalf Of Christopher
L. Wade
Sent: Tuesday, August 10, 2004 2:23 PM
To: [EMAIL PROTECTED]
Subject: Re: [Asterisk-Users] AbsoluteTimeout Inside A Macro
Interesting thing...
If I put my 'T' extension in the context that called the macro, yet put
the AbsoluteTimeout command inside
Sean Cheesman wrote:
I guess the question to ask is... Is the macro function designed to
execute one extension logic and then exit back to it's original context,
or is it designed to allow you to run multiple extension logics before
kicking back?
If I can do a Goto inside a macro, isn't that
Okay, time for an update.
I posted this as a bug. Very quickly got informed that it is not a bug,
but instead, an undocumented 'feature'.
AbsoluteTimeout is treated as an *exception* (ie it looks like a hangup)
by most applications, including Macro, which makes most applications exit.
This
Chris,
Actually it is a documented feature of Macro. Macro only executes
extension s there are no other extensions in the macro context. I ran
into this while working through building our dial plan. It was driving
me nutz. (But the WIKI rescued me.) What I had to do is use the Macro
to setup
Hi all,
Is it just me and not reading the docs right, or has anybody else had
problems with the AbsoluteTimeout application and the 'T' extension when
used inside a macro?
[macro-attended]
; ARG1 is the device to dial out on, SIP or Zap, or whatever
; ARG2 is the extension to dial using
18 matches
Mail list logo
