During a firmware update on a Room Alert 32S, 12S or 3S, your system communicates with your device using a combination of standard network traffic and a high volume of UDP packets.<\/p>\n\n\n\n
The update process includes the following steps:<\/strong><\/p>\n\n\n\n The actual firmware transfer process may generate a rapid burst of UDP traffic while firmware data is being transmitted to the device; this behavior is expected and is required to complete the update. Because firmware updates involve direct low-level communication with the hardware, the traffic pattern can look unusual compared to normal web browsing or office applications.<\/p>\n\n\n\n When HTTPS is enabled, communication between the utility and the device is encrypted and requires additional negotiation and validation steps.<\/p>\n\n\n\n This can introduce:<\/p>\n\n\n\n In environments with strict endpoint protection, deep packet inspection, or advanced firewall policies, HTTPS-enabled communication is more likely to experience interruptions during the firmware update process.<\/p>\n\n\n\n Many modern security platforms are designed to detect behavior commonly associated with malicious activity, including high-rate UDP traffic, unexpected device-to-device communication, and repeated packet transmissions. As a result, some security products may rate-limit packets, modify packet headers in transit, drop UDP traffic, interrupt the firmware transfer, or terminate the update entirely.<\/p>\n\n\n\n Examples of software that may affect updates include:<\/p>\n\n\n\n In some environments, the security software may interpret the firmware transfer as suspicious network activity or a flooding event.<\/p>\n\n\n The traffic generated during the firmware update process is expected behavior required to transfer firmware data to the device; however, because the transfer involves rapid UDP communication, some security systems can classify the activity as suspicious unless appropriate exceptions are configured.<\/p>\n\n\n<\/div><\/div>\n\n\n\n If updates are failing consistently, we recommend:<\/p>\n\n\n\n Your IT or security administrator may need to explicitly allow this traffic if aggressive filtering or flood protection is enabled.<\/p>\n","protected":false},"excerpt":{"rendered":" During a firmware update on a Room Alert 32S, 12S or 3S, your system communicates with your device using a combination of standard network traffic and a high volume of UDP packets. The update process includes the following steps: Step Protocol 1. Discover the device on the network UDP 2. Unlock the device\u2019s firmware update […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0},"categories":[2,9],"tags":[],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\t\nStep<\/th> Protocol<\/th><\/tr><\/thead> 1. Discover the device on the network<\/td> UDP<\/td><\/tr> 2. Unlock the device\u2019s firmware update mode<\/td> HTTP or HTTPS<\/td><\/tr> 3. Transfer firmware data to the device<\/td> Rapid UDP or HTTP\/HTTPS (device dependent)<\/td><\/tr> 4. Verify and completing the update<\/td> UDP and\/or HTTP\/HTTPS<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Updates Over HTTPS<\/h2>\n\n\n\n
\n
Updates On Networks With Endpoint Security<\/h2>\n\n\n\n
\n
Common symptoms of security software interference include:<\/h3>\n\n\n\n
\n
Best Practices<\/h2>\n\n\n\n
\n