-
Notifications
You must be signed in to change notification settings - Fork 19
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
Execution can not start , refuse to connect. #7
Comments
The problem is you moved rtpengine to listen for traffic on port 2223 instead of its default port 22222:
You then configured your node.js application to also try to listen on that same port, which of course fails. Leave your drachtio config file unchanged, and modify your rtpengine config to listen for ng traffic on port 2222. Again this is the default, and you caused your problems by changing this unnecessarily. |
Thanks for your feedback.
|
rtpengine is saying it ran out of ports, which is strange since it is configured to have a range of 10,000 ports. Look in /var/log/syslog for more logging from rtpengine to see if you can figure out why. Also try restarting rtpengine and running your tests again |
As you told I did the same, now “ran out of the port issue is solved”, restart the rtpengine, and tried to call. It seems like the call is going but I haven’t rec. any call. drachtio log |
turn drachtio server log level to debug, run the node.js app with DEBUG=drachtio:* and re-do your test. Seems like some bit of configuration between the app and the server is off |
Thank you for responding!
--Full Log List-- |
Your problem is with your rtpengine config. Specifically this
I can see from the drachtio logs that that address is not a local address on the server. So then, rtpengine has no ports and gives an error:
That address is a public address assigned to the VM, but is not explictly bound to an interface. Change your rtpengine config to this and it will probably work
|
Hi Dave and thanks for responding. This is this log file of drachtio. |
you should get a network trace and study it to see if you are receiving RTP on the B leg |
Hi Dave, I have checked, I think we haven't rec the RTP.
---full system log--- and also in drachtio log I have noticed some lines--
--drachtio log-- Is this the reason behind it? I haven't heard the one side voice or not rec. incoming call in SIP client? |
Hi Dave,
--drachtio log-- Is this the issue to making the call? Like I can not make a call to SIP client after registration (incoming call). |
drachtio config and rtpengine config | both are running in the same server and when I start to run this program getting error. ERROR, I know this is related to the port issue but I want to know how to solve it because when I change the port in rtpengine and start the service and then run this program it always gives me the same error.
drachtio-rtpengine-webrtcproxy config file
The text was updated successfully, but these errors were encountered: