On 7/9/07, <b class="gmail_sendername">Daniel Gradecak</b> <<a href="mailto:daniel@gradecak.com">daniel@gradecak.com</a>> wrote:<div><span class="gmail_quote"></span><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
are you sure the monitor is started and sotoped via the dialplan ?</blockquote><div><br><br>If you're using Monitor() or MixMonitor(), then just add a UserEvent() call just before it in the dialplan.<br><br>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)
<br><br>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.
<br></div></div><br>-- <br>j.