[asterisk-dev] Detailed SIP disconnect reason

CDR venefax at gmail.com
Mon Feb 22 17:08:27 CST 2010


I support to export the disconect reason in a variable, in numeric form, so
we may send it back to the caller. Right now, if the second leg returns a
"bad number" or any other message, we cannot convey such information to the
caller.
Philip

On Mon, Feb 22, 2010 at 5:54 PM, Kirill 'Big K' Katsnelson <
kkm at adaptiveai.com> wrote:

> From looking at the code, I do not think such a feature exists. If I am
> missing anything, please correct me. If not, them my question is how to
> implement that so it would be of interest to a wider audience.
>
> I need to know in the dialplan why (narrowly, a SIP) call was disconnected.
> In particular, immediately I want to distinguish a disconnection from RTP
> timeout or SIP session timer from another cause. But, more generally, if I
> were to create such a feature, I would also include other indications such
> as e. g. which party has issued a BYE.
>
> So, if I am implementing that,
>
> 1. Is that thing of a common interest and may go into the trunk as a new
> feature?
>
> 2. What is a better way to report that to the dialplan:
>   a - set a channel variable
>   b - report that through the CHANNEL() function.
>   c - other?
>
> Thanks,
>
>  -kkm
>
> --
> _____________________________________________________________________
> -- 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/20100222/e8896f0a/attachment.htm 


More information about the asterisk-dev mailing list