Hi, Check the 2 first bits of the raw rtcp packet, it is where the version is set (http://www.networksorcery.com/enp/protocol/rtcp.htm). In your case, it looks that the 2 bits are set, that's why you are getting 3. Are you sure it's the same packet for which you are seeing version = 2 in wireshark? It would be really interesting to check the version on each rtcp packet from the call to validate that some are indeed incorrect. But if you are willing to accept the bad version, you can apply the following patch (beware, it's a non tested hack): diff --git a/src/switch_rtp.c b/src/switch_rtp.c index 0ae3b641f0..fe975aca32 100644 --- a/src/switch_rtp.c +++ b/src/switch_rtp.c @@ -6586,8 +6586,8 @@ static switch_status_t process_rtcp_packet(switch_rtp_t *rtp_session, switch_siz return SWITCH_STATUS_SUCCESS; } else { switch_log_printf(SWITCH_CHANNEL_SESSION_LOG(rtp_session->session), - SWITCH_LOG_WARNING, "Received an unsupported RTCP packet version %d\n", msg->header.version); - return SWITCH_STATUS_FALSE; + SWITCH_LOG_WARNING, "Received an unsupported RTCP packet version %d, forcing to 2\n", msg->header.version); + msg->header.version = 2; } } Best Regards, -- Vallimamod Abdullah SIP Solutions vma@sipsolutions.fr .

On 16 Jan 2018, at 14:06, Alexander Haugg <Alexander.Haugg@c4b.de> wrote:

If i have a bit more time, it could be I can fix it, but not at the moment. At first I will open a JIRA ticket.

-----Ursprüngliche Nachricht----- Von: FreeSWITCH-users [mailto:freeswitch-users-bounces@lists.freeswitch.org] Im Auftrag von Madovsky Gesendet: Dienstag, 16. Januar 2018 14:02 An: freeswitch-users@lists.freeswitch.org Betreff: Re: [Freeswitch-users] Received an unsupported RTCP packet version 3

any skillful C programmers needed so,

it shouldn't be hard I think

On 1/16/2018 4:53 AM, Alexander Haugg wrote:

...

Yes, you are right. The interesting point is, the RTCP version is 2. That can i see in the wireshark trace

-----Ursprüngliche Nachricht----- Von: FreeSWITCH-users [mailto:freeswitch-users-bounces@lists.freeswitch.org] Im Auftrag von Madovsky Gesendet: Dienstag, 16. Januar 2018 13:19 An: freeswitch-users@lists.freeswitch.org Betreff: Re: [Freeswitch-users] Received an unsupported RTCP packet version 3

As the warning says, FS does not support RTCP version 3 message,

maybe a patch would be welcome.

On 1/16/2018 3:53 AM, Alexander Haugg wrote:

...

Thanks, but no, I need the event socket event "RECV_RTCP_MESSAGE". If the message will written, then the event will not fired. Switch_rtp.c line 6650 } else { switch_log_printf(SWITCH_CHANNEL_SESSION_LOG(rtp_session->session), SWITCH_LOG_WARNING, "Received an unsupported RTCP packet version %d\n", msg->header.version); return SWITCH_STATUS_FALSE;

-----Ursprüngliche Nachricht----- Von: Madovsky [mailto:infos@madovsky.org] Gesendet: Dienstag, 16. Januar 2018 12:17 An: Alexander Haugg <Alexander.Haugg@c4b.de> Betreff: Re: [Freeswitch-users] Received an unsupported RTCP packet version 3

I think it's safe to ignore unless you need

any management with RTCP

On 1/15/2018 11:16 PM, Alexander Haugg wrote:

...

I have the same Problem with the Bria 4 Client. My FS Verison is "Version 1.9.0+git~20170608T004121Z~00ab2b40b4~64bit (git 00ab2b4 2017-06-08 00:41:21Z 64bit)"

-----Ursprüngliche Nachricht----- Von: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] Im Auftrag von Mikhail Demekhov Gesendet: Donnerstag, 10. November 2016 09:27 An: freeswitch-users@lists.freeswitch.org Betreff: [Freeswitch-users] Received an unsupported RTCP packet version 3

Hello!

I have FreeSWITCH Version 1.6.12. After connecting partner FS-1.7 I had a lot of warning:

[WARNING] switch_rtp.c:6207 Received an unsupported RTCP packet version 3

How to fix it?

better to publish it on jira yes, thanks Abdullah On 1/16/2018 7:04 AM, Vallimamod Abdullah wrote:

Hi,

Check the 2 first bits of the raw rtcp packet, it is where the version is set (http://www.networksorcery.com/enp/protocol/rtcp.htm). In your case, it looks that the 2 bits are set, that's why you are getting 3. Are you sure it's the same packet for which you are seeing version = 2 in wireshark?

It would be really interesting to check the version on each rtcp packet from the call to validate that some are indeed incorrect.

But if you are willing to accept the bad version, you can apply the following patch (beware, it's a non tested hack):

diff --git a/src/switch_rtp.c b/src/switch_rtp.c index 0ae3b641f0..fe975aca32 100644 --- a/src/switch_rtp.c +++ b/src/switch_rtp.c @@ -6586,8 +6586,8 @@ static switch_status_t process_rtcp_packet(switch_rtp_t *rtp_session, switch_siz return SWITCH_STATUS_SUCCESS; } else { switch_log_printf(SWITCH_CHANNEL_SESSION_LOG(rtp_session->session), - SWITCH_LOG_WARNING, "Received an unsupported RTCP packet version %d\n", msg->header.version); - return SWITCH_STATUS_FALSE; + SWITCH_LOG_WARNING, "Received an unsupported RTCP packet version %d, forcing to 2\n", msg->header.version); + msg->header.version = 2; } }

Best Regards,