[Home]

Summary:ASTERISK-12048: [patch] enable chan_h323 to bind addr 0.0.0.0
Reporter:ddkprog (ddkprog)Labels:
Date Opened:2008-05-19 14:22:58Date Closed:2014-08-12 11:18:21
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_h323
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) channel.h323.bindaddr_v2.diff
( 1) channel.h323.bindaddr.diff
( 2) channels_h323_v3.diff
( 3) channels_h323.patch
( 4) channels.h323.patch
Description:this patch enable to bind address 0.0.0.0 as default

>; The NuFone Network's
>; Open H.323 driver configuration
>;
>[general]
>port = 1720
>;bindaddr = 1.2.3.4     ; this SHALL contain a single, valid IP address for
bindaddr = 0.0.0.0
Comments:By: Russell Bryant (russell) 2008-06-03 14:30:09

Feel free to reopen this issue once you get the license issue resolved.
By: ddkprog (ddkprog) 2010-05-31 15:59:55

plz, reopen the issue and recheck the license
By: ddkprog (ddkprog) 2010-06-07 00:55:58

the patch updated for svn trunk
By: under (under) 2010-06-11 16:29:25

AFAIK, Asterisk without modifications already binds to 0.0.0.0:1720 successfully
By: ddkprog (ddkprog) 2010-06-11 17:01:50

>under
My patch corrects the TCS Facility
after my patch can write in your config bindaddr = 0.0.0.0
and RTP will work correctly if TCS will come from another network
By: ddkprog (ddkprog) 2010-06-23 09:48:11

yeh, thx for reopen and relation with https://issues.asterisk.org/view.php?id=17454
this is same issue
but i am sure, that my patch is more correct

plz, update summary
0012685: [patch] enable chan_h323 to bind addr 0.0.0.0 to allow correct create RTP stream with TCS facility with more network direction
not the one network as chan_h323 to create by default (binding by single IP)
By: Leif Madsen (lmadsen) 2010-06-23 11:37:47

That summary update is too long and does not make any sense to me.
By: Matt Jordan (mjordan) 2014-08-12 11:18:12.961-0500

Unfortunately, {{chan_h323}} has been unsupported for a long time and was marked deprecated. Due to there being a supported replacement channel driver, {{chan_ooh323}}, {{chan_h323}} was removed from the Asterisk source tree in Asterisk 13:

http://lists.digium.com/pipermail/asterisk-dev/2014-June/068363.html

As such, this issue will be closed out as "Won't Fix". I recognize that this issue has been open for a long time, and as a project, we're sorry that the patch attached this issue didn't receive more attention. We've made some changes in the way the patch process works to try and alleviate the issue of patches not receiving attention; for more information, see [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process] on the Asterisk wiki. If you still need H323 support and are using Asterisk, I'd recommend switching to {{chan_ooh323}}, as it has a dedicated module maintainer who can help with patches to that channel driver.