[Asterisk-Dev] Manager proposal

[Daniel Montejo Biosca]

Hi,
In all cti middlewares the hold event and unhold event are two independent 
events. The most standar method is use two methods for that. I think that 
asterisk must become a PBX with a cti connector the most similar to other 
standars. For that I think that all events and methods must be the most 
similar to the other standars. That's my opinion.



>From: "Olle E. Johansson" <oej at edvina.net>
>Reply-To: Asterisk Developers Mailing List <asterisk-dev at lists.digium.com>
>To: Asterisk Developers Mailing List <asterisk-dev at lists.digium.com>
>Subject: [Asterisk-Dev] Manager proposal
>Date: Wed, 04 May 2005 16:29:43 +0200
>
>I see a lot of managare events named "Hold" and "Unhold", "ParkedCall", 
>"UnParkedCall".
>
>I would like to have *one* event name, say "Hold"
>and then an additional paramater signalling the state, like
>
>Event: Hold
>Holdstatus: On | Off
>
>Event: ParkedCall
>PCstatus: Parked | Unparked | GivingUp
>
>Does that make any sense?
>
>For me, it would be much easier writing a parser... We do this in the
>channel with registration status - one event name, then different status 
>lines marking the current status.
>
>/O
>_______________________________________________
>Asterisk-Dev mailing list
>Asterisk-Dev at lists.digium.com
>http://lists.digium.com/mailman/listinfo/asterisk-dev
>To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev

_________________________________________________________________
Móviles, DVD, cámaras digitales, coleccionismo... Con unas ofertas que ni te 
imaginas. http://www.msn.es/Subastas/