VOSS Discover: Do You Know What\u2019s in Your PBX?<\/h1><\/div>Understanding what is inside your existing PBX and what is worth moving is the first step towards a successful migration to Microsoft Teams or Cisco Webex<\/p><\/h4><\/div>
![](\"https:\/\/voss-media.imgix.net\/2023\/01\/Tim-Jalland-Colour-White-border.png?auto=compress%2Cformat&fit=scale&h=768&ixlib=php-3.3.1&w=768&wpsize=medium_large\" "\\"Tim-Jalland-Colour-White-border\\"")
<\/span><\/div><\/div><\/div>Author: Tim Jalland
\nSolution Manager, VOSS Solutions<\/h6>\n
Wednesday March 6, 2024<\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
We are regularly asked how to begin a successful migration project to Microsoft Teams Phone. The answer is that you must start at the beginning, with the existing PBX, and follow a process that we call VOSS Discover<\/a>. Read on \u2026<\/p>\nPBX Discovery: A necessary first-step towards a successful migration to Microsoft Teams Phone<\/h3>\n
Adding enterprise telephony to cloud collaboration platforms such as Microsoft Teams and Cisco Webex is an agenda item for most of our customers. A single desktop client for chat, meetings and now voice offers increased productivity and is aligned with a general IT strategy of moving to the cloud. Additionally, it offers significant cost savings on PBX hardware, licensing, and support costs.<\/p>\n
But where to start?<\/p>\n
PBX systems are notoriously difficult to figure out, having been configured by successive technical experts over many years. So just how do you create a suitable telephony capability in the cloud without first understanding what\u2019s in use currently and how that might be updated and moved? This first discovery step is critical to any successful migration project, to know where you are starting from. This process must:<\/p>\n
\n- Meet user needs and expectations<\/li>\n
- Run to planned costs and timescales<\/li>\n
- Avoid surprises and unnecessary risks<\/li>\n
- Go into production without myriad post migration support issues<\/li>\n<\/ul>\n<\/div><\/div><\/div>
VOSS Discover: Planning for success<\/h3>\n
At VOSS, we run discovery projects that are geared towards providing information from the existing PBX, to create a solid foundation for the migration plan. It\u2019s a project run by VOSS that removes the blindfolds on the current configuration, and helps with feature mapping and planning for the migration journey.<\/p>\n
Each project provides the following:<\/p>\n
\n- Discovery on the PBX set-up, including users, devices, services, and numbers<\/li>\n
- Analysis on features, identifying the equivalent on Microsoft Teams<\/li>\n
- A usage review to trim licensing and unnecessary configuration clutter<\/li>\n
- Guidelines on how to transfer the dial plan to the Microsoft tenant<\/li>\n
- Considerations to bear in mind when building a migration plan<\/li>\n<\/ul>\n<\/div><\/div><\/div>
![\"VOSS](\"https:\/\/voss-media.imgix.net\/2022\/06\/VOSS-Discover-promo-v2-mp4-image.png?auto=compress%2Cformat&ixlib=php-3.3.1\" "\\"VOSS")
<\/span><\/div><\/div><\/div>Each VOSS Discover project is delivered by a team of VOSS engineers with a track record in PBX systems and complex migration projects. They\u2019re supported by VOSS Migrate automation tooling that streamlines the entire audit process.<\/p>\n
The process itself is non-intrusive and secure, with the analysis conducted on an offline export of the PBX – no need to connect to the live PBX. This reduces the call on your technical and IT resources, freeing these up for higher priority projects and tasks. First results are available in a matter of weeks, to assist with early planning, budgeting, and resourcing.<\/p>\n
<\/h3>\nWhat to Expect<\/h3>\n
Each VOSS discovery project provides 5 things:<\/p>\n
\n- A Migration Readiness Report based on data extracted and covering PBX configuration, inventory, and migration \u2018gap\u2019 traffic-light analysis<\/li>\n
- A Line Usage Report indicating numbers in use or those that can be trimmed to reduce clutter and costs as part of migration planning<\/li>\n
- Best practice and advice on approaching migration planning based on experience from recent projects<\/li>\n
- A two-hour workshop to review findings<\/li>\n
- Support for ad-hoc queries resulting from the review and\/or specific business questions<\/li>\n<\/ul>\n
I\u2019ve included two sample reports for your reference:<\/p>\n<\/div>
<\/div><\/div><\/div><\/div><\/div><\/div>Two sample reports for migration readiness<\/h1><\/div><\/div><\/div>Detailed PBX inventory<\/h3><\/div><\/div><\/div>![\"VOSS](\"https:\/\/voss-media.imgix.net\/2024\/03\/PBX-inventory-v2.png?auto=compress%2Cformat&ixlib=php-3.3.1\" "\\"PBX")
<\/span><\/div><\/div><\/div>Potential migration issues<\/h3><\/div><\/div><\/div>![\"Two](\"https:\/\/voss-media.imgix.net\/2024\/03\/Migration-issues.png?auto=compress%2Cformat&ixlib=php-3.3.1\" "\\"Two")
<\/span><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>Getting started<\/h3>\n
VOSS will work with you to create a discovery strategy to suit your needs. We will ask you to provide four key things:<\/p>\n
\n- A stakeholder for the process –<\/strong> This is required to oversee and own the process from the customer side<\/li>\n
- An export from the existing PBX for us to work on –<\/strong> Produce an export from the existing PBX along with any other reports such as call CDRs\/reports and number ranges<\/li>\n
- Access to personnel during the assessment –<\/strong> During the planning workshop, we will require attendance of stakeholders, telephony, cloud, and infrastructure teams<\/li>\n
- A completed questionnaire –<\/strong> Contains questions about the environment, plans, requirements, and infrastructure<\/li>\n<\/ul>\n
There\u2019s more information on VOSS Discover on our website<\/a>. You can also get in touch with us here<\/a>.<\/p>\n<\/div><\/div><\/div><\/div><\/div>Keep up to date with our latest blogs and subscribe today<\/h4><\/div><\/div><\/div>
Understanding what is inside your existing PBX and what is worth moving is the first step towards a successful migration to Microsoft Teams or Cisco Webex<\/p><\/h4><\/div>
<\/span><\/div><\/div><\/div>Author: Tim Jalland
\nSolution Manager, VOSS Solutions<\/h6>\n
Wednesday March 6, 2024<\/p>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div>
We are regularly asked how to begin a successful migration project to Microsoft Teams Phone. The answer is that you must start at the beginning, with the existing PBX, and follow a process that we call VOSS Discover<\/a>. Read on \u2026<\/p>\n Adding enterprise telephony to cloud collaboration platforms such as Microsoft Teams and Cisco Webex is an agenda item for most of our customers. A single desktop client for chat, meetings and now voice offers increased productivity and is aligned with a general IT strategy of moving to the cloud. Additionally, it offers significant cost savings on PBX hardware, licensing, and support costs.<\/p>\n But where to start?<\/p>\n PBX systems are notoriously difficult to figure out, having been configured by successive technical experts over many years. So just how do you create a suitable telephony capability in the cloud without first understanding what\u2019s in use currently and how that might be updated and moved? This first discovery step is critical to any successful migration project, to know where you are starting from. This process must:<\/p>\n At VOSS, we run discovery projects that are geared towards providing information from the existing PBX, to create a solid foundation for the migration plan. It\u2019s a project run by VOSS that removes the blindfolds on the current configuration, and helps with feature mapping and planning for the migration journey.<\/p>\n Each project provides the following:<\/p>\n Each VOSS Discover project is delivered by a team of VOSS engineers with a track record in PBX systems and complex migration projects. They\u2019re supported by VOSS Migrate automation tooling that streamlines the entire audit process.<\/p>\n The process itself is non-intrusive and secure, with the analysis conducted on an offline export of the PBX – no need to connect to the live PBX. This reduces the call on your technical and IT resources, freeing these up for higher priority projects and tasks. First results are available in a matter of weeks, to assist with early planning, budgeting, and resourcing.<\/p>\n Each VOSS discovery project provides 5 things:<\/p>\n I\u2019ve included two sample reports for your reference:<\/p>\n<\/div> VOSS will work with you to create a discovery strategy to suit your needs. We will ask you to provide four key things:<\/p>\n There\u2019s more information on VOSS Discover on our website<\/a>. You can also get in touch with us here<\/a>.<\/p>\n<\/div><\/div><\/div><\/div><\/div>PBX Discovery: A necessary first-step towards a successful migration to Microsoft Teams Phone<\/h3>\n
\n
VOSS Discover: Planning for success<\/h3>\n
\n
<\/span><\/div><\/div><\/div><\/h3>\n
What to Expect<\/h3>\n
\n
Two sample reports for migration readiness<\/h1><\/div><\/div><\/div>
Detailed PBX inventory<\/h3><\/div><\/div><\/div>
<\/span><\/div><\/div><\/div>Potential migration issues<\/h3><\/div><\/div><\/div>
<\/span><\/div><\/div><\/div>Getting started<\/h3>\n
\n
Keep up to date with our latest blogs and subscribe today<\/h4><\/div><\/div><\/div>