[asterisk-bugs] [JIRA] (ASTERISK-30267) ooh323 plugin is out of date with Asterisk
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Tue Oct 18 09:07:09 CDT 2022
[ https://issues.asterisk.org/jira/browse/ASTERISK-30267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260464#comment-260464 ]
Asterisk Team commented on ASTERISK-30267:
------------------------------------------
Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.
A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.
Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.
Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].
> ooh323 plugin is out of date with Asterisk
> ------------------------------------------
>
> Key: ASTERISK-30267
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-30267
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Addons/chan_ooh323
> Affects Versions: 16.15.0
> Environment: SIP Client <-> Asterisk/ooh323 <-> GnuGk <-> H323 Client (ITU version > 2005).
> Remark : H323 client configuration is not modifiable for "transportCapability" parameters; this client is based on a previous H323 ITU standard of 2005
> Reporter: Benoît BERTHONNEAU
> Severity: Major
>
> *+Steps+* :
> - H.323 client send the following H323 message to Gnugk, then ooh323 :
> {code}
> 447 2022-08-31 17:19:09,669122 172.26.182.91 172.26.182.112 H.225.0/H.245 128 CS: empty masterSlaveDeterminationAck openLogicalChannel (g711A)”
> {code}
> - ooh323 tries to decode the received message content, and the 2nd item (Item #1 from previous capture) raises an error as indicated in h323_log logs
> {code}
> 19:19:09:820 Retrieving 2 of 2 tunneled H.245 messages.(outgoing, ooh323c_o_1)
> 19:19:09:820 Tunneled H.245 Message = {
> 19:19:09:820 Decoding 2 tunneled H245 message. (outgoing, ooh323c_o_1)
> 19:19:09:820 request = {
> 19:19:09:821 openLogicalChannel = {
> 19:19:09:822 forwardLogicalChannelNumber = {
> 19:19:09:826 101
> 19:19:09:828 }
> 19:19:09:828 forwardLogicalChannelParameters = {
> 19:19:09:829 dataType = {
> 19:19:09:830 audioData = {
> 19:19:09:832 g711Alaw64k = {
> 19:19:09:833 20
> 19:19:09:835 }
> 19:19:09:837 }
> 19:19:09:838 }
> 19:19:09:840 multiplexParameters = {
> 19:19:09:842 h2250LogicalChannelParameters = {
> 19:19:09:843 sessionID = {
> 19:19:09:845 1
> 19:19:09:848 }
> 19:19:09:851 mediaGuaranteedDelivery = {
> 19:19:09:864 FALSE
> 19:19:09:866 }
> 19:19:09:872 mediaControlChannel = {
> 19:19:09:875 unicastAddress = {
> 19:19:09:877 iPAddress = {
> 19:19:09:881 network = {
> 19:19:09:887 'ac1ab65b'H
> 19:19:09:891 }
> 19:19:09:895 tsapIdentifier = {
> 19:19:09:898 5025
> 19:19:09:903 }
> 19:19:09:906 }
> 19:19:09:909 }
> 19:19:09:913 }
> 19:19:09:914 silenceSuppression = {
> 19:19:09:919 TRUE
> 19:19:09:921 }
> 19:19:09:924 transportCapability = {
> 19:19:09:927 qOSCapabilities = {
> 19:19:09:929 elem[0] = {
> 19:19:09:933 Asn1Error: -2 at ooh323c/src/decode.c:67
> 19:19:09:933 Asn1Error: -2 at ooh323c/src/decode.c:621
> 19:19:09:933 Asn1Error: -2 at ooh323c/src/decode.c:1022
> 19:19:09:933 Asn1Error: -2 at ooh323c/src/decode.c:540
> 19:19:09:933 Error decoding H245 message (outgoing, ooh323c_o_1)
> ….
> {code}
> *+Results+*:
> The {{ooh323}} add-on could not decode the QoS parameters « LocalQoS » and « dscpValue » received from the H323 client (cf. Asn.1 decoding errors).
> The SIP part of Asterix is still usable but the h323 add-on is not more responsive as soon as the first « OpenLogicalChannel » with QoS « LocalQoS » et « dscpValue » parameters is received.
> *+Analysis+*:
> The {{ooh323}} add-on is based on a Asn.1 structure that does not include these 2 QoS parameters (cf file MULTIMEDIA-SYSTEM-CONTROL.h )
> *+Correction proposition+*:
> - still decode messages from H323 clients in accordance with ITU standard until 2005
> - do not try to decode QoS unknown parameters for H323 clients with ITU standard post 2005
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list