[asterisk-dev] Unified Asterisk Interface

[David Roden]

On Tuesday 11 December 2007 18:29:24 Tzafrir Cohen wrote:

> > 1. Setup an extension (say, "dialout") that executes AGI(agi://host/out).
> > 2. Setup an extension ("control") that executes AGI(agi://host/control).
> Why aren't those already set up in advance in the dialplan?

They are, that's what I meant below.


> Also: what is the "control" AGI for? Shouldn't you use AMI for
> controling other channels?

When I trigger a call to a local channel the other end has to connect 
somewhere as well. I can't leave it dangling around so I connect it to my 
server as well and simply wait for the call to be over.

Actually I could probably skip that line and simple call the local channel so 
that it executes the AGI command directly. That doesn't really simplify 
anything though. :)


> > (Okay, actually 1 and 2 only have to be done once.)
> (After reload?)

No, after installation. Those lines go indeed into the dialplan.


> I get the impression that you actually try not to touch the user's
> dialplan at all costs.

Precisely. Because we are using different PBX backends I can not put 
functionality of the application into the dialplan.


	David
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.digium.com/pipermail/asterisk-dev/attachments/20071212/731a42c2/attachment.pgp