The Planet still being used / blocked UDP traffic

**Russell** · 05-16-2009 07:32 PM

The following is from my router log. The IP addresses generating all the traffic seem to be coming from The Planet (174.132.131.131 and 74.52.58.50), Softlayer (67.228.251.106) and Slicehost (67.23.11.26). I'm puzzled - I thought VOIPo had moved away from the Planet. Also, I'm curious about all this traffic every few seconds - and it's getting blocked anyway. Do all providers generate this much traffic? Is this normal?

2009/05/16 21:05:55 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/16 21:05:56 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/16 21:06:00 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/16 21:06:13 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/16 21:06:23 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/16 21:06:23 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/16 21:06:28 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/16 21:06:40 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/16 21:06:40 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/16 21:06:41 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/16 21:06:45 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/16 21:06:59 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/16 21:07:08 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/16 21:07:08 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/16 21:07:13 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/16 21:07:25 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/16 21:07:25 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/16 21:07:27 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/16 21:07:30 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/16 21:07:41 : Blocked access attempt : UDP from 208.43.97.218:46154 to MY.IP.ADDR:16448
2009/05/16 21:07:44 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/16 21:07:53 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/16 21:07:53 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/16 21:07:58 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/16 21:08:10 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/16 21:08:10 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/16 21:08:12 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/16 21:08:15 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/16 21:08:29 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/16 21:08:38 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/16 21:08:38 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/16 21:08:43 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/16 21:08:55 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/16 21:08:55 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/16 21:08:57 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/16 21:09:00 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/16 21:09:14 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/16 21:09:23 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/16 21:09:23 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/16 21:09:28 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/16 21:09:40 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/16 21:09:40 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/16 21:09:42 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/16 21:09:45 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/16 21:09:59 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/16 21:10:08 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/16 21:10:08 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/16 21:10:13 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/16 21:10:25 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/16 21:10:25 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/16 21:10:27 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/16 21:10:30 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/16 21:10:44 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/16 21:10:53 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/16 21:10:53 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/16 21:10:58 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/16 21:11:10 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/16 21:11:10 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/16 21:11:12 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/16 21:11:15 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/16 21:11:29 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/16 21:11:38 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/16 21:11:38 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/16 21:11:43 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/16 21:11:55 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/16 21:11:55 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/16 21:11:57 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/16 21:12:00 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/16 21:12:14 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/16 21:12:23 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/16 21:12:23 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/16 21:12:28 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/16 21:12:40 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/16 21:12:40 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/16 21:12:42 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/16 21:12:45 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/16 21:12:59 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/16 21:13:08 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/16 21:13:08 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/16 21:13:13 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/16 21:13:25 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/16 21:13:25 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/16 21:13:27 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/16 21:13:30 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/16 21:13:44 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/16 21:13:53 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/16 21:13:53 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/16 21:13:58 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/16 21:14:10 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/16 21:14:10 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/16 21:14:12 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/16 21:14:15 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/16 21:14:29 : Blocked access attempt : TCP from 221.192.199.36:12200 to MY.IP.ADDR:9090
2009/05/16 21:14:29 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/16 21:14:38 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/16 21:14:38 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/16 21:14:43 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/16 21:14:55 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/16 21:14:55 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/16 21:14:57 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/16 21:15:00 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/16 21:15:15 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/16 21:15:23 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/16 21:15:23 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/16 21:15:28 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/16 21:15:40 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/16 21:15:40 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/16 21:15:43 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/16 21:15:45 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/16 21:16:00 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/16 21:16:08 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/16 21:16:08 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/16 21:16:13 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/16 21:16:25 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/16 21:16:25 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/16 21:16:28 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/16 21:16:30 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/16 21:16:45 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/16 21:16:53 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/16 21:16:53 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/16 21:16:58 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/16 21:17:10 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/16 21:17:10 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/16 21:17:13 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/16 21:17:15 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/16 21:17:30 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061

Internet time: Sat May 16 21:17:35 2009

**Xponder1** · 05-16-2009 07:42 PM

You need to unblock that traffic.

**Russell** · 05-16-2009 07:56 PM

Originally Posted by Xponder1

You need to unblock that traffic.

I've had VOIP for several years and multiple providers with this router and never had to forward ports or put ATAs in the DMZ. Afaik, my service is working fine. Why is the VOIPo situation different (about unblocking that traffic)?

