Hello Internets,
As we approach the completion of our migration to 3CX, I'm pondering a backup to Flowroute, in which we have over 500 DIDs ported in.
As a whole, I've found Flowroute to be very good with several caveats:
1. Some months ago, AWS had several outages over a short period of time and because Flowroute runs over AWS, our PSTN phone traffic was impacted
2. They have now changed hands and been bought out by BCM blah blah One Cloud mumbo jumbo. This is, in general, not great for clients. I will bet that our Monthly Recurring Charges will conveniently start to creep up.
Given that Telnyx rides over AWS, Azure, I'd like to give them a try. I've had a hard time trying to imagine how to design these redundant cloud providers.
Scenario one:
DID - 333 123 4321 that has been ported into Flowroute - that DID rides down our Flowroute SIP trunk and terminates on our SBC and then flows into 3CX and ultimately triggers a CFD.
If Flowroute had issues, one thought was I could go in and simply call forward that Flowroute DID over to a number in Telnyx which then rides down our Telnyx trunk and terminates against our SBC and then flows into 3CX and triggers the CFD. What I cannot remember is if the AWS outages impacted access to the Flowroute portal. If so, this model would not work as it requires us to access the Flowroute portal and modify the route associated with the DID.
Scenario two:
Port half of our DIDs over to Telnyx. This sounds like a PITA from a management perspective.
Does anyone have any ideas on building redundant cloud telephony providers in the most robust way?
TIA,
IPT Dude
As we approach the completion of our migration to 3CX, I'm pondering a backup to Flowroute, in which we have over 500 DIDs ported in.
As a whole, I've found Flowroute to be very good with several caveats:
1. Some months ago, AWS had several outages over a short period of time and because Flowroute runs over AWS, our PSTN phone traffic was impacted
2. They have now changed hands and been bought out by BCM blah blah One Cloud mumbo jumbo. This is, in general, not great for clients. I will bet that our Monthly Recurring Charges will conveniently start to creep up.
Given that Telnyx rides over AWS, Azure, I'd like to give them a try. I've had a hard time trying to imagine how to design these redundant cloud providers.
Scenario one:
DID - 333 123 4321 that has been ported into Flowroute - that DID rides down our Flowroute SIP trunk and terminates on our SBC and then flows into 3CX and ultimately triggers a CFD.
If Flowroute had issues, one thought was I could go in and simply call forward that Flowroute DID over to a number in Telnyx which then rides down our Telnyx trunk and terminates against our SBC and then flows into 3CX and triggers the CFD. What I cannot remember is if the AWS outages impacted access to the Flowroute portal. If so, this model would not work as it requires us to access the Flowroute portal and modify the route associated with the DID.
Scenario two:
Port half of our DIDs over to Telnyx. This sounds like a PITA from a management perspective.
Does anyone have any ideas on building redundant cloud telephony providers in the most robust way?
TIA,
IPT Dude
