[VoiceOps] Acquire MetaSwitch

Tue Aug 13 16:07:54 EDT 2024

"But you're also marrying that platform. Once you wed your backoffice and
tooling and business processes to it, the divorce is very messy."

That is generally true, though in our case the front-end/orchestration
layer is backend-platform agnostic. This was intentional, and gives
operators the ability to change a subscriber's provisioning from one
platform to another with a few clicks. That way we're not tied-in. Of
course this creates some additional complexity, but, gives us capabilities
I haven't seen offered elsewhere.

Jawaid

On Tue, Aug 13, 2024 at 3:54 PM Alex Balashov via VoiceOps <
voiceops at voiceops.org> wrote:

> Well, an off-the-shelf platform will certainly allow you to leapfrog quite
> a bit of development, especially development you may not wish to
> metabolise, either for reasons of being a service provider and not a
> software shop generally, or for reasons of GTM time specifically.
>
> But you're also marrying that platform. Once you wed your backoffice and
> tooling and business processes to it, the divorce is very messy.
>
> Depending on the complexity of your routing requirements, you may be
> better off going your own way, especially if you've managed to build a
> front-end and product fabric in <2 years.
>
> —
> Sent from mobile, apologies for brevity and errors.
>
> On Aug 13, 2024, at 3:43 PM, Jawaid Bazyar <jawaid at bazyar.net> wrote:
>
> 
> I have a use case. The use case is, be in a position to take customers
> tomorrow on a 5/9's platform.
>
> One alternative is Ribbon: that solution is out of my price range, and,
> likely out of price range of every rural ILEC I know.
>
> A second is Squire, but, I'm not willing to risk it w/o getting my hands
> on a long-term trial which was requested but not offered.
>
> The final alternative is to throw into developing one, likely in two
> phases. The orchestration and front end of the Elephant Talk project is
> complete, now just need to settle on a production backend.
>
>
> On Tue, Aug 13, 2024 at 3:33 PM Alex Balashov via VoiceOps <
> voiceops at voiceops.org> wrote:
>
>> I suppose this all raises the question of why on earth you'd want to
>> acquire a Metaswitch, but you've clearly got an angle.
>>
>> -- Alex
>>
>> > On Aug 13, 2024, at 3:20 PM, Jawaid Bazyar via VoiceOps <
>> voiceops at voiceops.org> wrote:
>> >
>> > "Microsoft's end game is for every operator to have a big pipe to Azure
>> to access Metaswitch, vSBC, Teams and other components."
>> >
>> > My question is, can you actually run a MetaSwitch CFS in Azure? Because
>> to my knowledge, you cannot.
>> >
>> > I would be very interested if I was wrong about this.
>> >
>> > Jawaid
>> >
>> >
>> > On Tue, Aug 13, 2024 at 12:56 PM Peter Rad via VoiceOps <
>> voiceops at voiceops.org> wrote:
>> > Besides getting rid of their Max UC softphone (to make MS Teams THEE
>> softphone), they did EOL a lot of the Meta product.
>> >
>> > We - RAD-INFO, ECG and Andrew Ward - did a webinar about it in May. You
>> can watch the recording here:
>> https://info.ecg.co/webinar-recording-broadworks-metaswitch-netsapiens-ribbon
>> >
>> > Microsoft's end game is for every operator to have a big pipe to Azure
>> to access Metaswitch, vSBC, Teams and other components.
>> >
>> >
>> > Let me know if there is anything I can do for you.  Thank you.
>> >
>> > Regards,
>> >
>> > Peter Radizeski
>> > RAD-INFO INC
>> > Telecom Consultant
>> > Bandwidth * Voice * Cloud * Data Center * Internet * CyberSecurity
>> > (813) 963-5884
>> >
>> >
>> >
>> > On 8/13/2024 8:41 AM, Mike Hammett via VoiceOps wrote:
>> >> "Given the MetaSwitch products are no longer sold, and Microsoft is
>> EOLing them, and not taking new support contracts..."
>> >>
>> >>
>> >> That's news to me.
>> >>
>> >>
>> >>
>> >> -----
>> >> Mike Hammett
>> >> Intelligent Computing Solutions
>> >> http://www.ics-il.com
>> >>
>> >>
>> >>
>> >> Midwest Internet Exchange
>> >> http://www.midwest-ix.com
>> >>
>> >>
>> >>
>> >> From: "Jawaid Bazyar via VoiceOps" <voiceops at voiceops.org>
>> >> To: "voiceops" <voiceops at voiceops.org>
>> >> Sent: Tuesday, August 13, 2024 7:23:05 AM
>> >> Subject: [VoiceOps] Acquire MetaSwitch
>> >>
>> >> Hello,
>> >>
>> >> We are in the market to acquire / take over a MetaSwitch CFS. In
>> particular, we're looking for the virtual edition that runs purely in
>> VMWare.
>> >>
>> >> The components we'd need are:
>> >>     CFS
>> >>     MRS (Media Resource Server)
>> >>     Perimeta
>> >>     SAS (Service Assurance Server)
>> >>     MetaView Server
>> >>
>> >> These are fairly common components.
>> >>
>> >> Given the MetaSwitch products are no longer sold, and Microsoft is
>> EOLing them, and not taking new support contracts, we're not talking about
>> a big cash up front kind of deal, but, instead a revenue share kind of
>> arrangement.
>> >>
>> >> Anyone that has one and is interested, contact me directly off-list.
>> >>
>> >> Cheers,
>> >>
>> >> Jawaid
>> >>
>> >>
>> >> _______________________________________________
>> >> VoiceOps mailing list
>> >> VoiceOps at voiceops.org
>> >> https://puck.nether.net/mailman/listinfo/voiceops
>> >>
>> >
>> > Virus-free.www.avast.com
>> _______________________________________________
>> > VoiceOps mailing list
>> > VoiceOps at voiceops.org
>> > https://puck.nether.net/mailman/listinfo/voiceops
>> > _______________________________________________
>> > VoiceOps mailing list
>> > VoiceOps at voiceops.org
>> > https://puck.nether.net/mailman/listinfo/voiceops
>>
>> --
>> Alex Balashov
>> Principal Consultant
>> Evariste Systems LLC
>> Web: https://evaristesys.com
>> Tel: +1-706-510-6800
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20240813/db148d06/attachment.htm>