SRTCP unprotect failed because of authentication failure

[dspaan]

This error was already reported in this thread: viewtopic.php?f=4&t=38891

But not in the vicibox forum.

Anyway i'm also seeing this error spammed in the Vicibox 8.1.2 console.

Best threads i found outbout it:
https://community.asterisk.org/t/srtp-u ... 60/74793/2
https://community.asterisk.org/t/srtcp- ... on/73349/2

I checked but the libsrtp version in Vicbibox is already 1.5.4 so the suggested upgrade is not a solution.

I also see:

ERROR[1936]: tcptls.c:447 tcptls_stream_close: SSL_shutdown() failed: error:00000005:lib(0):func(0):DH lib, Underlying BIO error: Broken pipe
[Dec 3 20:37:45] == WebSocket connection from 'xx.xx.xxx.xx:60204' forcefully closed due to fatal write error

This thread says those errors are expected:

https://github.com/chornyitaras/PBXWebPhone/issues/7

I also see this warning after every call:


WARNING[21606][C-00000063]: func_hangupcause.c:140 hangupcause_read: Unable to find information for channel


So, a lot of warnings/errors in the console on the new Vicibox.

[williamconley]

You didn't mention symptoms or lack thereof. Log entries are cute, but if they don't change the user experience, they're not really noteworthy. That raises a level or two if something stops working, yes?

[dspaan]

I couldn't find any broken functionality. But it would be nice to know if these messages can be ignored or not. All these errors and warnings on the console makes it harder to troubleshoot the real issues.

[williamconley]

I couldn't find any broken functionality. But it would be nice to know if these messages can be ignored or not. All these errors and warnings on the console makes it harder to troubleshoot the real issues.

Good post. And very true. Especially if someone can identify the cause.

[dspaan]

I'm still seeing this on every vicibox 8.1.2 server i install. Is no one else getting these messages?

[alo]

Did anyone learn more as to why these messages spam the asterisk console sometimes?

[dspaan]

Not me, i'd love to get rid of all these messages.

[uncapped_shady]

If you are using Viciphone (WebRTC), try adding the following in your WebRTC template: "rtcp_mux=yes" without the quotes of course and then reboot.

[carpenox]

you dont need to reboot after applying those settings, and it will not remove those error messages anyways but you should have that in your template for sure

[dspaan]

Hmm it did seem to have removed the error messages for me. I have to test on more servers and for a longer period to be completely sure.

[carpenox]

these warnings? WARNING[21606][C-00000063]: func_hangupcause.c:140 hangupcause_read: Unable to find information for channel

[dspaan]

No the one in the title of this topic.

[carpenox]

ohhhh, my bad yea actually mine has stopped since i started using the viciphone 2 version which requires the rtcp_mux=yes in the template, great post back

Chris