[asterisk-dev] Congestion parameter to RINGNOANSWER in queue_log & ami event

[Tim Ringenbach]

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.

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.

2010/6/8 Håkon Nessjøen <haakon at avelia.no>

> Hi,
>
> Just noticed that this issue (patch) has been lying around for a while now.
>
> Anyone have anything to say about this patch? Ideas, problems, tests?
>
> https://issues.asterisk.org/view.php?id=16925
>
> Regards,
> Håkon
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20100608/cc94a94a/attachment.htm