We've seen some interesting connectivity issues for ATT users recently. The most recent was some sort of ALG proxy on anything destined to udp/4569. This appears to intercept registration traffic and then selectively forward it on. I'm at a loss as to why this is happening. Last weekend ATT stopped allowing one of the subnets for the stats server in their routing table too. That was a bit easier to troubleshoot and easier to reach someone on their backbone with clue. The stats server isn't a critical part of the network either. If you're having any issues, please try registration on port 4566. I'll stress again, this really isn't an AllStar issue, it's a crappy ISP breaking the internet issue. There's not much the admin team can do if your ISP isn't going to route packets properly :( -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net
While I would agree that many ISP's are allays looking for a chance to mess things up for VOIP services, One has to consider how many complex types of attacks to their vast networks they get, Most times I doubt it is intentional, but not always. Many hacks are just looking for the knowledge of what it takes to disrupt communications. ...mike/kb8jnm On 6/23/2018 2:26 PM, Bryan Fields wrote:
We've seen some interesting connectivity issues for ATT users recently. The most recent was some sort of ALG proxy on anything destined to udp/4569. This appears to intercept registration traffic and then selectively forward it on. I'm at a loss as to why this is happening.
Last weekend ATT stopped allowing one of the subnets for the stats server in their routing table too. That was a bit easier to troubleshoot and easier to reach someone on their backbone with clue. The stats server isn't a critical part of the network either.
If you're having any issues, please try registration on port 4566.
I'll stress again, this really isn't an AllStar issue, it's a crappy ISP breaking the internet issue. There's not much the admin team can do if your ISP isn't going to route packets properly :(
On 6/23/18 2:41 PM, Mike wrote:
One has to consider how many complex types of attacks to their vast networks they get,
Not my pig, Not my farm.
Most times I doubt it is intentional, but not always.
The issue is the total lack of clue on their part, don't intentionally break how the internet works. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net
The issue is the total lack of clue on their part, don't intentionally break how the internet works.
The point is you are wanting to 'blame' them. How do you know it is something of their creation and not a response to a attack or just a attack itself. I don't like them, but not willing to go as far as to blame them. All of us in VOIP will face our own similar network security issues soon enough. Who do we blame then ? Still not your pig - not your farm ? They are likely doing what they can in response to a attack on their network. Same as you would in switching ports in response to a problem. It does not 'fix it', it just makes do. Problem is still there. So if you were them, would you do nothing and jeopardize the whole network ? I ask that you think about it more broadly. ...mike/kb8jnm On 6/23/2018 2:56 PM, Bryan Fields wrote:
On 6/23/18 2:41 PM, Mike wrote:
One has to consider how many complex types of attacks to their vast networks they get, Not my pig, Not my farm.
Most times I doubt it is intentional, but not always. The issue is the total lack of clue on their part, don't intentionally break how the internet works.
participants (2)
-
Bryan Fields -
Mike