That is something which needs to be worked out with the carrier, usually where the POP for the original organization transfers the calls for those TFNs to numbers in the other region. There are always variations based upon the carriers and countries involved, and careful setup of the trunks in each organization (and not trying to replicate the trunks from original organization to BCP).
George Ganahl GCP, GCSME, ICCE, ICHD, etc.
Original Message:
Sent: 01-08-2025 03:45
From: Dan Wong
Subject: Genesys Cloud: Disaster Recovery and Backup Automation
Thanks Jim - will review the Blueprint above with our DevOps Team to see what option 1 can offer :-)
------------------------------
Dan Wong
EUC Engineer
Original Message:
Sent: 01-07-2025 11:40
From: Jim Crespino
Subject: Genesys Cloud: Disaster Recovery and Backup Automation
Hi Dan,
I'm the Product Manager for CX as Code here at Genesys. CX as Code is a great tool but it takes a considerable amount of effort by some fairly technical DevOps resources to get things setup properly. We have a Blueprint on the Developer Center that shows what is possible: https://developer.genesys.cloud/blueprints/cx-as-code-cicd-gitactions-blueprint/
On the AppFoundry, there are several additional options available. Genesys Professional Services offers a pre-built product that utilized CX as Code called BCP Wizard (https://appfoundry.genesys.com/filter/genesyscloud/listing/630602fd-7b2e-447d-a9ff-0fb73af89d0f) and they have a second offering available via an engagement model. You can speech with your Genesys account manager about those if you are interested.
Additionally on the AppFoundry we have 3rd party partners that have tackled this problem using their own technology stacks. Off the top of my head I know that Blackchair, Eemaan, Pointel, and CloudCX all offer something in this realm.
I hope that helps.
------------------------------
Jim Crespino
Senior Director, Developer Evangelism
Genesys
https://developer.genesys.com
Original Message:
Sent: 01-06-2025 06:33
From: Dan Wong
Subject: Genesys Cloud: Disaster Recovery and Backup Automation
We are currently exploring disaster recovery strategies for Genesys Cloud, particularly focusing on how to handle the complete loss of our existing Genesys Cloud organization and the subsequent need to recreate a new organization from scratch.
Our primary goal is to recreate a "snapshot" or version of our production environment with minimal manual intervention, leveraging automation wherever possible to save time and resources.
From our research so far, we've identified a few potential approaches:
1. Genesys Cloud CX as Code: Utilizing Genesys' Infrastructure as Code tools for configurable items.
2. AppFoundry Tools: Leveraging third-party tools available in the Genesys AppFoundry marketplace.
3. Manual Configuration: Rebuilding the organization manually.
- We'd love to hear from others in the community about their experiences and insights:
- Are there other viable options we should consider?
- What are the pros and cons of using "Genesys Cloud CX as Code" versus tools from the AppFoundry?
- Any recommendations or best practices for disaster recovery in this context?
Looking forward to your thoughts and suggestions!
#API/Integrations
#ArchitectureandDesign
#Implementation
#PlatformAdministration
#Routing(ACD/IVR)
#Security
#SystemAdministration
#Telephony
#Unsure/Other
------------------------------
Dan Wong
EUC Engineer
------------------------------