AT&T Wireless is the big name that is moving to Azure for Operators and
some other Azure products for their 5G platform. Dish also did all AWS
cloud for their voice and data network.

If the uplinks from the metro network to the cloud fail, or a cloud fails,
I hope they have a plan B ready.

Does Microsoft at least offer Azure Stack (a local hosted set of servers
similar to AWS Outpost) for Azure for Operators that the small telcos could
use to keep calls local but get the benefits of newer switching software
and support?

Then I saw that Next Gen 911 has to move to SIP trunking
https://potsandpansbyccg.com/2024/08/14/next-generation-911/ and carriers
have to hand off in state. Which hopefully means that when one switch
center 3 states over goes out or a fiber cut doesn't take out the whole
network as it has done in the past few years with AT&T and Centurylink. I
haven't seen what it will mean for ITSPs yet that hand their 911 traffic
off to Bandwidth/Sinch/Hypercube.

~Jared



On Wed, Aug 14, 2024 at 11:55 AM Mike Johnston via VoiceOps <
voiceops@voiceops.org> wrote:

> On 2024-08-14 07:43, Mike Hammett via VoiceOps wrote:
> > "Do rural operators WANT to keep running expensive local switches? Or,
> > would cloud be more attractive if there was survivability? i.e., limited
> > local hosting of services?"
> >
> > I would imagine the demographic is very anti-cloud. I can't imagine
> > anything worse than running critical infrastructure in the cloud.
>
> I am interested in avoiding tromboning traffic all over the continent,
> especially when both ends are within my own network.
>
> It is really embarrassing when an outage/fiber cut hundreds of miles
> away, is preventing calling across the street...or worse, to the next
> cubicle.
> _______________________________________________
> VoiceOps mailing list
> VoiceOps@voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
_______________________________________________
VoiceOps mailing list
VoiceOps@voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

Reply via email to