If the port is open then it is vulbnerable. It doesn't matter whose backbone it is on.
There are lots of ways to protect it though. We are big fans of using mesh VPN's and removing that as an open port altogether. We have found our chosen method scales pretty well. In the meantime, your firewall might be able to limit connections per second from an IP address to that port. With some firewall products, we do that AND we block countries altogether (depending on the customer and their geographic footprint). There are lots of things you can do but you HAVE to do them or suffer the consequences. On Sun, Dec 16, 2012 at 2:02 PM, Tommy Laino <[email protected]> wrote: > > > Yes I know that 5060 is used for remote users. I had it > opened because they are going to be deploying a remote sales > team in a few months. They are using Comcast which has a > shared pipe. I am wondering if that has anything to do with > it. When I do remote deployments they almost exclusively use > FiOS which is a dedicated pipe. > -- > Tommy Laino > Dome Technologies > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013! <http://sipxcolab2013.eventbrite.com/?discount=tony2013> -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
