CNET On Port Blocking

CNET has followed up on my post a few weeks back about Port Blocking.

My gut says port blocking is a bigger issue than people know, and many chalk it up to their own lack of tech knowledge.

Last year Cox Communications blocked Port 25 to combat spam. It really didn’t work, as Cox servers remain on the spam block lists and I found a way around the issue using HotSpotVPN.com’s service, thus maintaining my ability to use a remote hosted SMTP server of my own choosing.

With respect to VoIP, my co-host on the World Technology Roundup, Ken Rutkowski, had a problem of port blocking with Comcast, his high speed ISP a few weeks back. While the problem has cleared up, and while our senior brass friends inside Comcast plead it never happened, but the tech folks did some testing and they have the information.

Bottom line is port blocking is a sleeping giant size issue, and facts have shown that Adelphia and a few others are blocking the ports that affect some, if not all of the VoIP carriers.

I’m also glad that nothing really has changed over at CNET. They still seem to follow Ken and I on all the news that matters..

4 thoughts on “CNET On Port Blocking”

  1. AT&T’s CallVantage VoIP calls blocked

    Some VoIP calls being blocked | CNET News.com Cnet.com has reported that some users are having issue receiving inbound calls. This has once again raised the issue of whether or not cable broadband companies are blocking VoIP calls. I discussed…

  2. AT&T CallVantage VoIP calls blocked

    Some VoIP calls being blocked | CNET News.com Cnet.com has reported that some users are having issue receiving inbound calls. This has once again raised the issue of whether or not cable broadband companies are blocking VoIP calls. I discussed…

Comments are closed.