Replacing Broadsoft Broadworks and other solutions – what are my options?
If you have a legacy IP Centrex solution in your B2B portfolio, such as a Broadsoft Broadworks solution, you may be thinking about how you can maintain this or evolve to launch new offers. Gintel has a range of proven options for replacing or extending legacy B2B platforms, providing you with future-proof service evolution and enhancement opportunities.
How can I evolve or replace my legacy B2B portfolio?
For a variety of reasons, many operators are evaluating their existing IP Centrex platforms, such as Broadworks from Broadsoft, and are considering how they can evolve to meet the challenges of new network standards and connectivity. We’ve been asked to provide several different replacement solutions by our customers – so, if you are evaluating how your B2B service portfolio should evolve and if you have a Broadsoft or other legacy platform, here are your options.
Option 1 – full replacement
In this situation, complete replacement of the existing solution is undertaken, on a like-for-like basis. Not only does this mean that the existing solution can be retired, but it also means that new functionality can be added – for example, deeper mobile integration, VoLTE / 5G compatibility and so on.
This process generally involves several phases – from alignment with the existing feature set, to deployment in the live network and full migration of the active and registered users to the new platform, without disruption.
In this case, the Gintel IP Centrex module, for example, can be deployed together with our other service enabling components, providing a platform for future evolution.
Option 2 – co-existence and extension
For a variety of reasons, it can also make sense to retain the existing platform, but to enable further integration around the current deployment. In this case, Gintel can co-exist with the legacy platform, but can take responsibility for new network interfaces and integration points – for example, enabling mobile integration with federated status, by handling all main number and mobile traffic (inbound and outbound).
This can be achieved through integration with existing interfaces – in the case of Broadsoft solution, using APIs such as XSI (Extended Services Interface) and OCI-P (Open Client Interface Provisioning).
Once achieved, this means that existing users can also use, for example, their mobiles as part of their call handling options – with full alignment of the device status. So, if a user is active on a Broadsoft client application, calls to their mobile will be diverted according to the rules established – to voicemail or to a fellow user. Similarly, if they make a call from the mobile, then the status will be updated in the Broadsoft client, so that calls will also be diverted appropriately.
This integration proved to be particularly useful during the pandemic. It allows call centre agents to use their mobiles while working remotely, and ensured full alignment across other user interfaces. Once established, other integrations can then be enabled – such as with Microsoft Teams, for example.
Option 3 – Target new segments
Sometimes an operator wishes to preserve an existing platform and make no changes to the experience of existing subscribers. However, it is acknowledged that no changes can be made to the current platform and that it cannot be repurposed in any way. In this situation, there is always the option to deploy a new platform to target a new segment or market opportunity.
For example, the operator may wish to launch a new SME-focused offer, or to provide a dedicated mobile-first service with virtual fixed numbers for small businesses. Here, Gintel can be deployed as the agile platform to enable new offers to be launched. So, the legacy platform is maintained for as long as support is possible – while new services are launched on the Gintel solution.
In time, when support contracts end, become too costly, or simply unavailable, the old platform can be retired and migration to Gintel can also be accomplished, as in Option 1.
Evolution in practice
We have customers that have opted for each of these approaches, with case studies we can share to highlight our success in helping them to evolve their B2B service suite from a legacy platform. What’s important to note is that migrations can be handled without disruption, while new service introductions follow clear steps for launch in the live network.
Put simply, you don’t have to replace your legacy solution – but you can if you want to. If you don’t, you can extend, enhance and complement it. In all cases, we can help you plot an innovative future that’s aligned with your investment plans and costs – so, why not get in touch to find out how we can help you evolve your B2B service portfolio?
Latest posts
Checking back in on our interns – demonstrating our APIs via games and automating SIP testing
Meet Gintel at MVNO Nation Live 2023 – launch B2B solutions to meet the needs of the underserved SME segment
Call recording services: a big opportunity?
Analysys Mason reckons SMEs are underserved. So, where’s the opportunity? Explore Gintelberg and find out!
ITEF RFC 7245 SIPREC call recording - a primer
Tags
Who are we?
Want to learn more about Gintel, our mission and our technology
Otto Nielsens vei 12
N-7004 Trondheim
Norway