Hello,
I'm new to the list so I hope I'm asking the question in the right
place. In our extensions.conf, we call an AGI script using the AGI command.
e.g.
exten => 11,1,Answer
exten => 11,2,Wait(0.5)
exten => 11,3,Playback(welcome1)
exten => 11,4,agi(agi://192.168.1.88/hello.agi?src=test|${C
Alex Hutton wrote:
> Hello,
>
> I'm new to the list so I hope I'm asking the question in the right
> place. In our extensions.conf, we call an AGI script using the AGI
> command.
>
> e.g.
>
> exten => 11,1,Answer
> exten => 11,2,Wait(0.5)
> exten => 11,3,Playback(welcome1)
> exten => 11,4,agi(a
How about agi debug on the CLI?
> Alex Hutton wrote:
> > Hello,
> >
> > I'm new to the list so I hope I'm asking the question in the right
> > place. In our extensions.conf, we call an AGI script using the AGI
> > command.
> >
> > e.g.
> >
> > exten => 11,1,Answer
> > exten => 11,2,Wait(0.5)
> >
Thanks for the replies. I have realised that I can catch the execution
after the agi statement (if it fails) in the h priority, which I then
use to play an error message to the caller.
As you suggested, I am setting a variable in the agi script so that the
h priority knows whether the agi scr
