Jump to content

Intruder in our PBXnSIP server


cmrabet
 Share

Recommended Posts

Hi

 

I have a new problem.

 

I detected someone form outside our network registering in one of our extensions to place calls through one of our trunks (CallWithUS) running out our credit. The CallWithUS call records show calls made from this extension to a crazy list of different countries (that we do not call to).

 

I changed the SIP password for the extensions but this happened again. So far 3 times.

 

What is your recommendation to protect the PBXnSIP server against this?

 

I had also set a Trusted IP Addresses to every extension but this did not make the trick either.

 

Thanks.

Link to comment
Share on other sites

I detected someone form outside our network registering in one of our extensions to place calls through one of our trunks (CallWithUS) running out our credit. The CallWithUS call records show calls made from this extension to a crazy list of different countries (that we do not call to).

 

I changed the SIP password for the extensions but this happened again. So far 3 times.

 

Don't choose trivial passwords! There is a reason that the PBX has a password policy (though it was a marketing decision to disable it by default).

 

Check the following passwords/items:

  • Set the password policy for the domain
  • Set a reasonably safe system admin password
  • Set reasonably safe extensions passwords
  • Set a reasonably safe domain provisioning password
  • Specify an outbound proxy for trunks, and possibly explicitly specify the addresses for inbound traffic.

Link to comment
Share on other sites

Don't choose trivial passwords! There is a reason that the PBX has a password policy (though it was a marketing decision to disable it by default).

 

Check the following passwords/items:

  • Set the password policy for the domain
  • Set a reasonably safe system admin password
  • Set reasonably safe extensions passwords
  • Set a reasonably safe domain provisioning password
  • Specify an outbound proxy for trunks, and possibly explicitly specify the addresses for inbound traffic.

 

Just to add to this, may be you can create some dial plans based on who can call where/who etc and assign them accordingly.

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...