[asterisk-bugs] [JIRA] (ASTERISK-20702) res_rtp_asterisk.c:3455 ast_rtp_read: RTP Read error: Invalid or incomplete multibyte or wide character. Hanging up.

[David Brillert (JIRA)]

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

David Brillert commented on ASTERISK-20702:
-------------------------------------------

Now I can't remember where I found this comment but it was somewhere on the official wiki.
I found the comment sensible.

Joshua Colp
The next release of Asterisk 11 will have ICE support enabled by default in res_rtp_asterisk, but disabled by default in chan_sip

I assume this to mean that best practice should do the following:
/etc/asterisk/rtp.conf/icesupport=yes
/etc/asterisk/sip.conf/icesupport=no
edit icesupport=yes per peer as needed
and provision the client as needed
                
> res_rtp_asterisk.c:3455 ast_rtp_read: RTP Read error: Invalid or incomplete multibyte or wide character.  Hanging up.
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20702
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20702
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_rtp_asterisk
>    Affects Versions: 11.0.1
>         Environment: Asterisk 11.0.1
> Snom 8.x firmware
>            Reporter: David Brillert
>            Assignee: David Brillert
>         Attachments: messages.txt
>
>
> All calls to Snom phones hangup when answer with WARNING res_rtp_asterisk.c:3455 ast_rtp_read: RTP Read error: Invalid or incomplete multibyte or wide character.  Hanging up.
> Snom config user_ice1!: off
> sip.conf
> icesupport = yes
> verbose log with sip debug attached.
> 234(192.168.192.96) calls Snom 223(192.168.192.119)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira