djanjic Posted June 22, 2017 Report Share Posted June 22, 2017 Hello all, we are running hosted PBX on CentOS currently with about 75 domains and 360 extensions on it. For 90% of our phones we use SNOM phones which we auto provision. All these phones are registering via TLS except the few fax ATA's and some wireless Incom phones. The problem we run in to is that after server is running for a while ( 3 months or less ) auto provisioning runs in to problems. The problem is that there are no sockets available for the phone to register, sometimes the phone eventually gets registered but it takes anywhere between 30 minutes to an hour. The only thing that seems to work to fix the problem is to reboot the server. Is there a way to increase the number of sockets available for registration in order to avoid rebooting the server every few months? Thanks, Dusan Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 23, 2017 Report Share Posted June 23, 2017 What does the picture look like on netstat level? There is should be possible to see if there are any stale sockets. There is a setting that controls the number of sockets for SIP and also for HTTP, did you check that already? Quote Link to comment Share on other sites More sharing options...
djanjic Posted June 24, 2017 Author Report Share Posted June 24, 2017 Hello, On a slow morning netstat shows about 220 tls sockets and I am including text file of active unix domain sockets, which I don't know how to interpret. Also, trying to find where on the settings for the number of sockets, is that under Settings--->Network---->Ports? If it is I see the following: LDAP Port (TCP, StartTLS): 389 LDAP Port (TLS): 2346 Dusan unixsockets.txt Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 26, 2017 Report Share Posted June 26, 2017 I would not put LDAP on port 389 because that causes a lot of scanners sitting there the whole day thinking this might be some old Microsoft server. This might actually be the reason why you are running out of sockets. Please try netstat -anp|grep pbx Quote Link to comment Share on other sites More sharing options...
djanjic Posted June 26, 2017 Author Report Share Posted June 26, 2017 I am including the result of that command. I have excluded all IP addresses connected to the PBX since I do not want to share those with public. Included is the text file of the rest of it. Ican send the whole result privately if it is needed? netstat.txt Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 26, 2017 Report Share Posted June 26, 2017 Yes please send it privately or just replace the public address with 1.2.3.4. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 26, 2017 Report Share Posted June 26, 2017 In the private message there is nothing really out of the ordinary. A few connections to 389, but no waiting connections. Did you check your settings for Maximum number of SIP connections (reg_sipsettings.htm)? Quote Link to comment Share on other sites More sharing options...
djanjic Posted June 26, 2017 Author Report Share Posted June 26, 2017 It was set to 200, I think that was default. What is the safe number to increase to? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 27, 2017 Report Share Posted June 27, 2017 If you have 360 extensions I would set it to 500. That should be still pretty good. Quote Link to comment Share on other sites More sharing options...
djanjic Posted June 27, 2017 Author Report Share Posted June 27, 2017 Ok, thanks, we will change that setting, thank you for your help. 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.