**VOIPoDylan** · 05-17-2009 04:35 AM

Russell,
Your STUN server was still set to zeus (74.52.58.50).
I have changed it so that it uses the same SIP server you're on.

With regards to the other IPs (primarily 67.228.251.106, 174.132.131.131 and 67.23.11.26) - I believe these may be NAT Keep Alive packets. I'll ask Brandon to confirm this when he is available.

**VOIPoTim** · 05-17-2009 07:44 AM

Originally Posted by Russell

I've had VOIP for several years and multiple providers with this router and never had to forward ports or put ATAs in the DMZ. Afaik, my service is working fine. Why is the VOIPo situation different (about unblocking that traffic)?

These connections are related to keepalive and failover systems.

While we're not using The Planet for any core equipment now, it is still used in failover situations. If the traffic is blocked and anything on your account is routed to them in a failover or load scenario, your calls could fail. We highly recommend not blocking any VOIPo traffic since it could cause service issues or failure. You should see a connection from each SIP server that your traffic could come from every 20 seconds.

In terms of the keep alives, it is a little more aggressive than some since we had the Grandstream issue and wanted to be sure that our system had nothing to do with their constant connection losses. So it may be tweaked some later, but currently it's working extremely well.

We've found that even slowing it some so there's only a connection every minute causes a bunch of routers out there to close their NAT bindings and stop allowing traffic to come through.

Sure, that shouldn't be the case, but many new routers on the market want to micromanage all traffic as they see fit.

If we start decreasing it, we would need to structure it so that it could be increased to this level on a per-user basis and determine the appropriate number for some hyper-sensitive routers. Alot of providers simply rely on the devices to initiate the keepalives. Given the Grandstream situation, we could not rely on the devices to do anything at all.

So this will likely be redesigned in the future, but is a pretty sensitive area since we've seen a small decrease in the rate of it cause a surge in support tickets almost instantly in the past since a lot of routers begin blocking traffic or not accepting any incoming connections from a server besides the one the user is registered to causing some calls to fail.

Forwarding ports just make sure all this traffic is simply redirected directly to the ATA. Again it may not be needed for some users, but those with new routers that like to filter anything and everything run into issues without forwarding ports. Ultimately at least 95% of service issues with audio, dead air, or calls not completing that come through our helpdesk are resolved with port forwarding. That's the main reason it's one of our first recommendations.

What happens is that if a connection comes in on an audio port, sometimes the router won't accept it if it doesn't know exactly what it is.

Sounds crazy, but if everyone used a 2 year old router, all of this would be a non-issue.

**Russell** · 05-17-2009 08:55 AM

Originally Posted by VOIPoDylan

Russell,
Your STUN server was still set to zeus (74.52.58.50).
I have changed it so that it uses the same SIP server you're on.

With regards to the other IPs (primarily 67.228.251.106, 174.132.131.131 and 67.23.11.26) - I believe these may be NAT Keep Alive packets. I'll ask Brandon to confirm this when he is available.

Thanks, Dylan. I checked my logs this morning ... I'm still seeing traffic from zeus (it probably doesn't matter what STUN server I use, but since you mentioned changing it).

2009/05/17 10:34:38 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/17 10:34:38 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/17 10:34:40 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/17 10:34:53 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/17 10:34:53 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/17 10:35:03 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/17 10:35:10 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/17 10:35:18 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/17 10:35:23 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060

**VOIPoTim** · 05-17-2009 08:57 AM

Zeus is actually a SIP server which falls in with the others. STUN runs locally on each of them.

Originally Posted by Russell

Thanks, Dylan. I checked my logs this morning ... I'm still seeing traffic from zeus (it probably doesn't matter what STUN server I use, but since you mentioned changing it).

2009/05/17 10:34:38 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060
2009/05/17 10:34:38 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5060
2009/05/17 10:34:40 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5061
2009/05/17 10:34:53 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5061
2009/05/17 10:34:53 : Blocked access attempt : UDP from 67.23.11.26:5060 to MY.IP.ADDR:5061
2009/05/17 10:35:03 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5060
2009/05/17 10:35:10 : Blocked access attempt : UDP from 174.132.131.131:5060 to MY.IP.ADDR:5060
2009/05/17 10:35:18 : Blocked access attempt : UDP from 67.228.251.106:5060 to MY.IP.ADDR:5061
2009/05/17 10:35:23 : Blocked access attempt : UDP from 74.52.58.50:5060 to MY.IP.ADDR:5060

