dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
9
share rss forum feed

DSLR98004

join:2012-07-16
Bellevue, WA
reply to rudeboy24

Re: [Voip.ms] Failover options when server down

Here is the best I can come up with for VOIP.ms. (And by the way decx is right, if a server is down, the failover logic will not work).

I have multiple three-line Aastra SIP phones (9143i). I actually only use lines 1 and 2 on a normal basis (one home office line and one personal residence line). Those two lines (DIDs) are registered to the Seattle server. I have a third line/DID that is registered to Houston but is normally not used ($0.99/month insurance).

Right now, if I determine Seattle is down, I go to the VOIP.ms web site and forward lines 1 and 2 to line 3. (No need to make any local config changes). Lines 1 and 2 then ring on line 3 on my Aastra phone, and I can make outgoing calls on line 3. I can tell on my phone when Seattle is down and when it comes back up.

The improvement to the above is to use the VOIP.ms API to track the state of your DIDs. If your programming logic determines, e.g., that Seattle is down and Houston is up, then your program can automatically uses the VOIP.ms API to set up the call forwarding logic described above. I intend to write that program “one of these days…”

real_goose

join:2001-04-13
Apollo Beach, FL
kudos:1
Reviews:
·Verizon FiOS
·callwithus
·voip.ms
said by DSLR98004:

I have multiple three-line Aastra SIP phones (9143i). I actually only use lines 1 and 2 on a normal basis (one home office line and one personal residence line). Those two lines (DIDs) are registered to the Seattle server. I have a third line/DID that is registered to Houston but is normally not used ($0.99/month insurance).

On my Aastra 6730i I have options to specify backup that seems to work automatically. For line 1 I set:
Proxy Server=tampa.voip.ms
Backup Proxy Server=chicago.voip.ms
Registrar Server=tampa.voip.ms
Backup Registrar Server=chicago.voip.ms
The Status screen field Backup Registrar Used? reports YES or NO to let you know which server is in use.

I will be looking for something other than an Obi with similar functions for the main house unless someone can tell me how to do something like this on an Obi.

DSLR98004

join:2012-07-16
Bellevue, WA
said by real_goose:

said by DSLR98004:

I have multiple three-line Aastra SIP phones (9143i). I actually only use lines 1 and 2 on a normal basis (one home office line and one personal residence line). Those two lines (DIDs) are registered to the Seattle server. I have a third line/DID that is registered to Houston but is normally not used ($0.99/month insurance).

On my Aastra 6730i I have options to specify backup that seems to work automatically. For line 1 I set:
Proxy Server=tampa.voip.ms
Backup Proxy Server=chicago.voip.ms
Registrar Server=tampa.voip.ms
Backup Registrar Server=chicago.voip.ms
The Status screen field Backup Registrar Used? reports YES or NO to let you know which server is in use.

I will be looking for something other than an Obi with similar functions for the main house unless someone can tell me how to do something like this on an Obi.

My understanding is that the backup server will only be operational if you also make the same server change on the VOIP.ms web site. In other words, I don't believe you can fully automate the server switch using only the Aastra side. Can anyone confirm or correct my understanding?

OZO
Premium
join:2003-01-17
kudos:2
said by DSLR98004:

My understanding is that the backup server will only be operational if you also make the same server change on the VOIP.ms web site. In other words, I don't believe you can fully automate the server switch using only the Aastra side

Precisely. And that's the reason why failover should be done on their side and not on clients side...
--
Keep it simple, it'll become complex by itself...

obiliving

join:2011-01-22

1 recommendation

reply to real_goose
You don't need voip.ms to support DNS SRV.

On the OBi, enable X_ProxyServerRedundancy (under ITSP Profile/SIP). On your OBi SP Service page, enter "voip.ms" for the ProxyServer. Leave other servers (Registrar, etc.) blank.

On your OBi Network settings, look for the section heading Local DNS Records, and enter a record like this:

voip.ms=tampa.voip.ms,chicago.voip.ms

Give it a try. The OBi Device Admin Guide has more details about these settings.