[asterisk-bugs] [JIRA] (ASTERISK-17164) [patch] if fastStart is enabled, Progress message is sent when it shouldn't

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221596#comment-221596 ] 

Matt Jordan commented on ASTERISK-17164:
----------------------------------------

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.

> [patch] if fastStart is enabled, Progress message is sent when it shouldn't
> ---------------------------------------------------------------------------
>
>                 Key: ASTERISK-17164
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17164
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Channels/chan_h323
>            Reporter: under
>            Severity: Minor
>         Attachments: 0018534.diff
>
>
> If fastStart is enabled, Asterisk sends H.323 Progress message immediately when incoming call arrives. H.323 Progress message contains media channel capabilities (RTP info: codec, port, IP address).
> After this some originating equipment "thinks" Asterisk has established a voice path to the called party (because Asterisk presents RTP info). But Asterisk might not have done this (for example no route configured in dialplan). After this Asterisk migh execute Hangup and send H.323 ReleaseComplete message. And after this originating party "thinks" : "This terminator (Asterisk) has established a voice path, but cleared the call. I won't try next route in my hunting table, because we had a voice path established.". 
> This is faulty situation because originating company has problems in delivering calls in this case.



--
This message was sent by Atlassian JIRA
(v6.2#6252)