We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If the RTPENGINE_URL env points to the wrong endpoint or there is an issue with WS establishment, the service crashed with the below error:
RTPENGINE_URL
7|sbc-rtpengine-sidecar | Error: connect ECONNREFUSED 127.0.0.1:8082 7|sbc-rtpengine-sidecar | at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) { 7|sbc-rtpengine-sidecar | errno: -111, 7|sbc-rtpengine-sidecar | code: 'ECONNREFUSED', 7|sbc-rtpengine-sidecar | syscall: 'connect', 7|sbc-rtpengine-sidecar | address: '127.0.0.1', 7|sbc-rtpengine-sidecar | port: 8082 7|sbc-rtpengine-sidecar | }
The text was updated successfully, but these errors were encountered:
probably good that it crashes though if misconfgured, silently continuing with configuration error doesnt seem like a good idea to me
Sorry, something went wrong.
The ws connection is needed just to dump the rtpenigne stats. Is this so important for the service?
Successfully merging a pull request may close this issue.
If the
RTPENGINE_URL
env points to the wrong endpoint or there is an issue with WS establishment, the service crashed with the below error:The text was updated successfully, but these errors were encountered: