Not the patches fault, but the RingNoAnswer name is kind of misleading because you get that event if the call fails in any way, not just what Dial would return NOANSWER for.<br><br>It would be nice to know both if the call timed out (in my mind, a real no answer), or if failed some other way, which I think is what this patch does. But I think it would be good to include the hangup cause too and not just a boolean.<br>
<br><div class="gmail_quote">2010/6/8 Håkon Nessjøen <span dir="ltr"><<a href="mailto:haakon@avelia.no">haakon@avelia.no</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;">
Hi,<br><br>Just noticed that this issue (patch) has been lying around for a while now.<br><br>Anyone have anything to say about this patch? Ideas, problems, tests?<br><br><a href="https://issues.asterisk.org/view.php?id=16925" target="_blank">https://issues.asterisk.org/view.php?id=16925</a><br>
<br>Regards,<br><font color="#888888">Håkon<br>
</font><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-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br></blockquote></div><br>