...
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.
| Table of Contents | ||
|---|---|---|
|
Supported Audit Methods for Voice Audits
...
Vendor | Model | Confirmed version support* | Also known as | Audit Method(s) | Ports Used (IP Audits Only) | Backup supported? | Expected Backup format | ||
|---|---|---|---|---|---|---|---|---|---|
3CX | 3CX | V16 | Backup only | - |
| XML Backup (.xml) | |||
Aastra | 430 | Mitel MiVO400,430 | Backup only | - |
| Excel Spreadsheet (.xls) | |||
MX-One | MD110 | SSH, Modem | 22 |
| Command dump (.zip) | ||||
Alcatel | OmniPCX | R9, R10 onwards | Backup, SSH, Modem | 22 |
| Config export (.txt) | |||
ASC | Recorder | XML File import | - | XML Backup (.xml) | |||||
Asterisk | FreePBX | 1.11.2 and V5.x onwards | SSH | 22 |
| Asterisk backup (.tar.gz) | |||
Avaya | BCM | 1.0R9 | Backup only | - |
| Excel export (*.xls) | |||
CM | G3 V15-V20 Release 6 onwards | Definity | ASA and SSH | 5022, 22 |
| UCentric backup (.ucx) | |||
IP Office | Release 8 onwards | TFTP | 69 |
| Config export (.txt) | ||||
Avaya / SDX | INDeX | Telnet / Modem | 23 | ||||||
Axxess | 5000 | Mitel 5000 | Backup only |
| Access DB (.accdb) | ||||
Broadsoft | Broadworks | V21-V24 | Direct audit - TCP/IP (Via XSP API) | 2208 |
| EMU (.json)||||
BT | CS2K | n/a | Backup only | - |
| Excel export (*.xls) | |||
Cisco | CME | V5.x | Backup only | - |
| Router export (.txt) | |||
CUCM | 6.0 - 12.5 | Backup only | - |
| CUCM BATS (.tar) | ||||
Genesys | PureConnect | Backup only | - |
| Excel backup (.xls) | ||||
GPT | BTeX | - | Modem | - | |||||
IBM/Siemens | ROLM, 9751 | - | Modem | - | |||||
Intertel/Mitel | Axxess | Mitel MiVO250 | HTTP and TCP/IP | 80, 4000 | |||||
Microsoft | Teams, Lync, Skype for Business, | PowerShell | - |
| MIT provided backup. | ||||
Mitel | 3300 | Rel 7.0 to 10.0 Inclusive | MiVB (Non MSL) | Telnet, SSH, SNMP and TCP/IP | 23, 22, 5022, 5023, 161 |
| Archive (.zip) | ||
SX2000 | M-Stream + | SX2000 Light | Telnet | 23 | |||||
MiCollab | Backup only | - |
| MSL Backup (.tar) | |||||
MiCC | Backup only | - |
| MSL Backup (.tar) | |||||
MiVoice Connect | MIVC: 1608 to 20 inclusive Shoretel: 19.50.1000.0 (14.2 GA 30) | Shoretel Shoreware | Backup only | - |
| MySQL Export (.sql) | |||
MiVoice Office 250 | Rel 5.0 to 6.3 SP7 inclusive | Axxess 5000 / Mitel 5000 | Backup only | - |
| Access DB (.accdb) | |||
MiVoice Office 400 | Aastra 430 | Backup only | - |
| Excel Spreadsheet (.xls) | ||||
NEC | NEAX | Backup only | - |
| Excel export (.xls) | ||||
NEC | NEC UX5000, SV8100, SV9100 | .PCPX format | |||||||
NEC/Philips | Sopho/IS3000 | Backup only | - |
| XML backup (.xml) | ||||
Nortel / Avaya | Meridian, Succession, CS1000, CS1K | Release 4 - 7 (00 R - 65 P) | rLogin, Telnet, Modem | 513, 23 |
| Command dump - Contact MIT for commands (.txt) | |||
OneAccess | One425 | Backup only | - |
| Archive (.zip) | ||||
Siemens/Unify | HiPath 4000 | V5, V6 - After this is OpenScape Voice | HiCom 1xx | Backup only | - |
| LastLoad/Regen (.txt) | ||
HiPath 3xxx series/HiCom 150 | |||||||||
iSDX | Realitis, HiPath DX | Telnet / Modem | 23 |
| Command dump - Contact MIT for commands (.txt) | ||||
OpenScape Voice OSV | V9 | Backup only | - |
| Cfg Archive (.zip) | ||||
OpenScape Business OSB | V2 R4 | ||||||||
Shortel | Shoreware | Mitel MiVC | FBackup onlyle | - |
| MySQL Export (.sql | |||
Unify | OSBiz | Backup only | - |
| XML backup (.xml) |
Outputs
Migration Plan
...
/Low-level Design Report (LLD)/Bulk Loaders
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”provisioning.
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 3rd 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.
...
Type
...
Typical export from
...
Default Field mappings
...
Info
...
Active Directory
...
Microsoft AD
...
Telephonenumber/Phone
DDI/Phone
CN
DisplayName/FullName/DirectoryName
firstName/givenname/forename
SAMAccountName
Company
Department
E-Mail/Email/EmailAddress/Mail
SIPADdress
ObjectSID
UPN/UserPrincipalName
Mobile/MobilePhone/Cell/CellPhone
...
Looks for Line1DN to patch telephonenumber/phone, if no match, attempts to match on name.
Will map all appropriate fields if it finds a match.
...
DDI
...
This is generated by us/you on a per-customer basis
...
EXTNPATTERN
DDIPATTERN
REGIONID
REGIONNAME
NAMESPACE
OVERRIDEREGIONNAME
This is used to bulk-map DDI and override locations if needed.
In this example, any extension in the form 420xxx will be given an appropriate line1DDI number, and the regionName will be overrriden to "Amsterdam" - The RegionId of -1 means "match all locations to find this number in the list"
The example 567x will only be overridden if the existing location (regionID /regionName ) matches.
Note: The number of underscores must be the same in the suffix of the 1st two columns for this to work
...
Devices
...
Generated by you/us if needed
...
userId
MAC
deviceType
...
Used primarily for Broadworks exports where device information isn't in the backup;
Looks for the Line1DN or Line1DDI matching userId, if matched, sets the MAC and primaryModel (if each not already populated)
...
Network
...
Edge switches
...
Number
MAC
IP
Switch
Port
Last Seen
...
Will try to match on Number, IP or MAC. If found, will set LANSwitch, LANPort and LANLastSeen values
...
Recorder
...
NICE NTR
...
Primary Extension Name
...
If the "Primary Extension Name" matches Line1DN, then the callRecordingMode column is set to "Yes"
...
Voicemail
...
Unity
...
FirstName
LastName
Extension
group
...
Will persVoicemail voicemail if found, or groupVoicemail if set
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.
...
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.
| Aura inline button | ||||
|---|---|---|---|---|
|
API
Our API allows for full audit, reporting of results and migration functionality.
More information on our API along with Schema documentation can be found within our Development Partner Portal
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 3rd 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.
Type | Typical export from | Default Field mappings | Info |
|---|---|---|---|
Active Directory | Microsoft AD | Telephonenumber/Phone | Looks for Line1DN to patch telephonenumber/phone, if no match, attempts to match on name. Will map all appropriate fields if it finds a match. |
DDI | This is generated by us/you on a per-customer basis | EXTNPATTERN | This is used to bulk-map DDI and override locations if needed. In this example, any extension in the form 420xxx will be given an appropriate line1DDI number, and the regionName will be overrriden to "Amsterdam" - The RegionId of -1 means "match all locations to find this number in the list" The example 567x will only be overridden if the existing location (regionID /regionName ) matches. Note: The number of underscores must be the same in the suffix of the 1st two columns for this to work |
Devices | Generated by you/us if needed | userId | Used primarily for Broadworks exports where device information isn't in the backup; |
Network | Edge switches | Number | Will try to match on Number, IP or MAC. If found, will set LANSwitch, LANPort and LANLastSeen values |
Recorder | NICE NTR | Primary Extension Name | If the "Primary Extension Name" matches Line1DN, then the callRecordingMode column is set to "Yes" |
Voicemail | Unity | FirstName | Will persVoicemail voicemail if found, or groupVoicemail if set |
UCentric ZT SPA (Zero Touch Single Page Application)
...