Summary:ASTERISK-20465: Updates to make work with latest SVN revisions + T.38 support + interoperability improvements + bugfixes
Reporter:Denis Kochmashev (kochmashev)Labels:
Date Opened:2012-09-24 09:03:04Date Closed:2014-08-12 11:20:10
Versions:SVN Frequency of
is related toASTERISK-17180 [patch] [new feature] support for T.38 pass-through
Description:Ported to Asterisk SVN trunk (r373402 for the moment of writing).

Support for using PTLib/H323Plus was added. Usage of PWLib and OpenH323 is no longer supported cause these projects are dead for at least 5 years.

T.38 support based on this patch (ASTERISK-17180) was added.

Interoperability with Avaya Communication Manager was improved:
1. ACM, when set to use DTMF over IP: rtp-payload, doesn't include receiveRTPAudioTelephonyEventCapability in it's TCS. If chan_h323 detects ACM on the other side it will try to use DTMF transport as set in dtmfmode config option.
2. When H.245 channel must be openned via separate TCP connection ACM reports h245Address too early (before it is ready to accept incoming TCP connection). If remote endpoint is Avaya Communication Manager, delay opening H.245 channel (processing h245Address) for 1 second.

Processing of progress_setup and progress_alert configuration options was corrected. ITU-T recommendation Q.931 05/98 specifies 6 different values for Progress Description (1,2,3,4,5,8) though previous code allowed to use only 3 of them (1,3 and 8).
Comments:By: Matt Jordan (mjordan) 2014-08-12 11:20:04.928-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:


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.