James FitzGibbon wrote: > On 7/9/07, *Daniel Gradecak* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > are you sure the monitor is started and sotoped via the dialplan ? > > > > If you're using Monitor() or MixMonitor(), then just add a UserEvent() > call just before it in the dialplan. > > If you're doing monitoring of queues, it's a bit trickier - you have > to watch for Join events to see what calls are being enqueued, then > when you see a Link event for that call, you can assume (based on > local policy) that the monitoring has started (assuming there was no > Leave event in the meantime - the logic in your AMI client has to > match the logic in your dialplan that deals with queues obviously) > > If you're talking about automon, there's no support for that, but a > cursory examination of the code doesn't show any reason why it > couldn't be added. Look at builtin_automonitor() in res_features.c. > > -- > j. > ------------------------------------------------------------------------ > > _______________________________________________ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users Adding a call to manager_event() in res_monitor.c and rebuilding asterisk is a trivial mod to get the result you desire.
_______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
