[asterisk-bugs] [JIRA] Updated: (ASTERISK-20288) PhonerLite reports RTP read error when ICE Support Enabled

[Richard Mudgett (JIRA)]

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

Richard Mudgett updated ASTERISK-20288:
---------------------------------------

    Attachment: jira_asterisk_20288_err_msg.patch

[^jira_asterisk_20288_err_msg.patch] should give a more meaningful message than "Fail: Success".

You should get these messages:
PJ ICE Rx error status code: %d '%s'.
RTCP Read error: Likely an ICE or SRTP failure. Hanging up.

> PhonerLite reports RTP read error when ICE Support Enabled
> ----------------------------------------------------------
>
>                 Key: ASTERISK-20288
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20288
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_rtp_asterisk
>    Affects Versions: SVN, 11.0.0-beta1
>         Environment: Linux Ubuntu
>            Reporter: Joern Krebs
>            Assignee: Richard Mudgett
>            Severity: Minor
>         Attachments: debug, debug, jira_asterisk_20288_err_msg.patch, phonerlite-capture-filtered2.pcap, phonerlite-capture-filtered.pcap, tcpdump.log, wireshark.pcap
>
>
> O.K. this is a bit hard to explain for me:
> If I use PhonerLite (and I can only replicate this issue with PhonerLite, but there it happens 100% of the time!) to call asterisk (any number, and any setup, nat, no-nat, etc.) I get the warning:
> RTP Read error: Success. Hanging up
> The "Success" part of the error should be the error message. BUT Success indicates, that there actually is no error.
> So what I did was changing the code and checking if the errno is 0, ignore that line ... and it works.
> I do not get this error with the SVN for Asterisk 10, just with SVN Asterisk 11.
> So basically under some circumstances (I cannot replicate the real issue, ... even the debug log doesn't show any issues at all!)
> the errno is set to 0, instead of whatever it should be...
> Can please someone have a look at this.
> (I would be open to test anything, although my dev capabilities are limited.)
> It really is a show-stopper to me! :-(

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