cmrabet Posted July 12, 2011 Report Share Posted July 12, 2011 I can't understand what is going on. I changed the SIP ports, then went to the console of our Debian server where PBXnSIP is installed, and restarted the process as follows: root@ITE-Server:/etc/init.d# ./pbxnsip restart Shutting down pbxnsip daemon:/usr/local/pbxnsip/pbxctrl: no process killed Starting pbxnsip daemon The went to the Web browser and did as usually : http://192.168.1.3:20000 That's the IP of the PBXnSIP server, and the port we configured for web access... AND NOTHING, the web is not UP. I went back to our Linux server, and it doesn't start any service, no error, no nothing. The PBXnSIP daemon doesn't restart!!! Any help please? Quote Link to comment Share on other sites More sharing options...
pbx support Posted July 12, 2011 Report Share Posted July 12, 2011 It is possible under the Linux, the ports are not released yet by the OS during the PBX restart. So, stop the PBX, wait for a minute and start it. Quote Link to comment Share on other sites More sharing options...
cmrabet Posted July 12, 2011 Author Report Share Posted July 12, 2011 It is possible under the Linux, the ports are not released yet by the OS during the PBX restart. So, stop the PBX, wait for a minute and start it. root@ITE-Server:/usr/local/pbxnsip# ./pbxctrl --dir /usr/local/pbxnsip/ --config config.xml --log log.file --no-daemon Starting up [0] 20110712154847: UDP: bind() to port 5060 failed [0] 20110712154847: FATAL: Could not open UDP port 5060 for SIP But I restarted many times since the first time, and the daemon never came up since then, no process is running for PBXnSIP, and NETSAT doesn't show anything.... ???? Quote Link to comment Share on other sites More sharing options...
cmrabet Posted July 12, 2011 Author Report Share Posted July 12, 2011 The only thing I did was setting the SIP TLS port to the same as the regular SIP one, 5060. I restarted and since then I'm having this problem. The daemon doesn't come up, so I don't have access to the Web interface anymore. Quote Link to comment Share on other sites More sharing options...
pbx support Posted July 12, 2011 Report Share Posted July 12, 2011 You can't have them as same port. That's why you are seeing this issue. You can edit the pbx.xml file and change the value of ip_sip_tls_port back to 5061 or something other than 5060 and start the service. Quote Link to comment Share on other sites More sharing options...
cmrabet Posted July 13, 2011 Author Report Share Posted July 13, 2011 You can't have them as same port. That's why you are seeing this issue. You can edit the pbx.xml file and change the value of ip_sip_tls_port back to 5061 or something other than 5060 and start the service. Yes you are right, I fixed the issue editing manually the config.xml file. I did this because support from Skype told me that Skype connect doesn't support TLS ports, and he told me to set it to 5060...wrong guy. Fixed. Thanks. 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.