[asterisk-dev] Re: FastAGI behaviour in trunk changed recently?
Alistair Cunningham
acunningham at integrics.com
Thu Jul 27 01:51:13 MST 2006
Russell,
If the call has hung up when the AGI is invoked, that would certainly
explain it, but where shows you it has? As far as I can tell the call is
still active at this point. Am I being blind?
Alistair Cunningham,
Integrics Ltd,
+44 20 799 39 799
sip:acunningham at integrics.com
http://integrics.com/
Russell Bryant wrote:
> On Tue, 2006-07-25 at 12:11 +0100, Alistair Cunningham wrote:
>> Here is an entire Asterisk console output. The Asterisk version is
>> SVN-trunk-r38187, checked out today.
>
> Thanks for following up.
>
>> [to-voiptalk]
>> exten => _X., 1, Set(CALLERID(number)=44${CALLERID(number):1})
>> exten => _00., 2, Dial(IAX2/voiptalk/${EXTEN:2})
>> exten => _0., 2, Dial(IAX2/voiptalk/44${EXTEN:1})
>> exten => _X., 2, Dial(IAX2/voiptalk/${EXTEN})
>> exten => _X., 3, Hangup
>> exten => h, 1, DeadAGI(agi://127.0.0.1/end)
>> exten => t, 1, Hangup
>
> I'm not sure what you expect to actually happen here. You are running
> the AGI on a channel that has already been hung up. Then, in the AGI,
> you are trying to set the context and extension to another extension for
> further processing? That doesn't make any sense to me and could never
> work, but perhaps I am misunderstanding the situation.
>
More information about the asterisk-dev
mailing list