Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Problems with changing Wan's on FortiGate firewall

Discussion in '3CX Phone System - General' started by MagicDave, Sep 21, 2017.

Thread Status:
Not open for further replies.
  1. MagicDave

    Joined:
    Mar 5, 2015
    Messages:
    2
    Likes Received:
    0
    HI,

    We are changing over from WAN1 to WAN2 on a fortigate firewall. I'm not programming the firewall, the customer is and we are having problems whenever we over the lines over. The firewall checking is failing on the first check of 5060. Is there anything I can do on the 3cx side of things or is this all firewall?
     
  2. us1

    us1

    Joined:
    Oct 19, 2015
    Messages:
    80
    Likes Received:
    21
    Without having more details of the config, this will be tough to troubleshoot. That said, the issue resides in the firewall. My assumption is the states table on the Fortigate are likely maintaining the 5060 connection on WAN1. After swapping the connection over to WAN2, try killing the states for the 3cx system or otherwise reboot the router. This will allow the traffic to use the new WAN2 (assuming the routing is setup correctly).

    At the end of the day, the configuration that worked for WAN1 should work for WAN2 if it was setup properly. This does not appear to be a 3cx issue.
     
  3. Archie Frederic

    Joined:
    Jan 31, 2017
    Messages:
    72
    Likes Received:
    1
    There's nothing you can do on the pbx side.The problem with that is port forwarding. Base on your statement, WAN1 was working fine but when transferring the cable to WAN2, your firewall checker would fail. This is because all ports required by the 3cx was port forwarded to WAN1. Tell your client to look at the ports forwarded from internal port to WAN1 then port forwards these ports to WAN2.
     
Thread Status:
Not open for further replies.