[asterisk-bugs] [Asterisk 0013502]: Arbitrarily set the release cause on an inbound h.323 channel

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13502 
====================================================================== 
Reported By:                davidcsi
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13502
Category:                   Channels/chan_h323
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.21.2 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-09-17 07:54 CDT
Last Modified:              2008-10-14 11:50 CDT
====================================================================== 
Summary:                    Arbitrarily set the release cause on an inbound
h.323 channel
Description: 
Hello,

    IMHO, it is necessary to be able to set the release cause on an
inbound h.323 channel. I'm working with 1.4.21.2 and I can't do that. Most
carriers want you to send them a 34 (no circuit available) on all but
answered/busy calls so they can re-route the call. It is imperative to be
able to do this, even if it is hardcoded.

david
====================================================================== 

---------------------------------------------------------------------- 
 (0093614) blitzrage (administrator) - 2008-10-14 11:50
 http://bugs.digium.com/view.php?id=13502#c93614 
---------------------------------------------------------------------- 
Unfortunately, without a patch associated with this issue, there is
practically no chance of this issue moving forward as there are so few
people actively developing on H.323. If you are able to supply a patch for
this, please reopen. But since this is a feature request (which are not
supported on the bug tracker; please use the other open forums for this),
and with the likelyhood of this issue becoming stale, I'm going to close
this as suspended for now. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-14 11:50 blitzrage      Note Added: 0093614                          
======================================================================