3cx failover with to different ISp's

[Mark Jones]

Hi i would like to set 3cx up to failover using two different ISp's. is this possible and where are the documents or have anyone done this before that can make a recommendation.

 

[Saqqara]

Yes it can be done, is your existing SIP provider using IP authenication or username and password.

If IP then you need to contact them to see if they can handle different wan IP's

Then you need a router with dual or more wan ports - and setup the necessary rules to route traffic from the 3cx server down wan1, if wan1 goes down then failover to wan2.

Within 3CX management, change Public IP Network Settings to use Dynamic IP

We use draytek routers , and have not issues - but our sip provider is using username and password.

Only issue if you have remote connections (stun, sbc , mobile devices) - it can take 6hrs for the dns to populate if using std / pro license

 

[Mark Jones]

we are not using sip providers, we have a pri gateway.

thanks for shedding some light on this.

 

[cobaltit]

Then the different ISP portion doesn't matter unless you have remote phones/devices.

 

[leejor]

we are not using sip providers, we have a pri gateway.

So...it is the PRI, that you want going to a different provider, or to the same provider, over a different ISP?

 

[Mark Jones]

So...it is the PRI, that you want going to a different provider, or to the same provider, over a different ISP?

3cx

 

[cobaltit]

So looking back on your other threads, it seems to already have failover setup. The fact that you want to use different ISPs is mostly irrevelant to 3CX given the fact that your dial tone is provided via a local gateway and the how is dependent on your actual network design. But the document referenced in your other thread covers pretty much the only thing you have to be concerned about with different public IPs (the fact that it is actually different ISPs) doesn't matter. The thing to note is that when you failover, 3CX will reach out to the internet via the method you configure. If that path is a different public IP than what the primary server used, the FQDN will update accordingly. Beyond that there really isn't much to it.

 

[Mark Jones]

yes thanks! I do have it all set up but we are planning to make it better,with our backup data connection, just in case we have an outage on our current circuit.

 

[Mark Jones]

3cx

the pri is with the same provider, but just incase our data circuit goes down.

 

[leejor]

The PRIs I usually deal with are a direct T1 connection to a providers class 5 PSTN switch. If your gateway goes to a provider other than your ISP, then it just register, or your provider has the static IP of the gateway. If you are able to make use of a second internet connection, then I have to assume you have a router with two different public IPs and is able to balance traffic between the two, or do a complete switch from one to the other if one fails. the question is hen...how does you provider know where to send calls, what your "new" IP is. Do you use an FQDN (3CX's) or DNS service? Will the Gateway know to re-register when a switch is make, or is there a delay? Some providers get upset if you re-register too often.

 

[Mark Jones]

The PRIs I usually deal with are a direct T1 connection to a providers class 5 PSTN switch. If your gateway goes to a provider other than your ISP, then it just register, or your provider has the static IP of the gateway. If you are able to make use of a second internet connection, then I have to assume you have a router with two different public IPs and is able to balance traffic between the two, or do a complete switch from one to the other if one fails. the question is hen...how does you provider know where to send calls, what your "new" IP is. Do you use an FQDN (3CX's) or DNS service? Will the Gateway know to re-register when a switch is make, or is there a delay? Some providers get upset if you re-register too often.

Now the backup ISP is not in place yet, we are planing this out as we speak. we currently use 3cx fqdn and we would like to manage our own dns, which require a reload, in which we are willing to do. the gateway is setup to point traffic to the primary server, and secondary server in a fail over scenario.

 

[Mark Jones]

Now the backup ISP is not in place yet, we are planing this out as we speak. we currently use 3cx fqdn and we would like to manage our own dns, which require a reload, in which we are willing to do. the gateway is setup to point traffic to the primary server, and secondary server in a fail over scenario.

so it the pri circuit goes down, we would use SIP trunks as a backup.

 

[leejor]

Does your PRI provider have a plan in place that will route incoming calls to the SIP provider if the PRI fails? that is a big issue. Outgoing calls can continue over another provider, and even show your "regular" caller ID, but what happens to incoming calls?

 

[Mark Jones]

Does your PRI provider have a plan in place that will route incoming calls to the SIP provider if the PRI fails? that is a big issue. Outgoing calls can continue over another provider, and even show your "regular" caller ID, but what happens to incoming calls?


yes we will set up a cf no answer to one of the sip trunks.

 

[leejor]

If forwarding is being done on a "main" number, be sure to check (with your PRI provider) how many simultaneous calls this feature will forward. In many cases, providers will limit this to one. If this is being done on DID's you will need to check that DID information is passed correctly, and that DID rules will handle any differences (from the PRI provider) in the number being sent. You will want to test a number of scenarios once everything is in place.

 

[Mark Jones]

If forwarding is being done on a "main" number, be sure to check (with your PRI provider) how many simultaneous calls this feature will forward. In many cases, providers will limit this to one. If this is bing done on DID's you will need to check that DID information is passed correctly, and that DID rules will handle any differences (from the PRI provider) in the number being sent. You will want to test a number of scenarios once everything is in place.

Awesome thanks for the heads up!

 

[chitownpbx]

Here is where I see the problem when I test. When the outside IP changes to carrier 2, all new calls have 1 way audio. When I look under the parameters settings for Media server and a few other entries, the Carrier 1 static IP address is listed. If I manual change to the new Carrier 2 IP address everything works fine. Once carrier 1 comes back up I have the same problem until I change the address again.

My thought was to replace those outside IP addresses with the Dual WAN router (inside) address. Any thoughts? Will 3CX kick up another error.

The registration I am not worried about as I have both carriers IP addresses whitelisted in my trunk. This part works fine.

 

[leejor]

@chitownpbx, you really be starting your own post, rather than "hijacking" an existing post, as there may be totally different issues at play here.




Report