something like an extra table translating custom codes to hangup causes and sip causes?<br><br>customcode => { hangcause => YYY, sipcause => 891, pricause => YYY }<br><br>why not. it would have to work in the other direction too. so that sipcause 891 translates to customcode. same for YYY. collisions might be tricky.<br>
<br><div class="gmail_quote">On Fri, Sep 11, 2009 at 12:35 PM, Olle E. Johansson <span dir="ltr"><<a href="mailto:oej@edvina.net">oej@edvina.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
11 sep 2009 kl. 12.29 skrev Marcus Hunger:<br>
<div class="im"><br>
> I can't see how a little addon to chan_sip would break asterisk's<br>
> architecture. Though being a multi protocol platform, asterisk has a<br>
> lot of protocol specific features. None of them breaking the<br>
> concept. I do not suggest to replace asterisk's traditional cause<br>
> codes, but to add the possibility to set more specific protocol<br>
> specific codes when needed.<br>
><br>
> I still remember discussions about this and I also remember that I<br>
> was not the only one requesting that feature. Sorry for being so<br>
> persistent on this one.<br>
><br>
> Anyway. You suggested another approach to achieve that goal. Do you<br>
> think it's realistic? I am not sure if I understood it right, but<br>
> wouldn't custom codes break compatibility with other channel drivers?<br>
<br>
</div>Well, we need to sort that out, it was an idea. If you're sending<br>
something unexpected to chan_sip we might behave the same way across<br>
board...<br>
<br>
Or have a translation table saying "I really mean this for other<br>
channels" so you do hangup(customcode) in the dialplan and we'll send<br>
891 to chan_sip and ISDN cause YYY to the rest of the bunch.<br>
That way, you have one cause to set in the dialplan, not one for every<br>
channel you use.<br>
<div><div></div><div class="h5"><br>
/O<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>
AstriCon 2009 - October 13 - 15 Phoenix, Arizona<br>
Register Now: <a href="http://www.astricon.net" target="_blank">http://www.astricon.net</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>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Dipl.-Inf. (FH)<br>Marcus Hunger - <a href="mailto:hunger@sipgate.de">hunger@sipgate.de</a><br>Telefon: +49 (0)211-63 55 55-61<br>Telefax: +49 (0)211-63 55 55-22<br>
<br>sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf<br>HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois<br>Steuernummer: 106 / 5724 / 7147, Umsatzsteuer-ID: DE219349391<br><br><a href="http://www.sipgate.de">www.sipgate.de</a> - <a href="http://www.sipgate.at">www.sipgate.at</a> - <a href="http://www.sipgate.co.uk">www.sipgate.co.uk</a><br>