Project

General

Profile

Actions

Bug #16817

open

Unable to make specific outbound VOIP calls unless "Disable hardware checksum offload" is checked on system_advanced_network.php

Added by Garrett Culver about 10 hours ago. Updated about 9 hours ago.

Status:
Incomplete
Priority:
Normal
Assignee:
-
Category:
Hardware / Drivers
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
26.03
Affected Architecture:
All

Description

Details:

Hardware:
• Netgate SG4860, in place for 5+ years, no recent settings changes.
• Sangoma P325 VOIP phones connected to an externally hosted Switchvox software PBX; system in place for 2+ years, no recent settings changes.
• When pfSense+ firmware was updated from 25.07.1 to 25.11.1, the bug seemed to be introduced. Bug persists in 26.03.

When we (USA based) place outbound long-distance calls without the country code, they fail to go through, despite the fact that our switchvox software has a rule that should "add" the "+1" automatically. In other words, functionally, dialing "555-555-5555" should be exactly the same as dialing "1-555-555-5555." From the software hosting provider NOC: " ...the call is not being sent to the provider. Instead, the phone itself is not sending the second INVITE required for authentication to proceed due to this reason the fails. "

However, visiting system_advanced_network.php and checking the box to "Disable hardware checksum offload" then rebooting the device appears to resolve the issue.

Was there a driver change or is there another bug that may affect others? I understand that this may be specific to the SG-4860 so it may not be high priority, but if it is more widespread I would hope a solution could be found that helps more people.

Actions #1

Updated by Jim Pingle about 9 hours ago

  • Status changed from New to Incomplete

There is no known issue with passing any type of traffic on that platform with hardware checksums enabled.

There isn't enough information here to classify this as a bug, discussing it further and getting packet captures to analyze on the Forum would be a better way to proceed.

Actions

Also available in: Atom PDF