alphacep/vosk-asterisk

Web socket closed abruptly

gobindabd opened this issue · 1 comments

Anyone faced this kinds of error

-- Executing [2000@default:1] NoOp("SIP/9000-00000001", "") in new stack
-- Executing [2000@default:2] Wait("SIP/9000-00000001", "1") in new stack
-- Executing [2000@default:3] SpeechCreate("SIP/9000-00000001", "") in new stack

[Jun 14 05:41:16] NOTICE[2527][C-00000002]: res_speech_vosk.c:83 vosk_recog_create: (vosk) Create speech resource ws://localhost:2700
[Jun 14 05:41:16] NOTICE[2527][C-00000002]: res_speech_vosk.c:91 vosk_recog_create: (vosk) Created speech resource result 0
-- Executing [2000@default:4] SpeechBackground("SIP/9000-00000001", "020") in new stack
[Jun 14 05:41:17] NOTICE[2527][C-00000002]: res_speech_vosk.c:196 vosk_recog_start: (vosk) Start recognition
[Jun 14 05:41:17] WARNING[2527][C-00000002]: res_http_websocket.c:523 ws_safe_read: Web socket closed abruptly
[Jun 14 05:41:17] ERROR[2527][C-00000002]: res_http_websocket.c:1415 __ast_websocket_read_string: Client WebSocket string read - error reading string data
[Jun 14 05:41:18] WARNING[2527][C-00000002]: res_http_websocket.c:523 ws_safe_read: Web socket closed abruptly
[Jun 14 05:41:18] ERROR[2527][C-00000002]: res_http_websocket.c:1415 __ast_websocket_read_string: Client WebSocket string read - error reading string data
[Jun 14 05:41:18] WARNING[2527][C-00000002]: res_http_websocket.c:523 ws_safe_read: Web socket closed abruptly
[Jun 14 05:41:18] ERROR[2527][C-00000002]: res_http_websocket.c:1415 __ast_websocket_read_string: Client WebSocket string read - error reading string data
[Jun 14 05:41:18] WARNING[2527][C-00000002]: res_http_websocket.c:523 ws_safe_read: Web socket closed abruptly
[Jun 14 05:41:18] ERROR[2527][C-00000002]: res_http_websocket.c:1415 __ast_websocket_read_string: Client WebSocket string read - error reading string data
[Jun 14 05:41:19] WARNING[2527][C-00000002]: res_http_websocket.c:523 ws_safe_read: Web socket closed abruptly
[Jun 14 05:41:19] ERROR[2527][C-00000002]: res_http_websocket.c:1415 __ast_websocket_read_string: Client WebSocket string read - error reading string data
[Jun 14 05:41:19] WARNING[2527][C-00000002]: res_http_websocket.c:523 ws_safe_read: Web socket closed abruptly
[Jun 14 05:41:19] ERROR[2527][C-00000002]: res_http_websocket.c:1415 __ast_websocket_read_string: Client WebSocket string read - error reading string data
[Jun 14 05:41:19] WARNING[2527][C-00000002]: res_http_websocket.c:523 ws_safe_read: Web socket closed abruptly
[Jun 14 05:41:19] ERROR[2527][C-00000002]: res_http_websocket.c:1415 __ast_websocket_read_string: Client WebSocket string read - error reading string data
[Jun 14 05:41:20] WARNING[2527][C-00000002]: res_http_websocket.c:523 ws_safe_read: Web socket closed abruptly
[Jun 14 05:41:20] ERROR[2527][C-00000002]: res_http_websocket.c:1415 __ast_websocket_read_string: Client WebSocket string read - error reading string data
[Jun 14 05:41:20] WARNING[2527][C-00000002]: res_http_websocket.c:523 ws_safe_read: Web socket closed abruptly
[Jun 14 05:41:20] ERROR[2527][C-00000002]: res_http_websocket.c:1415 __ast_websocket_read_string: Client WebSocket string read - error reading string data

It's fixed. another application using that port.