<br><br><div class="gmail_quote">2009/3/14 Vieri <span dir="ltr"><<a href="mailto:rentorbuy@yahoo.com">rentorbuy@yahoo.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
<br>
--- On Sat, 3/14/09, Olivier <<a href="mailto:oza-4h07@myamail.com">oza-4h07@myamail.com</a>> wrote:<br>
<br>
</div><div class="im">> > If I understand correctly, you're suggesting to<br>
> implement the h priority<br>
> > instructions (or a "hangup macro") to:<br>
> ><br>
> > 1) run a deadagi or a system() script to see if<br>
> someone has left a request<br>
> > (eg. in astdb) to call-back-when-avail<br>
> ><br>
> > 2) create a call file with, say:<br>
> > Channel: SIP/102<br>
> > and<br>
> > Context: internal<br>
> > Extension: 101<br>
> > Priority: 1<br>
> ><br>
> > Is that what you would do, more or less?<br>
><br>
><br>
> yes, that's exactly what I meant.<br>
> As I'm not too fluent in AEL scripting, I'm afraid<br>
> I can't easily be more<br>
> helpful but you eactly got what I suggested.<br>
><br>
> What would think of that ?<br>
> Would it fit for you ?<br>
<br>
</div>Thanks for the feedback but there are some things that would not work right:<br>
<br>
1) when 102 hangs up, the call file would try to reach 101</blockquote><div>yes but it can be done the other way if think 102 is very likely to be busy ...<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
but if 101 is busy, it may retry later (MaxRetries in call file)</blockquote><div>You can also set MaxRetries to 0 and strictly rely on the fact that extension 102 hangups ...<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
and finally reach it and send 101 to the context where it would then Dial(SIP/102). However, inthe meantime, 102 could have received or made another call and be busy again (and that would "irritate" the 101 user).</blockquote>
<div><br>So ?<br>When Telcos implement this service they limit retries in a 30mn time frame so that you're not called back at 2am, for intance.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
2) 102 may not necessarily be "on the phone" when 101 first tries to contact. The 102 extension could simply be off-line/Unavailable/unregistered, so the 102 user would never "hang up" (thus the hangup macro would never be executed).<br>
<br>
Anyway, I was hoping Asterisk already had a trick up its sleeve for this ;-) but I guess I'll have to implement a custom event listener and try to bridge extensions.<br>
<div><div></div><div class="h5"><br>
Thanks,<br>
<br>
Vieri<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</div></div></blockquote></div><br>