PBXnSIP Service Crashing

[AurumPotabile]

Good morning, all. We have had a troubling recurring problem for about a month now in a small business implementation we recently set up. The phone system will run smoothly for a while and suddenly all phones will go down. When I remote into the server to look at things, the service is still showing as running, but a restart of the service causes the phones to come back up. During this time, the business does not receive any incoming calls. Initially this happened infrequently (maybe once every couple weeks), but it's occurred both yesterday and today, which is cause for my concern.

 

My problem is two-fold. Primarily, I'm not quite sure how to read the logfile. I have a feeling that if I can understand what it's telling me, it'll help me get to the root of this problem much more quickly. If anyone can point me to something that explains the various codes in the log, or is willing to devote some time to help me understand it, I'll genuinely appreciate it.

 

Secondarily, though, there remains the persistent problem of the crashing service. If you have any experience with this sort of behavior, I'd like to know how to resolve this. I'm not even certain what configuration settings might be involved with this, so I'm refraining from putting them all here until I have some more direction.

 

Thanks in advance for your help-- I appreciate your time.

[mattlandis]

our experience is that pbxnsip runs extremely solid. (we run on Windows o/s)

 

What version are you running? If you have an older than v4 without the automatic blacklisting sip attacks can take your pbx down. Restarting the service could stop the attack? just a wild thot.

 

Matt

[Vodia PBX]

You have to find the root of the problem, the PBX should under no circumstances crash. I would check:

 

• I guess the rest of the server is still working okay? Then we can rule out general problems.
  
• Do you have enough hard disk space left?
  
• Maybe you have too many CDR in your system (check the file system space that is being occupied in the working directory of the PBX)
  
• What OS are you running? And what version are you using? Depending on the OS it might make sense to enable a core dump.
  

[AurumPotabile]

our experience is that pbxnsip runs extremely solid. (we run on Windows o/s)

 

What version are you running? If you have an older than v4 without the automatic blacklisting sip attacks can take your pbx down. Restarting the service could stop the attack? just a wild thot.

 

Matt

 

Thanks for the response, Matt-- the version is indeed 4.0.1.3499 (Win 32). In all cases where this has happened, a restart of the service has brought the phones back up immediately.

[AurumPotabile]

You have to find the root of the problem, the PBX should under no circumstances crash. I would check:

 

• I guess the rest of the server is still working okay? Then we can rule out general problems.
  
• Do you have enough hard disk space left?
  
• Maybe you have too many CDR in your system (check the file system space that is being occupied in the working directory of the PBX)
  
• What OS are you running? And what version are you using? Depending on the OS it might make sense to enable a core dump.
  

 

Thanks for the response.

 

[*] The server is working fine otherwise. Even when the phone service is down, we're still able to access email (this server doubles as the Exchange server) and the Internet.

[*] We have 336 GB of space left on the drive.

[*] The working directory size is 54.4 MB (62.8 on disk).

[*] It's running Windows Small Business Server. The PBX version is 4.0.1.3499 (Win 32).

[Vodia PBX]

[*] The server is working fine otherwise. Even when the phone service is down, we're still able to access email (this server doubles as the Exchange server) and the Internet.

[*] We have 336 GB of space left on the drive.

[*] The working directory size is 54.4 MB (62.8 on disk).

[*] It's running Windows Small Business Server. The PBX version is 4.0.1.3499 (Win 32).

 

That should all be fine.

 

Do you get emails from the PBX? Make sure that you get emails for important events. For example, it could be that the PBX starts blacklisting IP addresses because users entered the wrong password and then they are locked out for some time.

 

I would just update to a newer build, like 4.2.0.3958 (backup first, you have plenty of space left anyway). If you are using extensively TCP (SIP/HTTP) there were issues in this build, thought I doubt there were too serious, it could help doing an upgrade.

 

Do you have a good password set for the admin? Of course noone should be able to log in as admin and do bad things.

 

The other thing coming to my mind is the Windows firewall that could kick in for whatever reason. Make sure that the PBX is a trusted process and that the firewall does not cut the network connectivity from time to time... Maybe the same thing applies for virus scanner that thinks the PBX sends out SPAM emails.

 

This windows setup should be very very rock solid.