Open

Overview

This page details the supported vendors and capabilities for UCentric Voice Audit and Migration.

It is designed as a broad overview of capabilities and the types of data that can be captured. It is not intended to be a complete specification of each decoder and should be used as a general reference guide only.

Supported Audit Methods for Voice Audits

This section details the supported methods for auditing each voice platform/PBX methods.

Audits can be performed in a variety of ways such as directly via IP using SSH or Telnet, by collecting a backup or extract from the system to import into UCentric or via Dial up/Modem connection.

The pages linked below contain guides for each type of audit method, please refer to the table for which methods are supported on each vendor/PBX Type.

*Note: Where “Confirmed version support” is shown, this means it is known to work on that version. The solution usually works on higher or lower versions than shown, but this shows the versions that have been previously seen and audited by the MIT support team.

Outputs

Migration Plan

Open

The migration plan exporting allows blending of additional data (e.g. AD, CDR, DDI ranges etc.) and then export to either “Bulk loaders” or direct provisioning through a script, backup or direct “Orchestration”.

Additional Data Imports and Blending

When exporting data for the purposes of migration, additional data sources can be imported into UCentric to blend it with audit data. Supported additional datasets and formats are shown in this section

DDI number ranges / extension ranges

This data ensures DDI information is associated with a device, user, or extension. It can be used to highlight any issues a migration would encounter from users who have moved locations but retained their extension number. Hunt groups spanning multiple locations can also be identified with this information. Fields shown in the table below as fieldName represent the columns in the LLD (Bulk Loader Excel sheet) that is generated.

Call Logging SMDR/CIL

This data allows for identification of any extensions or users that have no or little activity, and therefore may not need to be migrated.

Network MAC/IP captures (CDP/LLDP logs)

Network data allows for IP devices that have not been connected to the network to be identified which may then be considered as inactive or unused.

Active Directory/LDAP

An export from Active Directory or an LDAP server allows for the correct allocation of names against extension numbers where an integrated telephone directory is either unpopulated or inaccurate. Departmental information can also be associated against a user.

Voicemail Exports (i.e. Cisco Unity)

We can also blend in exports from Voicemail systems such as unity or 3^rd party voicemail if it contains a list of users with voicemail configured. This allows for identification of voicemail users in the LLD reports for replication on the hosted voice or system that is being migrated to.

LLD Low-Level-Design/Bulk Migration Plan Export Formats

LLD/Bulk Loaders

UCentric has the capability to export the audited data in several pre-defined export formats suitable for direct bulk-loading into client platforms.

Excel Spreadsheet

This is the standard format for export, which provides separate tabs for devices, profiles, hunt groups, pickup groups, and region information and allows blending and highlighting of usage and out-of-service, and the blending and transformation of data.

JSON

This provides the same data as the Excel output, but in JSON format suitable for consumption by orchestration platforms.

Custom formats

In addition to the above, there are several client-specific bulk export formats.

High-Level Design (HLD) Report

The high-level design document is a user-friendly/customer facing document that contains a full high-level overview of the current

Example Outputs

Our demonstration portal has some sample HLD and LLD reports in our default formats. Click the button below to check these out.

UCentric ZT SPA (Zero Touch Single Page Application)

SPA, or “Zero Touch” refers to the “Single Page Application”, a simplified interface for Auditing and Provisioning within UCentric.

Call flows

The following PABX vendors exports also include ‘Call Flows’ – This details where a DID/DDI call originating from the public network is routed to an IVR, Hunt Group or ACD call path.

At present this is supported for:-

Mitel MiVC, Mitel MiVB, Avaya CM and Skype for Business

These call flows are included within the Excel Bulk Loader and High-Level Design documents.

Direct orchestration

The “Direct Orchestration” provides the means to directly build or ‘Orchestrate’ the config of a new system though a script, a backup, or through direct API Orchestration

RingCentral

Direct API provisioning to the RingCentral cloud solution using SSO credentials. This is licensed through RingCentral’s partner programme, and you should contact them directly for access to this feature.

WebEx by Cisco

Direct provisioning into the WebEx by Cisco cloud solution using SSO credentials. A trial of this is available via the WebEx app store.

BroadWorks (Broadsoft)

With BroadWorks credentials, this can directly populate a Broadsoft/Cisco BroadWorks platform through their web API.

Microsoft Teams

Using the Graph API or PowerShell scriptlets, this automatically creates users, direct connect and presence groups - most integrators have their own methods, so generally a generic LLD is used in conjuction with existing processes.

Cisco BATS

Creates a v12.5 compatible BATS backup that can be restored directly onto a Cisco CUCM / HCS solution

Skype PowerShell Script (Deprecated)

This generates a script that can be locally executed on a private cloud / on-premise Skype-for-Business platform to create all the users, groups and direct connects.

EMU

Generates a EMU JSON export that can be pushed into the EMU service allowing provisioning of a Cisco BroadWorks platform through intermediate JSON.

8x8

Provides an 8x8 compatible spreadsheet that can be bulk loaded into the 8x8 platform.

Unify XML

Creates an XML file compatible with the Unify OpenScape bulk loading process.

Index

Revision history

Please refer to Supported Vendors List document in SharePoint or Repo for revision history prior to moving article to Confluence