hosted Posted June 14, 2010 Report Share Posted June 14, 2010 on these latest versions whenever i restart pbxnsip it doesnt work: 20100613190710: Could not bind socket to port 80 on IP 0.0.0.0 is pbxnsip hanging on the port 80 after i stop it? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 18, 2010 Report Share Posted June 18, 2010 is pbxnsip hanging on the port 80 after i stop it? Yea, we changed the way the PBX binds to the port. In 4, it requires that no other application is listening on port 80. Same for 443, 5060 and 5061 (or cource, the numbers can be changed in the settings). This is because sharing the port with another application results in absolutely unpredictable behavior ("Voodo"). You can start the application with "--no-check-ports", then it will start up no matter if it can bind to the port or not. Quote Link to comment Share on other sites More sharing options...
hosted Posted June 21, 2010 Author Report Share Posted June 21, 2010 Yea, we changed the way the PBX binds to the port. In 4, it requires that no other application is listening on port 80. Same for 443, 5060 and 5061 (or cource, the numbers can be changed in the settings). This is because sharing the port with another application results in absolutely unpredictable behavior ("Voodo"). You can start the application with "--no-check-ports", then it will start up no matter if it can bind to the port or not. the problem isnt pbxnsip binding to a port. its when you stop pbxnsip and it doesnt unbind for a LONG time. so when you restart the service it fails because the port is still bound to the old pbxnsip process. (according to linux) Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 21, 2010 Report Share Posted June 21, 2010 so when you restart the service it fails because the port is still bound to the old pbxnsip process. (according to linux) We also saw that. Seems that waiting just for one seconds is not enough any more. I now usually wait one minute. I still believe that is is progress if we can be sure there is no other process (not even another pbxnsip executable) running on the same socket. Question is how do we tell the OS that we dont want to use the socket any more? Ideally, there would be something that we can call from the shell that cleans up the dangling socket. Quote Link to comment Share on other sites More sharing options...
hosted Posted June 24, 2010 Author Report Share Posted June 24, 2010 one minute is an eternity Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.