[VoiceOps] Issues with ISPs blocking SIP 5060 - 5061

[Mark R Lindsey]

In 2005, the FCC fined a NC based ISP $15,000 for blocking VoIP ports.

	http://transition.fcc.gov/eb/Orders/2005/DA-05-543A2.html

Since that time, in my IANAL way, I've always worked as if  "section 201(b) of the Communications Act of 1934, as amended" meant you couldn't block VoIP ports simply for the sake of preventing VoIP use. 

>>> mark at ecg.co +1-229-316-0013 http://ecg.co/lindsey

On Nov 20, 2013, at 19:14 , Hiers, David <David.Hiers at adp.com> wrote:

> I don’t know of anything that obligates an ISP to carry any particular form of traffic.  All the AUPs that I've seen have plenty of room for them to block pretty much whatever they want, but it's been a while since I've one do this kind of thing.
>  
> You might get some traction with your state consumer protection or public utility office.
>  
>  
>  
> David
>  
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of David Thompson
> Sent: Wednesday, November 20, 2013 15:51
> To: voiceops at voiceops.org
> Subject: [VoiceOps] Issues with ISPs blocking SIP 5060 - 5061
>  
> Has anyone been having problems lately with ISPs’ actively blocking UDP 5060 – 5061? I’m having problems with Road Runner in Hawaii apparently blocking those ports preventing me from communicating with the customers PBX. My customer has a ticket open with them but we aren’t confident that we’ll get anywhere with them. If we don’t is there an authority that we can speak with that can make them open those ports or face sanctions?
>  
> David Thompson 
> Network Services Support Technician 
> (O) 858.357.8794 
> (F) 858-225-1882 
> (E) dthompson at esi-estech.com
> (W) www.esi-estech.com
>  
> 
> This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
> 
> 
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20131120/07988d7f/attachment.html>