[VoiceOps] Issues with ISPs blocking SIP 5060 - 5061

Ryan Delgrosso ryandelgrosso at gmail.com
Thu Nov 21 13:54:05 EST 2013

We see this with alarming regularity. Often it conveniently corresponds 
with a marketing push from the MSO for triple play offerings. I recall 
this happened at my home when I was with one of those players, and 
suddenly my home line on my network stopped being able to talk to my 
border elements. The MSO support played the "well youll need to talk to 
your ITSP about that, OR you could just switch to our phone service" 
card at which point I explained I was my ITSP and then it magically 
started to work...

Eventually we just abandoned the usual ports completely. When this 
happens to the customer the perception is you suck and the MSO has their 
act together because THEIR phone works. Not worth the fight, since you 
will have it every promotional cycle and evidence is VERY difficult to 

On 11/20/2013 03:51 PM, David Thompson wrote:
> 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 <mailto:dthompson at esi-estech.com>
> (W) www.esi-estech.com <http://www.esi-estech.com>
> _______________________________________________
> 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/20131121/0eaec4cb/attachment.html>

More information about the VoiceOps mailing list