[asterisk-bugs] [JIRA] Updated: (ASTERISK-20465) Numerous updates to make work with latest SVN revisions + T.38 support

[Richard Mudgett (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-20465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Mudgett updated ASTERISK-20465:
---------------------------------------

    Description: 
Ported to Asterisk SVN trunk (r373402 for the moment of writing).

Support for using PTLib/H323Plus was added. Using 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. 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.

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).


  was:
Ported to Asterisk SVN trunk (r373402 for the moment of writing).

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

T.38 support based on this patch (http://issues.asterisk.org/jira/browse/ASTERISK-17180) was added.

Interoperability with Avaya Communication Manager was improved. 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.

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).



> Numerous updates to make work with latest SVN revisions + T.38 support
> ----------------------------------------------------------------------
>
>                 Key: ASTERISK-20465
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20465
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Channels/chan_h323
>    Affects Versions: SVN
>            Reporter: Denis Kochmashev
>         Attachments: asterisk-svn-chan_h323.tar.bz2
>
>
> Ported to Asterisk SVN trunk (r373402 for the moment of writing).
> Support for using PTLib/H323Plus was added. Using 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. 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.
> 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).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira