Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebSocket connection forcefully closed due to fatal write error #519

Open
henry-ok opened this issue Feb 2, 2025 · 1 comment
Open

WebSocket connection forcefully closed due to fatal write error #519

henry-ok opened this issue Feb 2, 2025 · 1 comment
Labels
Out of scope The problem described isnt an issue with this package, its likely something else in their setup

Comments

@henry-ok
Copy link

henry-ok commented Feb 2, 2025

i am getting this error on my asterisk server that is is connecting to my softphone that uses websocket

2025-02-01 18:00:38] VERBOSE[27266] res_http_websocket.c: WebSocket connection from '80.171.120.98:65097' forcefully closed due to fatal write error
[2025-02-01 18:00:38] VERBOSE[27266] res_http_websocket.c: WebSocket connection from '80.171.120.98:65097' forcefully closed due to fatal write error
[2025-02-01 18:00:40] ERROR[29178] res_http_websocket.c: Error reading from web socket: Connection reset by peer
[2025-02-01 18:00:40] ERROR[29178] res_http_websocket.c: Error reading from web socket: Connection reset by peer
[2025-02-01 18:00:40] VERBOSE[27266] res_http_websocket.c: WebSocket connection from '185.104.138.61:47570' forcefully closed due to fatal write error
[2025-02-01 18:00:40] VERBOSE[27266] res_http_websocket.c: WebSocket connection from '185.104.138.61:47570' forcefully closed due to fatal write error
[2025-02-01 18:00:41] WARNING[29181][C-00000039] sip/config_parser.c: nat=yes is deprecated, use nat=force_rport,comedia instead
[2025-02-01 18:00:41] WARNING[29181][C-00000039] sip/config_par

@mikaelwills
Copy link
Collaborator

@henry-ok you're simply going to need to investiage it further to provide more information and logs.
No files in those logs are from this package as far as im aware.

@mikaelwills mikaelwills added the Out of scope The problem described isnt an issue with this package, its likely something else in their setup label Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Out of scope The problem described isnt an issue with this package, its likely something else in their setup
Projects
None yet
Development

No branches or pull requests

2 participants