[asterisk-bugs] [JIRA] (ASTERISK-22852) Error decoding H245 message - ooh323c

[Alexander Anikin (JIRA)]

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

Alexander Anikin commented on ASTERISK-22852:
---------------------------------------------

Gabriele,
I see some strange packet from RMX that can cause asn1 decode error.

Frame 29: 60 bytes on wire (480 bits), 60 bytes captured (480 bits)
...
Internet Protocol Version 4, Src: 10.71.0.51 (10.71.0.51), Dst: 10.100.202.88 (10.100.202.88)
...
TPKT
    Continuation data


Asterisk can't understand this packet.
I think there must be terminal capability set from RMX instead of this packet.

All another packets in call handshake are correct. Asterisk send TCS to RMX, RMX send TCS ACK,
then RMX send this strange packet, then Asterisk send MSD request and RMX send MSD ACK.
But because there isn't completed TCS exchange logical channels can't be opened and
voice path can't be established.

I'll investigate what is this packet, but you can try to change config parameters on RMX.
Most H.323 devices use faststart and h245tunneling for more fast and easy call establishement,
on your RMX these parameters are off. Please try to switch on these parms and make test calls.
Also change to on Asterisk if they are off there also.



                
> Error decoding H245 message - ooh323c
> -------------------------------------
>
>                 Key: ASTERISK-22852
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22852
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/chan_ooh323
>    Affects Versions: 11.4.0, 11.6.0, 12.0.0-beta1
>         Environment: RH 5.5
>            Reporter: Gabriele Odone
>         Attachments: failure.pcap, success.pcap
>
>
> Environment:
> - Asterisk 11.4
> - H323 trunk between Asterisk and "Polycom CMA" (H323 Gatekeeper) using
> ooh323c module.
> - An H323 MCU  ("Polycom RMX") is registered to "Polycom CMA" gatekeeper.
> When H323 calls are placed by Polycom RMX, the following lines are written
> in /var/log/asterisk/h323_log:
> =========================
> 16:42:04:417  Asn1Error: -2 at ooh323c/src/decode.c:67
> 16:42:04:418  Error decoding H245 message (incoming, ooh323c_2)
> =========================
> The same code generating this error is also in the latest 11.6 and 12.0
> beta.
> Symptom: From the "Polycom RMX" side, the call is heard ringing. From the
> SIP side, the call is received and answered. See attached tcpdump example: failure.pcap
> If, instead of placing the call from the "Polycom RMX", I place the call
> from another H323 endpoint (registered to the same H323 Gatekeeper,
> "Polycom CMA"), the call goes through without such error (example: success.pcap).
> I suppose it is a H245 parsing error.
> In the attached tcpdumps:
> 10.44.1.60 = SIP client
> 10.100.202.88 = Asterisk server
> 10.71.0.55 = H323 Gatekeeper (Polycom CMA)
> 10.71.0.51 = H323 "client" (Polycom RMX) registered to H323 gatekeeper
> 10.44.1.156 = H323 client (Polycom CMA Desktop) registered to H323 gatekeeper

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira