Knowledge Article

< Back
You are here:

UDP Timeout Test

UDP timeout refers to the length of time that a device or system will wait for a response to a UDP (User Datagram Protocol) message before timing out and discarding the message. UDP is a connectionless protocol that is often used for real-time, low-latency communications, such as video and voice over IP (VoIP) and online gaming.

Test Methodology

This Reply Cloud test establishes UDP communication from the Sidekick or Reply Desktop Application through a location Firewall server to determine how much time a UDP connection will remain active in the Firewall and along the entire network path before dropping if not refreshed with continuous traffic to keep the UDP ports open.  The test range is MAX: 300 seconds MIN: 30 seconds.


The specific steps for changing the UDP timeout setting will depend on the device or system that you are using. Here are some general guidelines for adjusting the UDP timeout setting on different types of devices:

  • On a router or firewall:
    • Log in to the device’s web-based management interface.
    • Navigate to the advanced settings or firewall settings.
    • Look for a setting related to UDP timeout or NAT timeout.
    • Change the value of the timeout setting to the desired value.
    • Save the changes and apply them to the device.

  • On a Linux or Unix system:
    • Open the sysctl.conf file in a text editor. This file is usually located in the /etc directory.
    • Add a line with the following syntax: net.ipv4.udp_rmem_min = value
    • Replace “value” with the desired timeout value in bytes.
    • Save the file and apply the changes by running the following command: sysctl -p
  • On a Windows system:
    • Open the Command Prompt as an administrator.
    • Type the following command and press Enter: netsh int ip set global udpconsentexpireduration=value
    • Replace “value” with the desired timeout value in milliseconds.
    • Close the Command Prompt.

It is important to note that changing the UDP timeout setting may affect the performance and behavior of your device or system, so you should carefully consider the implications of any changes that you make. You may also want to consult the documentation for your specific device or system to see if there are any recommended or recommended timeout values.