[asterisk-bugs] [JIRA] Commented: (ASTERISK-20288) ICE Support Enabled, RTP Read Error - Hangup

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-20288:
----------------------------------------

The issue to fix here is ast_rtp_read's assumption that a failure in rtp_recvfrom implies that errno has been set.  While in many cases that should be true, pj_ice_sess_on_rx_pkt can cause __rtp_recvfrom to fail without setting an errno.

Other than that, we should document that PhonerLite appears to not play nicely with the ICE settings.  If you could provide a DEBUG log complete with 'sip set debug on' enabled, that might give us some more clues as to what PhonerLite responds with when we send it an INVITE with an SDP containing ICE candidates.

> ICE Support Enabled, RTP Read Error - Hangup
> --------------------------------------------
>
>                 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
>         Environment: Linux Ubuntu
>            Reporter: Joern Krebs
>         Attachments: debug
>
>
> 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