Results 1 to 10 of 33

Thread: The Planet still being used / blocked UDP traffic

Threaded View

Russell The Planet still being used /... 05-16-2009, 07:32 PM
Xponder1 Re: The Planet still being... 05-16-2009, 07:42 PM
Russell Re: The Planet still being... 05-16-2009, 07:56 PM
VOIPoDylan Re: The Planet still being... 05-17-2009, 04:35 AM
Russell Re: The Planet still being... 05-17-2009, 08:55 AM
VOIPoTim Re: The Planet still being... 05-17-2009, 08:57 AM
VOIPoTim Re: The Planet still being... 05-17-2009, 07:44 AM
Russell Re: The Planet still being... 05-17-2009, 09:09 AM
Xponder1 Re: The Planet still being... 05-17-2009, 09:14 AM
burris Re: The Planet still being... 05-17-2009, 12:17 PM
Russell Re: The Planet still being... 05-17-2009, 01:13 PM
burris Re: The Planet still being... 05-17-2009, 02:32 PM
Xponder1 Re: The Planet still being... 05-17-2009, 02:56 PM
chpalmer Re: The Planet still being... 05-17-2009, 03:26 PM
Russell Re: The Planet still being... 05-17-2009, 04:40 PM
sr98user Re: The Planet still being... 05-17-2009, 10:53 AM
Russell Re: The Planet still being... 05-17-2009, 01:12 PM
sr98user Re: The Planet still being... 05-17-2009, 06:47 PM
Russell Re: The Planet still being... 05-17-2009, 09:11 PM
sr98user Re: The Planet still being... 05-20-2009, 03:58 PM
Russell Re: The Planet still being... 05-20-2009, 06:34 PM
Previous Post Previous Post   Next Post Next Post
  1. #7
    Join Date
    Feb 2007
    Location
    Irvine CA
    Posts
    1,542,128,044

    Default Re: The Planet still being used / blocked UDP traffic

    Quote Originally Posted by Russell View Post
    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.
    Last edited by VOIPoTim; 05-17-2009 at 07:53 AM.
    Timothy Dick
    Founder/CEO
    VOIPo.com

    Interact with VOIPo: Twitter, Facebook

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •