Is it Possible to have a "High-Availability" Solution with Multiple SPs?

[Torvette]

Hi, folks.

Here is the proposed scenario:

SP1 = Service Provider 1, (let's say, CallCentric), with a local DID
SP2 = Service Provider 2, (let's say, freephoneline.ca) with a second local DID (but obviously distinct from the DID with SP1)

(I mean, if I could somehow have the same DID, but simultaneously with two distinct SPs, that would be AWESOME, but I don't think it's possible).

I want to provide a high-availability solution, whereby SP1 is 'the preferred SP', always to be used when everything is working), and SP2 is only engaged when there is a perceived service outage with SP1.

Kind of like an active/passive scenario, but with service providers.  The solution I am trying to achieve is similar to what can be done with IP dynamic routing (e.g. OSPF or EIGRP).

(1) Is there a way to 'monitor' SP1 for any service outage, and if there is an outage, effectively disengage SP1, and use SP2 instead? (In essence, fail over to SP2 if SP1 is 'down')

(2) To add complexity, but a more robust solution, I'd also like to be able to 'fail back' to SP1 when service to SP1 has been restored.

(3) I need all this to happen auto-magically.


Here is how this helps me:

Inbound Calls:

I have a toll-free number for customers, where they dial the toll-free number and get connected to any phone I choose (preferably, SP1).  If I notice an outage, I can make a manual change at the toll-free number provider to direct calls to my SP2, just until SP1 has recovered.  I could implement a 'follow me' with both numbers, but I think that if SP1 was having a service outage, I would likely not be able to accurately predict the behaviour.   I have to work on making this portion of the HA solution auto-magic, but one step at a time.


Outbound Calls:

I suppose my staff could just punch in **2 to invoke SP2 for their outbound calls, but they are not tech savvy, and too much confusion would arise... and there would be too many fist-shaped holes in my office's drywall from having to explain things over and over.  With an auto-magic fail-over to SP2, my drywall repairs would be drastically reduced.

How far out of reality am I heading with this idea?  Any thoughts on how I could achieve my goal?

Many thanks in advance!

[Lavarock7]

I ended up moving my toll free number to a Voip provider that had more call options than the one who was managing it before.

Some VOIP services have options for what happens to a call if there is "nobody home" so to speak :-)

These are inbound call solutions at the VOIP provider.

CallCentric - Call Treatment:

Not registered - Specifies that this rule should only apply when your Callcentric phone is not registered with the Callcentric service. Not registered means that your user agent (Softphone or telephone adapter) is either unplugged, not running (for software user agents), not configured, has a loss of power, or your internet connection is down. This would be the case in any situation where you cannot place a call from your Callcentric phone because of one of the above situations.

VOIP.MS - Manage DID - Failover:

Aditional Failover Options: This setting let you define where to redirect the call when the destination is Busy, Unreachable or No Answer.

So you can decide what to do with each call if you are busy, don't answer, the phone is not registered, etc, and that can also be determined by time of day.

I have not used these functions, but assume they work as advertised.

[Torvette]

Thanks very much.

I think I now have some options to research with the automagic handling of inbound calls.  May I ask who your toll-free provider is?

Now, on to how to inject a fail-over for the outbound calls... I was hoping the Obi`s had something built in, but I just can`t seem to find it.

[Lavarock7]

MY Toll Free provider used to be TelCan.Net. I had no problems with them, but decided to create a VOIP.MS account for other reasons. When Voip.Ms offered free porting, I ported and dropped my costs by a whopping 50 cents a month. I don't get many calls on the toll free number so I don't really worry about failover.

I use Voip.Ms because they allowed extensions and subaccounts. I understand CallCentric is adding similar functionality.

I've not had issues with CallCentric, although there were issues others had a while back.

You can certainly create accounts at these or other VOIP services and test out their failover and routing functions. You should also be able to test their quality of service and then port your number IF you decide this can solve part of your issue.

A neighbor just transferred an inbound number to a new provider because he was paying $6 a month to have it go to voicemail. Now he pays $1.50 a month and he gets an email with any messages attached. Even this type of backup plan may suffice for you without having to forward to your cell or another number.

[giqcass]

I don't know if there is an automagic way to do outbound call fail-over on the Obi but many of the service providers provide number spoofing (like callcentric).  With that you could dial the service provider prefix to dial out in the case of an outage.

Callcentric call Spoofing External Caller ID

http://www.callcentric.com/features/external_caller_id

[ianobi]

Outbound call fail-over can be achieved to a limited extent using trunk groups. It would work well if say sp1 had all of its sessions in use (usually 2), then the next outbound call would use sp2. However, in a failure of a service provider situation the OBi takes a while to see that registration has failed, so in that situation fail-over takes a time to work.

Do a search on this forum for "trunk groups" and post back here if you would like more information.

[Torvette]

Thanks for all the feedback, folks!

I now have lots of reading and tinkering to do!