Wahsington DC Network Outage

[Russell]

I appreciate your long and detailed response to my post, Tim. I do see your point about a certain section of your users trying to aim for the closest server (I guess I'm guilty of that too, as I requested to be assigned to a certain server within the first few days) and this becoming a support burden and especially in hte context of dynamic load balancing more difficult

Anyway, I'm glad that the the looping issue has been addressed ... as I have a vested interest in softphones at the present time. I have a child who will be spending about 2-3 months volunteering in Central America and I was planning on installing a softphone on her laptop - not sure what kind of Internet connection she'll have. At this moment, I'm not sure I want the softphone to "register" as I don't want our calls also ringing on her laptop (if connected) so the looping issue may be irrelevant in this case.

Which reminds me ... should I open a ticket for the record, so that you guys don't freak out if you find "domestic" calls with my credentials originating in Central America over the summer? Is there some way to "notate" my account to that effect?

[usa2k]

Perhaps it is a liability having servers with recognizable names that relate to location? Or how would they know to be angry and want to be moved? The marketing would need to be such, that they assume the are kept on a close server, but leave it unverifiable so they don't generally have a cause for concern.

On the flip-side, customers may be with VOIPo because there is a server closer to them. It is too bad a VoIP device manufacturer couldn't add a primary/secondary profile for a service. If the primary number cannot complete, it auto-tries the next profile. (Two different services, or like VOIPo, one service, different servers. The second profile does not register until needed.) I think Asterisk can do that, so its not like you can patent the idea, and have hardware manufacturer provide a custom firmware that if used for other, there are royalties ...

For failover conditions, how would you handle same number, multiple devices? You would need a database that crosses the number to a status from each server. You would then know its registered X times on server A, and Y times on server B. When would a failover number happen? When only one device fails? Or all devices? At present, I expect its when the provisioned device fails.

What if its BYOD? Is there no failover protection? Do you guess which device is the softphone? You could have a place to register each device (by MAC ID makes sense) and a grid of options.

Device#1, MAC ___, Failover if not registered/No Failover (Clone#1)
Device#2, MAC ___, Failover if not registered/No Failover (Clone#2)
Device#3, MAC ___, Failover if not registered/No Failover (SPhone)
Register all SERVER#1/SERVER#2
Fallback all SERVER#1/SERVER#2

If Bold was used like my example, I would use underline to show the active choice being used by VOIPo. Or maybe underline would visible be for a beta group that can help with feedback, and your support team so they can see better the current settings.

(Fallback in effect)
Register all SERVER#1/SERVER#2
Fallback all SERVER#1/SERVER#2

[dswartz]

The outage at the DC center was disturbing. An entire data center off the area for that long? Something there screwed the pooch

[burris]

The outage at the DC center was disturbing. An entire data center off the area for that long? Something there screwed the pooch

I think these data centers have organized a conspiracy against Tim..

[usa2k]

Maybe HostGator is big enough now, to have their own Data Center?

That would be something many hosting companies could not brag about!
(Going to need a bigger building!)

[VOIPoTim]

For failover conditions, how would you handle same number, multiple devices?

Basically it should just fork the call out to all of the registrations and whichever one answers first will get it.

[usa2k]

Basically it should just fork the call out to all of the registrations and whichever one answers first will get it.

And as long as one device is registered, no failover occurs?
I may have been thinking too far out the box.

[VOIPoTim]

And as long as one device is registered, no failover occurs?
I may have been thinking too far out the box.

Yeah, failover would only be if none are registered.

[Russell]

Yeah, failover would only be if none are registered.

I think this makes sense. After all VOIPo is providing phone service to ONE residence. I think of any other use as a nice perk.