LogMeIn support sites no longer support Microsoft's Internet Explorer (IE) browser. Please use a supported browser to ensure all features perform as they should (Chrome / FireFox / Edge).

The GoTo support site no longer supports Safari 15. Please upgrade your browser to Safari 16 (or newer) or switch to a supported browser such as Google Chrome, Mozilla Firefox, or Microsoft Edge.

Anchored by your desk phone? Access your calls, meetings, and messaging on any device. Switch to the GoTo app now.

We are currently experiencing an unplanned outage for this product. View Service Status
  • Support
  • Products

    Explore support by product

    GoTo Connect

    All-in-one phone, meeting and messaging software

    GoTo Meeting

    Video and audio meeting software

    GoTo Webinar

    All-in-one webinar and virtual events software

    GoTo Room

    Conference room hardware

    GoTo Training

    Online training software

    OpenVoice

    Audio conferencing software

    Grasshopper

    Lightweight virtual phone system

    join.me

    Video conferencing software

    LogMeIn Resolve

    IT management & support

    LogMeIn Resolve MDM

    Mobile device management

    LogMeIn Pro

    Remote device access

    LogMeIn Central

    Remote monitoring & management

    LogMeIn Rescue

    Remote IT support

    GoToMyPC

    Remote desktop access

    GoToAssist

    Remote support software

    Hamachi

    Hosted VPN service

    RemotelyAnywhere

    On-prem remote access solution
  • Community
  • Trainings
  • Service Status
  • Try the improved My Cases portal

    Easily manage your ticket, track its status, contact us from an existing case, and more.

    Sign in to try
  • Language selector icon Language selector icon
    • English
    • Français
    • Italiano
    • Deutsch
    • Español
    • Português
    • Nederlands
  • Contact Support
  • Service Status
  • User Avatar User Avatar
    • Support
    • Contact Support
    • Browse Products
    • Service Status
    • Community
    • Trainings
    • Sign in
    • User Avatar
    • My Account
    • Personal Info
    • Sign In & Security
    • My Cases
    • Billing Center
    • https://link.goto.com/myaccount-billing
    • My GoTo Connect
    • My Meetings
    • My Webinars
    • My Trainings
    • My Conferences
    • My Resolutions
    • My Mobile Devices
    • My Sessions
    • My Sessions
    • My Incidents
    • Sign out
  • Phones and meetings
  • Get Started
  • Network Readiness
  • Network Settings
product logo
Back button image Back
Back button image
product logo

NAT keepalive setting requirements

Our handsets initiate connections with our cloud infrastructure and use NAT keepalives to keep the binding open. If your firewall drops these NAT keepalives or ‘prunes’ more aggressively than every 300 seconds, the handsets will not function properly. They will be able to call out, but will not receive inbound calls (inbound calls will go straight to voicemail).

The following settings are required. If updates need to be made, please contact your IT or ISP provider.

Increase UDP Timeouts

  • UDP sessions are typically given shorter timeout intervals on firewalls. The default for most is 30 seconds, which is too aggressive for an application like SIP. Increase UDP timeouts to a minimum of 90 seconds, however, our recommendation is 300 seconds or longer.
  • You can specify that only SIP sessions have increased timeouts rather than all UDP sessions, if your firewall allows for that specific delineation. Just make sure to set timeouts for UDP ports 5060, 5061, 5080, 5081, and 5082 of at least 300 seconds, as those are the standard SIP ports we use (and most user agents (phones) do as well).

Enable Consistent/Persistent NAT

  • In much the same way that ensuring the NAT binding does not get dropped or pruned — ensuring that the NAT binding (public IP and UDP port) remains the same for each phone’s internal private IP address and port pairing will help with an application like VoIP.  If that binding were to change suddenly, there would be a discrepancy between the IP address/port to which the VoIP server thinks it should be sending requests and the phone's current binding in the firewall.
    • For example, a phone can make calls because NAT is working, but can’t receive calls because the VoIP server hasn’t received a new REGISTER request from that phone since that binding changed and is therefore sending it to the old IP address/port pairing.
  • Most of the other settings are generic, whereas this one is more vendor-specific (SonicWall and Juniper for example). It is a recommended setting if your firewall has it available, but unlike the other settings, it is not usually an issue if it cannot be configured.
Related Articles:
  • Internet requirements
  • PoE switch requirements
  • Router/firewall setting requirements
  • SIP Application Layer Gateway setting requirements
Article last updated: 9 May, 2023
You are viewing the latest version of this article.

Need help?

Contact icon Contact support
Manage Cases icon Manage cases
Community icon Ask the Community
Training icon Attend trainings
Video icon Watch videos
  • Language selector icon Language selector icon
    • English
    • Français
    • Italiano
    • Deutsch
    • Español
    • Português
    • Nederlands
  • About Us
  • Terms of Service
  • Privacy Policy
  • Trademark
  • Do Not Sell or Share My Personal Info
  • Browse Products
  • Copyright © 2025 GoTo Group, Inc. All rights reserved

Collaboration Products

GoTo Connect

GoTo Meeting

GoTo Webinar

GoTo Training

join.me

Grasshopper

OpenVoice

Remote Solutions Products

GoTo Resolve

Rescue

GoToAssist

Access Products

Pro

Central

GoToMyPC