|Summary:||ASTERISK-00532: Events in dialplan|
|Reporter:||Paul Cadach (pcadach)||Labels:|
|Date Opened:||2003-11-16 12:13:00.000-0600||Date Closed:||2011-06-07 14:05:06|
|Environment:||Attachments:||( 0) app_event.c|
|Description:||Many features requires to perform some actions on some events. For example, you need to enable call monitoring (recording) when call is answered, so, you need handling "OnAnswer" event, and, to cleanup monitoring, you need to handle "OnHangup" event. Other events may be needed by others.|
****** ADDITIONAL INFORMATION ******
OnAnswer and OnHangup events are related to Dial application only. Also, those events can be available when "hidden" dial is executed (for example, at queue handling).
Event handlers must be configurable for each sort of Dial application (by local/global variables with context which will be "called" when such event is appeared?).
|Comments:||By: Brian West (bkw918) 2003-11-16 15:44:33.000-0600|
Their is one problem with that.. OnHangup for example is doen via exten => h but h will not be called if you say park the call then pick it back up.. you are flipping the call direction when you do that. Or thats how it was explained to me.
By: Anthony Minessale (anthm) 2004-03-19 17:11:56.000-0600
Waddya know...... I made this app_event
exten => s,1,Event(Event=MyEvent|Info=cool|Size=12)
By: Paul Cadach (pcadach) 2004-03-19 22:28:18.000-0600
Anthony, the decision for events was to provide some sort of interface to catch and handle internal call events (answer, transfer, hangup, busy, etc.) rather than to send messages to manager interface.
By: twisted (twisted) 2004-04-29 08:46:31
HouseKeeping - I believe these requests have been answered through other apps. Monitoring does have a cleanup operation now, and if that's not good enough, there is a patch out there that will do exactly what you want. see ASTERISK-1261 for details.