**Russell** · 05-17-2009 09:09 AM

Originally Posted by VOIPoTim

These connections are related to keepalive and failover systems.

While we're not using The Planet for any core equipment now, it is still used in failover situations. If the traffic is blocked and anything on your account is routed to them in a failover or load scenario, your calls could fail. We highly recommend not blocking any VOIPo traffic since it could cause service issues or failure. You should see a connection from each SIP server that your traffic could come from every 20 seconds.

In terms of the keep alives, it is a little more aggressive than some since we had the Grandstream issue and wanted to be sure that our system had nothing to do with their constant connection losses. So it may be tweaked some later, but currently it's working extremely well.

We've found that even slowing it some so there's only a connection every minute causes a bunch of routers out there to close their NAT bindings and stop allowing traffic to come through.

Sure, that shouldn't be the case, but many new routers on the market want to micromanage all traffic as they see fit.

If we start decreasing it, we would need to structure it so that it could be increased to this level on a per-user basis and determine the appropriate number for some hyper-sensitive routers. Alot of providers simply rely on the devices to initiate the keepalives. Given the Grandstream situation, we could not rely on the devices to do anything at all.

So this will likely be redesigned in the future, but is a pretty sensitive area since we've seen a small decrease in the rate of it cause a surge in support tickets almost instantly in the past since a lot of routers begin blocking traffic or not accepting any incoming connections from a server besides the one the user is registered to causing some calls to fail.

Forwarding ports just make sure all this traffic is simply redirected directly to the ATA. Again it may not be needed for some users, but those with new routers that like to filter anything and everything run into issues without forwarding ports. Ultimately at least 95% of service issues with audio, dead air, or calls not completing that come through our helpdesk are resolved with port forwarding. That's the main reason it's one of our first recommendations.

What happens is that if a connection comes in on an audio port, sometimes the router won't accept it if it doesn't know exactly what it is.

Sounds crazy, but if everyone used a 2 year old router, all of this would be a non-issue.

I appreciate your response, Tim. Quite honestly, I feel for you guys having to provide a service where just one of the variables (the router) can behave so differently!

1) From a consumer perspective, I was quite surprised by the blast of packets from 4 different IP addresses every few seconds. Since I'd never examined the traffic with any of my previous providers I can't comment on whether this is typical or not. I'm curious as to exactly what this adds to bandwidth consumption? I realize each "probe" by itself is probably small, but cannot help but wonder what it adds up to cumulatively. Whether I port forward or not, I'm still going to have this traffic.

2) Port forwarding: as I mentioned, I like the ability to have multiple ATA's behind my router. If I port forward, wouldn't this kill the ability of my other ATA's to handle calls? In a case like this will DMZing be a better option? Or, ideally, would a device that acted like a router and ATA (like the 2102?) be the solution? Were the Grandstream's (that I keep hearing mentioned) similar devices (ATA + router)?

**Xponder1** · 05-17-2009 09:14 AM

Originally Posted by Russell

I appreciate your response, Tim. Quite honestly, I feel for you guys having to provide a service where just one of the variables (the router) can behave so differently!

1) From a consumer perspective, I was quite surprised by the blast of packets from 4 different IP addresses every few seconds. Since I'd never examined the traffic with any of my previous providers I can't comment on whether this is typical or not. I'm curious as to exactly what this adds to bandwidth consumption? I realize each "probe" by itself is probably small, but cannot help but wonder what it adds up to cumulatively. Whether I port forward or not, I'm still going to have this traffic.

2) Port forwarding: as I mentioned, I like the ability to have multiple ATA's behind my router. If I port forward, wouldn't this kill the ability of my other ATA's to handle calls? In a case like this will DMZing be a better option? Or, ideally, would a device that acted like a router and ATA (like the 2102?) be the solution? Were the Grandstream's (that I keep hearing mentioned) similar devices (ATA + router)?

It's not that much traffic. It just looks like it.

**sr98user** · 05-17-2009 10:53 AM

Russell,

Since Voipo does not use SRV records anymore, I don't think the ATA is initiating the traffic to these SIP servers. I wonder why the other SIP servers are sending packets to your router unless they think that you are registered with that server.

You might want to shutdown your router and ATA (and probably your softphone too) for 5-10 minutes until the connections clear in the "Devices" page and then see if you are getting the packets from all the SIP servers.