vicidial.org

trying to upgrade one of my clusters, has anyone else ran into this error message with 8.1.2 install using viciphone?


[Nov 7 07:11:01] == Manager 'sendcron' logged on from 192.168.1.1
[Nov 7 07:11:01] == Manager 'sendcron' logged on from 192.168.1.1
[Nov 7 07:11:01] == Manager 'sendcron' logged off from 192.168.1.1
[Nov 7 07:11:01] == Manager 'sendcron' logged off from 192.168.1.1
[Nov 7 07:11:01] == Manager 'sendcron' logged off from 192.168.1.1
[Nov 7 07:11:03] == SRTCP unprotect failed because of authentication failure
[Nov 7 07:11:03] == SRTCP unprotect failed because of authentication failure

[Nov 7 15:47:23] Connected to Asterisk 13.21.1-vici currently running on tel1 (pid = 2111)
[Nov 7 15:47:26] == SRTCP unprotect failed because of authentication failure
[Nov 7 15:47:27] == SRTCP unprotect failed because of authentication failure
[Nov 7 15:47:29] == SRTCP unprotect failed because of authentication failure
[Nov 7 15:47:30] ERROR[2163]: tcptls.c:447 tcptls_stream_close: SSL_shutdown() failed: error:00000005:lib(0):func(0):DH lib, Underlying BIO error: Broken pipe
[Nov 7 15:47:30] == WebSocket connection from '12.X.X.X:43916' forcefully closed due to fatal write error
[Nov 7 15:47:35] == SRTCP unprotect failed because of authentication failure
[Nov 7 15:47:36] == SRTCP unprotect failed because of authentication failure
[Nov 7 15:47:40] == SRTCP unprotect failed because of authentication failure
[Nov 7 15:47:42] == SRTCP unprotect failed because of authentication failure
[Nov 7 15:47:47] == SRTCP unprotect failed because of authentication failure
[Nov 7 15:47:48] == SRTCP unprotect failed because of authentication failure

I see this On a few boxes too. Anyone know what the error means? is it someone(malicious someone) Trying to trying to connect through webphone or something?

I believe the unprotect failed error doesnt mean viciphone wont work.

You say you are getting this error. But is viciphone working?

I saw this about this. whats the recommended version of asterisk 13 vicidial recommends?

https://issues.asterisk.org/jira/browse/ASTERISK-26979

alo wrote:I saw this about this. whats the recommended version of asterisk 13 vicidial recommends?

https://issues.asterisk.org/jira/browse/ASTERISK-26979

Asterisk v.13.21.1-vici (from vicibox.com) seems likely.

I can also confirm this error. Viciphone does work, but for some reason this message just spams the console. No idea why I can't seem to figure it out.

I noticed this happens until I reboot, then as soon as I reboot the messages stop. then after some heavy dialing they start again.

What if you just restart asterisk without an actual reboot?

It would be funny if it were just a single call that somehow gets stuck in a loop.

I am seeing the same issue on a new ISO install if Vicibox 9.0.1 using Google Chrome.
[Apr 19 12:31:07] == Manager 'sendcron' logged on from 127.0.0.1
[Apr 19 12:31:07] == Manager 'sendcron' logged off from 127.0.0.1
[Apr 19 12:31:18] == WebSocket connection from '68.204.132.3:53333' for protocol 'sip' accepted using version '13'
[Apr 19 12:31:19] -- Registered SIP '6666' at 68.204.132.3:53333
[Apr 19 12:31:19] NOTICE[13946]: chan_sip.c:24672 handle_response_peerpoke: Peer '6666' is now Reachable. (88ms / 2000ms)
[Apr 19 12:31:29] == Manager 'sendcron' logged on from 127.0.0.1
[Apr 19 12:31:29] == Using SIP RTP CoS mark 5
[Apr 19 12:31:29] -- Called 6666
[Apr 19 12:31:29] -- SIP/6666-00000008 is ringing
[Apr 19 12:31:29] > 0x7fdeec0060a0 -- Strict RTP learning after remote address set to: 68.204.132.3:58135
[Apr 19 12:31:29] > 0x7fdeec0060a0 -- Strict RTP learning after remote address set to: 68.204.132.3:58135
[Apr 19 12:31:29] -- SIP/6666-00000008 answered
[Apr 19 12:31:29] -- Executing [8600051@default:1] MeetMe("SIP/6666-00000008", "8600051,F") in new stack
[Apr 19 12:31:29] -- Created MeetMe conference 1023 for conference '8600051'
[Apr 19 12:31:29] -- <SIP/6666-00000008> Playing 'conf-onlyperson.gsm' (language 'en')
[Apr 19 12:31:29] > 0x7fdeec0060a0 -- Strict RTP learning after ICE completion
[Apr 19 12:31:29] > 0x7fdeec0060a0 -- Strict RTP switching to RTP target address 68.204.132.3:58135 as source
[Apr 19 12:31:30] == Manager 'sendcron' logged off from 127.0.0.1
[Apr 19 12:31:31] == SRTCP unprotect failed because of authentication failure
[Apr 19 12:31:32] == SRTCP unprotect failed because of authentication failure
[Apr 19 12:31:34] > 0x7fdeec0060a0 -- Strict RTP learning complete - Locking on source address 68.204.132.3:58135
[Apr 19 12:31:35] == SRTCP unprotect failed because of authentication failure
[Apr 19 12:31:35] == SRTCP unprotect failed because of authentication failure
[Apr 19 12:31:39] == SRTCP unprotect failed because of authentication failure
[Apr 19 12:31:42] == SRTCP unprotect failed because of authentication failure
[Apr 19 12:31:42] == SRTCP unprotect failed because of authentication failure
[Apr 19 12:31:45] == SRTCP unprotect failed because of authentication failure
[Apr 19 12:31:49] == SRTCP unprotect failed because of authentication failure
[Apr 19 12:31:52] == SRTCP unprotect failed because of authentication failure
[Apr 19 12:31:53] == SRTCP unprotect failed because of authentication failure

