u/Ballads4Llamas

Yesterday we renewed our lease lines and got a new public IP.

I created the new interface and default WAN gateway, traffic is flowing correctly and there has been no effect to our RDS and WireGuard services.

Unfortunately, the Alcatel PBX we host onsite receives inbound calls to all but our main DDI and on those lines that the calls are received the callers can be heard but their voice cannot be heard by the recipient. After 10-11 seconds the call will then drop showing “call failed” for the inbound caller.

Initially I changed the destination address on our TCP and UDP rules in NAT to reflect our new public IP. I also updated the Outbound Mappings to the new IP.

This is when during testing I discovered the above issue. So I rang the comms provider and confirmed that the SIP Trunks and PBX ports were correct against the aliases set but they were set correctly.

I have been running test packet captures and can see the following packets from the DDIs that do connect when rung:

INVITE
100 TRYING
183 SESSION PROGRESS
180 RINGING
200 OK
ACK SIP
BYE SIP
200 OK (BYE)

I have checked the states and cannot see any references of our old public IP in source or destination when using filter expression. I did not want to clear the states without confirmation of this being the issue as I was unsure of the knock-on effect (I only have 1 years experience) with pfSense.

I have been through Netgates Firewall Best Practices for VoIP video and our setup matches the recommended setup (albeit this is from 2017)

The only other thing I noticed was that the previous public IP used by the outgoing NAT had been set up as a Virtual IP. We now only have 1 public IP from our ISP so I have entered that directly as the Destination Address on the Port Forward and NAT Address on the Outbound Mapping.

Any assistance or advice would be greatly appreciated! :)

UPDATE: I would love to claim I fixed this, I spent most of the night reviewing the rules, verifying the NAT rules and outbound and listening to my own voice via packet traces (I didn’t realise you could do that with SIP!)

I walk in this morning and it works… I am thinking maybe I missed a state referencing the old public IP or there is some sort of DNS’ing with our new public IPs that causes issues with VoIP?

I’m glad it’s fixed, but annoyed I couldn’t solve the mystery.

Hey all,

I am dealing with an issue on a 2-node Hyper-V Cluster with Storage Spaces Direct (Windows Server 2016 Datacenter). Every month I will apply the latest windows cumulative update using the following steps:

1. Drain roles on HV-01
2. Verify roles are all on HV-02
3. Install updates
4. Restart HV-01
5. Monitor Storage job repairing using "Get-StorageJob" and "Get-VirtualDisk" commands.
6. Repeat process for HV-02

This week HV-01 had just finished repairing and now states HV-01-VOL1's Operational Status is "No Redundancy" and Health Status is "Unhealthy". HV-02-VOL2 is showing as OK and Healthy.

HV-01 is in a paused state so we are currently running on a single hypervisor.

On Server Manager on HV-02 the following error is beginning to crop up:

HV-02	7	Error	Disk	System	HV-02 7 Error Disk System

And:

The device, \Device\Harddisk9\DR9, has a bad block.

On Failover Cluster Manager all Physical Disks are showing as healthy with the Virtual Disk in a Unhealthy, NoRedundancy state. I have restarted HV-01 hoping that the repair job corrects the issue but it went into the same failed state and shows the repair job as suspended.

This is an issue I have not encountered (nor hoped to encounter) any advice would be greatly appreciated.