Problem with 2nd LAN after hard shutdown, cant ping outbound

[WalkerYYJ]

Hey all,
A little new to this, so I'm hoping I'm in the right spot for this question.

We have the following setup:

WANs:

-1 Dynamic IP on dedicated modem used for main LAN/commodity internet
-1 Static IP on dedicated modem used for PBX.

LANs:
-Main Lan for computers, printers, WIFI, etc on dedicated switches
-2nd Lan(PBX) for Asterisk/Phones also on dedicated switches

We have been running great for the past few months, however over the weekend a power outage lasted long enough to drain all the UPSs to zero and everything went down hard (Servers, PFSense, terminals, etc.)  (we hadn't gotten around to setting up remote shutdown…....Oops...)

Anyway I come back into the office today and all of the phones (Digium IP phones) are reporting communication errors. I check the servers and it seems that nothing on LAN2 (we call it the PBX lan) is going out.
If I go to the PFsense box I can ping outbound from WAN2(which is what PBX is bound too) but when I try to ping outbound from PBX I get a time out. Everything has been rebooted "cleanly" since the power down, but clearly something has been muddled.

I'm not sure if this is a hardware error or something but I was hoping someone here could look at our configs and see if anything looks off before I start pulling hardware apart. Its possible that PFsense had NOT been powered down since it was first setup to an operational state so depending on when/how a setting is saved, there may or may not be a config problem here.

Thanks!

[viragomann]

Are your outbound NAT rules working correctly?
You have to set up manual outbound NAT rules to tell pfSense to translate packets from PBX to WAN2 address. Otherwise the packets get the WAN address, which is a private one and will not be routed in the WAN2 net.

[WalkerYYJ]

@viragomann:

Are your outbound NAT rules working correctly?
You have to set up manual outbound NAT rules to tell pfSense to translate packets from PBX to WAN2 address. Otherwise the packets get the WAN address, which is a private one and will not be routed in the WAN2 net.

These are the current outbound manual rules… I "think" these are right?