Direct Routing (Replacement of Openscape PBX to Teams Telephone System)

Tender description

Currently SCC have an on prem PBX (Openscape) and SBC located at our main office (County hall). Calls are currently delivered into the PBX via a 150-sip channel connection from our current supplier (BT). Outbound calls are routed via 60 ISDN30 channels. Calls to and from branch sites are routed over the WAN. Staff working from home connect via VPN to the telephony system to make and receive calls. SCC roadmap is to move most of the IT service into the cloud. SCC have already the moved most of its IT service into Microsoft Azure cloud services. SCC are currently using Microsoft Teams for chat and internal calling and are now looking to use it for external DDI calling. SCC have already purchased E5 licenses and Microsoft phone system is now available to us. SCC require a supplier to provide a direct routing cloud solution for inbound and out outbound calling to and from MS Teams. The new supplier will provide a sip link (150 channels) from their platform via SCC's internet connection to the legacy PBX located at County Hall for inbound calls. The supplier will manage OOH the porting/migration of our DDI ranges (see Openscape numbers doc) from the current supplier to their platform and route inbound calls directly into the legacy PBX. The sip circuit will be required for a min of 6 months. The new supplier will provide a sip link (150 channels) from their platform to SCC's Microsoft tenant for inbound and outbound calls to Teams Phone System. Calls will route from SCC's Microsoft tenant via SCC's express route into County Hall and will break out of SCC's internet connection to staff WFH and route across SCC's WAN for staff located at remote sites. New supplier will assist SCC staff on the setup of Team Telephone system (see appendix Y doc). SCC staff will then migrate individual DDI and hunt group numbers from legacy PBX to Teams telephone System in a phased approach. *SCC must have control over the migration and be able to migrate individual numbers from our DDI ranges hosted by the new supplier*. Once the migration has been completed the sip circuit provided by the new supplier connected to the legacy PBX will be ceased and SCC will decommission the legacy PBX.