However, if we login as an agent using FireFox......... there are no errors
[Apr 19 12:34:06] == WebSocket connection from '68.204.132.3:53439' for protocol 'sip' accepted using version '13'
[Apr 19 12:34:06] == Manager 'sendcron' logged on from 127.0.0.1
[Apr 19 12:34:06] == Manager 'sendcron' logged off from 127.0.0.1
[Apr 19 12:34:06] -- Registered SIP '6666' at 68.204.132.3:53439
[Apr 19 12:34:10] == Manager 'sendcron' logged on from 127.0.0.1
[Apr 19 12:34:10] == Using SIP RTP CoS mark 5
[Apr 19 12:34:10] -- Called 6666
[Apr 19 12:34:10] -- SIP/6666-00000009 is ringing
[Apr 19 12:34:10] > 0x7fdef4016b90 -- Strict RTP learning after remote address set to: 68.204.132.3:53083
[Apr 19 12:34:10] > 0x7fdef4016b90 -- Strict RTP learning after remote address set to: 68.204.132.3:53083
[Apr 19 12:34:10] > 0x7fdef4016b90 -- Strict RTP learning after remote address set to: 68.204.132.3:53083
[Apr 19 12:34:12] == WebSocket connection from '68.204.132.3:53333' closed
[Apr 19 12:34:15] -- SIP/6666-00000009 answered
[Apr 19 12:34:15] -- Executing [8600051@default:1] MeetMe("SIP/6666-00000009", "8600051,F") in new stack
[Apr 19 12:34:15] -- Created MeetMe conference 1023 for conference '8600051'
[Apr 19 12:34:15] -- <SIP/6666-00000009> Playing 'conf-onlyperson.gsm' (language 'en')
[Apr 19 12:34:15] > 0x7fdef4016b90 -- Strict RTP learning after ICE completion
[Apr 19 12:34:15] > 0x7fdef4016b90 -- Strict RTP switching to RTP target address 68.204.132.3:53083 as source
[Apr 19 12:34:16] == Manager 'sendcron' logged off from 127.0.0.1
[Apr 19 12:34:20] > 0x7fdef4016b90 -- Strict RTP learning complete - Locking on source address 68.204.132.3:53083
[Apr 19 12:35:02] == Manager 'sendcron' logged on from 127.0.0.1
[Apr 19 12:35:02] == Manager 'sendcron' logged on from 127.0.0.1
[Apr 19 12:35:02] == Manager 'sendcron' logged off from 127.0.0.1
[Apr 19 12:35:02] == Manager 'sendcron' logged off from 127.0.0.1
[Apr 19 12:35:07] == Manager 'sendcron' logged on from 127.0.0.1
[Apr 19 12:35:07] == Manager 'sendcron' logged off from 127.0.0.1
[Apr 19 12:36:01] == Manager 'sendcron' logged on from 127.0.0.1
[Apr 19 12:36:01] == Manager 'sendcron' logged on from 127.0.0.1
[Apr 19 12:36:01] == Manager 'sendcron' logged off from 127.0.0.1
[Apr 19 12:36:01] == Manager 'sendcron' logged off from 127.0.0.1
[Apr 19 12:36:06] == Manager 'sendcron' logged on from 127.0.0.1
[Apr 19 12:36:06] == Manager 'sendcron' logged off from 127.0.0.1
[Apr 19 12:37:01] == Manager 'sendcron' logged on from 127.0.0.1
[Apr 19 12:37:01] == Manager 'sendcron' logged on from 127.0.0.1
[Apr 19 12:37:01] == Manager 'sendcron' logged off from 127.0.0.1
[Apr 19 12:37:01] == Manager 'sendcron' logged off from 127.0.0.1
[Apr 19 12:37:06] == Manager 'sendcron' logged on from 127.0.0.1
[Apr 19 12:37:06] == Manager 'sendcron' logged off from 127.0.0.1

chrome and firefox may have different dns and certificate validation charts. or one may have a different default setting for a security requirement.

My advice, of course, just use firefox.

williamconley wrote:chrome and firefox may have different dns and certificate validation charts. or one may have a different default setting for a security requirement.

My advice, of course, just use firefox.

Yes ofc. Just some advice for others that might come across the same issues.

in webrtc template add rtcp_mux=yes and reboot

yes great reply LC2003 - good shit