[asterisk-dev] [Asterisk 0014810]: [patch] channel-specific hangupcauses

[Marcus Hunger]

I can't see how a little addon to chan_sip would break asterisk's
architecture. Though being a multi protocol platform, asterisk has a lot of
protocol specific features. None of them breaking the concept. I do not
suggest to replace asterisk's traditional cause codes, but to add the
possibility to set more specific protocol specific codes when needed.

I still remember discussions about this and I also remember that I was not
the only one requesting that feature. Sorry for being so persistent on this
one.

Anyway. You suggested another approach to achieve that goal. Do you think
it's realistic? I am not sure if I understood it right, but wouldn't custom
codes break compatibility with other channel drivers?

Marcus

On Fri, Sep 11, 2009 at 11:29 AM, Olle E. Johansson <oej at edvina.net> wrote:

>
> 11 sep 2009 kl. 11.10 skrev Marcus Hunger:
>
> > Unfortunately, 13140 does not allow the user to set it's sip-hangup-
> > cause in the dialplan, nor does it pass the original hangupcause to
> > the master-chansip.
> >
> > Do you think, it would be a good idea to create a patch so that
> > chansip uses SIP_CAUSE to generate a cause for a hangup?
>
> It would certainly break most of Asterisk's architecture, make CDRs
> hard to parse and cause havoc in the internal bridges.
>
> Do remember that we're a multiprotocol platform. The cause codes needs
> to correlate. You can't set one cause code in a channel driver and
> have a totally different one in the bridge to the other side, which
> might use a totally different channel driver.
>
> What we can do is open up the translation tables between SIP and ISDN
> causes and add some custom codes that you can configure for your own
> use. That would be a bit more clever approach.
>
> Sorry for being harsh, but this has been discussed many times and I am
> still afraid of opening up this pandora's box. The multiprotocol
> architecture is a foundation for Asterisk's success story. If we start
> breaking it apart by allowing too much protocol specific stuff into
> the core, like the dialplan, we're not multiprotocol any more. There
> are many platforms out there that are single protocol. Many of them
> being replaced with a multiprotocol engine like Asterisk ;-)
>
> /O
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> AstriCon 2009 - October 13 - 15 Phoenix, Arizona
> Register Now: http://www.astricon.net
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>



-- 
Dipl.-Inf. (FH)
Marcus Hunger - hunger at sipgate.de
Telefon: +49 (0)211-63 55 55-61
Telefax: +49 (0)211-63 55 55-22

sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf
HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois
Steuernummer: 106 / 5724 / 7147, Umsatzsteuer-ID: DE219349391

www.sipgate.de - www.sipgate.at - www.sipgate.co.uk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20090911/e780b6d4/attachment.htm